A branch problem rarely arrives as a clean ticket. It arrives as a message: "stock shows twelve but the shelf has three". The first job is to convert that into a symptom you can trace: which item, which branch, which time, which system, expected value and observed value.
This guide works through the six problems that appear most often in multi-branch operations, with likely causes, a fix and the control that prevents a repeat. The sequence matters: fix the data path before you retrain the staff.
Start with the symptom, not the system
Ask for the transaction identifier, the timestamp, the user and the branch. Preserve the evidence before anyone edits the record. A screenshot taken after a correction is not evidence; the audit log is. If the system has no audit log, that absence is itself a finding.
Then decide which layer is failing: capture at the branch, transmission between systems, transformation in a report, or interpretation by a person. Each layer has a different owner. Sending a stock discrepancy to the IT team when the real cause is an unrecorded transfer wastes a week.
Symptom: branch stock counts disagree
Likely causes: transfers dispatched but not received, offline sales queued and replayed twice, negative stock allowed at the till, unit-of-measure confusion between cases and units, or duplicate item codes created at different branches.
Fix: replay the sync queue and compare the audit trail for the affected items. Match the transfer document to the receipt. Merge duplicate item codes only after checking historical movements. Block negative stock at the point of sale if the process can support it.
Prevention: one item master with one code per sellable unit, a transfer workflow with dispatch and receipt, cycle counts on high-value items, and a daily exception report for negative or implausible balances.
Symptom: prices and promotions differ by outlet
Likely causes: a local price override that was never expired, a promotion published to some branches only, a tax or service-charge setting applied differently, or a price update that synced after the store opened.
Fix: compare the effective price record, not the shelf label. Check the start and end timestamps, the branch list and the tax rule. Correct the record and issue a credit or apology policy if customers were overcharged.
Prevention: a central price list with branch-level exceptions approved and dated, a pre-opening price check, and an audit report of manual overrides. A promotion should have an owner and an expiry, not just a poster.
Symptom: end-of-day cash does not reconcile
Likely causes: tender types mapped incorrectly, refunds recorded in one system but not another, opening float counted twice, a payment gateway settlement that arrives after the cut-off, or duplicate transactions from a retried sync.
Fix: reconcile by tender type and by cut-off time, then match the gateway settlement file to the sales record. Do not adjust the cash figure until the missing transaction is identified. If the difference is a timing issue, label it as such rather than writing it off.
Prevention: one cut-off time across branches, a daily sign-off by the branch manager, a settlement matching routine, and a variance threshold that triggers review rather than a manual correction.
Symptom: transfers vanish between branches
Likely causes: goods dispatched without a transfer document, receipt recorded against the wrong dispatch, partial receipt left open, or a cancellation that never reversed the in-transit quantity.
Fix: run an in-transit ageing report and contact both branches for each open line. Receive against the original dispatch, not a new document. Reverse the cancellation and record the physical count.
Prevention: a dispatch document that the receiving branch must accept, an ageing alert for transfers open beyond the expected transit time, and a monthly reconciliation of in-transit stock.
Symptom: head office and branch reports disagree
Likely causes: different date ranges or time zones, one report using a live snapshot and the other a nightly extract, cancelled orders included in one view, or tax and currency handled differently.
Fix: reconcile one row end to end, then compare the filter sets. Publish the definition and the refresh time beside the report. If the difference is legitimate, explain it in the report rather than in a footnote nobody reads.
Prevention: a metric catalogue with one definition per number, a shared reporting layer, and a visible "last refreshed" timestamp. The goal is not identical screens; it is explainable differences.
Symptom: staff cannot see another branch's stock
Likely causes: permissions designed by location rather than by role, separate databases per branch, replication delay, or a deliberate restriction that no longer matches the process.
Fix: define who needs read-only cross-branch visibility and for which purpose. Add a view with a latency indicator rather than granting edit access. Test with a branch supervisor and a head-office user.
Prevention: design access by role and task, review it quarterly, and separate the ability to see stock from the ability to move it.
A diagnostic sequence for any branch incident
- Write the symptom in one sentence with expected and observed values.
- Identify the transaction or item and preserve the audit trail.
- Confirm whether the issue affects one branch, one item or all branches.
- Check the capture layer: was the event recorded correctly at the source?
- Check the transmission layer: queues, sync status, retries and timestamps.
- Check the transformation layer: joins, filters, unit conversions and duplicates.
- Reproduce the number from source to report and record where it diverges.
- Fix the cause, then verify with a second transaction before closing the incident.
Prevention: the controls that stop recurrence
- One item master and one code per sellable unit.
- Transfer dispatch and receipt with an ageing report.
- A single daily cut-off for cash and settlement matching.
- Central pricing with dated, approved exceptions.
- Sync monitoring that alerts on queue growth, not only on failure.
- A monthly branch reconciliation that compares stock, cash and sales.
- An incident log with causes and fixes, reviewed by operations rather than only by IT.
Where this fits in our work
We design branch operations and reporting inside our Business Automation division. The business operations automation service covers order, stock and reconciliation workflows. The pricing page explains how assessment and implementation are scoped. For the inventory cost angle, read what inventory synchronisation costs in Bangladesh.
Sources
- Shopify Help, Locations and multi-location inventory, accessed 17 November 2026.
- WooCommerce, Managing products and inventory, accessed 17 November 2026.
- GS1, Global Trade Item Number (GTIN), accessed 17 November 2026.
- Shopify Help, Orders, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.