A Shopify order CSV can open with dozens of columns, repeated order numbers, and blank cells under totals. It is carrying order, customer, payment, tax, fulfillment, and product-line data in one flat table.

The better question is not “What does every column mean?” It is “Which columns does this bookkeeping job need?” Shopify’s standard export supplies a broad file each time; LedgerLeaf Free is the missing repeatable layer. It lets you choose the useful sales fields, export them to CSV or Excel, and save that decision as a named profile.

Leafy’s Quick Answer

Read Shopify order CSV columns in groups: identity and dates, order amounts, payment activity, line items, and tax or destination. One order can span several rows, so never count rows or repeat blank totals blindly. In LedgerLeaf, build a focused column profile for the task and reuse the same structure next period.

This is operational guidance, not accounting or tax advice. Confirm the records and treatment your business needs with your bookkeeper or adviser.

First, know what one row represents

Shopify’s order export reference says that extra products in the same order appear on separate lines. Many order-level cells are blank on those additional lines.

An order containing three products might therefore look like this:

Name Lineitem name Lineitem quantity Total
#1048 Ceramic mug 1 €54.00
Gift box 1
Tea 1

That is one order, three line items, and one €54 total. Counting spreadsheet rows as orders overstates activity; repeating the total turns €54 into €162.

Use Name or Id to identify an order. Use the Lineitem columns to analyze products. LedgerLeaf makes that distinction reusable: start every saved profile with the identifier that keeps its rows traceable.

Build a LedgerLeaf profile from five column groups

Shopify explains the headers. LedgerLeaf turns that explanation into a file you can reproduce. Use these groups as profile building blocks, not a requirement to keep every field.

1. Identity and timing

  • Name is the familiar order number; Id is the stable underlying ID.
  • Created at records when the customer completed the order.
  • Paid at, Fulfilled at, and Cancelled at record later events.

Do not substitute one date for another. A sales review, payment review, and fulfillment review can legitimately use different boundaries. In LedgerLeaf, add only the dates that define the profile’s job.

2. Order amounts

  • Subtotal is the amount before shipping and tax.
  • Shipping, Taxes, and Discount Amount separate major components.
  • Total is the order cost; Currency is the store’s base currency then.
  • Refunded Amount shows refunds applied to the order.

These are order-level values. Keep them separate from Lineitem price, Lineitem quantity, and Lineitem discount, which describe individual products. A monthly-books profile should preserve that order-versus-line distinction instead of inviting the same total to be counted on every row.

3. Payment activity

Financial Status tells you whether an order is paid, authorized, refunded, or in another payment state. Payment Method can contain more than one method.

For matching, use Payment References: Shopify says it can include IDs linked to failed payments, captures, and refunds. The singular Payment Reference is deprecated. Payment ID is narrower—it omits captures and refunds.

For a payment-check profile, keep Financial Status, Payment Method, Payment References, and Refunded Amount beside the order ID.

4. Products and SKUs

Lineitem name, Lineitem SKU, Lineitem quantity, Lineitem price, Vendor, and fulfillment fields explain what was sold. Shopify says the export preserves product information from the order date, not today’s catalog values. A LedgerLeaf SKU-review profile can keep those fields and the order link without unrelated address and payment columns.

5. Tax and destination

Billing and shipping columns answer different questions. Shipping country describes the destination; it is not a universal tax rule.

Tax # Name and Tax # Value expose up to five line taxes in the standard export. Build a tax-handoff profile around the tax, country, rate, currency, and refund fields the review requires, then confirm the resulting treatment for your jurisdiction.

Leafy’s Watch-Out

A blank cell can mean “same order as the row above,” “not applicable,” or “not supplied.” Decide which it is before filling, deleting, or calculating from it.

Turn the useful columns into a LedgerLeaf profile

At Studio Eucalipto, our view is simple: a bookkeeping export should contain the columns its recipient can explain, not every field Shopify can provide.

LedgerLeaf Free is the working solution:

  1. Choose the period and purpose—monthly books, accountant handoff, payment check, tax review, or SKU analysis.
  2. Select the relevant order, payment, customer, tax, and OSS fields.
  3. Export CSV for a portable table or XLSX for direct spreadsheet review.
  4. Save the column selection as a named profile.
  5. Reuse it next period, changing it only when the bookkeeping requirement changes.

The result is not just a shorter spreadsheet. It is a repeatable contract: the same identifiers, dates, amounts, and supporting fields arrive in the same structure each time. Without the saved LedgerLeaf profile, the workflow falls back to interpreting, deleting, and rearranging the broad export again. With it, the column decisions become part of the bookkeeping process.

Before handoff, check that IDs and SKUs were not reformatted, currencies and date boundaries are explicit, multi-line orders were not double-counted, and customer data is handled appropriately.

If the current workflow begins by deleting columns and rebuilding the sheet every month, start with LedgerLeaf’s free customizable sales exports. Build the profile once; let the next correct export begin there.