A well-prepared CSV reduces the time spent fixing a product import. Start with a copy of the catalogue and keep one row per simple product or variation according to the importer’s expected format. Use stable SKUs and consistent category names. Keep prices numeric, stock values explicit and product visibility intentional.
Use consistent fields
Prepare names, descriptions, short descriptions, prices, sale dates, tax status, stock, shipping class, images, categories, tags and attributes. Confirm which columns are required by your theme or extensions. For variable products, define parent relationships and attribute values consistently. A color called “Navy” in one row and “Dark Blue” in another can create poor filters.
Test before the full batch
Import a small sample to staging. Check images, categories, prices, stock, visibility and variations. Decide whether the import creates new listings or updates products by SKU. Make a backup before changing a live catalogue, and document which fields may be overwritten on a later import.
Product copy and photography research are separate from importing structured data. The importer can place information accurately, but it cannot verify that a product claim is true. Keep a final approved source sheet so future price and inventory updates use the same conventions.
Written by Code Papa, an independent WordPress developer based in the UAE with 15 years of experience.