One Sale Flow
Follow one sandwich from the till to the ledger. Most systems record the sale and stop there; this is everything that moved afterwards, timestamped to the millisecond.
Nineteen hundred milliseconds, end to end
Scroll, and the rail fills as each system reacts. Every figure is the real before and after for that one sale.
0 ms
The tap
0 ms
The tap
A card, a sandwich, terminal 3. On most systems this is where the story ends: a line in a sales report, reconciled by someone on Friday.
120 ms
A number that means something
120 ms
A number that means something
Receipt R3-000482, from this register's own series rather than a slice of a random id. Two sales can be put in order, and a hole in the sequence is a question worth asking.
340 ms
Three things leave the shelf
340 ms
Three things leave the shelf
Not one sandwich. The recipe is unpacked into its components and each one is deducted at its own weight, which is the only way the stock count still matches the shelf at the end of the week.
610 ms
The margin moves on its own
610 ms
The margin moves on its own
Stock is valued on a running weighted average, so the last delivery landing 8% dearer re-costs every item built from it. You did not change the price. The margin changed anyway, and now you know.
980 ms
The books, without an export
980 ms
The books, without an export
Four balanced lines post to the ledger. The register and the accounts are the same database, so the sale is the journal entry rather than something that becomes one overnight. The exact lines are below.
1,450 ms
Next week gets re-scored
1,450 ms
Next week gets re-scored
One sandwich barely moves a forecast, which is the point: it moves it a little, immediately, instead of a lot on Monday when someone finally exports the week.
1,900 ms
The order writes itself
1,900 ms
The order writes itself
Chicken crosses its par level, so a draft purchase order appears, grouped by supplier and priced from your agreed costs. It waits for you. Nothing is ordered without a person.
The sale is the journal entry
Not a nightly export that turns into one. Here are the exact lines that posted at T+980ms, in the account codes from your own chart. Check the footing.
| Account | Why | Debit | Credit |
|---|---|---|---|
| 1000Cash at bank | the customer paid | 18.50 | |
| 4100Sales revenue | the sale is earned | 18.50 | |
| 5100Cost of goods sold | the sandwich cost this to make | 7.03 | |
| 1100Inventory | the components left the shelf | 7.03 | |
| Balanced, to the cent, before the drawer closed | 25.53 | 25.53 | |
$18.50 sold · 38% material cost · nothing to reconcile at month end
The same sale, on the stack you have now
Every line below still has to happen. On separate systems, a person does it, or it quietly does not get done.
- Ring the saleSame actionPOS appinstant
- Deduct the componentsIncludedSpreadsheet, by hand~4 min
- Re-cost the itemIncludedNobody does this weeklyskipped
- Post to the ledgerIncludedCSV export into accounts~15 min/day
- Update the forecastIncludedGut feelskipped
- Reorder what ran lowIncludedWhatsApp the supplier~10 min
Call it half an hour a day of re-typing, and two things that never get done at all. The two that get skipped are the ones that tell you whether you made money.
Frequently asked questions
What happens in Holo when a sale is made?+
In under two seconds a single sale deducts stock down to its recipe components, re-runs the weighted-average cost, posts a balanced double-entry journal, refreshes the live P&L, re-scores the seven-day forecast and updates any draft purchase order. Nothing waits for an end-of-day export.
Do I have to reconcile my POS with my books?+
No, and there is nothing to reconcile: the register and the ledger are the same database, so the sale is the journal entry rather than something that later becomes one. Month end is a review, not a rebuild.
Why does the margin change on a sale I have made a hundred times?+
Because your costs move. Holo values stock on a running weighted average, so the moment a delivery lands at a different price, every item built from it is re-costed. The 62% in the timeline above is 64% until the last chicken delivery is folded in.
How does Holo know when to reorder?+
It watches consumption against your reorder points in real time and drafts purchase orders grouped by supplier, priced from your agreed costs, using the same live forecast. You review and send; it does not order anything on its own.
See your business in Holo.
Start free in minutes, no card. Or talk to us first and we will walk you through it.