Prepare ecommerce product data by identifying each product and stocked variant, then mapping attributes, images, prices and inventory sources. Write descriptions from those records. Use the sample fields below to find gaps in your catalogue before importing it.
Separate the product from its sellable variant
A marketing name can change; a stock code needs to identify the option sold. Give each separately stocked colour, size or pack quantity its own code and link it to the parent product. Do not use the code as the customer-facing title.
Sample data: a coffee sold in 250 g and 1 kg packs could have “Whole-bean coffee” as its parent name, with KAH-250 and KAH-1000 as separate stock records. Selecting 1 kg should also select the matching image, price and basket description. These are illustrative records, not a client catalogue.
Create an attribute dictionary for each category
One field list does not suit every product. Dimensions and materials may guide a furniture decision, while compatibility and model information guide a spare-part purchase. Define category attributes, permitted values and measurement units first.
Shopify's product-detail guidance explains that data affects display and organisation, with specialised information supported through separate fields. The practical lesson is to avoid burying reusable attributes solely in a long description. Information needed elsewhere should be structured and consistent.
Connect fields to their intended use
Use this table as a starting point for catalogue preparation. Flag incomplete records instead of filling unknown specifications with guesses.
| Field | Sample value | Check |
|---|---|---|
| Parent / variant code | KAH / KAH-250 | Which stock record does an order reduce? |
| Product title | Whole-bean coffee, 250 g | Are the product type and pack size clear? |
| Net quantity | 250 g | Do comparable records use consistent units? |
| Option | Whole bean | Does the option describe a verified product attribute? |
| Image | Photograph of the 250 g pack | Does selecting 1 kg show its matching image? |
| Price and stock source | Store admin or ERP | Which system supplies the authoritative update? |
Use descriptions to explain what the data means
Turning technical fields into sentences is not enough. Answer the questions affecting selection: why does an attribute matter for a particular use, when is the product unsuitable and how do the options differ? Do not add unsupported performance or durability claims.
Align imagery with the same information. Use an understandable dimensional view where size matters and the correct option photograph where variants differ. Decorative imagery should not hide a product's essential details, particularly on mobile.
Test five sample records before a CSV import
WooCommerce's CSV guidance identifies field formatting and character encoding as important import considerations. On any platform, saving a file and displaying its contents correctly are separate checks. Test language characters, decimal formatting and fields containing multiple values.
Review search, filtering, variant selection and basket information together. Then make the same dictionary available to whoever adds the next product. Catalogue quality depends on a consistent ongoing process as well as the initial cleanup.
- Import a title with language-specific characters and check that the saved file uses UTF-8.
- Verify that a stock code with a leading zero remains intact.
- Select each variant of a product and compare its price, code and image.
- Test a comma-containing field and a decimal price against the platform’s CSV format.
- Decide which fields a repeat import will update, then verify that no unrelated product is overwritten.