Shopify’s order export produces a CSV with a fixed set of columns, in a fixed order, using Shopify’s header names. You can choose which orders are included. You cannot choose which fields come with them, what order they sit in, or what the headers are called.
That’s fine when a human reads the file. It stops being fine the moment the file is an input to something else — an accounting import, a partner’s upload form, a production sheet — because those systems care about column order and header text, and they will reject or, worse, silently misread a file that doesn’t match.
Running the built-in export
- In your Shopify admin, open Orders.
- Filter or search to narrow the list to the orders you want.
- Click Export.
- Choose the scope — current page, all orders, selected orders, or everything matching your current filter — and confirm.
- Download the file, or wait for the emailed link if the export is large.
Note that orders with multiple line items produce multiple rows, with the order-level values repeated. Any system consuming the file needs to expect that shape.
The spreadsheet workaround, and why it wears thin
The common fix is to clean the file up by hand: delete the columns you don’t need, drag the rest into position, retype the headers, save. It works, and for a one-off it’s genuinely the fastest path.
As a recurring job it degrades in predictable ways:
- It has to be done identically every time, by whoever happens to be doing it, and a column in the wrong position produces a file that looks right and imports wrong.
- Opening the CSV in Excel to edit it introduces the type problems covered in the Excel guide — stripped leading zeros, reformatted dates.
- It cannot be scheduled, so it always costs a person's time.
- When the receiving system changes its spec, the change lives in someone's memory.
Producing the right CSV directly
The alternative is to define the output once and have the export match it. In Exportify, that’s a template:
- Pick your fields from the full set of Shopify order, line item, customer, shipping, billing, tax, and financial fields — plus any custom attributes detected on your orders.
- Drag them into the exact order the receiving system expects.
- Rename every header so the file speaks the other system’s language rather than Shopify’s.
- Set the delimiter — comma, tab, pipe, or something custom — and a file-name pattern using date variables.
- Choose the row shape, one row per order or one row per line item, depending on what the consumer expects.
Save it, and every future export of that template is byte-for-byte consistent. Basic includes two custom templates, Standard ten, Advanced fifteen. The help centre walks through it click by click: Create a custom template, and Choose a file format for the CSV delimiter, qualifier, and encoding options.
Sometimes the target schema wants something Shopify doesn’t store directly — a tax code derived from the shipping country, a flag set only when an order carries a particular tag, two fields concatenated into one column. Those are calculated fields, and on the Standard and Advanced plans our support team builds them for you rather than leaving you to approximate it in a spreadsheet formula.
Getting the spec right first
Before building anything, get the exact requirements from whoever consumes the file: the header row verbatim, column order, delimiter, text qualifier, encoding, date format, and whether they want one row per order or per line item. A template built from a guess is a template you rebuild.
Exportify starts at $14.99 per 30 days with a 15-day free trial — the plan comparison covers what each tier includes.
