The order upload file and CSV Mappings
- Reference
- Orders
- For: Admin, Warehouse Manager, Account Manager
- Checked on 28 October 2026
The columns of a CSV file of orders, how a CSV Mapping reads a client's own spreadsheet, and what each result and refusal means.
In short
This lists the columns of an Order Upload file and what each result means. It also says how a CSV Mapping reads a client's own headings. Use it when you build a file or read an upload's results.
The file
- A CSV file, with commas or semicolons between values. A spreadsheet saved as
.xlsxis refused, so save it as CSV first. - The first row names the columns, in any order. Capitals, spaces, hyphens and underscores don't matter, so
Order Noandorder_nomatch. - Each other row is one order line. Rows with the same Client Order Reference make one order, in any capitals.
- The order's delivery details can be on its first row only. A later row may leave them blank, but may not give different ones.
- At most 5,000 rows in one file, and one client's orders only. Blank rows are skipped.
- A row with no reference, or with neither a
product_codenor aquantity, refuses its order. - Rows are numbered as a spreadsheet numbers them, with the headings as row 1.
Standard columns
A file with these headings needs no CSV Mapping.
| Column | Needed | What it takes |
|---|---|---|
client_order_reference |
Yes | The client's own number for the order, such as #NT-50270 |
product_code |
Yes | The product's SKU or one of its SKU Aliases, such as NTC-TEE-NVY-M |
quantity |
Yes | A whole number above zero |
recipient |
No | Who the order goes to |
company |
No | The recipient's company |
email |
No | The recipient's email, which some Carrier Services need |
phone |
No | The recipient's phone number |
address_line_1 |
No | The first line of the address |
address_line_2 |
No | The second line |
town |
No | The town or city |
county |
No | The county |
postcode |
No | A UK postcode, such as EH1 1YZ |
country |
No | GB or IM. Left blank, it is GB. |
service_level |
No | A Service Level's name, such as Next Day, or a value the mapping names. Left blank, the client's Default Service Level is used. |
Northern Thread's order #NT-50270 for a tee and a pack of socks is two rows. Both give #NT-50270, with NTC-TEE-NVY-M on one and NTC-SOCK-3PK on the other. Only the first needs the delivery details.
A blank delivery detail doesn't refuse the order: it is taken in and held until someone fills it in.
CSV Mappings
A CSV Mapping matches a client's export headings to the standard columns, such as Order No for the reference. A client can have several, one for each shop or system it exports from.
| Part of a mapping | What it holds |
|---|---|
| Client | The client it belongs to. It stays with that client. |
| Name | Such as the shop the export comes from, unique for the client |
| Column headings | The client's heading for each column. The reference, product and quantity columns are needed; leave the rest blank if the file has none. |
| Service Level values | What the file writes for each Service Level, such as NDD for Next Day. A value that is a Service Level's own name needs no row. |
Account Managers and Admins keep them under Orders › CSV Mappings, with Add a CSV Mapping, Edit and Delete. Whoever uploads a file can also save a new one when Stockist asks them to map the columns.
Which mapping reads a file
| The file's headings | What Stockist does |
|---|---|
| Hold every heading of one of the client's mappings | Uses that mapping. If several fit, it uses the one naming most headings. |
| Fit two mappings equally | Asks you to choose one. |
| Fit none, but use the standard columns | Reads the file by the standard columns. |
| Fit nothing | Asks you to map the columns, and saves the mapping for next time. |
You can also choose a mapping in CSV Mapping before you check the file. The upload's page names the mapping it used.
The Result column
Download with results gives back the file with a Result column on every row of the order.
| Outcome | Before you confirm | After you confirm |
|---|---|---|
| Taken in | Will be taken in. | Taken in as ORD-00000018. |
| Taken in and held | Will be taken in and held, with the hold and its reasons | Taken in as ORD-00000020 and held, with the hold and its reasons |
| Refused | Will be refused, with the reasons | Refused, with the reasons |
| Duplicate | Duplicate of the earlier order and its status: left out unless confirmed as a new order. | Duplicate of the earlier order and its status: not taken in. |
Why a whole file is refused
Stockist shows "File refused" and creates nothing.
| Reason | What to do |
|---|---|
| The file could not be read as a CSV file. | Save the spreadsheet as CSV, with the headings in the first row, and upload it again. |
| The file has headings but no rows of orders. | Add the orders' rows. |
| The file has more than 5,000 rows. | Split it into files of at most 5,000 rows, and upload each one. |
| The file has no column for the reference, the product or the quantity. | Add the column, or fix the mapping's heading for it. |
| This file was already uploaded and taken in. | Upload a file of the new orders only. |
Still stuck? Email [email protected]