This inventory automation case study starts with a client who didn't think they had an inventory problem at all. A regional F&B chain running six outlets believed their waste was "normal for the industry," somewhere around 8-10%. Monthly stock reports, done in spreadsheets, backed that belief up. It took switching from monthly to daily counts, on a genuinely simple app, to reveal the real number was closer to 30%.
The technology involved was almost trivial. What changed the outcome was frequency and visibility, not sophistication. I'm sharing this one because it's a pattern I keep seeing: owners assume their waste problem needs a smarter system, when what they actually need is a faster feedback loop on the system they already understand.
Everything below is anonymized. The chain, its exact locations, and specific product names are not disclosed.
The Starting Point
The client's process before we got involved:
- Monthly physical stock counts, done manually, entered into a shared spreadsheet
- Waste logged inconsistently, some outlets wrote it down, most didn't
- "Shrinkage" bucketed as a vague catch-all line item, never investigated further
- Reports reviewed by ownership once a month, weeks after the waste actually happened
By the time anyone saw a number, the month was over and the specific spoiled batch, over-ordered ingredient, or portioning error behind it was long forgotten. Nobody could connect a number on a spreadsheet to a specific Tuesday shift three weeks earlier.
What Did We Actually Build?
The build itself was four deliberately unglamorous pieces, not new technology: a mobile-friendly stock count form per outlet, a shift from monthly to daily counts on high-waste categories, a mandatory waste-reason field instead of free text, and a next-morning rollup visible to outlet managers. Here is what each piece looked like in practice:
- A simple mobile-friendly stock count form, one per outlet, filled by shift leads
- Daily (not monthly) counts on high-waste categories: perishables, prepped ingredients, and anything with a short shelf life
- A mandatory waste-reason field, dropdown options like "expired," "over-prepped," "customer return," "prep error," not a free-text box people skip
- A daily rollup visible to outlet managers the next morning, not buried in a monthly report
No predictive algorithms, no automated reordering, no integration with the POS system in phase one. Just faster, more granular, more honest data capture. This is the same principle behind KPI dashboards: most businesses don't have an analytics problem, they have a data freshness problem, and fixing that alone changes behavior before any deeper system is built.
Most businesses don't have an analytics problem, they have a data freshness problem.
Ervandra Halim
What Did Daily Visibility Actually Expose?
Daily visibility exposed three patterns that a monthly rollup had hidden for years, each surfacing within the first two weeks of counting: one outlet's recurring Friday over-prepping, an expiry spike tied to delivery-schedule mismatches between two outlets, and a single prep station's disproportionate share of errors across all six locations.
- One outlet was consistently over-prepping a specific ingredient every Friday, anticipating weekend demand that hadn't been that high in months
- Two outlets showed a spike in "expired" waste tied directly to delivery schedule mismatches, stock was arriving faster than it could be used before shelf life ran out
- A single prep station accounted for a disproportionate share of "prep error" waste across all outlets, pointing to a training gap rather than six separate local problems
None of this was visible in the monthly spreadsheet because by the time anyone looked, the waste from week one was averaged in with corrections from week three, and the pattern flattened out into a number that looked "normal."
The Behavior Change, Not the Tech Change
Here's the part that mattered most: waste started dropping before we changed a single process. Just the act of shift leads logging waste daily, with a manager who could see it the next morning, changed behavior on the floor. Nobody wants to be the outlet with a visible spike in "prep error" waste appearing in a report their manager reads every day. That accountability pressure alone drove roughly half of the eventual improvement, before any formal process redesign happened.
The remaining improvement came from acting on what the data showed: adjusting Friday prep quantities at the one outlet, renegotiating delivery timing to reduce the expiry mismatch, and running a short retraining session at the prep station with the recurring error pattern.
Results After Three Months
| Metric | Before | After 3 months |
|---|---|---|
| Waste (% of ingredient cost) | ~28-30% (previously believed to be ~8-10%) | ~20% |
| Waste visibility lag | 30+ days | Next-day |
| Outlets logging waste consistently | 2 of 6 | 6 of 6 |
The 30% reduction in waste came almost entirely from the first three months of daily visibility plus small, targeted fixes. No inventory forecasting software, no automated purchasing, no POS integration. Those are reasonable next steps, but they weren't what drove the initial win, and building them first would have delayed the value by months for no added benefit.
Why Does This Matter Beyond F&B?
This pattern matters beyond F&B because it generalizes to any business running monthly reconciliation on something that actually happens daily: cash handling, stock movement, service tickets. Averaged, stale data gets called "normal" simply because nobody has a fresher comparison. The fix usually isn't a bigger system, it's counting more often and surfacing the number to whoever can act within a day, not a month. That same logic is behind why payment reconciliation should never be a monthly scramble either, faster cycles catch problems while they're still small and specific.
The Practical Takeaway
Before investing in forecasting software or a complex inventory system, ask a simpler question: how often are we actually counting, and how fast does the person who can fix a problem see the number? If the honest answer is "monthly" and "weeks later," you likely have hidden waste that a daily count, on nothing more sophisticated than a form and a dashboard, will expose within the first two weeks. Fix the visibility gap first. The technology upgrade can wait.
