Food-cost counts
Recipes say what the kitchen should have used. Only a physical count says what it did use. A food-cost count is a stock count made for that purpose: it opens and closes a food-cost period.
It works like any stock count, with three differences:
- FlowPOS freezes the book at a cutoff, a moment you choose: when you start the count, or at a time you schedule (for example 11:00 p.m. on the last day of the month). Nobody can move the cutoff afterwards.
- You can keep selling while you count. A sale, a receipt or a transfer between the cutoff and the moment an item is counted is added back, so the item is compared with what should have been on the shelf when you counted it.
- Approving the count posts it, in one step, and only the items someone counted.
Inventory → Stock Count Sessions. Open Stock Count Sessions
Create a food-cost count
Choose New Session and turn on Food-cost count.
- Location: one branch.
- Cutoff: When I start, or At a scheduled time. A scheduled cutoff can't be in the past. At that time FlowPOS freezes the book by itself, even if nobody has the screen open.
- What to count: All items at the branch, some Categories, or a Saved list (see below).
Generate the tasks and start the session as usual. With When I start, the book is frozen the moment you start.
Count
Count with the usual task and scanner screens. You don't need to stop service: every item is adjusted for what moved between the cutoff and the moment it was counted.
Example. The cutoff is 11:00 p.m. and the book says 12.35 kg of beef. At 11:20 a burger sells (0.15 kg). At 11:40 you count 10.85 kg.
| At cutoff | 12.35 kg |
| Moved after cutoff | −0.15 kg |
| Expected | 12.20 kg |
| Counted | 10.85 kg |
| Difference | −1.35 kg (Q −108.00 at Q 80/kg) |
Without the adjustment the difference would read −1.50 kg, blaming the kitchen for a burger that was sold.
If you recount an item, the new count replaces the old one.
Review
Review variance shows, for each counted item: At cutoff, Moved after cutoff (open it to see each sale or movement), Expected, Counted, the Difference and its Value. For each line you can choose a Reason — Miscount, Unrecorded waste, Unrecorded transfer, Unit error, Other — and add a Note, until the count is posted.
- Uncosted: the item has no cost, so the difference has no value (never 0).
- Incomplete: something moved after the cutoff that FlowPOS can't place; check the item before relying on it.
- Not counted lists the items nobody counted. They are not posted, and the food-cost period treats them as not counted.
Close and approve
Close the session, then choose Approve and post. The counted items' differences are posted to stock in one step, and you are recorded as the approver. There is no separate "post" step for a food-cost count.
Count lists
Most kitchens count the same 40–80 items every time. Save them: Count lists on the sessions page → New list: a name, a branch (or All branches) and the items in the order you walk the storeroom. Then choose Saved list when you create a count.
Who can do what
| Create and count | Approve and post | |
|---|---|---|
| Owner, administrator, store manager, inventory manager | ✓ | ✓ |
| Purchasing, warehouse, accountant | ✓ |