If your catalog lives in a spreadsheet, CSV import is the quickest way in. (If it lives in BigCommerce or Shopify, connect the store instead — the BigCommerce and Shopify connectors bring across far more, including variants and images.)
Before you start
- Create the product type first. Import fills one attribute family per run, so the family and its attributes need to exist. Split the spreadsheet by product type if it mixes them.
- One row per product. The first row must be the column headers.
- Up to 500 rows per import. Split larger files.
- Import creates new products. It doesn’t update existing ones yet, so don’t re-import the same rows to change them — use bulk edit for that.
Preparing values
minipim converts each cell to the attribute’s type, so format values the way the type expects:
| Attribute type | In the CSV |
|---|---|
| number, decimal | 12 or 12.5 |
| boolean | true / false |
| multiselect | comma-separated values in one cell: cotton, linen |
| text, select | the value as written |
Values for localizable attributes are imported as the en_US locale; add other languages afterwards.
Running the import
On the Products page, click Import CSV and follow the four steps:
- Upload CSV — choose the file. It’s read in your browser.
- Destination family — pick the product type.
- Map columns — for each column, choose the field it fills: name (required), slug, status, or any attribute in the family. Leave columns you don’t need unmapped.
- Run.
When rows fail
Every row is validated on its own, so one bad row doesn’t stop the rest. Failed rows are reported individually — usually a value that doesn’t match its attribute’s type or rules, or a required attribute left empty. Fix those rows in the spreadsheet and import just them again.
After the import
New products start as drafts unless you mapped a status. Check a few in the editor, then use channel readiness to see what’s still missing before they go anywhere.