ERP for catering businesses: what we learned building one for a real kitchen
By Apex Horizon Digital
Catering software pitches usually start with accounting. But when we audited Delima Mandiri Catering, the money was not leaking in the books: it was leaking between the WhatsApp order and the kitchen. This article walks through what the audit found, what we built, and what any catering operation can copy without buying anything.
Key takeaways
- Fix order intake first so sales, kitchen, and invoicing share one record.
- Replace parallel production lists with one schedule generated from confirmed orders.
- Connect inventory alerts to planned menu demand instead of static minimums.
One order, typed four times
An order arrived on WhatsApp, was copied into a sales spreadsheet, again into the kitchen production sheet, and finally into an invoice template. Four copies of the same information, four chances to introduce an error, and errors happened weekly: a wrong quantity here, a missed delivery time there. Each one cost goodwill, and some cost the whole order.
The fix was structural, not disciplinary: order intake became a single structured form that feeds sales, kitchen, and invoicing from one record. Order errors went to zero, not because people got more careful, but because there was nothing left to re-type.
The kitchen ran on parallel lists
Before the build, the kitchen worked from a printed list that was already stale by mid-morning. Changes lived in chat messages that reached some cooks and not others. The ERP generates the production schedule from confirmed orders, and changes update the one list everyone reads. That single change (one schedule instead of parallel lists) is where most of the operational calm came from.
What we would tell any catering owner
You do not need to buy software to act on the audit lesson: count how many times one order is re-typed between intake and invoice. If the answer is more than once, that is your leak: every copy is labor plus error risk. Fix intake first; it is the smallest module with the largest effect. Kitchen scheduling second, inventory third. Invoicing last, because by then it is nearly free: the data already exists.