How We Standardized WooCommerce Product Imports with a Folder-Based Schema

Description and use

Implementing a folder‑based product package format for WooCommerce enables pre‑import validation, ensuring consistent attributes, categories, and variations, thereby improving catalog quality.

Problem

Large WooCommerce catalogs suffer from inconsistent product data, missing required values, and poorly structured taxonomy when importing from spreadsheets or supplier documents.

Outcome

The folder‑based schema reduced import errors, enforced consistent taxonomy, and prevented malformed products from entering the catalog, improving data quality and reducing manual cleanup.

Workflow

• Create a product folder containing required files (product.json, attributes.json, optional variations.json, taxonomy txt files, description txt files, and images folder).
• Run schema validation to check JSON structure and required fields.
• Validate attributes: ensure existence, valid values, allowed for variations, no duplicates, no empty values.
• Validate taxonomy: confirm categories exist and do not auto‑create missing ones.
• If validation passes, send the package to WooCommerce via API or middleware.
• If validation fails, review error (e.g., CATEGORY_NOT_FOUND) and correct before retrying.

Evidence

We kept running into the same problems: Product names stored separately from descriptions; images arriving with inconsistent filenames; attributes structured differently across products

Source

One of the most important design decisions is that validation happens before the product reaches WooCommerce.

Source

The project currently includes: simple product examples, variable product examples, JSON schemas, attribute structures, variation structures, taxonomy guidance, image organization rules, validation documentation, category matching guidance

Source