Supported custom fields

Supported sources

• Order custom attributes become “Order: <key>” columns.

• Line-item custom attributes become “Item: <key>” columns.

Every distinct included custom-field key creates its own Order: or Item: column. After Analyze, deselect fields to omit their columns; this does not remove order or line-item rows. All fields default to included unless your shop has saved an exclusion. There is no frequency threshold, implicit key filtering, trimming, case folding, or Unicode normalization.

Private-style and duplicate keys

Keys beginning with an underscore are included by default because personalization apps may rely on them. They are ordered after ordinary keys within the Order or Item namespace.

If the same object contains the same key more than once, all values are preserved in source order and joined with “ | ” in one cell.

Missing and empty values

A missing attribute or a Shopify attribute with a null value produces an empty cell. The app does not write null, N/A, or another placeholder.

Not included in the MVP

The export does not include order or product metafields, customer name/email/address/phone, notes, tags, financial or fulfillment fields, saved mappings, third-party parser rules, or historical orders that require read_all_orders.

If a field is not found, confirm that it is stored in Shopify as an order custom attribute or line-item custom attribute in the selected date range.