Product catalog checklist: prepare your products for an online store
A store-ready product catalog gives every sellable item a clear name, accurate description, correct price, matching images and an agreed inventory process. Prepare this information in one structured file before the build begins. Separate products from their variants, identify missing information and assign someone to maintain the data after launch. This guide explains what to collect, how to check it and what to give your website developer.
Decide what counts as one product
Start by listing what customers believe they are buying. A notebook with five cover colors may be one product with five variants. A notebook and a matching pen are usually separate products, even if they can also be sold together. The aim is to make comparison natural for the shopper while preserving the stock detail your team needs. Do not decide the product structure simply by counting photographs in a folder.
Prepare a sample before organizing the full catalog. Choose an item with options, an item without options and a bundle if you offer one. Sketch what the customer sees, then list each combination that the warehouse can pick. If two options have different stock, prices or fulfillment rules, that difference must be represented in the data. Shopify and WooCommerce both distinguish products from their sellable variants or variations, but the setup needs to reflect your actual offer.
Agree this structure with the person quoting the project. A request to upload twenty products can mean twenty simple listings or twenty listings with many combinations. Those are different workloads. Record both the customer-facing product count and the total number of sellable combinations so the scope is clear.
Create a master sheet your team can maintain
Use one row per sellable item or variant, with consistent columns. Useful fields include product title, product family, SKU, option name, option value, selling price, currency, description, category, material, dimensions, weight, image references and inventory approach. Add a column for the person approving each record. The sheet should make missing answers visible rather than hide them inside long notes.
Separate facts from presentation. Keep a numeric weight in a defined unit, rather than mixing kilograms and grams in the same column. Store the product dimensions consistently and explain whether they refer to the item or its packaging. If the data is going into an import template, keep a separate working copy with business notes. The platform template can then be generated from an approved source without losing your team's explanations.
Protect the sheet from competing versions. Give one person responsibility for accepting changes and use an approval status such as draft, checked or ready. Do not let a designer, supplier and store administrator each maintain a different final catalog. A simple version rule often prevents more work than a complicated import tool. For help structuring the upload, review our e-commerce and catalog services.
Make names and descriptions answer buying questions
A product title should identify the item and its meaningful distinction. Avoid internal supplier codes as the main name unless customers already search by those codes. A title such as Ceramic Mug, 350 ml, Blue gives a buyer more context than Premium Product 07. Save descriptive flourishes for supporting copy after the essential identification is clear.
For each product, answer what it is, who it suits, what is included, how large it is and what the customer needs to know before ordering. Clothing may need a size guide and care instructions. Furniture may need assembled dimensions and access considerations. A food product may need ingredients and storage information. The relevant details depend on the item, so do not force every category into one generic paragraph.
Write from verified product information. Do not invent certifications, origin claims, health benefits or compatibility promises because a description seems short. Mark unanswered questions for the supplier or business owner. Then use a common content order so customers can compare items without relearning the page. Our product description guide explains how to turn this factual inventory into useful customer-facing copy.
Assign SKUs without confusing them with barcodes
A SKU is an internal identifier for a sellable item. Decide whether the business already has reliable SKUs before creating new ones. If the warehouse, accounting tool or supplier integration depends on existing identifiers, changing them casually can break the relationship between systems. A store build is a good time to clean up inconsistencies, but changes need a mapping from old values to new ones.
Use a format that is readable and stable. For a hypothetical stationery business, NB-A5-BLU could identify a blue A5 notebook. That example is an internal naming suggestion, not a universal standard. Avoid using a price or a temporary shelf position in the code because those details change. Make the identifier distinct enough that staff can find the right item without relying on memory.
Keep barcode information in its own field. A SKU and a manufacturer barcode solve different identification needs and should not be treated as interchangeable by default. Check the requirements of any external sales channel before supplying identifiers. Shopify's SKU guidance emphasizes uniqueness within the store for effective tracking. Use the same identifier for the same variant across locations rather than pretending each shelf is a different product.
Match images to the correct variant
Give every image a clear relationship to a product record. Record the primary image, supporting image order and any image that should appear when an option is selected. A folder full of files called image1 and finalnew is difficult to audit. Use consistent filenames or an image reference column, then keep the approved originals in a separate folder from exported website files.
Review the images against the actual item. Confirm the color, pack quantity, included accessories and current packaging. A beautiful photograph can still be misleading if it shows two units when the customer receives one. If props appear in a lifestyle image, make it clear which items are included. Ask the product owner to approve any retouching that could alter a material, texture or finish.
Plan a useful minimum image set by product type. A storage basket might need a clean main view, scale reference, interior detail and dimensions graphic. A shirt may need front, back, fabric and fit views. This is a shot planning exercise rather than a requirement to make every product look identical. See the product photography checklist for a practical capture and export workflow.
Connect stock and fulfillment to the catalog
Record where each item comes from and how its availability is updated. Stock held in a Nairobi shop, a supplier's warehouse and a made-to-order workshop cannot automatically share the same promise. Identify who confirms the item is available, who picks it and what event reduces the stock count. If you accept backorders, describe the customer expectation and the internal approval process.
Distinguish stock availability from delivery time. An item can be available to order but need production before dispatch. Equally, an item on a shelf may still require packing and courier collection. Put production or handling information in an appropriate product field, and explain the broader delivery policy separately. Avoid using a single fast-delivery banner when some products operate differently.
For bundles, decide whether the store deducts component stock or treats a prepared bundle as its own item. Either approach can work, but the catalog and fulfillment process must agree. Test the result with a small example before loading every bundle. A record that looks right on the product page can still oversell a component if the stock relationship is wrong. Our inventory guide covers these operating decisions in more detail.
Review prices, categories and policy dependencies
Confirm the selling price and what it includes with the business owner. Keep currency explicit and record whether separate fees apply. Do not assume a price on an old social post is still approved. If a comparison price or discount will be displayed, keep evidence of the relevant pricing decision and check the platform's rules. Promotional settings should be intentional rather than inherited from an import file.
Assign each item to a customer-friendly category. A supplier department name is not always useful store navigation. Group items by how people shop, such as product type, intended use or an important compatibility requirement. Record both the main category and any supporting collections. Be cautious about making so many categories that each contains only one unexplained product.
Identify policy exceptions while the catalog is being checked. Fragile, personalized, oversized or temperature-sensitive items may need different handling or clearer information before purchase. This is the point to ask operational questions rather than discovering them during a delivery complaint. Policy wording should reflect the business's real process and be checked against applicable requirements. The catalog should flag exceptions so the page designer knows where essential information belongs.
Test a small import and hand over ownership
Approve a pilot containing the difficult cases before a full upload. Include a simple item, a multi-option item, an out-of-stock item and a product with a shipping exception. Check the customer-facing pages and the administration records. Look at product names, prices, option selection, image changes, stock behavior and category placement. A successful import message does not prove the catalog is ready to sell.
Ask someone unfamiliar with the products to find and describe a few items using only the store. If they cannot tell what is included or which option fits their need, the missing information is usually more useful than another visual effect. Record corrections in the master source first, then update the storefront. This keeps the approved data and live shop aligned.
Finish by assigning maintenance responsibilities. Who approves a new price, replaces a photograph, archives a discontinued item and checks supplier stock? Write down the update path and give staff an example they can follow. Keep a copy of the approved upload and a short record of unresolved exceptions. The catalog is a working business asset, and its value depends on staying accurate after the launch project ends.
Common questions
Can I give a developer a PDF instead of a catalog spreadsheet?
A PDF is useful background, but a structured sheet is easier to review and import. If the PDF is your only source, include a separate list of missing prices, options and images so the extraction work can be quoted accurately.
Does every product need several variants?
No. Create variants only when the customer chooses a meaningful option or your stock process requires separate sellable combinations. Avoid adding unnecessary options that make ordering harder without representing a real difference.
Should I upload products before the website design is finished?
Prepare the data early and approve a small pilot during the build. Real product information exposes layout and navigation needs that placeholder text often hides. Keep final bulk uploads controlled so unapproved records do not go live.
