Sound familiar?
What WooCommerce stores that keep books in Xero tell us before a project starts.
- Someone exports orders from WordPress every week and pastes them into Xero.
- Our payment gateway pays out in batches and I can't tell which orders are in which deposit.
- Shipping and tax end up in the same account as sales.
- A plugin syncs orders but creates a new contact for every guest checkout.
- Cancelled and refunded orders still show as income.
What we build
Each one is a working piece you can open and check when it's done.
Orders to invoices or sales
Orders, line items, shipping, coupons and tax each land on the account and tax rate you choose, and customers are matched by email before a new contact is made.
QuickBooks, Xero and HubSpot integrations API integrations and data syncRefunds, fees and gateway payouts
Refunds post as credit notes, gateway fees go to an expense account, and each payout is booked as one bank transaction that equals the deposit.
QuickBooks, Xero and HubSpot integrations Stripe integration and billingVariations, stock and multiple rates
Product variations, mixed tax rates, backorders, split shipments and bundles are handled by rules agreed beforehand, so odd orders do not break the run.
API integrations and data sync Python scripts and utilitiesAlerts on a failed order
An unmapped product, a missing tax rate or a Xero timeout sends the order number and cause to email or Slack, and the order can be replayed after it is repaired.
n8n, Make and Zapier automationBackfill of past orders
Orders from your chosen start date are loaded into a test file first, compared with your books, and only then added to the live organisation.
ETL and data pipelinesAudit report and notes
A weekly list shows orders against payouts and invoices, and short notes explain the mapping so your bookkeeper can adjust it without us.
Dashboards and reportingThe two tools: WooCommerce, Xero.
Also connected on request: WooCommerce, Xero, WordPress, Stripe, PayPal, Google Sheets, Slack.
Example projects
Illustrations of the shape of the work, not past clients. Yours gets its own written scope.
Example project
Orders without the weekly paste
Example: a garden supplies shop wants each paid WooCommerce order to reach Xero as a sale with its tax and shipping lines, so no one exports a file on Fridays.
WooCommerce webhooks, Xero API, Slack alertsExample project
Wholesale accounts on terms
Example: a tea importer with a wholesale role on its store wants those orders to arrive in Xero as invoices due in thirty days, not as paid sales.
WooCommerce REST API, Xero invoices, scheduled jobExample project
Subscriptions renewing monthly
Example: a pet food seller on a subscription plugin wants every renewal posted to Xero with the right tax, and a failed renewal flagged to the owner.
WooCommerce, Xero API, email alertsQuestions people ask first
Isn't there already a native connector or app for this?
Plugins and marketplace apps that connect WooCommerce to Xero exist, and many stores run well on one. We look at yours first. If it fits, we set it up properly. If how it summarises sales, handles gateway fees or treats tax is the problem, we build around those limits.
Will it change our existing books?
Only in the ways agreed. We test in a copy first and compare totals with your own before anything reaches the live organisation.
Who owns what you build?
You do. It runs in your own WooCommerce and Xero accounts, with notes on how to change it.
How do we start?
Tell us which payment gateways you use and what your bookkeeper does by hand now. We reply with questions or a written scope.
Tell us what you need built.
Email a few lines about what you want and which tools you use, or call. We reply with questions or a written scope.
hello@pushbuild.com