Quantities against SKUs the shop already has. Either a stock take or a delivery — you say which on the next screen.
The columns
Your file can name its columns any of the ways shown: the importer matches them whatever their case or spacing. Columns it does not know are left out.
| Column | Also read from | Notes |
|---|---|---|
SKU (required)sku | variant sku item code code article number barcode | The variant code. Stock is matched on it, and a SKU this shop does not have is reported rather than created. |
Quantity (required)quantity | qty stock on hand count inventory quantity available stock level | Whole garments. What the number means — a count or a change — is the choice below. |
Locationlocation | warehouse shop branch stock location inventory location | By name, as it appears on the locations screen. Left out, everything goes to the location that fulfils online orders. |
Notenote | reason comment reference memo | Kept on the movement. A delivery note number here is what makes the ledger worth reading later. |
Questions it asks
What the numbers mean
The one question this import cannot guess, and the expensive one to get wrong in either direction.
- These are counts — this is what is on the shelf (the default): A stock take. Each number replaces what the system thinks it has, and the difference is recorded as a movement. Importing the same file twice leaves the same answer.
- These are changes — add them to what is there: A delivery, or a write-off. Each number is added to the current count, and a negative number takes stock away. Importing the same file twice counts it twice.
A template to start from
The template has every column and a few example rows. The examples show the things most often got wrong on a first go.
SKU,Quantity,Location,Note
NAVY-COAT-M,12,,Counted 2026-08-22
NAVY-COAT-L,7,,Counted 2026-08-22
RED-SCARF-OS,0,,None left