Export your sync results and your catalogue

Everstock gives you two CSV downloads. A run export lists the records a sync changed, or would have changed, plus the records it flagged for review. A catalog export lists what your Shopify store currently holds. Both are plain CSV files that open in any spreadsheet.

Download a run as CSV

You can export any run, preview or real. Open the run from Sync history and use Download CSV in the page header. The same download sits in the Preview: proposed changes modal that opens after Preview changes, and in the Run details panel that opens when you select a run under Recent runs on a connection page.

The file has 12 columns in this order: matching_key, sku, barcode, reason, action, status, qty_from, qty_to, price_from, price_to, message, changes.

reason, action and status hold the raw recorded values, such as quantity-changed, inventory-set and planned. That is the same information the Per-record audit shows in its Change, Action and Status columns, just unformatted. matching_key keeps the identifier it resolved on as a prefix, so it reads barcode: or sku: followed by the value, and it is blank for a record that resolved no key at all.

Prices export in major units with two decimals, and the file carries no currency column. A blank price cell means the run had no price on that side, and a blank quantity cell means the same for quantity. The changes column is a compact summary of product-field edits, in the form vendor: A -> B; tags: x -> y.

Four things are worth knowing before you reconcile against the file. Records that were already in sync are not in it: a run counts them under Skipped in the Run summary and writes no per-record row for them, and records excluded by the connection's ignore list never reach the file either. The export always covers the run's whole audit trail, so the Item status filter on the run detail page does not narrow it. The preview modal's table stops at the first 2,000 records and says so when it does, while the CSV keeps going. And a run stores at most 5,000 audit records, so the export carries at most 5,000 rows, while the Run summary counts still cover every record fetched.

Expect one quirk in any spreadsheet: a cell whose value starts with =, +, - or @ is written with a leading apostrophe so the spreadsheet treats it as text instead of a formula. Plain negative numbers are left as they are.

The file saves as sync-run- plus the run id, or sync-preview- plus the run id for a dry run.

Export your store catalogue

Use Export catalog CSV to get a snapshot of your Shopify catalogue. It is in the overflow menu next to any row on the Connections list, and in the header of a connection's own page.

The file has 8 columns: matching_key, sku, barcode, product_title, product_status, vendor, quantity, price. There is one row per product variant in your store, read live from Shopify at the moment you click. It is not the supplier's feed, and the export never writes anything.

matching_key is the key the connection you exported from would match that variant on, following the fixed barcode then SKU order, and it carries the same barcode: or sku: prefix as the run export. A blank matching_key is the useful signal: those variants have neither a barcode nor a SKU, so a supplier record can never match them, and they are the rows a later run flags for review as unmatched, with the message "no matching key".

That makes the catalogue export good for two jobs. Use it while building a mapping, to see the identifiers your store actually carries before you decide what to map. Use it as an audit, to check titles, vendors, statuses, quantities and prices across the store in one place, or to keep a before-and-after record around a sync.

Prices in this file also export in major units with two decimals. The file saves as catalog- plus the connection id.

One export at a time

Only one catalogue export can run per store at a time, because it pages your whole catalogue while you wait. Start a second one before the first has finished and the app refuses it; what you see is a "Catalog export failed" toast. Wait for the first download to land, then try again.

The same toast appears if the export cannot complete for any other reason. Very large stores are a known limit: above roughly 20,000 variants the export stops instead of handing you a partial file, because a truncated catalogue CSV looks complete once it is open in a spreadsheet.

Need help? Visit the support page or email hello@usenormalize.com.