Send Shopify Orders to Google Sheets Automatically
Short answer: Decide first whether you want one row per order or one row per product line, because that choice shapes everything else. Then pick a tool: Shopify Flow can add a row to a Google Sheet when an order is created and needs no extra subscription; Zapier and Make add more control over formatting, line-item loops and updates. Map only the fields the sheet's readers need, include the order ID as a unique key, record timezone and currency explicitly, and plan for refunds and edits with a separate update step or a second tab. With a stable key and a "find row before adding" check, you avoid the duplicate rows that ruin most order sheets.
Who the sheet is for
Before building, write down who reads the sheet and what they do with it. Three common cases:
- Packing team: a small candle brand in Portland wants a list of today's orders with items, quantities and shipping method, so the packer works from a tablet.
- Reporting: the owner wants daily revenue by product and channel without logging into the admin.
- Partner: a wholesale partner or fulfillment house needs only their products' orders, without access to the store.
Each needs different columns. A packing sheet with refund amounts and tax columns just gets in the way.
One row per order or per line item?
| Layout | Good for | Drawback |
|---|---|---|
| One row per order | Revenue totals, customer lists, shipping overview | Items squeezed into one cell, hard to count units |
| One row per line item | Packing, product-level reporting, partner sheets | Order totals repeat on each row, so summing needs care |
For packing and product reporting, line items win. For finance summaries, orders win. Some stores keep both: an Orders tab and a Line items tab, each fed by its own step.
Comparing the tools
Shopify Flow
Flow is Shopify's built-in automation app. Check its availability for your plan in the Shopify Flow help center. A basic workflow:
- Trigger: Order created.
- Optional condition: for example, only orders with a certain tag or sales channel.
- Action: add a row to a Google Sheet, after connecting your Google account.
- Map columns using Flow's variables for order name, created date, total, customer and shipping.
Flow is excellent for the one-row-per-order case. Line-item rows require looping over the order's line items, which is possible with Flow's "for each" logic but more fiddly to set up. Updating an existing row when an order changes is limited.
Zapier
Zapier's Shopify trigger for new paid orders plus the Google Sheets "create spreadsheet row" action is quick to set up. For line items, Zapier can send line item fields as lists and create multiple rows using its line-item support in the Sheets action. To update rows later, use "lookup spreadsheet row" followed by "update spreadsheet row". Each step uses tasks, so a busy store should estimate monthly volume against the plan.
Make
Make handles loops natively with an iterator, so one-row-per-line-item is straightforward. It also makes "search rows, then update or add" logic easy to read in a single scenario. The learning curve is slightly steeper than Zapier's, but it scales well with volume.
Field mapping
A sensible starting set for a line-item sheet:
- Order ID (the long numeric ID, used as the key)
- Order name (for example #1042, what staff recognise)
- Created at, with the timezone stated
- Financial status (paid, partially refunded)
- Fulfillment status
- SKU
- Product title and variant
- Quantity
- Line price
- Currency
- Shipping method
- Customer first name and ship-to city (only if the readers need them)
Leave out email addresses, phone numbers and full addresses unless the sheet's readers genuinely need them. A spreadsheet shared with a partner is an easy place for customer data to leak.
Timezone and currency columns
Shopify timestamps come with a timezone offset, while Google Sheets uses the spreadsheet's own timezone setting (File, Settings). Mismatches shift late-evening orders into the next day and skew daily totals. Either convert dates in the automation tool to your store's timezone before writing them, or set the spreadsheet timezone to match the store.
If you sell in several currencies, write both the presentment currency and the shop currency amount, with a currency code column. Summing a column that mixes dollars and euros produces a meaningless number. Format number columns as numbers in Sheets, not text, so formulas work; see Google's help on number formats if values arrive as text.
Refunds and edits
Orders change after they are created: items are refunded, quantities edited, addresses corrected. Options:
- Append-only with an events tab: add a second workflow triggered by refunds that writes a row to a Refunds tab with order ID, amount and date. Reporting formulas subtract refunds by order ID. Simple and auditable.
- Update in place: when an order is updated, look up its rows by order ID and overwrite status and amounts. Cleaner for packing views, harder to audit.
For most small stores, append-only plus a refunds tab is easier to trust.
A duplicate-safe key
Duplicates appear when a workflow is replayed, when both "order created" and "order paid" triggers fire, or when someone tests with a real order. Prevent them:
- Use the order ID (or order ID plus line item ID for line rows) as a key column.
- Before adding a row, search the sheet for that key. If found, update or skip.
- Use only one trigger per sheet: either created or paid, not both.
- Add a conditional formatting rule that highlights repeated keys, using
=COUNTIF($A:$A,$A2)>1, so any duplicate is visible immediately.
Keep the sheet healthy
- Protect the header row so columns are not renamed and mappings do not break.
- Build reports on a separate tab that reads from the raw data tab; do not let people sort or edit the raw data.
- Archive older months to a separate file when the sheet gets large and slow.
FAQ
Can we backfill old orders into the sheet?
Automations only catch new events. For history, export orders from the Shopify admin as a CSV and paste them into the sheet, matching the same column order.
Why do some orders appear twice?
Usually two triggers are firing, or a run was replayed. Check the trigger, then add the key lookup step.
Is Flow enough for a partner sheet?
If the partner only needs order-level rows filtered by tag, yes. For line-item rows filtered by vendor, Zapier or Make are often simpler to maintain.
Will editing the sheet break the automation?
Renaming headers or inserting columns in the middle can. Add new columns at the end and keep headers locked.
If you would like an order sheet, packing view or partner feed built and tested for your store, message us and we will scope it with you.