Supplier CSV to WooCommerce Variations — Files + Exceptions

Have a generic supplier catalog but no WooCommerce-specific file? Convert one declared supplier CSV into a reviewable draft WooCommerce import without giving an automation access to your store. One run handles up to 10,000 data rows and also delivers a row-by-row source map plus a separate exceptions file for relationships it cannot establish truthfully.

Good fit

Use this Actor when you or your implementer can identify the source columns and parent-SKU pattern, but need deterministic parent/variation rows, normalized size or color labels, case-to-each inventory conversion, and an audit trail. This is a file-preparation step for a controlled WooCommerce import—not a store repair service, product-information manager, or recurring supplier sync.

Do not buy a run expecting it to infer unknown relationships, clean arbitrary descriptions or categories, modify an existing store, or process more than 10,000 rows. Review the free public synthetic input and actual output first: https://github.com/troublerone/winston-supplier-catalog-sample

The same input and mapping are prefilled in this Apify Example Task: https://apify.com/winstonvale/supplier-csv-to-woocommerce-variations/examples/prepare-supplier-csv-for-woocommerce-variations Starting the task is a paid USD 9 completed-bundle run; inspect the free files above, then replace the synthetic CSV and mapping with your own before running.

This first version is intentionally narrow: UTF-8 comma-delimited CSV, one declared schema, at most 10 MiB and 10,000 data rows. You identify the source columns, the parent-token pattern, any removable case-pack SKU suffix, and unit and variant synonyms. Missing parents, missing case sizes, duplicates, unsafe spreadsheet formulas, and unsupported units are excluded as explicit exceptions instead of guessed.

The outputs are:

• woocommerce-corrected.csv — draft parent, variation, and simple-product rows;
• source-to-output-mapping.csv — one decision for every source row;
• exceptions.csv — every refused row and the required correction; and
• OUTPUT plus a dataset manifest containing counts and SHA-256 hashes.

The Actor does not connect to or write to WooCommerce. Review the draft and keep a backup before importing it. An exception-bearing completed bundle is useful and chargeable; a fatal input or schema failure does not produce the bundle event.

Billing recovery

OUTPUT reports chargeState, bundleChargedCount, and reconciliationRequired separately from conversion status. A pre-charge artifact write or readback failure records zero bundle charges. A confirmed charge remains recorded as confirmed even if the final summary write fails. If the platform charge call returns an exception or unusable response, the count is null and the state requires reconciliation against the run's platform event records before any retry. Never rerun an ambiguous or confirmed-charge request merely because its final OUTPUT is incomplete.

Price

A completed bundle costs USD 9.000: Apify's one-time USD 0.005 Actor-start event plus one USD 8.995 corrected-file-bundle event after all files have been stored and read back successfully. There is no dataset-item charge and platform usage is included. The USD 0.005 start event can still apply when fatal input validation prevents a bundle; the USD 8.995 event does not.

Set the maximum total charge to at least USD 9.000. Output records are stored in the run's default Apify storage. Treat their URLs as data-bearing links, not as a confidentiality guarantee, and download the files promptly. Retention and access depend on your Apify plan and storage settings.

This tool does not prove an arbitrary supplier catalog will import into a live store. It provides a reviewable draft from the declared mapping and records what it refused.