Shopify and your accounts: app or custom build?

Getting shop sales into the accounts is one of the first jobs a growing store wants off its plate. Typing orders into Xero or QuickBooks by hand is slow, and the payout from Shopify never matches the orders on the same day, because fees, refunds and timing get in the way. There are two ways to fix it: an off-the-shelf app, or an integration built around how your business works. This guide helps you choose, and we will say plainly when you do not need us.

Start with what an app does well

Accounting apps for Shopify are built for the common case. Xero and QuickBooks both list Shopify connections in their app stores, and specialist apps such as A2X and Link My Books focus on turning each Shopify payout into a clear summary entry in the accounts. For a store that sells mainly through Shopify, in one currency, with standard VAT and Shopify Payments, an app is usually the right answer: quick to set up, priced monthly, and maintained by someone else.

If that describes you, try an app first. Most offer a trial. Set it up against a month you have already reconciled by hand and compare the results line by line.

Signs you have outgrown an app

Apps follow a fixed model of how a store works. The more your business departs from it, the more you end up fixing by hand after the app has run. Watch for these:

More than one channel. Shopify plus Amazon, eBay, a wholesale portal or a till in a shop, and you need them in the accounts the same way.
A warehouse or 3PL in the middle. Stock and cost of sales need to come from the warehouse system, not the shop.
Unusual tax or currency. Several currencies, goods with different VAT rates in one order, or sales into the EU and beyond with different treatment.
Your own chart of accounts. You want sales split by brand, channel or product range, and the app can only map to a few accounts.
Other systems that need the same data. A CRM, a reporting pack or a forecasting sheet that someone fills from the same orders by hand.
Still reconciling every month. The app runs, but someone still spends hours each month making the numbers agree.

One of these on its own rarely justifies a custom build. Three or more, or one that costs hours every week, usually does.

What a custom integration does differently

A custom integration is built around your rules rather than a standard model. Typically it:

posts each order, refund and payout with the tax, fee and account lines you choose;
combines channels and the warehouse into one consistent picture;
holds anything that does not match, with the reason, instead of posting it and leaving you to find it later;
keeps a log of every entry it made, so your accountant can trace any figure back to the order.

The trade-off is cost and ownership. A custom build costs more up front and someone has to look after it when Shopify or the accounts package changes. That is why the decision should rest on numbers, not preference.

Decide on numbers

Write down three figures for the last three months:

Hours per week spent on getting sales into the accounts and making them agree, including the month-end reconciliation, spread over the weeks.
Errors you can point to: wrong VAT, missing refunds, payouts that never matched, and what each cost to put right.
What an app costs each month at your order volume, plus the hours it still leaves you with.

If the hours left after an app are small, stay with the app. If they are not, our free process scorer turns those figures into a yearly cost and a payback period, and writes a one-page brief you can give to any builder.

Check these whichever you choose

Test on a month you already know. Run the app or the build against a reconciled month and compare totals for sales, VAT, fees and refunds before you switch it on for real.
Agree the account mapping with your accountant first. Which sales, fees and refunds go to which accounts, and how VAT is treated.
Decide what happens to exceptions. Orders that do not fit the rules should be held and reported, not posted quietly.
Know who looks after it. For an app, the vendor. For a custom build, agree support and what happens when either system changes.
Keep your data clean upstream. SKUs, tax settings and product types in the shop feed everything downstream. Our guide to fixing catalogue errors covers the common gaps.

Key takeaways

For a single-channel store with standard tax, start with an app and test it against a month you know.
Several channels, a 3PL, unusual tax or your own account structure are the signs an app will leave work behind.
Decide on the hours and errors left after the app, not on preference.
Whichever you choose, agree the mapping with your accountant and decide how exceptions are handled.