One Shopify order appears in your spreadsheet three times. It looks like a duplicate—until you notice that each row contains a different product. The order was exported once; its three line items were given separate rows.

Leafy’s Quick Answer

Shopify’s standard order export is a CSV, and orders with several line items can occupy several rows. Decide what the spreadsheet needs to show before choosing columns or writing formulas. For a direct Excel file or a reusable custom layout, LedgerLeaf Free exports CSV or XLSX and saves column profiles.

The important question is not simply “How do I export?” It is “What should each row represent when the file opens?” Answer that first and the spreadsheet becomes far less likely to mislead you.

LedgerLeaf is useful here because it turns that answer into a saved export profile. You decide the file’s purpose once, keep the columns that support it, and generate the same CSV or Excel structure again when the work returns.

Why one Shopify order can become three rows

Shopify’s current order-export documentation explains that additional line items appear on separate lines. Many order-level cells on those extra lines are left blank to show that the products belong to the same order.

Imagine order #1048 contains:

  • one ceramic mug;
  • one gift box;
  • one packet of tea.

The export can represent that order like this:

Order Line item Quantity Order total
#1048 Ceramic mug 1 €54.00
Gift box 1
Tea 1

That is still one €54 order. The line-item rows let you analyse the products separately, while the order total appears only where the export expects it. Blank cells on the later rows are structural; they are not necessarily missing information.

The row structure creates four common mistakes:

  • counting spreadsheet rows as orders;
  • copying the order total into every line and then summing it three times;
  • deleting apparently incomplete rows that contain additional products;
  • filling blank order-level cells before deciding how the table will be analysed.

Use the order name or ID when counting orders. Use line-item fields when analysing products, SKUs, quantities, or fulfilment. Do not treat the physical row count as a business metric until you know what one row means.

Decide what the export is for

An export becomes easier to use when it has one job. Before choosing columns, identify who will receive the file and what they need to do with it.

Accountant handoff

An accountant might need order identifiers, dates, sales, discounts, returns, shipping, taxes, payment status, currency, and destination fields. They probably do not need every fulfilment or marketing column in the same worksheet.

Product or SKU review

Product analysis needs line-item names, variants, SKUs, quantities, prices, and order references. In this file, repeated order identifiers are expected because the products—not the orders—are the unit of analysis.

Payment or tax review

Payment and tax work might require gateway, payment status, tax amount, country, rate, currency, and refund fields. Mixing these into a product-analysis file can make both tasks harder.

Leafy’s Tip

Name the export after its purpose, not the attempt number. “June accountant handoff” is more useful than “Orders final v3.”

Choose CSV or Excel

CSV and Excel are not competing versions of the same thing. They suit different workflows.

Choose CSV when… Choose Excel when…
Another system or script will import the data A person will review, filter, or annotate the file
Portability and simple text data matter most Formulas, tables, or workbook formatting will be added
You want a lightweight data file The accountant specifically requests XLSX

A CSV contains one plain table. It does not preserve Excel formulas, worksheet tabs, cell styles, or notes. An XLSX file can support those features and is often more comfortable for a person working directly in Excel.

Shopify’s standard order export is CSV. If you need an Excel workbook, importing that CSV and saving it as XLSX adds another conversion step. A direct XLSX export avoids that step and reduces the chance of identifiers, dates, or leading zeros being reformatted during import.

Build the export once in LedgerLeaf, then reuse it

The first export often reveals the real problem: not getting data out of Shopify, but turning a broad dataset into the same useful file again next week or next month.

A repeatable LedgerLeaf workflow looks like this:

  1. Set the date range and confirm the reporting time zone.
  2. Decide whether the file is primarily about orders, products, payments, or tax.
  3. In LedgerLeaf, choose only the sales columns needed for that job.
  4. Keep stable order identifiers and the line-item structure clear.
  5. Export CSV for a system import or XLSX for a person working in Excel.
  6. Save the column selection as a profile and reuse it for the next period.

LedgerLeaf Free handles that complete loop inside Shopify admin. The practical benefit is not simply another download button; it is consistency. The accountant or spreadsheet process receives the same kind of file each period without another round of deleting, rearranging, converting, and renaming columns.

Check the file before sending it

Before handing off any export, confirm:

  • the date range and time zone are correct;
  • the intended currency is clear;
  • order IDs, SKUs, and postcodes have not been reformatted;
  • you know whether rows represent orders or line items;
  • refunds, tax, shipping, and discounts are represented as expected;
  • the filename identifies the store, period, and purpose.

If the spreadsheet contains customer data, store and share it with appropriate access controls. Keep a final copy of the exact file used for the bookkeeping period so a reported figure can be traced later.

Make the saved profile the handoff standard

Once the file passes the checks above, treat its LedgerLeaf profile as the starting standard for that job. Give it a clear purpose—such as “monthly accountant handoff” or “SKU review”—and change it deliberately when the recipient’s requirements change.

A focused CSV or Excel file remains portable: an accountant can review it, Excel can filter it, a pivot table can summarise it, and an approved AI tool can question it. The structure stays useful because the order and line-item meaning was decided before export.

The memorable LedgerLeaf benefit is simple: the next correct export starts from the profile you already built. Customisable CSV and Excel sales exports and saved profiles are included in the free plan.