Import Products
Table of Contents
1. Features
When you need to create or update a large number of products at once, importing is much faster than adding them one by one. On the Product List, click "Import" in the top-right corner to open the import window; download the template, fill in the whole batch, and upload, and the system creates or updates products row by row. Import matches products by SKU (SKU): if a SKU in the file isn't found under the merchant, a new product is created; if it is found, the existing one is updated.

Quick jump: Import Steps | Override Existing Data | Import Rules for Certain Fields | Units for Dimension and Weight Columns
1.1 Import Steps
▸ Choose the merchant and download the template
In a multi-merchant environment, first choose which merchant this batch belongs to — the whole batch is imported under that merchant. Then click "Download Template" to get the template, whose header is the set of fields to fill. If the merchant has import templates configured, you can pick one from the dropdown, and the downloaded template will align with that template's field mapping.
▸ Fill in and upload the file
Fill in the products row by row per the template; each row is one product. When done, drag the file into the upload area or click to upload. Only Excel files (.xlsx, .xls) are accepted, with a 10 MB per-file limit.
▸ Submit and review results
Confirm the "Override Existing Data" checkbox state, then click "Upload". After submitting, check the result in the background-task notifications, which show how many were created, how many updated, how many failed, and the reason for each failed row.
1.2 Override Existing Data
The "Override Existing Data" checkbox at the bottom of the window determines how duplicate SKUs are handled:
| Checkbox state | Behavior |
|---|---|
| Checked | Products whose SKU already exists are updated with the file's contents |
| Unchecked | Rows whose SKU already exists are blocked and reported as "existing product found", and are not overwritten |
Either way, rows whose SKU isn't found under the merchant create a new product. SKUs also cannot repeat within the same file, or they are blocked.
1.3 Import Rules for Certain Fields
| Field | Rule |
|---|---|
| SKU | Required per row; used to match for create or update |
| Name | Required per row |
| Temperature | Must be a temperature value the system recognizes, or the row fails |
| Category | Enter the name of a category available to this merchant (the template dropdown lists only these); if it isn't available or doesn't exist, the row fails |
| Default Shelf | Enter a shelf location in the warehouse you are signed in to; only this warehouse is set. If the shelf isn't found, belongs to another warehouse, or is a staging or other system shelf, the row fails. A value that matches the product's current default shelf in this warehouse counts as unchanged and never fails |
| Other Barcode | Multiple values separated by commas; a blank value clears the existing other barcodes; if the template has no such column at all, the original values are kept |
| Activation Status | Enter Y to activate or N to deactivate; a blank value, or a template with no such column at all, keeps the original value; newly created products default to activated |
| Other Y/N columns | Same rule: only Y or N changes the value; a blank value, or a template with no such column, keeps the original value. Custom attribute columns follow the same rule |
| Unit names | Cannot start with a digit |
| Length / Width / Height / Weight, plus the large unit's outer-case dimensions and weight | Fill in the length and weight units from Organization Settings; the system converts to centimeters and kilograms when storing. For how units are read, see 1.4 Units for Dimension and Weight Columns below |
Import processes row by row: an error on one row only skips that row, while the rest of the correct rows import as usual. The reasons for all failed rows are listed in the background-task results.
1.4 Units for Dimension and Weight Columns
Applies to: Length / Width / Height / Weight, plus the large unit's outer-case dimensions and weight.
▪ How units are read on import
Fill in the length and weight units from Organization Settings; the template states the current units at the bottom, and the system converts to centimeters and kilograms when storing. The downloaded template headers carry no unit; if a column header in your file states a unit, that column is read in the unit the header states, and only columns without a unit follow the organization units.
A header is only recognized when it is written exactly as the system writes it, for example "Length(CM)", "Width(CM)", "Height(CM)", "Weight (kg)", "Box Length (cm)" or "Box Weight (kg)"; any other spelling (for example "Weight(KG)") makes the whole column get skipped.
▪ When using a custom import template
When you use a custom import template, the unit of the dimension and weight columns depends on the column names you set in the template; the template no longer shows the organization-unit note at the bottom.
▪ Importing an exported file again
An export without an export template writes these columns in the organization units with no unit in the header, and can be imported again directly after editing.
An export with an export template always writes them in centimeters and kilograms, regardless of the organization units. Newly created templates label these column headers "(CM)" / "(KG)", so the file can be imported again directly after editing.
Templates created earlier may have headers with no unit; importing a file exported with such a template reads the values in the organization units, so in an organization set to inches or pounds 10 cm is read as 10 in (stored as 25.4 cm) with no error. Before importing such a file, rewrite those headers to include the unit, or export with a re-created template.
2. FAQ
2.1 FAQ
▪ Why did some rows fail to import?
There are four common causes: required fields (name, SKU) left blank; values the system can't find for temperature, category (including a category not available to this merchant), or shelf; duplicate SKUs within the same file; and, when "Override Existing Data" is unchecked, products whose SKU already exists. The reason for each row is listed in the background-task results — fix per the message and re-import.
▪ Can I batch-update existing products via import?
Yes. Put the products to update in the file with SKUs matching the system, check "Override Existing Data", and the import updates the existing products instead of creating new ones.
▪ With "Override Existing Data" unchecked, what happens to duplicate SKUs?
Those rows are blocked and reported as "existing product found", leaving the original products untouched; rows with new SKUs still create normally.
▪ Can I change the template header myself?
Please fill in per the downloaded template header. If the merchant has import templates configured, the template downloaded after selecting one aligns with that template's fields — just fill it in accordingly.
▪ File upload fails with a file-type or size error?
Only Excel files (.xlsx, .xls) are accepted, and each file must not exceed 10 MB. If the file is large, split it into several files and import in batches.
▪ Will leaving the "Other Barcode" column blank clear the original barcodes?
Yes. If the template includes this column but a row leaves it blank, it is treated as clearing that product's other barcodes. To avoid changing existing barcodes, leave this column out of the template entirely.
▪ What if the "Default Shelf" column is blank, or the template doesn't have it?
If the template has this column but a row leaves it blank, that product's Default Shelf in the warehouse you are signed in to is cleared; other warehouses are not affected. If the template doesn't include the column at all, every warehouse's setting stays unchanged.
2.2 Notices
⚠️ Important
- With "Override Existing Data" checked, products with matching SKUs are overwritten by the file's contents — verify the file is correct before importing.
- A blank "Other Barcode" column clears the existing barcodes; when you don't want to change barcodes, leave this column out of the template.
- The whole batch imports under the chosen merchant — in a multi-merchant environment, confirm the right merchant before importing.
💡 Tip: For a first import, test with just a few rows first; once the fields and values are confirmed correct, import the full file.
3. Related Features
| Feature | Description | Link |
|---|---|---|
| Product List | Back to the product list | Go |
| Add Product | Add a single product manually | Go |
| Brands | Maintain the brands to match during import | Go |
| Categories | Maintain the categories to match during import | Go |