A merchant sends 400 products to an upload team with one instruction: "write natural descriptions." The team calls on the first day, asking what tone to use, what to do for a product that has no supplier copy, and what the format should be when a product fits two categories.
A description style guide for upload team jobs is the document that answers those questions before anyone picks up the phone. It is not a copywriter brief. It is a set of field-level decision rules the team reads before writing a single line.
Key takeaways
- A description style guide for an upload team needs decision rules, not only brand voice guidance: the team writes hundreds of products in a day and cannot pause on every ambiguous case.
- Eight things to cover: tone and brand voice, description length by category, what each description should lead with, how to handle missing supplier data, which Shopify fields to fill, SEO instructions, category-specific rules, and a worked example.
- The worked example is the most practical section: one description that meets your standard and one that does not, with the reasons why each succeeds or fails.
- Preparing the guide before the job starts reduces back-and-forth and gives you consistent output from day one.
What upload teams need from a description brief
Most merchants give an upload team a copywriter brief: brand voice, adjectives such as "warm but professional," maybe a sentence about who their customers are. That is not enough for a catalog job.
A copywriter reads a brief and uses judgment to fill the gaps. An upload team is entering data at volume (dozens or hundreds of products in a session). They need rules for when there is no obvious answer: what to write when the supplier gave no copy at all, how to format a product that fits two categories, which Shopify field gets the main keyword, and what to do when a field cannot be filled.
Without those rules, every ambiguous product becomes a question. The team pauses, you answer, they continue, and then the next one comes.
A useful description style guide closes those gaps in advance, so your team can work through the catalog without interruption.
What a description style guide for upload team must cover
1. Tone and brand voice (with examples, not only adjectives)
Describe the voice in concrete terms: write one sentence that matches your tone and one that does not. "Detailed but never technical" means something different to every reader. "Write this, not that" means the same thing to everyone.
Include:
- The intended audience (a seasoned gardener, a first-time pet owner, a professional buyer)
- The person and tense to use (second person "you," present tense)
- Whether contractions are acceptable ("you'll get" vs "you will get")
- Whether to name the brand in descriptions or avoid it
2. Description length by category
Set a word range for each category in your catalog, not a single target for everything. A basic accessory does not need the same length as a technical product. Some typical ranges:
| Category type | Suggested word range | Reason |
|---|---|---|
| Basic accessories (belts, socks) | 40 to 80 words | Little to describe beyond material and fit |
| Apparel (jackets, dresses) | 80 to 150 words | Fit, fabric, occasion, care |
| Skincare and beauty | 100 to 200 words | Skin type, ingredients summary, how to use |
| Furniture and homewares | 80 to 150 words | Materials, dimensions, assembly, use case |
| Technical or specialty products | 150 to 250 words | Specs, compatibility, use case |
Adjust these for your catalog. The point is to set them in advance so the team does not have to judge length product by product.
3. What each description should lead with
Every description should open with the most useful thing for the shopper. Decide in advance which element that is for your products, because it is not the same for everything.
Three common options:
- What the product is and who it is for. "A lightweight merino base layer for cool-weather running, cut close to the body and loose at the hem."
- The key benefit. "Keeps moisture away from the skin for up to four hours, so you stay comfortable across long days in warm weather."
- The main use case. "Designed for outdoor dining and picnics, this folding tray clips securely onto most standard picnic baskets and folds flat for storage."
Pick one default for each category in your catalog and document it. The team follows the rule; you review the output for exceptions.
4. What to do when supplier data is missing
This is the section most merchants leave out and most upload teams need. Missing data is common: suppliers send incomplete spreadsheets, images without labels, or weight data for some products but not others.
Your guide needs to state:
- Write a placeholder vs skip the field. Should the team write "Contact us for more information" or leave the field empty?
- Use supplier copy as a starting point vs rewrite it. If the supplier sent a description, do you want it rewritten to match your brand, or lightly edited?
- Flag it and continue vs hold it. Should the team mark a product with missing data and keep going, or hold it for your review before moving on?
Without a rule, the team will develop their own conventions, which may not match yours.
5. Which Shopify fields to fill
Shopify's product page has several fields relevant to descriptions (as of November 2026): the main product description (which supports HTML for formatting), the product title, the SEO meta title, and the SEO meta description in the "Search engine listing preview" section. You can read how these fields work in the Shopify Help Center: Add and update products.
Your guide should say which fields the team writes and in what order:
- Does your team write both the product title and the SEO title, or do you handle SEO titles separately?
- Does the meta description come from the product description, or does the team write a dedicated sentence?
- Are product tags and collections part of the scope for the description job, or handled separately?
For more on how the product title field interacts with the SEO title in Shopify, see Shopify Product Title SEO for Upload Teams.
6. SEO instructions for title and meta description
If your upload team is writing SEO meta descriptions as part of the job, give them a format to follow, not a bare request to "include the keyword."
The format: [product name] plus [key attribute or benefit] plus [a reason to buy]. Keep it under 155 characters. Include the primary keyword once, naturally. Shopify's own guidance on using keywords in product fields is covered in the Shopify Help Center: SEO.
Example: "Merino wool base layer for men. Moisture-wicking and odor-resistant, designed for running and hiking in cool weather. Sizes XS to XXL."
If there are specific keywords you want on certain products, list them separately by product or by category. Do not leave the team to guess which keyword to target.
For how image alt text fits into the same brief, see Shopify Image Alt Text: What Upload Teams Enter.
7. Category-specific rules
Some product types need rules that do not apply to others. Document them by category rather than adding a general note the team has to remember for everything:
- Regulated products (supplements, skincare with active ingredients, food): do not make health claims; describe what the product contains and how it is used, not what it does to the body. List the active ingredients from the label as supplied.
- Products with sizing: note which measurement system to use and where to place it in the description.
- Bundle or set products: describe the set as a whole first, then list the individual components.
If you work with a Shopify product data entry service, share the category rules before the job starts: they affect how the team interprets your supplier files.
8. A worked example: one good, one bad
This is the most useful section in any style guide, and the most often skipped.
Pick one product from your catalog and write two descriptions: one that meets your standard, and one that fails it. Annotate each with the reasons.
Good:
Structured cotton tote with a flat base, 40 cm x 35 cm, two internal slip pockets and a zip closure. Natural duck canvas, 8 oz weight. Machine washable.
Why it works: leads with what the product is, includes dimensions and key features, neutral and factual.
Not good:
This beautiful, versatile tote bag is great for everyday use and is made with high-quality materials that will last for years.
Why it fails: no dimensions, no materials, adjectives that describe nothing ("beautiful," "high-quality"), filler that adds no information.
Worked examples give the team a calibration point. They can check their own output against yours before sending anything back.
Before you hand it over
Before sending the guide to your upload team, read it as if you had never seen your catalog before. Check that every rule answers a specific question a team member could ask. If a section only repeats what a reasonable person would assume, cut it and replace it with a rule they would not know without being told.
The most actionable guides are usually short. Two pages with concrete rules beats ten pages of brand philosophy.
If your descriptions are part of a larger upload job, review a small batch of 10 to 20 products before the team continues with the full catalog. It costs an hour but catches misunderstandings before they affect the whole job.
For descriptions that also rank in search, see the SEO product descriptions service.
Frequently asked questions
How long should a description style guide for an upload team be?
Most useful guides are one to three pages. Long enough to cover every category-specific rule and include a worked example, short enough for the team to read before starting the job. If it runs longer, split the category rules into a separate reference sheet the team can look up as they go.
Do I need a separate guide for each product category?
Not necessarily. One guide with a section for each category is usually enough. If two categories are very different (for example, technical equipment and clothing), a category-specific notes section handles the difference without requiring two separate documents.
What if my upload team also writes SEO titles and meta descriptions?
Add a section on SEO field targets to your guide: which fields to fill, a format for the meta description, and any keyword instructions. Your team should know whether the SEO title and the product title are the same or different, because Shopify treats them differently when both are filled (as of November 2026). See Shopify Product Title SEO for Upload Teams for the field-by-field breakdown.
Should the guide include rules for using HTML formatting in descriptions?
Yes, if you want formatting. Shopify's description field supports HTML (as of November 2026), so your team can add bullet points, bold text, and paragraph breaks. If you use them, your guide should say when: for example, bullet points for features lists and plain paragraphs for short product descriptions. Without guidance, some teams format everything and others format nothing.
When briefing a done-for-you description service, is this the same document?
Mostly yes, with one addition: a done-for-you description service also needs to know what output format you want (a spreadsheet with a description column, or descriptions entered directly into Shopify) and whether you need them in a specific CSV column name. For a more detailed walkthrough of briefing a description service, see Briefing a Shopify Description Writer: What to Include.
