Before an ecommerce website launches, prepare an approved record of every product and sellable variant: its name, description, options, price, stock rule, images and delivery information. Map those records to the store’s format, import a representative sample, and check that the product page, cart and order all describe the same item.
Assign one catalog owner. A developer can map the fields, but the business must confirm what it sells and what each price includes. A successful upload does not establish that the catalog is ready for customers.
The checklist below is a practical working process for a small business selling physical products. Subscriptions, made-to-order goods and complex bundles may need additional fields and tests.
Start with one approved source of product information
Use one controlled catalog sheet or product system for the launch. Give each record an owner, approval status and last-reviewed date. Keep supplier files as reference material rather than letting several versions become competing sources of truth.
Separate your working sheet from the platform’s import file. The working sheet can contain internal questions and approvals; the import file should contain the fields and formats the store expects.
| Information group | Prepare before handoff | Evidence that it is ready |
|---|---|---|
| Identity | Product name, category, internal SKU and confirmed manufacturer identifiers where applicable | Each sellable item can be identified without guessing |
| Options | Sizes, colours, pack quantities and valid combinations | The business has approved the actual combinations for sale |
| Customer details | Materials, dimensions, contents, care and relevant limitations | Details match the goods and supporting supplier information |
| Commercial information | Approved price, currency, stock source and out-of-stock behaviour | An owner has checked what the customer will pay and receive |
| Fulfilment | Shipping weight, dimensions where needed and delivery restrictions | The fulfilment team can use the record to dispatch the correct item |
| Media | Approved images, variant mapping, usage rights and alt text | Each image represents the item or option beside it |
A blank field may mean “not applicable,” “unknown” or “forgotten.” Resolve its meaning before import.
Separate a product family from its sellable variants
A product family groups related choices. A variant is the specific combination a customer can buy. An SKU is your internal stock identifier; it should not be confused with a manufacturer-assigned barcode or other product identifier.
Consider a hypothetical cotton tote available in Natural and Navy, sold individually or in pairs. This creates four sellable combinations. The examples below are fictional planning records, not WaveINO customer data.
| Family | Colour | Pack contents | Example SKU | Photo requirement |
|---|---|---|---|---|
| Cotton tote | Natural | One tote | TOTE-NAT-1 | Natural tote shown clearly |
| Cotton tote | Natural | Two totes | TOTE-NAT-2 | Pair contents made clear |
| Cotton tote | Navy | One tote | TOTE-NAV-1 | Navy tote shown clearly |
| Cotton tote | Navy | Two totes | TOTE-NAV-2 | Pair contents made clear |
Each combination needs an approved price and stock rule. Decide whether pairs are separately stocked packs or assembled from individual units. That choice affects stock handling and should reach the implementation team before import.
The family record should not become a fifth item for sale. Option labels should stay consistent across the store.
Resolve factual gaps before writing attractive descriptions
Customer-facing copy should explain what arrives, how it can be used and which limitations matter. Confirm measurements and distinguish the product’s weight from the packed shipping weight. For a pack, state the number of units instead of assuming the photograph communicates it.
AI can help organise supplied facts or draft clearer sentences. It should not fill missing information with plausible materials, certifications, compatibility claims, warranties or origin statements. Send unresolved facts back to the business owner or supplier.
For an India-focused store, use an explicit currency such as INR in the working sheet and review the resulting storefront display. Have the responsible business owner approve prices and commercial settings. The data handoff should record those decisions clearly.
Treat images as part of the catalog
Give each approved image a clear relationship to a product or variant. Record the intended order of gallery images and write alt text that describes what the image actually shows. Confirm permission to use supplier photographs before adding them to the store.
Check more than whether a file exists. Does the Navy option show Navy? Is the pair’s contents clear? Can a mobile shopper understand the product without zooming into tiny text?
The import path matters too. WooCommerce’s documentation explains that image URLs must be accessible and that its core CSV importer does not add or update image alt text. Include a separate post-import check for that field. See the WooCommerce import documentation.
Test a small import before releasing the catalog
Choose examples that represent the complexity of your actual range: a simple item, an option-based family, a pack, an unavailable item and any special shipping case you offer. The right sample is determined by those differences, rather than an arbitrary number of products.
Use the current template for your platform. Shopify documents dependencies between variant and option columns, as well as different effects when fields are blank or omitted during updates. Preserve those relationships and review the Shopify CSV guidance before changing an existing catalog.
Keep a backup or export and test in a suitable staging environment. Compare the approved source record with the imported admin record, then follow the customer journey. Keep unapproved products in draft while questions are resolved.
Record what a passing check looks like
Use a short acceptance record with the test date, reviewer, expected result, actual result and evidence. These are proposed checks to adapt to your store.
| Test | Expected result | Useful evidence |
|---|---|---|
| Select Navy in a two-tote pack | The selected option, image, SKU and contents agree | Product page and cart screenshots |
| Add the selected pack to the cart | The cart retains the approved option and price | Cart record checked against the source |
| Select an unavailable combination | Purchase follows the deliberately approved stock rule | Screenshot and stock-setting review |
| Enter a supported delivery postcode | The expected delivery choice and charge appear | Checkout test record |
| Complete a test order through the approved test process | The order identifies the correct product and quantity | Order record reviewed by fulfilment |
If Google Merchant Center is part of the launch, compare its submitted offer with the website too. Google’s specification calls for consistency in price, currency and availability across relevant surfaces and warns against guessing manufacturer identifiers. Refer to the product data specification for your product and destination requirements.
Agree on release ownership and ongoing updates
Hold an affected product back when its selected variant, charged price, availability, essential image or factual description is wrong. Record the issue, owner and expected correction, then repeat the failed check after the fix.
The business owner should approve commercial facts. The implementation owner should confirm the mapping and customer behaviour. Assign responsibility for later price, stock and image changes so the approved launch sheet does not become outdated immediately.
Accurate catalog data also gives further optimisation a sound starting point. Use the ecommerce SEO checklist for category and product discoverability. Clean data alone does not guarantee Google listings, rankings or inclusion in AI answers.
If your team needs help turning approved product information into a working store, explore WaveINO’s ecommerce development service or contact us with a representative sample of your catalog and its unresolved questions.
Reviewed 24 September 2026. Catalog examples and acceptance checks are illustrative; adapt them to your products and platform.