Sector · Institutional catering and corporate kitchens
The goods on the invoice must be the goods that arrived.
A procurement, warehouse, and invoice-control system for institutional caterers and corporate kitchens. The incoming invoice is compared with the goods received, and a short delivery is always flagged “Difference”. Permissions are filtered on the server, not merely hidden on screen.
The incoming invoice is compared with the goods received, and a short delivery is always flagged “Difference”. Percentage tolerance applies only to price deviation — a 5 kg shortfall is never mistaken for being within tolerance and missed.
Every user sees only the products and prices they are permitted to. Permissions are enforced by filtering on the server rather than hiding things on screen: the package is built per user on the server, products outside permission never enter it, and the chef never receives a price.
The language is deliberately plain (“My Warehouse”, “Who Did What”); it was designed for a kitchen team that does not want technical wording. Because every action is recorded with who did it and when, the person responsible can be found when something goes wrong.
A short delivery always reads “Difference”. Percentage tolerance applies only to price deviation; a 5 kg shortfall never slips through, and nobody pays for goods that did not arrive.
Groups such as pulses, vegetables, and meat sit on their own manager's screen; products outside permission never enter the package. Everyone manages only their own group.
The chef never receives a price; the server does not send the information at all, and hiding it on screen is not treated as enough. Price data does not circulate in the kitchen.
The supplier signs in with their own account and sees only their own records; correspondence with suppliers moves into the panel.
Every action is recorded with who did it and when, so there is no argument over responsibility.
Refund money is not written into turnover and materials are not deducted a second time; “Back in Warehouse” adds it back to stock. Neither stock nor turnover gets inflated.
Technology stack
The calculation and role tables live in one place, and the panel imports those same files directly. The number shown on screen and the number the server calculates therefore come from the same function: recipe requirement, portion cost, daily profit/loss, and VAT are calculated there.
Permissions are filtered on the server: a product outside permission never enters the package, and the chef's price arrives empty. Hiding it on screen is not enough; if the rule is not on the server, the data is visible in the network request.
Setup is a simulation: it replays 60 days day by day. Rule and API tests (26 core, 38 end-to-end) run automatically; a production install opens only the schema, the product groups, and the first administrator, and loads no sample data.
What people ask us, answered briefly and plainly.
Catering ERP is a sector-specific ERP for institutional catering and corporate kitchens. A procurement, warehouse, and invoice-control system for institutional caterers and corporate kitchens. The incoming invoice is compared with the goods received, and a short delivery is always flagged “Difference”. Permissions are filtered on the server, not merely hidden on screen.
The quantity on the invoice not matching the goods that entered the warehouse, with a 5 kg shortfall going unnoticed; Not being able to trace who changed what, so nobody can be found responsible when something goes wrong; A chef or product-group manager seeing prices and products they should not see.
Invoice ↔ delivery comparison: A short delivery always reads “Difference”. Product-group managers: Groups such as pulses, vegetables, and meat sit on their own manager's screen; products outside permission never enter the package. Chef screen: The chef never receives a price; the server does not send the information at all, and hiding it on screen is not treated as enough. Supplier portal: The supplier signs in with their own account and sees only their own records; correspondence with suppliers moves into the panel. Who Did What: Every action is recorded with who did it and when, so there is no argument over responsibility. Return rules: Refund money is not written into turnover and materials are not deducted a second time; “Back in Warehouse” adds it back to stock.
Node 20, Express 5, Sequelize, MySQL 8, React 18, Vite, MUI v9.
Pricing depends on how many people will use it, which sections are opened, and whether it must connect to other programs. After the conversation we send a written quote with scope, timeline, and a firm price within 48 hours at the latest.
Yes. For one year after delivery, updates, technical support, and server maintenance continue at no extra charge.
Let's begin
Which units do you work in, which document chain do you follow? We map the scope and prepare a clear quote within 48 hours.
