October 29, 2026

How to Prepare a Supplier CSV for WooCommerce Without Breaking Categories

Importing a supplier file is often the easy part. The difficult work begins when thousands of products have inconsistent category paths, duplicate identifiers or descriptions written for a wholesale catalogue instead of a customer-facing shop. This checklist covers the decisions to make before importing supplier data into WooCommerce.

1. Keep an unchanged copy of the supplier feed

Preserve the original CSV, XML or spreadsheet and record its download date. Work on a separate transformed file. If the importer produces unexpected results, you need to distinguish an error in the supplier source from an error introduced during preparation.

2. Decide which identifier controls updates

Products need stable identifiers, usually supplier SKU or EAN. Do not rely on product names to match daily updates. A supplier may correct a name without changing the item. WooCommerce’s built-in CSV importer supports updates using an existing product ID or SKU; newer versions also support a mapped global unique identifier in certain circumstances. Test the matching rules for the version installed in your store.

3. Preserve category hierarchy

A supplier might classify an item as Home & Garden > Tableware > Mortars. Importing only the final term can place the product in a category that loses its context. WooCommerce’s built-in product CSV format uses > to denote hierarchy inside the Categories field, while different import plugins may use different syntax. Check the importer rather than assuming every tool handles the same delimiters.

Where an importer requires a full path for each level, prepare it explicitly. For example, the parent can be Home & Garden, the child Home & Garden > Tableware, and the final term Home & Garden > Tableware > Mortars.

4. Separate initial imports from recurring updates

An initial import may require product images, description fields, attributes and category assignments. A daily price or stock update should normally touch only the fields that need changing. Re-importing every field can overwrite editorial improvements and manually corrected categories.

5. Treat image URLs as data to verify

Some feeds contain short-lived links or inconsistent image formats. Test representative files and check how the importer handles download failures. If a shop relies on external images, plan for what happens when the supplier’s image host becomes unavailable. Keep image rights and attribution requirements clear.

6. Never describe delayed feeds as real-time inventory

If a supplier updates stock several times a day, your site cannot know about changes between those updates. Set an honest synchronisation schedule, define how unavailable products are handled and log failed imports. A product being present in a feed does not automatically mean it is available to buy.

7. Run a small test before the full catalogue

Choose ten to twenty representative products: one simple item, a variant, an item without an image, and several products from deep category paths. Check them on the storefront and in WordPress admin. Verify the SKU, price, tax class, images, category path and stock status, then test an update of those same records.

What to check before launch

  • Can the store match updates to the right products?
  • Are category paths preserved?
  • Do existing descriptions survive stock updates?
  • Are product images accessible and licensed for use?
  • Is there a log of skipped, changed or failed items?

WooCommerce maintains a detailed official product CSV importer guide. Check it against your installed version and import plugin.

BAO Group can help prepare a supplier file or review an existing WooCommerce catalogue. See WooCommerce catalogue management and import file preparation.