Bulk import (CSV)
The import file format, row limits and error messages.
Available on Startup and above
Bulk import creates products from a CSV spreadsheet — the fastest way to load an existing catalogue. Like bulk edit, it is all-or-nothing: a file with any error creates nothing, so a half-imported catalogue cannot happen.
Who can do this: importing is its own permission, separate from creating products one at a time — and a plan capability, per the badge above.
The file#
Start from the template — "The 16 columns and their order must match." The page's Template columns and Formatting guidelines sections explain every column with a sample; the short version:
- Product Name is required. Rows sharing a name become one product with variants — each such row then needs its own Variant Name.
- Product Type may be
standardorserializedonly. Composites, pre-orders and customized products are built in the app, not imported. - SKU (6 digits) is optional — a blank gets a generated code. Global Identifier Value (13 digits) is optional too (one is generated only when the row's Barcode/QR column is enabled); typed codes must be unique in the file and in your catalogue.
- Price, Cost, MSRP are ordinary money amounts in your currency — write
1450.00, not minor units. - Track Inventory / Batch Tracking / Expiry Tracking take
yes/no(blank means no), with the usual ladder: batch needs tracking, expiry needs batch. - Up to 500 data rows per file; split a bigger catalogue into parts.
Errors name the exact cell#
The file is validated in full before anything is created. Every problem comes back pinpointed — row, product and column:
Row 12 | Product "Red rice 5kg" (Column: SKU): SKU must be exactly 6 digits.
The page collects them into a table you can work through in your spreadsheet, then upload again. Only a file with zero errors writes anything.
The exact column-by-column reference lives at CSV templates.