Why a single source of truth matters.
Two-way sync between two systems is the classic distributed-data problem: when both sides accept writes, you eventually get conflicts. A pair of customers buy the last unit, one in-store and one on Shopify, in the same minute. Without a master, both transactions succeed and you owe goods you do not have.
The fix is a single canonical inventory ledger that both systems read from and write to. Stock levels live there. Sales decrement there. Receipts and transfers credit there. Shopify and POS become projection layers on top of the canonical ledger, not authorities. In Nonari, stock lives per branch in the ledger and the POS sells straight from it; a connected Shopify store is kept in step both ways — Nonari pushes the branch’s count out, and changes made in Shopify flow back in — as the next sections explain.
Branch as the unit of stock.
Stock is per branch, not per organization. A SKU has 40 units at the Austin warehouse, 12 at Brooklyn retail, 8 at Manchester retail, 0 at the EU drop-ship branch. Each Shopify storefront connects to a branch and reads/writes that branch’s stock. Each physical store is also a branch.
When a Shopify order ships from the Austin warehouse, the decrement happens on the Austin branch ledger. The other branches’ stock is unchanged. When a customer buys at Brooklyn POS, only the Brooklyn branch decrements. The Shopify storefront connected to Brooklyn (if any) gets the new stock count pushed straight away.
Outbound stock sync to Shopify.
When a sale, a POS sale or a purchase receipt changes the connected branch’s stock, Nonari pushes the branch’s new on-hand count to Shopify. It sends the absolute level, not a delta, so pushing the same number twice is harmless, and it skips the call when the number has not changed since the last push. For anything else that moves stock — a transfer, a count adjustment — there is a manual push for one product or every product on the branch.
Each push records when it last succeeded and the last error if it failed. Pushes are best-effort rather than queued, so after a Shopify outage run the bulk push to bring every SKU back in line with the branch.
- Trigger: sales, POS sales and purchase receipts on the connected branch
- Absolute levels: the push sets the count, it never adds or subtracts
- Idempotent: the same level twice is safe, and unchanged levels are skipped
- Manual push: one product or the whole branch, after adjustments or an outage
Inbound order events from Shopify.
When an order is placed on the connected store, it arrives in Nonari as an invoice on that branch, with each line matched to its product by variant or SKU; a line Nonari cannot match is flagged with its Shopify SKU so you can fix the mapping. Shopify then lowers its own count and sends an inventory update, and Nonari writes that level onto the branch, so the online branch reflects committed stock as soon as Shopify does.
The flip side is that a count edited in Shopify admin also lands in Nonari. Decide where people are allowed to change stock — ideally in Nonari, through receipts, transfers and adjustments — and the two stay honest. Either way the inventory side is more aggressive than the bookkeeping: stock is gone the moment the order is committed, regardless of payment status.
Multi-location Shopify and the mapping problem.
Shopify supports multiple locations per store. If you have a Shopify store with three locations (Austin warehouse, Brooklyn retail, Manchester retail) all selling on the same storefront, the order specifies a fulfillment location, and something has to decide which branch’s stock that order consumed.
In Nonari the mapping is one store to one branch: each branch holds at most one Shopify connection, a store cannot be wired to two branches, and stock is pushed to the store’s primary location. If your shops also fulfil online orders from their own shelves, keep the online stock on one branch and move units to it with transfers, rather than letting three locations share one storefront count.
Transfer events.
Inter-branch transfers are common: 20 units move from the Austin warehouse to Brooklyn retail to restock. Both branches’ counts change, and any store connected to either one needs the new number. In Nonari a transfer moves the stock but does not push it to Shopify by itself, so follow a transfer into or out of an online branch with a stock push.
The cost moves with the goods. In Nonari a transfer leaves the source branch at its cost and arrives at the destination at that cost (plus any freight you add) — or at a markup, with the unrealized profit eliminated when the branches consolidate — and the destination’s average re-blends on receipt. Nonari never sends cost to Shopify, so report margin from Nonari, not from Shopify’s cost field.
Reconciliation runs.
Periodic reconciliation compares Shopify stock to your ledger. Drift indicates a missed event (push failed, webhook dropped, manual edit in Shopify admin) or a configuration error (location mapping). Catch it as an exception you can investigate, not a silent inventory loss.
Nonari’s tool here is the bulk push, which sets every SKU on Shopify to the branch’s count in one run; use it after an outage or a large adjustment, and spot-check your fastest movers against Shopify each week. Most drifts are explainable (a recent edit, a delayed webhook); the unexplainable ones are usually the real bugs and worth investigating.
Where Nonari fits.
Nonari keeps one inventory ledger with stock and average cost held per branch, online or physical. The POS sells from it directly, each Shopify store connects to one branch that pushes its count out and takes Shopify’s updates in, and transfers move stock and cost between branches, with the receiving branch confirming what arrived.
For a multi-branch retailer running an Austin warehouse plus Brooklyn retail plus Manchester retail plus an EU online storefront, that is one ledger with four branches and one Shopify connection. Stock decisions, COGS and reorder points all flow from the same data, and adding branches or stores adds rows, not new systems.