Status: Delivered. Described from our own delivery records. Client identity, brand and commercial terms are withheld. Figures, where given, cover the period stated and nothing beyond it.
Context
A multi-branch fast-food chain that had grown past the point where its operational systems could be run as separate tools.
It needed end-to-end automation across its value chain but could not justify the cost of a dedicated in-house systems team — which is why this was delivered on a shared-resource managed model rather than as a fixed-scope project.
The problem
- Online orders, counter sales and kitchen production were tracked in different places, so the same transaction was handled more than once.
- Ingredient depletion was not driven by what was actually sold, so stock counts and expected usage never reconciled.
- Purchasing was reactive, based on someone noticing a shortage.
- Accounting received summary figures after the fact rather than transactions as they happened.
- Nobody could state the margin on a dish by channel, because the costs sat outside the system that recorded the sale.
What we built
One system covering the chain end to end
E-commerce ordering, point of sale, kitchen routing, inventory, vendor management and accounting, configured as a single flow rather than six integrations.
Recipe-driven depletion
Selling a dish consumes its ingredients at the configured yield rather than requiring a separate stock adjustment.
Automatic posting to the ledger
From every channel, so accounting reflects operations continuously.
Purchasing driven by consumption
With reorder logic based on what the branches actually used.
How we delivered it
- 1
Process mapping across the value chain
With branch and kitchen staff, not only with head office.
- 2
Foundation
Entities, chart of accounts, tax, environments, hardware.
- 3
Menu and recipe build
With the chefs, because yields are what make costing true.
- 4
Channel wiring
Storefront, point of sale, payments.
- 5
Pilot branch
Through a full week including a physical stock count, before any roll-out.
- 6
Branch-by-branch roll-out
Then ongoing managed operation.
How it was phased
Indicative phasing for work of this shape. Actual duration varies with data quality, access and decision speed.
What the client keeps
- The production system
- The recipe library as structured data
- Configuration documentation
- Branch and kitchen runbooks
- The reporting layer