Exporting data
Filters, column presets, formats and delivery - how to produce exactly the sheet you need instead of a dump you have to clean.-
Exports are the other half of the app, and in practice most merchants use them more often than imports. An export can be a report, a backup, a supplier feed, or the first half of a bulk edit.
Running an export
- Go to Export → New export and choose a data type.
- Filter what to include - by collection, vendor, tag, status, location or date range. Leave filters empty to export everything.
- Choose columns. Pick exactly the fields you want, and save the selection as a preset you can reuse.
- Pick a format and press Run export. Download from the Jobs page, or have it delivered automatically.
-
Filtering
Filters are combined with AND - every condition must be true for a record to be included.
| Filter | Applies to | Example |
|---|---|---|
| Date range | Orders, customers, products | Orders created between 2026-07-01 and 2026-07-31 |
| Status | Products, orders | Active products only; unfulfilled orders only |
| Collection | Products | Everything in summer-sale |
| Vendor | Products | One supplier's catalogue |
| Tag | Products, orders, customers | Products tagged clearance |
| Location | Inventory | Stock at the Manchester warehouse only |
| Tag | Customers | Customers carrying a given tag |
Order dates are filtered in your store's timezone. An order placed at 23:50 on the last day of the month can land in the next month's file if your accounting runs on a different timezone. Confirm which one you are using before you file anything.
Choosing columns
The default column set is deliberately generous. For most real uses you want far fewer.
Export only the key columns plus the ones you intend to change. The narrower the file, the less it can accidentally affect.
Handle Variant SKU Option1 Value Variant Price
Edit Variant Price, import the same file back. Nothing else can move.
One row per order, with every figure that explains the difference between what the customer paid and what you banked.
Name Created At Financial Status Subtotal Shipping Taxes Discount Code Discount Amount Refunded Amount Total Gateway Billing Country
One row per line item, so you can pivot by product. Do not use this file for revenue totals.
The order total repeats on every line, so summing it double-counts multi-line orders. Use a per-order export for revenue.
Everything. Select all columns, no filters, and schedule it weekly. Backups are the one case where a wide file is the right answer.
One row per order, or one per line?
| Shape | Good for | Weak for |
|---|---|---|
| One row per order | Bank reconciliation, VAT returns, revenue by month | Product-level margin, best sellers |
| One row per line item | Product performance, cost of goods, stock analysis | Revenue totals - order values repeat and get double-counted |
Formats and delivery
-
The export → edit → import loop
This is the fastest bulk-edit workflow on Shopify, and it is worth learning as a single habit rather than three separate features.
- Export the records you want to change, with the key columns plus the ones you will edit.
- Save a copy of that file untouched. This is your rollback.
- Edit in Excel or a shared file URL. Use formulas freely, but paste the results back as values before saving.
- Import the edited file. The preview should say 0 created - if it does not, your keys have changed and you should stop.
Calculate in a working column, then paste-special as values over the real column and delete the working column. A formula written into a CSV exports as text and imports as nonsense.
-
Automating exports
Any export can be scheduled to run on its own. The most common setups are covered in Scheduled & repeat jobs, and the reasoning behind a weekly finance export is in Exporting orders your accountant will actually accept.