Shopify Orders Column Reference

This reference covers all 204 visible Orders export controls in EditEngine: 51 Base, 13 Customer, 40 Addresses and Browser Details, 6 Company, 31 Line Items, 13 Line Items Product Data, 8 Refunds, 30 Transactions and Risk, 11 Fulfillments, and 1 Metafields control. ID and Name are selected by default. The tax and metafield controls expand into several spreadsheet headers, so a file can contain more than 204 columns.

The screenshot shows the Orders column selector in the signed-in app. The column list is an export reference; it does not mean that every exported value can be imported.

Public Advanced Import supports Orders NEW, UPDATE, MERGE, and IGNORE. Order REPLACE, DELETE, refunds, order cancellation, and fulfillment cancellation are unavailable to normal merchant shops during the current rollout. A destructive-operation setting does not unlock them. Export templates and columns may still include those fields for reporting and format compatibility.

The comparison source is the official Matrixify Orders reference. The import treatment below describes EditEngine, including its narrower support for tax, discounts, customer matching, and line-item changes. Use the Orders export/import guide for filters and the complete workflow.

Read the import labels first

• Create and update: a non-empty value can be applied to a new order or a supported existing-order update.
• Create only: use it deliberately with Command = NEW. Do not include it in a routine update file; some populated creation fields make an existing-order update fail.
• Existing only: an operation on an order that already exists. It is not applied during NEW.
• Report only: the column can describe exported data, but EditEngine does not write that value through Orders import.
• Unavailable: the operation is not enabled for public Orders imports.

Use ISO currency codes such as USD, decimal money such as 19.95, positive whole-number line quantities, and explicit TRUE or FALSE for booleans. Exported dates include the store's time zone. IDs are store-specific: keep destination-store IDs for updates, and remove source-store IDs during migration.

Keep all rows of one order together. EditEngine groups by ID, then Name; an identity-free child row can join the preceding group. Neither Number nor Row # identifies an existing Shopify order. A Name must match exactly and uniquely. A public MERGE lookup miss does not create an order: use explicit NEW for creation.

Do not upload a full export unchanged. Exports write Command = NEW, and exported Line Item rows can append duplicate lines when changed to UPDATE. For an ordinary note or tag update, retain only ID, Command, and the fields you intend to change.

Base — 51 controls

Order totals, weight, tax columns, Note, Order Status URL, and order metafields appear only on the top row of an exported order group. Most other order fields repeat on child rows. Money uses the order's presentment amount when available, with shop money as the fallback; Transaction columns separately expose shop currency.

The order tax selector emits at least three tax blocks and expands up to 100 when the exported data needs them. A rate of 0.20 means 20%. Preserve the difference between order header Tax 1: Title and line header Line: Tax 1 Title—the latter has no colon after the number.

Customer — 13 controls

These columns describe the linked customer, not the shipping recipient. Editing customer profile fields belongs in a Customers import. EditEngine does not reproduce Matrixify's documented customer lookup/create behavior from the Orders customer block.

Addresses and Browser Details — 40 controls

Billing fields are create only. Shipping fields can create or update an address. Blank address fields are omitted; they do not clear existing values. Supply a consistent full destination address when changing its country or province, then verify Shopify's result. Preserve ZIP codes and phone numbers as text.

Company — 6 controls

The company block reports the B2B purchasing company and location. None of these fields changes an order's purchasing entity through the current EditEngine Orders importer.

Line Items — 31 controls

One order can contain Line Item, Discount, Shipping Line, Refund Line, Refund Shipping, Transaction, and Fulfillment Line rows. A column's meaning depends on that row type. Fulfillment and refund rows can echo the original product line; their negative quantities are reporting conventions, not instructions to subtract items.

For existing orders, EditEngine appends a variant or custom item; it does not edit, replace, or remove an existing line by its Line: ID. A Variant ID is the supported catalog reference. SKU, product handle, product ID, and variant title do not resolve a variant in this importer. Repeating an append file can add the item again.

