The CSV file format

Summary: The order-import CSV has seven columns; four are required. Start from the Download template button on the Order Imports page so the header row is correct.

The file's first row must be the column header. The Download template button gives you a starter file with the header and a couple of example rows already filled in.

Required columns

• sku — the product's SKU or barcode. It must match an existing product or variant in your store, or the row fails validation.
• qty — units sold, as a positive whole number.
• unit_price — the price collected per unit. Prices are treated as tax-inclusive; set the tax rate in the import flow rather than adding a tax column.
• payment_method — either cash or card. Every row that belongs to the same order must use the same method.

Optional columns

• order_ref — groups rows into orders. Rows that share the same order_ref become one order; a row with a blank order_ref becomes its own single-line order.
• sold_at — the sale's date and time, for example 2026-06-15 20:30. Leave it blank to use the event's start time. A sold_at that falls far outside the event's window is rejected as a likely typo.
• email — a customer to attach the order to. No receipt or notification is sent to this address.

How rows become orders

• Rows sharing an order_ref are combined into a single multi-line order; the order-level fields (such as payment_method) must agree across those rows.
• A blank order_ref makes that row its own order.
• Because prices are tax-inclusive, the Tax rate (%) you enter in the import flow is applied on top of the same figures for every row — see Import orders from a CSV.

Related articles

• Import orders from a CSV — the upload, validate, and confirm flow.