If you run one Shopify store with a straightforward range, the right way to connect it to Xero, MYOB or QuickBooks Online is an existing connector app. Pick one that supports your accounting system, map your sales, shipping and payment accounts once, and let it post orders to the books. It will cost far less than anything built for you, and it will be running the same day.
A custom integration starts to make sense when the connector is running but your accounts team still spends hours each week fixing what it posts. The usual causes are several stores feeding one set of books, tracking and freight data from another system, supplier costs, payments that don’t line up with invoices, and tax codes that don’t match how you actually sell. The rest of this guide covers each of those, and what a custom build does about them.
Start with a connector app if your setup is simple
Connector apps are built for the common case: one store, one currency, one set of tax rules, and products that sell the way they’re listed. They usually charge a monthly subscription, often scaled by order volume. For a single store, that trade is a good one. You get a supported product, a vendor who keeps up with changes to Shopify and your accounting system, and nothing to maintain yourself.
Signs the connector is doing its job:
- Your bookkeeper reconciles the Shopify clearing account each month without much digging.
- Refunds and discounts land in the right accounts.
- Nobody keeps a spreadsheet on the side to track which orders were fixed by hand.
If that describes you, stop here. Custom software won’t save enough to cover its price, and we’d tell you the same on a call.
Where off-the-shelf connectors break down
The problems tend to show up as the business grows around Shopify, not inside it.
Several stores, one set of books
Many businesses run more than one storefront: a retail store, a trade store, a store per brand. Each has its own order numbers, customers and payment settings, but they all report into one company file. Connectors are usually set up per store, so you end up with several syncs that each make their own decisions about customers, accounts and numbering. Merging them cleanly is left to your accounts team.
Tracking and freight from another system
If you ship through ShipStation or a similar freight system, the tracking number and actual freight cost live there, not in Shopify. Getting them onto the invoice in your books is often a person copying and pasting each morning.
Supplier costs
Your margin depends on what you paid the supplier, and that changes every time a new price list arrives. A connector moves sales. It doesn’t read a supplier’s spreadsheet and update your cost prices.
Payments that don’t match
Payouts arrive as one deposit covering many orders, less fees, sometimes with refunds netted off. Orders paid by bank transfer or on account arrive days later. When the connector can’t tie a payment to an invoice, someone matches it by hand.
Tax codes and one-cent GST rounding
Shopify works out GST at checkout. Your accounting system works it out again on the invoice. On some line combinations the two disagree by a cent, and the invoice total no longer matches the payment. One cent is nothing, but dozens of them a week leave a trail of small differences your bookkeeper has to clear. Mixed carts with GST-free food, freight and gift cards make the tax mapping harder again.
Orders that silently never reach the books
This is the one that hurts. A sync fails on one order because of a missing customer field or an unmapped product, logs an error nobody reads, and moves on. The order is in Shopify and not in your books, and you find out at month end or when a customer asks for a tax invoice.
What a custom integration does differently
A custom integration is software written for your stores and your chart of accounts. It reads from Shopify and writes to your accounting system the same way a connector does, but the decisions inside it are yours.
- Your rules. Which store maps to which income account, how trade customers are named, how freight is coded, what happens to a gift card. Written down once, applied to every order.
- Checks for missing orders. A regular comparison of what’s in Shopify against what’s in the books, with a list of anything that didn’t arrive.
- Exceptions go to a person. When an order or payment can’t be matched with confidence, it isn’t guessed. It lands in a short list for someone to look at.
- Run history. Every run records what it did, so when your accountant asks why an invoice looks the way it does, there’s an answer.
It can also pull in the data a connector can’t: tracking from ShipStation, costs from supplier price lists, payments from other channels. That’s the point where it stops being a sync and becomes part of a hub. Our accounting integrations page covers the wider picture.
What this looked like for Raw Blend
Raw Blend sells blenders, juicers and commercial kitchen equipment through six Shopify stores, all reporting into one QuickBooks Online company. Orders reached the books through OneSaas, a third-party sync tool, and the gaps were filled by staff.
We replaced that sync with one built for their setup. Shopify orders from all six stores become QuickBooks invoices, customers and payments under one set of rules. A missing-order watch lists any order that hasn’t reached the books, so nothing disappears quietly. The one-cent GST rounding differences are cleared daily instead of piling up.
Tracking was the first job. Warehouse staff had been copying tracking numbers from ShipStation onto invoices by hand. On the first run, the sync matched and updated 361 of 383 invoices, clearing about a month’s backlog. The other 22 were ambiguous, so they went to a person rather than being guessed. It now runs every hour.
The same hub reads price lists and stock feeds from 26 suppliers and updates cost prices in QuickBooks, so the margin in the books reflects what Raw Blend actually paid. The full story is in the Raw Blend case study.
Xero, MYOB and QuickBooks Online: where we’ve built
To be straight about it, our production accounting work for Shopify is in QuickBooks Online. That’s where the Raw Blend hub posts invoices, customers, payments and costs every day.
We have also built against Xero. A Brisbane clinical nutrition practice’s hub connects to Xero to pick up bank transfers and match them to the right client, alongside its Stripe payments. You can read about that in the clinic case study.
For a Shopify to Xero or Shopify to MYOB build, we check API access and limits for your accounts before we quote. Accounting systems change what they allow and how much traffic they accept, and the plan you’re on can matter. We’d rather find a limit in the first week of scoping than halfway through a build.
| Your situation | Sensible starting point |
|---|---|
| One store, simple products, books mostly reconcile | A connector app |
| One store, but tracking, costs or payments are fixed by hand each week | A connector plus one small automation for the gap |
| Several stores into one company file | A custom integration with your rules and a missing-order check |
| Orders, stock, supplier costs and freight all re-typed somewhere | A hub that connects Shopify, your accounts and your freight system |
A practical next step
Before you change anything, measure the gap. For the next month, ask your bookkeeper to note every Shopify order, payment or invoice they fix by hand, and how long it took. Also run a count: orders in Shopify for the month against invoices in your books for the same period. If the numbers match and the fixes take minutes, keep your connector. If they don’t, you have a clear list of what a custom integration needs to handle, and a number to judge its price against.