How to Sync WooCommerce with Xero: A UK Ecommerce Accounting Guide

If you sell through WooCommerce and keep your books in Xero, the monthly close can be a slog: exporting orders, working out which Stripe or PayPal payout covers which sales, accounting for processing fees, handling refunds, and hoping the VAT adds up. Done by hand, it eats hours and quietly introduces errors. Done well, sales, fees, refunds and payouts land in Xero cleanly, and reconciliation takes minutes.

This guide explains how to sync WooCommerce with Xero properly for a UK business: what actually needs to flow between the two systems, the realistic ways to connect them (a WordPress plugin, middleware, or a custom build), how to handle payment gateways and their fees, and the VAT and reconciliation gotchas that catch people out.

What "syncing WooCommerce with Xero" actually means

WooCommerce is a WordPress plugin, so unlike a hosted platform it runs on your own site. That gives you more control, but also more responsibility for how cleanly data leaves it. "Syncing with Xero" usually bundles several distinct jobs together, so get clear on which you need before choosing a tool.

• Sales revenue — your takings, ideally split by tax rate, product type or region.
• Payment fees — what Stripe, PayPal, GoCardless or your gateway deducts before paying you.
• Refunds and chargebacks — money going back out, which reduces revenue and usually reverses VAT.
• Payouts — the actual lump sums hitting your bank, which rarely match a single day's sales.
• Stock and COGS — inventory levels and the cost of goods sold, if you track margin in or alongside Xero.
• Customers — usually optional, and often best left out of Xero for a busy store.

The most common mistake is pushing every WooCommerce order into Xero as its own invoice. A store doing 40 orders a day creates roughly 1,200 invoices a month, none of which match your bank deposits. Your accountant will not thank you, and reconciliation becomes harder, not easier.

Per-order vs summarised: choose the right granularity

There are two broad models for getting sales into Xero.

1. Per-order invoices or sales receipts. Each WooCommerce order becomes its own Xero transaction. This suits low-volume, high-value businesses — bespoke goods, B2B wholesale, trade accounts — where you genuinely want order-level detail and may be invoicing on credit terms.
2. Summarised entries. WooCommerce activity is grouped, usually per day or per payout, into a single summary with lines for sales, shipping, discounts, fees and tax. This is right for most retail-style stores and keeps Xero clean.

If you process more than a handful of orders a day, summarised is almost always the correct answer. If you trade B2B on invoice terms, per-order may be exactly what you want — and the two aren't mutually exclusive if you sell through more than one channel.

The ways to connect WooCommerce and Xero

There's no single "best" approach. It depends on volume, how your gateways pay out, and how much you care about clean reconciliation. Here's an honest comparison.

Approach	Best for	Strengths	Weaknesses
WordPress/Xero plugins	Simple, low-to-mid volume stores	Cheap; quick to install; live in WordPress	Often per-order; weak on payouts and fees; quality varies
Middleware (A2X, dedicated connectors)	Most retail stores at scale	Payout-level reconciliation; fees and VAT handled; accountant-friendly	Monthly fee scales with volume; limited custom logic
Zapier / Make	Light glue, alerts, edge cases	Flexible; no code; connects many apps	Per-order by default; hard to reconcile payouts; costs add up
Custom integration	Complex, high-volume, multi-channel	Exactly your rules; full control; scales	Build cost; needs maintenance; only worth it past a threshold

Option 1: WordPress and Xero plugins

Because WooCommerce lives in WordPress, the obvious first port of call is a plugin that connects the two directly. Several exist, and for a small single-currency UK store with straightforward VAT, a well-maintained one can be genuinely fine.

The catch is that many default to creating a Xero invoice per order and stop short of proper payout reconciliation or fee handling, and plugin quality and support vary widely. Before committing, ask specifically how it handles payment fees and payouts, check it's actively maintained and compatible with your WordPress and WooCommerce versions, and confirm what happens to refunds. The cheapest plugins tend to fall down exactly where accounting gets hard.

Option 2: Middleware (A2X and dedicated connectors)

For a busier retail store, purpose-built middleware such as A2X is often the pragmatic choice. Rather than syncing orders one by one, it groups WooCommerce sales by settlement or payout and posts a summarised journal or invoice into Xero, breaking out gross sales, discounts, shipping, fees and tax — so the total matches the deposit in your bank.

That matching is the whole point. When the Xero entry equals the bank deposit, reconciliation becomes a one-click match rather than detective work. The trade-offs are a monthly fee that scales with volume, and a ceiling on unusual logic.

Option 3: Zapier or Make

Zapier and Make are good for lightweight automation, and both connect to WooCommerce and Xero. They suit specific jobs — drafting an invoice for each B2B order, posting an alert on large orders, or covering an edge case your main tool misses.

Where they struggle is the core accounting job. Out of the box they fire one action per order, which recreates the per-order problem and ignores payout reconciliation. You can build payout-aware logic in Make, but you're effectively rebuilding what middleware already does, and the task pricing mounts up at volume. Use them as glue, not as your primary ledger sync. We cover where these tools genuinely shine on our AI automation page.

Option 4: Custom integration

A custom build talks directly to the WooCommerce REST API, your payment gateways' APIs and the Xero API, applying exactly your rules. More on when that's worth it below.

Payment gateways, fees and payouts: the part everyone underestimates

The core truth of ecommerce accounting is that the money hitting your bank is not the same as your sales.

