Not known
An ingredient nothing has ever moved reads Not known. It does not read zero, because zero is a claim that somebody checked.
Inventory
The walk-in, counted where it stands
Stock comes off the shelf when the ticket fires — against the recipe that was in force at that moment, not the one you edited afterwards. Waste, deliveries and counts are recorded on the floor, with no connection.
- Certified in a browser and on the register
- Counted offline
- Included in the price
How stock moves
Depletion happens when the ticket fires. Once.
Not at completion, not at payment. The order state machine makes firing structurally once per order, so nothing double-counts and nothing is missed.
Stage 1
The recipe book
What a plate is made of, versioned. Changing a portion today never moves last month’s usage.
Stage 2
The ticket fires
The recipe version travels in the event itself, so the depletion is against the book in force at that moment.
Stage 3
The shelf moves
Ingredients come off in millionths of a base unit. A restaurant portions 1.5 oz, and the arithmetic has to survive it.
Stage 4
Receiving and waste
A delivery goes on, a dropped bin comes off with a reason. Both recorded where they happen rather than remembered later.
Stage 5
Actual against theoretical
What the count found, beside what the recipes predicted. The difference is the question worth asking.
A void does not put food back. A void before the ticket fires consumes nothing. A void after it does not return the ingredients to the walk-in, because the kitchen already cooked them — if the food was genuinely unused it is waste, with a reason attached. Stock is a projection of what left the building, not of what was sold.
On the floor
The work happens where the shelves are
Receiving, waste and marking an item unavailable are all done on the tablet, standing in front of the thing being recorded — with the network unplugged.
- Recorded with no signal. Waste, deliveries and availability go into the local log and sync when the line comes back.
- Survives a force-stop. The tablet was killed mid-entry during the certification run and came back to the same work.
- Lands exactly once. 294.4 oz of chicken less a 2 lb bin came back 262.4. 240 oz of lettuce plus a 10 lb delivery came back 400.
- On hand is read, never stored. It is a projection of the movements, and the screen states how old the reading is.
The Inventory workspace has not been captured yet.
It is certified on the tablet at 0.9.13 build 918. This frame stays empty until there is a real screenshot of it, because a mocked-up one would be the only invented interface on this site.
Honest figures
Unknown is not zero, and short is not empty
Two of the cheapest lies a stock system tells are a zero it invented and a negative it hid. DineStack does neither.
Below zero stays below zero
A projection of −3.2 lb means a receipt was never entered or a recipe is wrong. Clamping it to zero would replace a question with a lie.
A cost nobody entered
Stays unknown in every figure downstream of it. A total built partly on one is shown as a floor that says so.
Counting
Opened in the back office. Counted on the floor.
Count policy is not something to invent on a tablet, so the register does not invent it. A sheet is opened and signed off in the office; what the device does is the clipboard work.
- Written down with no signal
- Shelves are counted offline and held on the device until there is a line to hand them over.
- Survives an app restart
- A sheet half filled in is still half filled in after the tablet has been killed and reopened.
- Refuses a premature hand-in
- A sheet cannot be handed on while any line is still buffered on the device, because a partial count submitted as a whole one is worse than no count.
- Uncounted is not zero
- In the certified run, 492 lb was counted where the books said 500.9 — with two shelves left explicitly uncounted rather than treated as empty.
- Opened and finalised elsewhere
- The device does not open a sheet and does not sign one off. Both are back-office acts, and they stay there.
Cost
What a plate costs, to the extent you have told us
Valuation, cost of goods and what a plate costs are computed from the receipts you have entered, by one costing reader — never by dividing a cost by a quantity somewhere downstream.
Recipe and plate costing is not certified yet. accurate to what has been entered; no restaurant has yet entered a month of invoices It is in the price and it is built. What exists and what has been proven against a real restaurant’s invoices are two different questions, and the second is the one worth asking us about.
Evidence
What that certification actually was
We would rather show you the run than describe the feature. Inventory passed on a clean tenant, over real HTTP, and on the register with the network unplugged.
- 43 / 43browser checks across all nine Admin screens, on a clean tenant
- 38 / 38through the full lifecycle over real HTTP
- 0.9.13 / 918the build physically certified on the tablet, count sheet included