Parent SKU printed on every variation
A variable product can need distinct identifiers for size or colour rows.
Export a product table through your trusted WooCommerce workflow, then inspect each available column in BatchLabel. Because barcode values can live in extension-specific metadata rather than one universal field, mapping stays explicit instead of guessing from a plugin name.
Choose a CSV or XLSX to continue in the full mapping workspace. Nothing is uploaded.
A practical workflow
Use the current store export and include the fields or metadata that hold the intended scan value.
Map name, SKU, price and code from the actual headers; variation and plugin fields differ between stores.
Resolve blank/duplicate values and test scans against the system used for inventory or checkout.
Avoid rework
A variable product can need distinct identifiers for size or colour rows.
Barcode plugins store values under different metadata keys and may not include them in a default export.
This WooCommerce workflow uses a manual file export; it does not connect to a store REST API or OAuth account.
WooCommerce is a trademark of its owner; compatibility does not imply affiliation or extension support.
Questions, answered
BatchLabel only needs a CSV/XLSX containing the fields you intend to use. How a store exports custom barcode metadata depends on its existing configuration.
No. Printing is not an inventory transaction, and the local tool does not write back to WooCommerce.