Most operations problems are visible. A late job, an angry customer, a missed call. This one was not. It sat quietly inside a spreadsheet, in the gap between an order going out and the money for it landing in the bank. By the time anyone noticed the gap, stock had already left the building.
This is a case study of a centralized kitchen supplying 18 retail outlets for an MNC. The business is anonymised at the client’s request, but the numbers and the mechanics are real.
The setup
The kitchen runs as a central supplier inside a larger group. It does not sell to the public. It produces for 18 outlets belonging to an MNC, each one placing its own orders against its own schedule, at roughly 1,000 pieces per outlet per run. Multiply that out and the kitchen is moving close to 18,000 units through one facility, coordinated by five people handling production, order intake, invoicing, payment follow-up, and dispatch, all at once.
That team was not understaffed in the traditional sense. They were drowning in coordination, not production. Every outlet’s order sat in its own message thread or spreadsheet row. Every invoice had to be raised, sent, and then chased by someone remembering to check the bank feed. Every dispatch decision depended on someone holding the full picture in their head: has this outlet paid, is that order ready, which truck is going out next.
Three problems landing at once
1. Eighteen outlets, one kitchen, no shared view
With 18 outlets ordering independently, the kitchen’s back office was reconciling 18 separate order histories by hand. Nobody on the floor could answer “what do we owe outlet 11 today” without stopping to go and check. That is a coordination cost that scales badly. Adding a 19th outlet does not add one-eighteenth more work, it adds a whole new thread to hold in someone’s head alongside the other 18.
2. Food does not wait
This is a perishable-goods operation. There is no buffer for “we will get to your delivery tomorrow.” An order that sits an extra half day waiting on someone to notice it is ready costs freshness, and in an MNC supply relationship, freshness and on-time delivery are the terms of the contract, not a nice-to-have. Every hour of admin delay was an hour taken directly out of the delivery window.
3. Cash is the business
This is the one that actually put the business at risk. A supplier to an MNC does not get to dictate payment terms. Invoices go out, and the kitchen waits. If stock keeps leaving the building on the assumption that payment will eventually arrive, the kitchen is effectively financing its own customer, unpaid, outlet by outlet, indefinitely. For a business this size, a handful of slow-paying outlets stacking up at once is enough to choke cashflow completely. The team knew this. It is exactly why they were manually chasing invoices before releasing anything. The problem was never that they lacked the discipline to check. It was that checking 18 outlets by hand, every single day, does not scale.
The build
The fix was not more staff. It was putting the entire order-to-payment-to-delivery chain on one dashboard, with the one rule that mattered most, no payment, no dispatch, built into the system instead of left to memory.
1. Order intake, per outlet, in one place
Trigger to action: Each of the 18 outlets places its order through a single intake point instead of 18 separate threads. The order lands on the dashboard tagged to that outlet, with quantity, run date, and status visible immediately.
Why it matters: The back office stopped reconstructing “what is outstanding” from memory and message history. It is a live list, sorted by outlet, sorted by status, always current.
2. Invoicing and payment tracking, automated
Trigger to action: Order confirmed → invoice generated and sent automatically → payment status pulled in against that invoice and shown against the outlet on the dashboard, no manual bank reconciliation required to know where things stand.
Why it matters: Chasing payment used to mean someone remembering to check, then remembering which outlet still owed what. Now the dashboard shows it without being asked, for all 18 outlets at once.
3. Payment-gated dispatch
Trigger to action: Payment lands → order for that outlet flips to cleared for dispatch on the dashboard → the delivery run is released the same day, without anyone having to manually confirm the invoice was paid before letting the truck go.
Why it matters: This is the core of the whole build. The business’s cashflow protection used to depend on a person remembering to check before every dispatch. Now it is a rule the system enforces on its own. The moment payment clears, delivery launches. Nothing waits on someone noticing, and nothing ships on the hope that payment is probably coming.
4. One dashboard, all 18 outlets, live
Trigger to action: Every stage, order placed, invoice sent, payment received, dispatch cleared, delivered, sits on one screen the whole team can see at once, instead of five people each holding a slice of the picture.
Why it matters: Nobody has to ask “where are we with outlet 7” anymore. The answer is already on the screen.
The result
We are not going to hand you a made-up percentage here. What changed is this: the five-person team stopped manually cross-checking 18 outlets’ payment status against a dispatch schedule every single day. Cashflow protection moved from “someone has to remember to check” to “the system will not let it slip through.” Delivery is no longer delayed by admin catching up, it is gated purely by whether payment has actually cleared, which is the one thing that was supposed to matter all along.
The team’s own words on it: they used to spend the first hour of every morning just figuring out where things stood across the 18 outlets. That hour is gone, because the dashboard already knows.
If you are running a supply operation where cashflow depends on someone remembering to check before stock goes out the door, that is not a discipline problem, it is a systems problem, and it is exactly what we build for. Book a quote-to-cash audit and we will map your own order-to-payment-to-delivery chain the same way.
Leave a comment
Your email won't be published