CSV Import & Export
Overview
The Orders screen has an Import Orders CSV action for adding many orders at once, and an Export that produces a file in the same layout — so a batch can be exported, edited in a spreadsheet, and re-imported. Like single order entry, CSV import is an Admin action.
File Format
Import accepts a .csv file with a header row. Use Download template to get a correctly-shaped file with an example row. Each row is one order width; rows that share an Order Number are grouped into a single order (the header fields are taken from that order's first row). Rows with no Order Number are skipped.
Columns
| Field | Type | Description |
|---|---|---|
Customer* key: Customer | text | Matched to an existing customer by name. If none matches, you can create it during review. |
Order Number* key: Order Number | text | The customer's PO number. Also the grouping key — rows with the same value form one order. Must be unique in the file. |
Order Date* key: Order Date | date | YYYY-MM-DD. |
Delivery Date key: Delivery Date | date | YYYY-MM-DD. |
Notes key: Notes | text | Order-level notes. |
Labels key: Labels | text | Pipe-separated, e.g. Priority|Export. |
Paper Type* key: Paper Type | text | Matched by name; can be created during review. |
GSM* key: GSM | number | Matched under the paper type; can be created during review. |
Minimum Trimming (mm) key: Minimum Trimming (mm) | number | Used only when a new GSM has to be created. |
Size Type* key: Size Type | REEL / SHEET / THERMAL | Defaults to REEL if blank or unrecognized. |
Size (mm)* key: Size (mm) | number | Width (or L for a sheet). |
Height (mm) key: Height (mm) | number | H for a sheet; blank otherwise. |
Weight (MT)* key: Weight (MT) | number | Target weight for the width. |
Sale Price / MT key: Sale Price / MT | number | Optional revenue figure. |
Allowed Variance (%) key: Allowed Variance (%) | number | Optional per-width variance. |
Descriptors key: Descriptors | text | Pipe-separated key=value pairs, e.g. BF=30|Kit=8. |
Review & Commit
Importing opens a review screen — nothing is saved yet. Every parsed order is listed with its widths, and for each unmatched customer, paper type, GSM, label or descriptor you decide whether to link it to an existing record or create a new one. Rows with problems (a duplicate order number, a missing required value) are flagged. When everything resolves, Commit creates the orders. Orders come in as Draft; confirm them when you're ready to plan.
Exporting Orders
The Orders screen's Export writes the currently-filtered orders to a CSV in this exact layout (one row per width). Orders without any widths are skipped. This is the fastest way to seed a template with real data before a bulk edit.
Was this page helpful?
Something unclear or missing? Reach out and we'll update this page.