Say you have chosen a Shopify upload service and sent them your supplier spreadsheet. The first batch comes back and half the product titles are formatted differently from what you expected, the collections are set up wrong, and several variants are missing. None of that is a data error. It is a briefing gap. Briefing a Shopify upload service properly takes about an hour up front and saves several hours of corrections later.
Key takeaways
- A good brief covers naming conventions, variant structure, category assignments, and the files the service needs alongside your product data.
- The naming conventions section is the most important part: it prevents product titles from being formatted in a way you will need to change across your whole catalog.
- Send a completed example product as part of the brief. Seeing a finished product in Shopify is clearer than any written rule.
- Ask the service to upload a small test batch of 10 to 20 products before the full job. It is the most reliable way to find gaps in your brief before they affect hundreds of rows.
- A brief does not need to be long. A one-page document with clear rules and an example product is enough for most standard catalogs.
What to include when briefing a Shopify upload service
A brief for an upload service is a short document that tells them how you want your products to look in Shopify before they start. It is not the same as your supplier spreadsheet or your product data. Your data tells them what your products are. Your brief tells them what to do with it.
Most briefs cover four areas: how product titles should be formatted, how variants should be structured, which collections and product types each product belongs in, and what files to include alongside the product data.
Product naming conventions
This is the section most merchants skip, and it is the one that causes the most rework.
Before the upload starts, decide how product titles should be formatted. For example, do you want "Women's Linen Blazer in Navy, Size 10" or "Linen Blazer | Women | Navy | 10"? Both are valid formats in Shopify. But if the service uses one and you wanted the other, every product title needs to be corrected by hand after the upload.
Write down:
- The exact order of information in the title (product name, gender, color, size, or whatever applies to your range)
- Whether to use separators like pipes, dashes, or commas, or none at all
- Whether to capitalize every word, or only the first
- Whether the brand name appears in product titles
A single example title is worth more than a paragraph of rules. Write out two or three sample titles so the service can match the pattern.
The same applies to SKUs if you want the service to create or format them. Tell them the structure: for example, "CATEGORY-COLOR-SIZE" or the brand prefix you use. If your supplier file already has SKUs you want kept as-is, say that clearly.
Variant structure and size runs
Shopify groups size, color, and other differences as variants on a single product. The brief should tell the service how you want variants structured.
The main decision is how many options each product has. A T-shirt might have size only. A shoe might have size and color. A paint product might have size, finish, and color. Tell the service which fields are options and in which order (for example, "Size first, then Color").
Also tell them what to do when your supplier file is inconsistent. For example, if some rows say "S, M, L" and others say "Small, Medium, Large", do you want the service to standardize them, or keep them as supplied?
For size runs, include the full range your products use. If you sell clothing, give the service your size run so they know that XS comes before S and 3XL is the largest, not the other way around. Shopify lists variants in the order they are added, so a size run entered out of order is harder to fix later (see Shopify's guide to product variants for how variant order works, as of November 2026).
Category and collection assignments
Tell the service which collections each product belongs to and which product type to use. If you are using Shopify's Standard Product Taxonomy, tell them which category path applies to your products.
For collections, the clearest approach is a written rule in the brief: for example, "All hoodies go into 'Knitwear' and 'New Arrivals'." If the logic is based on a field in your data (for example, "products tagged 'seasonal' go into the 'Sale' collection"), write that rule down.
If you have set up automated Shopify collections that add products by tag or product type (as of November 2026), the service only needs to set the right tags and product types on each product, and the collections will fill automatically. Tell them this, and confirm which tags or types trigger each collection.
For product types, give the service a short list of the types you use. Product type is a freeform field in Shopify, which means every service might write it differently ("T-Shirt", "T-shirt", "Tee", "Tshirt") unless you specify the exact values.
The files to send with your brief
Your brief document is the instructions. The files are the materials.
The core file is your product data, usually a spreadsheet with one product per row (or one variant per row if your products have variants). If your data comes directly from a supplier, you may need to explain which columns the service should use and which to ignore. For example, a supplier file might have 40 columns but you only need 12 of them in Shopify.
Send these files alongside your product data:
- Your brief document. A short written document with the rules above. A PDF or a shared Google Doc both work.
- A completed example product. Either a screenshot of a finished product in your Shopify admin, or a note in your brief that says "see the product at [URL] in our store." A real example in Shopify is the clearest possible brief.
- Your image files. If you want images uploaded with the products, send them in a labeled folder. The file names should match something in your product data (for example, the SKU) so the service can match each image to its product. See our guide on what to send your upload team before a Shopify job for more on file formats and folder structure.
- Any supplier data dictionary. If your supplier uses codes or abbreviations in the data (for example, "BK" for Black or "S/M/L" size codes), include a key.
Reviewing the first batch before the full upload
A brief reduces rework. A test batch eliminates it.
Ask the service to upload 10 to 20 products before the full job. Review them in your Shopify admin using this checklist:
- Product titles are formatted according to your naming conventions.
- Variants are structured in the correct order with the labels you specified.
- Each product is in the right collections with the correct product type.
- Images are attached to the right products and display at the right size.
- SEO titles and meta descriptions are filled in if that is part of the job.
If something is wrong, correct the brief and confirm the approach before the full upload starts. It is far faster to fix ten products than to fix a full catalog.
This step is worth including in your brief as an instruction: "Before uploading the full catalog, please upload the first 10 to 20 products for review." Most services expect this, and it protects both sides. For more on setting expectations when you first outsource, see what to expect when outsourcing Shopify product data entry.
Once the test batch looks right, you can confidently hand the full job to your Shopify product data entry service knowing that the first product they upload will look exactly like the last one.
Frequently asked questions
How long should a product upload brief be?
One to two pages is enough for most catalogs. A brief that is too long often gets ignored. Focus on the naming conventions, variant structure, collection assignments, and an example product. If your catalog is complex (many product types, different rules for different categories), use a table to organize the rules clearly.
Do I need a brief if the service has uploaded products for Shopify stores before?
Yes. Experienced services know Shopify well, but they do not know your preferences. Without a brief, they will make reasonable assumptions about title format, variant labels, and collection structure that may not match what you want. A brief is not about their capability; it is about your standards.
What if I do not have a style guide or naming convention yet?
Create one as part of writing the brief. Look at two or three products already in your store and decide how you want new products to match them. If your store is new, write the naming rule you would want all future products to follow. The brief is a good opportunity to make this decision once, so you do not need to make it again for every new range you add.
Should I include SEO instructions in the brief?
Yes, if you want the service to write SEO titles and meta descriptions. Tell them the character limits (around 60 characters for a title, 155 for a meta description), whether to include the product name, brand, or category in the title, and any words to avoid. If you have an existing tone of voice or keyword style, include an example. Our Shopify product uploading service handles SEO fields as part of a standard upload job.
What is the most common mistake merchants make when briefing an upload service?
Sending the data without the instructions. Many merchants hand over their spreadsheet and assume the service will fill in the gaps from context. The fields in Shopify that cause the most rework are product titles, collection assignments, and variant labels, because these are the ones where there is no single right answer. Specifying them in the brief removes the guesswork.