The line tax selector also emits at least three blocks and expands up to 100. Refund taxes can be negative; fulfillment rows echo the source line's positive taxes. EditEngine preserves the line's recorded weight, using current catalog weight only when it agrees at Shopify's recorded precision. Use the next group to inspect today's catalog values separately.

Line Items Product Data — 13 controls

Every field in this group is report only and reads the current linked catalog, not a historical order snapshot. A deleted or custom variant leaves its variant columns blank. Editing these cells changes neither the order nor the product.

Refunds — 8 controls

Use these columns to inspect historical refunds. Public Orders imports cannot execute refunds, even when a refund-related export template is visible. Remove Refund Line, Refund Shipping, and refund Transaction rows from an ordinary update file.

Transactions and Risk — 30 controls

Transaction rows report payment events; their IDs and card details cannot be edited to alter a payment. For deliberate NEW orders, EditEngine accepts the supported transaction inputs below. Non-refund transactions cannot be added to an existing order through this importer. A refund kind requests an unavailable public operation.

Fulfillments — 11 controls

The public existing-order operation here is a tracking update for an existing Fulfillment: ID. It does not create a fulfillment. Use Line: Type = Fulfillment Line and remove copied product-line columns; an existing shipment may export several child rows, but a tracking update needs only one intentional row per fulfillment.

Metafields — 1 dynamic control

Use the exact namespace, key, and Shopify type. If a type is omitted, the Orders importer assumes single_line_text_field. Order list metafields export as comma-separated display values, but this importer passes your supplied cell value to Shopify without converting a list back to JSON. For a list update, provide the type's valid JSON array, for example ["priority","gift"], rather than re-importing the display text unchanged. Reference and structured types likewise require destination-valid values. Do not treat an exported list or source-store reference as automatically ready for import.

Worked example: add a reviewed tag safely

This updates one existing order without changing its note, address, customer, archive state, or lines.

1. In EditEngine → Export, select Orders, filter to the intended order, and export ID, Name, and Tags. Keep that file untouched as your reference.
2. Make a new CSV named Orders.csv or an XLSX worksheet named Orders. Keep one row per intended order with the following headers. Replace the example ID with an actual ID from your export.

ID,Command,Tags,Tags Command
1234567890,UPDATE,reviewed,MERGE

3. Open EditEngine → Import → Advanced import, upload the file, and confirm the detected resource is Orders. Check the selected sheet, command, column diagnostics, and any sample rows shown before starting your own import. A sample is not a full-file or before-and-after validation; review all rows in the spreadsheet separately.
4. Test one non-critical order first. After it completes, review the result file and confirm in Shopify that the old tags remain and reviewed was added. Only then expand the file.

A missing Tags Command defaults to REPLACE in EditEngine, so keep MERGE explicit. To remove the newly added tag later, you can prepare another targeted UPDATE with Tags = reviewed and Tags Command = DELETE, but only if that tag was not already present before the change. This is a corrective import, not app-native undo.

Before you import any Orders file

Verify the row count, identity, and row types. Public files are limited to 50,000 data rows. Keep an untouched export and start with one non-critical order. Remove report-only columns and copied child rows from update files. Pay particular attention to the three blank-cell actions: Customer: ID removes the customer, Closed At unarchives, and a selected Metafield cell deletes that value.

Matrixify documents broader Orders imports, including customer resolution, explicit taxes, discounts, and destructive commands. Those instructions do not establish EditEngine support. The Matrixify Orders reference and bulk order-update tutorial are useful format comparisons; follow the EditEngine treatment in this reference for your file.

Related tutorials

• Export and import Shopify Orders — templates, filters, row grouping, and the Advanced Import workflow.
• Export and import Shopify Draft Orders — use the separate draft lifecycle when preparing orders that are not yet final.
• Export and import Shopify Customers — change customer profiles separately from order contact fields.
• Export and import Shopify Metafields — plan typed custom data and owner references.