WooCommerce to Google Sheets: 4 Methods Compared
Every credible method compared - direct plugin, Zapier, Apps Script, Google Sheets API. Costs, setup time, ongoing maintenance, and the operational decisions that separate a working integration from one that breaks at scale.
In This Guide
- Why integrate WooCommerce with Google Sheets in the first place?
- What WooCommerce data can flow to Google Sheets?
- Method 1: Direct WordPress plugin (recommended)
- Method 2: Zapier or Make (middleware)
- Method 3: Google Apps Script DIY
- Method 4: Custom plugin against the Google Sheets API
- Methods compared at a glance
- Which columns can you capture?
- Order status and event rows
- Common pitfalls and how to avoid them
- Frequently Asked Questions
Why integrate WooCommerce with Google Sheets in the first place?
WooCommerce ships with solid built-in reports for revenue, products, and refunds. They are also limited. You cannot pivot by SKU then by customer LTV. You cannot share a filtered view with an accountant who does not have a WordPress login. You cannot run a quick formula across last week's orders to flag any over $500 that have not shipped. The moment your reporting needs anything custom, the built-in reports stop being enough.
A Google Sheets integration gives you the rest. Live order data flows into a spreadsheet your team can sort, filter, pivot, and chart without ever opening wp-admin. Your accountant gets a read-only view of orders this month. Your operations lead sees a fulfillment queue. Your CFO runs a pivot table on revenue by country. No manual exports, no CSV downloads, no copy-paste from the WooCommerce dashboard.
This guide covers every credible method for connecting WooCommerce to Google Sheets in 2026, the trade-offs each one carries, and the practical setup decisions (which columns, when to update vs append, how to handle order-status changes) that determine whether the integration actually holds up long-term.
What WooCommerce data can flow to Google Sheets?
The right starting question is not "how do I connect WooCommerce to Sheets" but "which events do I actually need on the spreadsheet side." WooCommerce fires dozens of relevant hooks; you do not want all of them.
The high-value events most stores capture:
- Order created (
woocommerce_thankyou,woocommerce_order_status_processing) - new orders land on the spreadsheet for fulfillment, accounting, and reporting - Order completed - shipped or delivered, useful for revenue recognition and triggering review-request flows
- Order refunded (
woocommerce_order_refunded) - refunds get their own row or update the original row depending on workflow - Customer created - new accounts feed downstream marketing or onboarding flows
- Subscription events (renewals, cancellations, failed payments) - if you run WooCommerce Subscriptions
- Product changes - SKU updates, stock changes, price changes - useful for inventory dashboards
Lower-value events that rarely justify the noise: cart updates, viewed-product events, every status transition. Capture them only if a specific report needs them.
A good integration lets you pick which events flow to which sheet (or which tab within a sheet) so your fulfillment view is not cluttered with refund rows.
Method 1: Direct WordPress plugin (recommended)
A purpose-built WordPress plugin is the simplest, fastest, and most reliable path. The plugin hooks WooCommerce's native action set on the same WordPress install, builds a row, and posts it to a Google Apps Script web app that you deploy in your own sheet. Your Google account writes the row. SheetLink Forms's WooCommerce Sync add-on follows this model.
Setup time on a typical store is 10-20 minutes:
- Install the free plugin and SheetLink Pro, and activate the licence (5 min)
- Deploy the SheetLink Apps Script as a web app in your sheet and copy its URL (5 min)
- On the WooCommerce Sync screen, switch on the events you want, paste the URL into each one's Receiver URL, and choose which fields each event sends (5-10 min)
Pros: no monthly fees per submission, no third-party intermediary holding your data, no per-event quotas, retry queue handles transient outages, runs on the same site so checkout latency is not affected (deliveries fire async).
Cons: you depend on Google Apps Script staying up (it does), and Apps Script's 6-minute execution cap (2026 quotas) means very large bulk operations need batching. For typical stores this is irrelevant.
This is the right default for any store doing more than a handful of orders per week. Full setup walkthrough is in the WooCommerce Sync documentation.
Method 2: Zapier or Make (middleware)
Zapier and Make sit between WooCommerce and Google Sheets. WooCommerce fires a webhook to the middleware, which then writes to Sheets via OAuth. The setup is point-and-click and no plugin install is needed beyond enabling WooCommerce webhooks.
The catch is cost. Zapier's 2026 pricing charges per task. A "task" is one Zap step. Writing one order to Sheets is 1-2 tasks. At 1,000 orders per month you are looking at 1,000-2,000 tasks; the Professional plan ($73/mo as of January 2026) caps at 2,000 tasks. At 5,000 orders per month you need the Team plan ($300+/mo). Make's 2026 pricing is meaningfully lower per operation but still scales with volume.
Other downsides: every order's data passes through a third-party server, latency is 3-30 seconds depending on plan tier, debugging is harder when something fails inside the middleware, and you are renting a recurring dependency for what should be a one-time setup.
Middleware makes sense for one-off prototypes or for stores under 100 orders per month where the convenience outweighs the recurring fee. Above that, the math turns against it quickly. See the full cost breakdown for Zapier-tier middleware.
Method 3: Google Apps Script DIY
Skip the WordPress plugin and the middleware entirely. Write a Google Apps Script that hits the WooCommerce REST API on a schedule, pulls new orders, and writes them to your sheet.
Setup is JavaScript-flavored: an onOpen or time-driven trigger fetches /wp-json/wc/v3/orders with REST API credentials, iterates the response, and appends rows. The Apps Script editor handles authentication, scheduling, and the spreadsheet write. Total cost: zero, plus your time.
Pros: no plugin installed on the store side, fully transparent code, runs entirely on Google infrastructure (no extra moving parts), good fit for engineers who already maintain the store and prefer code over configuration.
Cons: you own the maintenance. WooCommerce REST API auth tokens expire and rotate. Apps Script triggers can fail silently. The 6-minute execution cap means you cannot pull a year of historical orders in one go without batching logic. Order-status changes do not propagate to the sheet unless your script polls and reconciles the diff each run.
This method is correct for technically inclined operators who want maximum control and zero recurring spend. For non-engineers, the DIY path turns into a maintenance bill that exceeds the cost of a one-time plugin license within months.
Method 4: Custom plugin against the Google Sheets API
The fully custom path: write your own WordPress plugin that uses Google's Sheets API v4 (2026) directly, with OAuth, service accounts, and PHP libraries.
This is the most flexible method and almost never the right answer. You are now responsible for OAuth refresh-token storage, error handling, retry logic, rate-limit backoff, and ongoing API version support. You will spend 4-12 hours getting it working and several hours per quarter maintaining it.
Real reasons this can be justified: you need server-to-server auth without per-customer Google accounts, you have compliance requirements (HIPAA, FedRAMP) that rule out Apps Script's web-app trust model, or your store is doing 50,000+ orders per day and Apps Script's 6-minute cap genuinely limits you. For 99% of WooCommerce stores, none of those apply.
If you do need this path, prefer a managed library (Google's PHP client) over hand-rolled HTTP calls and store credentials with WordPress's options-encryption helpers or a dedicated secrets store. Treat it as a real engineering project with code review, monitoring, and an upgrade path - because that is what it becomes.
Methods compared at a glance
For most operators the choice is between Method 1 (direct plugin) and Method 3 (DIY Apps Script), with middleware as a quick-prototype escape hatch and the custom-API path reserved for edge cases. Cost, setup time, ongoing maintenance, and data-privacy posture each favor different methods, so the right pick depends on order volume, technical comfort, and how strict your data-handling rules are.
The table above summarises the relevant axes. "Data privacy" matters more than it sounds: middleware methods route every order through a third-party processor, which can be a problem for EU stores under GDPR or for any merchant with PCI-scoped data flowing through checkout custom fields.
A pragmatic rule of thumb: pick Method 1 unless you have a specific reason not to, and reserve Method 3 for cases where you actively want to own and maintain the integration code. Methods 2 and 4 should each clear a high bar before being chosen. Most stores end up on Method 1 within a year if they started elsewhere - the recurring cost of middleware compounds and the maintenance load of DIY exceeds expectations.
Which columns can you capture?
A common mistake is dumping every available field into Sheets and ending up with a spreadsheet nobody can scan. Choose columns for the workflow that uses the sheet.
With SheetLink's WooCommerce Sync, an order row can carry these fields:
order_id,status,date_createdemail,first_name,last_name,phone(the billing contact)total,net_total,total_refunded,currencyitems(all line items in one cell: "Product A x2, Product B x1")billing_city,billing_country
That is the whole list for an order. Subtotal, tax, shipping total, payment method, coupon codes and the shipping address are not sent, so a sheet that needs them has to get them from WooCommerce's own reports or from another method in this guide.
On each event's card you switch individual fields off, so a fulfillment sheet can carry less than an accounting one. For accountants who need order-level data the emphasis is on totals, refunds and currency.
Order status and event rows
Orders change status. Pending becomes processing becomes completed becomes, sometimes, refunded weeks later. How an integration handles that decides whether your totals can be trusted.
There are two designs. An upsert finds the order's existing row by order_id and overwrites it, so the sheet has one row per order. An event log appends a row each time something happens, so the sheet has one row per event.
SheetLink's WooCommerce Sync is an event log. It writes a row when an order is created, another when it is completed and another for each refund. It does not update an earlier row, and other status changes, such as processing or on hold, write nothing. Update Mode, which form rules can use, does not apply to WooCommerce events.
Reading an event log takes two habits. First, keep each event in its own sheet (each has its own Receiver URL), or filter on the _sheetlink_wc_event column, before you add anything up: summing total across created and completed rows counts every order twice. Second, to see where an order stands now, take its latest row by order_id. Each row carries net_total, which is the order total less refunds at that moment.
If you need exactly one row per order that changes in place, that is the upsert design, and it means the Apps Script DIY or custom API methods below, where you write the lookup yourself.
Common pitfalls and how to avoid them
A few setup mistakes show up repeatedly across stores:
- Apps Script execution timeouts: stores doing 100+ concurrent orders during a flash sale can blow past Apps Script's 6-minute cap. Mitigation: use a plugin with a retry queue, so a delivery that times out is sent again rather than lost.
- Formula injection in customer notes: a malicious order note starting with
=HYPERLINK("evil.com","click")becomes an executable formula in the sheet. Any modern integration plugin should escape this; SheetLink Forms ships a Formula Guard that prefixes unsafe values with an apostrophe. - PII in the wrong sheet: GDPR-restricted EU orders should not land in a sheet shared broadly with the team. Decide who can open each sheet before orders start arriving. With WooCommerce Sync each event has its own Receiver URL, so customer rows can go to a sheet with tighter sharing than product rows.
- Multisite networks with separate stores: give each store its own sheet and script. Do not share a single Apps Script across stores or you will mix order data.
- Custom checkout fields are not in the row: check what an integration sends before you rely on it. SheetLink's WooCommerce Sync sends a fixed set of order fields and does not include custom checkout fields.
Most of these are operational rather than technical: the integration works fine, but assumptions about how the sheet will be used were not made explicit during setup. Spending 30 minutes up front to define column sets, routing rules, and access boundaries pays back within the first week.
| Method | Cost | Setup time | Maintenance | Data privacy |
|---|---|---|---|---|
| Direct WordPress plugin (SheetLink + WC Sync) | Pro tier: $79/yr or $199 lifetime | 10-20 min | Low | Direct to your Google account |
| Zapier middleware | $30-300+/mo | 10 min | Medium | Third-party processor |
| Make middleware | $10-100+/mo | 15 min | Medium | Third-party processor |
| Apps Script DIY | Free | 30-60 min | High (you own it) | Direct to your Google account |
| Custom Sheets API + plugin | Free + dev time | 4-12 hours | Very high | Direct, fully custom |
Frequently Asked Questions
Does WooCommerce have a native Google Sheets integration?
No. WooCommerce ships with built-in reports inside the WordPress dashboard but no native bridge to Google Sheets. To get order data into Sheets you need either a plugin, middleware like Zapier, or a custom Google Apps Script that polls the WooCommerce REST API on a schedule. Direct plugins are the fastest setup; Apps Script DIY is the cheapest if you are comfortable writing code.
What about extensions like "WC Google Sheets" or "Sheets Connector for WooCommerce"?
Several plugins exist with names like these. Quality varies widely. The questions to ask before installing one: how does it authenticate (OAuth on every site or a relay through the vendor's server), does it handle order-status updates without duplicate rows, can it route different events to different sheets, and what is the support story when WooCommerce or Google ships breaking changes. SheetLink Forms's WooCommerce Sync add-on is built into the same plugin many WordPress sites already use for form-to-sheet, so the operational footprint is one rather than two.
Can I sync historical orders or only new ones going forward?
It depends on the method. Forward sync is the default everywhere: any new order from the moment you enable the integration flows to the sheet. A backfill of earlier orders is a separate job. SheetLink's WooCommerce Sync does not have one; it writes rows from the moment an event is switched on. With the Apps Script DIY method you can page through the WooCommerce REST API, in chunks that stay under Apps Script's 6-minute execution cap.
Will this slow down checkout?
A correctly built integration fires asynchronously - the customer's checkout completes immediately and the spreadsheet write happens in the background within the next 1-3 seconds. SheetLink Forms's WooCommerce Sync uses async delivery so the buyer never waits for Google. Middleware solutions are similar (the webhook fires after order completion). Custom integrations that block the order-completion redirect on a Sheets API call are a misconfiguration; avoid that pattern.
How do I handle order updates without duplicate rows?
Know which design your integration uses. An upsert overwrites the order's existing row; an event log adds a row per event. SheetLink's WooCommerce Sync is an event log: a row when the order is created, one when it is completed and one per refund, and no in-place update. Keep each event in its own sheet, or filter on the _sheetlink_wc_event column, and take the latest row per order_id for the current state.
What about WooCommerce Subscriptions?
Subscription events (initial signup, renewal payment, cancellation, failed payment) are separate hooks in WooCommerce Subscriptions. SheetLink's WooCommerce Sync does not listen for them; it sends the six store events listed on its integration page. For subscription reporting, use the Apps Script or custom API methods, or middleware with a Subscriptions trigger.
Can different products go to different sheets?
Not with SheetLink's WooCommerce Sync: every row of an event goes to the Receiver URL on that event's card. Split by product in the sheet instead, with a FILTER or QUERY on the items column feeding a second tab. Middleware and custom code can branch on line items before writing.
Is this GDPR-safe for EU customers?
The integration itself is GDPR-compliant when implemented carefully: the data path stays inside your WordPress plus your Google account, with no third-party processor in the middle (Method 1 and Method 3). The compliance work is on the operator side: pseudonymise PII columns where possible, restrict sheet sharing, and respect right-to-erasure requests by deleting the corresponding sheet row. A deletion request has to be carried out in the sheet as well as in WooCommerce.
More Tutorial guides
Ship a WooCommerce-to-Sheets integration in 20 minutes
SheetLink Forms with WooCommerce Sync sends orders, refunds, new customers and product changes to your own Google Sheet. Part of the Pro tier, with no per-order fees.
