SKUs and the CSV Import
A client's products are their SKUs. You load them from a CSV file, and each SKU becomes a product in OpenBoxes coded <client code>-<SKU>. Two clients can use the same SKU without clashing, because the client code is part of the OpenBoxes code.
Watch the video: Import a Client's SKUs (1 min) checks a client's CSV file, shows what will be added, and imports every SKU into that client's catalog.
Importing SKUs#
- Go to Clients, open the client, and choose Import SKUs.
- Under 1. Choose a file, drop a CSV file on the page or click to choose one, then choose Check file.
- Under 2. Check the result, Lift shows how many rows are New SKUs, Changed SKUs and Already up to date, and lists any Rows with a problem. Nothing changes until you start the import.
- Choose Import N rows (the number of valid rows) to apply them, or Discard to start again. Rows with a problem are skipped.
- Under 3. Importing, Lift creates or updates each product in OpenBoxes. The import runs on our side, so you can leave the page and come back from the client's page.
The same file can be imported again safely: a row is applied by its SKU, so importing the same file twice changes nothing. To change a product, import a file with the new values for that SKU.
The file#
The file must be a UTF-8 CSV, up to 2 MB and 5,000 rows. The first row holds the column names. In Excel, use Save As and choose CSV UTF-8 (Comma delimited).
The columns are:
- sku (required): the client's own SKU. Letters, digits, dots, dashes or underscores, up to 50 characters.
- name (required): the product name, up to 255 characters.
- barcode: letters, digits or dashes, up to 64 characters.
- weight_g: weight in whole grams, up to 1,000,000.
- length_mm, width_mm, height_mm: size in whole millimetres, up to 10,000 each.
- lot_controlled:
yesorno. A lot-controlled product tracks lots, and OpenBoxes asks for an expiry date at receipt unless the product is marked as not expiring. It cannot be changed once the product exists in OpenBoxes, so decide before the first import. - does_not_expire:
yesorno, andyesonly when lot_controlled isyes. Use it for a lot-tracked product that has no expiry date. Not available for kits. A new product is then made so OpenBoxes does not ask for an expiry date when it is received, and Lift checks the lot instead (see Products that do not expire). A file without this column, or an empty cell, leaves the SKU's current setting as it is; a new SKU starts asno.
When kits are on for your account, two more columns are accepted, kind and components. See Kits and Subscription Boxes.
A column Lift does not recognise rejects the whole file, so leave out any extra columns.
An example file:
sku,name,barcode,weight_g,length_mm,width_mm,height_mm,lot_controlled
MUG-01,Ceramic mug,0123456789012,350,120,90,100,no
TEA-50G,Green tea 50 g,0123456789029,60,80,40,120,yes
When a row has a problem#
Rows with a problem are listed with their row number, SKU and the problem. Row numbers count from the first row after the column names. The valid rows can still be imported; fix the others and import them again. Common problems:
- The same SKU appears more than once in the file: only the first row is used.
- A number is not a whole number, or is over its limit.
lot_controlledchanged for a product that already exists.does_not_expireisyesfor a product that is not lot controlled.
Products that do not expire#
Some lot-tracked products have no expiry date, such as spare parts or most consumer goods. Mark them as not expiring with the does_not_expire column, or with the Does not expire tick box in the Lots column of the client's SKU table (it can be ticked only for a lot-controlled SKU, and is not available for kits). Then:
- A product Lift makes from then on is made so OpenBoxes does not ask for an expiry date when it is received.
- Lift checks the lot instead. An ASN can still leave the lot blank. When the product is received on the handheld, the handheld asks for its lot number before the line can be saved (it asks for no expiry date; a return is handled as before). Stock received without a lot anywhere else, for example at a desk in OpenBoxes, shows on the ASN as a Received without a lot number discrepancy for your team to look into, and a returned unit that arrives without a lot is held until your team settles it. The same applies to kits.
If the product already exists in OpenBoxes when you tick the box (or untick it), Lift does not change the product there. The SKU shows a note, and someone on your team changes Lot and expiry control on that product in OpenBoxes to match: untick it for a product that does not expire, tick it again for one that does. Then choose Done beside the note. Until then, OpenBoxes keeps asking for an expiry date as before, and Lift keeps checking the lot whenever OpenBoxes does not.

