For multi-branch food & retail businesses
Every branch, one dashboard. Sales, cash, stock and staff reconcile themselves the moment a shift closes — so you already know, instead of asking.
Runs in a browser on hardware you already own. No terminals to buy.
The problem
Three branches, three shifts a day, and every number you rely on has been through at least one person's memory before it reaches you.
“I find out on Friday.”
Every branch reports when someone gets round to it. By the time the numbers reach you, the week they describe is already gone.
“The drawer is short and nobody knows why.”
A cash discrepancy surfaces hours after the shift ended, with no record of what was counted, by whom, or against what.
“Stock on paper is not stock on the shelf.”
The spreadsheet says you have thirty. The shelf says eleven. Nobody can tell you where the other nineteen went.
“I take someone's word for it.”
Cash is collected, expenses come out of it, the rest is banked. The only record of what happened in between is a person's memory.
How it works
Staff use the app that matches their job and hold nothing but a PIN. You get one dashboard that agrees with all of them, because it is built from them.
The register runs on any tablet or phone. It keeps selling when the connection drops, and every sale is attributed to the open shift and the person who rang it up.
Expected cash is derived from the sales and the expenses. Counted cash is a denomination ladder. The difference is recorded against a named cashier — or recorded as not counted, which is a different thing.
When every shift is in, the day's report assembles from the shifts themselves. Nobody keys it in, so nobody can key it in wrong.
One dashboard across every branch, with the gaps stated rather than smoothed over. A day covering one shift of three says so.
Features
Each of these replaces a paper form, a group chat, or a conversation that starts with “are you sure?”
01 · Point of sale
A browser-based register that runs on hardware you already own, and keeps taking sales when the signal doesn't.
02 · Shifts & cash
Every shift opens, closes and reconciles once. Expected cash is derived, counted cash is measured, and the difference is attributable.
03 · Inventory & recipes
An append-only ledger of every movement, with a reason and a cause — so a variance can always be explained rather than argued about.
04 · Cash collection
The collector's round is a record, not a memory: what each branch counted, what was handed over, what the round cost, and what reached the bank.
05 · Attendance
A PIN time clock with a selfie at each end, on the app's own camera. Hours total per day, month or year.
Every location plotted, with the ones missing a pin listed rather than dropped.
The full day report per branch, printable, plus CSV of the whole filtered set — not just the page on screen.
Permits, contracts and signed records, filed by a scheme you define, tied to a person or a place.
Staff hold a PIN and see only their branch. Admins hold an account and see only their organization.
Two branches in one business can legitimately run a different number of shifts a day.
An open shift contributes live totals, so today reads as today rather than as zero.
See it
Opening the drawer, ringing up a split payment, keying an expense, counting down and closing — then the day assembling itself on the dashboard.
Why trust the numbers
Most systems make a figure look confident. The useful ones tell you when they don't know. Branchflow is built to refuse to invent numbers, and that shows up as four specific refusals.
It reads “not counted”, and it is excluded from the variance rather than flattering it. A fabricated zero would say “counted and balanced”, which is the most misleading thing a report can claim.
Voided orders are excluded from every total, and reported separately rather than disappearing. An invisible void is how a reconciliation argument starts.
It does not rewrite the book quantity. If counting became the system's truth, shrinkage would appear once and then vanish into the running balance.
A closed shift stays closed. Corrections are appended — what the value was, what it became, who changed it and why — so sign-off can never make a wrong number permanent.
Who it's for
Branchflow is opinionated. That makes it a very good fit for some businesses and a poor one for others, so here is both.
FAQ
Yes for selling. The catalogue is held on the device so search and checkout keep working, and a sale that could not reach the server is retried with an idempotency key — so a dropped connection never produces a duplicate order. Reports and the admin dashboard do need a connection.
Any tablet, phone or laptop with a browser. The register, the collector app and the time clock all run as web apps, so there is nothing to install and no per-terminal licence. A cash drawer and receipt printer are optional.
No. Staff sign in with a PIN, and every staff-facing endpoint takes the branch from that credential and ignores any branch named in the request. A PIN cannot read another store's takings even deliberately.
They are stored in a private bucket, shown only through short-lived signed links, and deleted automatically after 60 days — the record, the times and the hours are kept, the photograph is not. Staff should be told the app photographs them and why.
Yes, and the correction is recorded rather than applied silently. The original figure, the new figure, who changed it and the reason are all kept, and the day's report re-derives from the corrected shift.
We set up your organization, branches and shift lineup, load your products and raw materials in bulk from a spreadsheet paste, and issue PINs to staff. Recipes — which let a sale deduct raw materials — are entered afterwards and are optional to start.
Yes. Everything is exportable as CSV, and the full day report prints. There is no lock-in mechanism that makes leaving expensive.
Talk to us. Branchflow is early and we are onboarding businesses one at a time, which means pricing and terms are a conversation rather than a page.
Get started
We're onboarding businesses one at a time, so a demo is a conversation about your branches rather than a scripted tour. Tell us what you're trying to fix and we'll show you that part first.