Reference
Where the ledger
has to tie
Most merchants arrive at this question from the wrong end: can the accounting package run the stock. It is the wrong end because it treats a valuation system as an availability system, and the two answer different questions on different clocks.
This is the structural answer — what an accounting package genuinely owns, where it stops, and the four reconciliations that break first when a storefront, a stock system and a ledger are asked to agree.
Every commercial relationship, declared
Shopify. StoreBuilder Ltd is a Shopify Partner and earns referral commission when a merchant moves to or upgrades a Shopify plan through the practice. That is a real financial interest in the platform recommendation, and it is stated here rather than on a page a reader may never reach.
No accounting vendor pays us anything. Not Xero, not Sage, not QuickBooks, not NetSuite, not any bookkeeping or reconciliation tool named on this page. No referral fee, no commission, no rebate, no affiliate link, no sponsored placement. If that ever changes, the vendor's name and the arrangement appear in the same sentence as the recommendation.
Valuation is not availability
An accounting package is built to answer what the stock was worth at a moment that has already passed, in a form an accountant and HMRC will accept. A stock system is built to answer what can be sold in the next thirty seconds. Both hold a number called stock, and it is not the same number.
What the ledger genuinely owns
Stock value at period end, cost of goods sold, margin after landed cost, VAT treatment, and the audit trail behind all of it. These are accounting questions and an accounting package answers them properly.
What it cannot own on a real catalogue
Live availability across channels, allocation between a website order and a trade order landing in the same second, multi-location stock, and replenishment. Not because the software is poor — because that is not the job it was designed for.
Where the line usually falls
One channel, one location, a catalogue in the hundreds and slow movement: the accounting package can carry stock, and adding a second system is cost without benefit. Multi-channel, multi-location, or fast movement: it stops, and it stops quietly.
How it announces itself
Not with an error. With oversells during a promotion, a stock figure staff have learned not to trust, and a month-end that takes days because the spreadsheet reconciling the two has become the real system.
The four reconciliations that break first
Every one of these is a question to settle before an architecture is chosen. Settled afterwards, each becomes a monthly manual job that nobody owns and nobody costed.
Payouts against orders
A storefront produces individual orders. A payment processor produces batched payouts, net of fees, on a lag, sometimes spanning a period end. The ledger sees a lump sum that matches no order. This is the most common mess we are called into, and it is the one that makes revenue look wrong rather than merely untidy. On the commonest UK pairing it is one of four flows that have to cross — Shopify and Xero.
Landed cost
Duty, freight and handling are incurred long before the sale and often in another currency. Where they are captured decides whether the margin figure on a product is real. Captured nowhere, gross margin reads several points better than it is, and pricing decisions get made on it.
VAT across channels
Some VAT is collected by the marketplace rather than the merchant, some by the storefront, and the treatment differs by destination. A ledger fed only from the storefront reports a position that is confidently wrong on the channels it cannot see.
Returns and their timing
A return moves stock, revenue and often a fee, and rarely in the same period as the sale. Whether the stock comes back saleable, damaged or not at all is a warehouse fact the ledger has no way of knowing unless something tells it.
How a system physically connects — native app, middleware, bespoke, or a scheduled file drop — and where each of those breaks is covered on the systems reference. Where stock truth should live in the first place is stock and fulfilment, and which system gets nominated to hold it is stock control software. The payouts-against-orders mess above starts one layer up, in whatever is making the order promise.
What this reference does not yet contain
The per-vendor rows — what Xero, Sage, QuickBooks and NetSuite each do with stock at this merchant size, which connectors hold up under volume, and what each arrangement costs to run rather than to buy — are not written here.
The obvious page is a feature grid with ticks and prices. Assembled from vendor marketing it would be worth nothing, and a reader cannot tell the difference between a matrix built from implementations and one built from datasheets. Those rows appear named, dated and attributed as real implementations produce them.
The practical answer in the meantime is the diagnostic: which system holds stock truth, where the ledger takes its numbers from, and which of the four reconciliations above is already being done by hand.
Book the diagnosticTell us what is breaking
What the systems are doing now, and what you need them to do. We will tell you whether it is a platform problem or something cheaper.