When a customer pays £100 through Stripe, you don't receive £100. You receive £100 minus the processing fee, and not instantly — payouts are batched and arrive a day or several later. A single payout can cover dozens of orders, partial refunds and fees, all netted together. WooCommerce itself doesn't reconcile this; it records the order, but the settlement detail lives in your gateway.

So a clean sync has to reconstruct each payout: gross sales for the orders included, less processing fees, less refunds and chargebacks settled in that batch, plus any adjustments, to arrive at the net amount matching your bank line.

Gateways behave differently

• Stripe exposes payout and balance-transaction data, so fees and timing can be reconstructed cleanly. This is the easiest case, and what most middleware handles well.
• PayPal is the classic headache: funds can sit in a PayPal balance, fees are deducted per transaction, FX can happen inside PayPal, and withdrawals to your bank are separate events. It usually needs its own clearing account.
• GoCardless and direct debit settle on their own schedule, often netting fees, and suit subscription or invoice-based WooCommerce stores.
• Klarna and "buy now, pay later" providers pay out net of their (often higher) fees and on their own terms, so treat each as a separate reconciliation stream.

A robust setup uses a clearing account per gateway. Sales post to the clearing account; payouts move money from it to the bank. The clearing balance represents money earned but not yet paid out — if it drifts to an odd number, something's wrong, which makes it a useful early-warning signal.

VAT and refunds: the UK gotchas

This is where well-meaning setups quietly go wrong.

• Tax rates by product and region. Standard, reduced, zero-rated and exempt items must map to the correct Xero tax rates. Your WooCommerce tax classes and your Xero mapping have to agree, or your VAT return will be misstated.
• Refunds reverse VAT. A refund isn't just negative revenue; it reverses the output VAT too. Confirm your tool handles partial refunds, not just full ones.
• Cross-border rules. Sales to EU consumers, the OSS/IOSS schemes, and sales outside the UK each carry different VAT treatment. If you ship internationally, this needs deliberate mapping, not a default rate.
• Marketplace and multi-channel. If you also sell via Amazon or eBay, the platform may account for VAT on some sales, so those amounts must be treated differently from direct WooCommerce orders.
• Making Tax Digital. Your VAT figures ultimately feed an MTD-compliant return in Xero, so the audit trail from order to ledger needs to be intact and explainable.

Most VAT errors come from a mismatch between what WooCommerce charged and what the sync recorded. Test a known order, including a refund, before trusting the setup.

Stock and COGS

Two related but separate questions.

• Stock levels. If WooCommerce is your single source of truth for stock, you may not need to sync inventory into Xero at all. If you sell across several channels, a dedicated inventory tool (Cin7, Unleashed and similar) usually sits between your channels and Xero. Forcing Xero to be a multi-channel inventory hub is usually a false economy.
• Cost of goods sold. To see true gross margin you want costs reflected against revenue. Many growing stores start with a simple monthly COGS journal and only move to perpetual inventory once margin by SKU genuinely drives decisions.

Be honest about whether you need stock and COGS automation now, or whether it's a later phase.

When is a custom integration worth it?

Off-the-shelf tools cover the common cases well. A custom build earns its keep when you outgrow them. Signs it's time:

• High volume where plugin or middleware pricing has become painful, or summarisation needs to be smarter than standard tools allow.
• Multiple stores or channels (WooCommerce plus Amazon, eBay, EPOS, a B2B portal) needing consistent posting into one Xero file.
• Unusual revenue recognition — subscriptions, deposits, deferred revenue, bundles — that standard summaries can't express.
• Bespoke tax logic across regions and schemes that no single connector maps correctly.
• Operational coupling — the same pipeline also updating a warehouse system, triggering fulfilment, or feeding a reporting warehouse.

A custom build talks to the WooCommerce and Xero APIs directly and writes clean, payout-matched entries on your exact rules. The cost is real — design, build and maintenance — so it makes sense once the cost of getting it wrong (misstated VAT, hours of reconciliation, margin you can't see) clearly exceeds the build. As an indicative UK market guide, a focused WooCommerce-to-Xero build commonly sits in the low-to-mid five figures depending on channels and complexity — treat that as a range to sanity-check quotes against, not a price.

There's often a sensible middle path: use middleware for the standard flow and add a small custom piece only for the edge case it can't handle. That's the pragmatic, vendor-neutral call we help make in our API integration work, tied into your wider data integration where reporting matters.

A practical rollout checklist

1. Map your accounts first — sales, shipping, discounts, fees, refunds, FX and clearing — before connecting anything.
2. Choose granularity (per-order vs summarised) based on volume and whether you trade B2B on terms.
3. Pick the lightest tool that does the job, usually a plugin for small stores or middleware for scale.
4. Set up clearing accounts per gateway and confirm payouts reconcile to the penny.
5. Verify VAT mapping against a known order, including a partial refund.
6. Run a parallel month alongside your old process before trusting it.
7. Document the setup so the next person, or your accountant, understands it.

How APIwise can help

Getting WooCommerce and Xero talking is rarely the hard part. Getting them to reconcile cleanly — with the right VAT treatment and payouts that match your bank to the penny — is. As the UK's API and AI integration specialists, we're vendor-neutral: if a maintained plugin or middleware plus a small tweak is right for you, that's what we'll recommend. If your volume, channels or tax rules genuinely call for a custom build, we'll scope and price it up front, fixed.

The simplest next step is our fixed-price Integration Health Check: we review how your systems connect today, find the gaps and risks, and give you a clear, costed plan. The fee is credited against any build Sprint that follows.

Book your Integration Health Check and make your WooCommerce-to-Xero sync something you never have to think about again.