Cook for four hundred, billed to the tray.
Lanemi runs your meal contracts the way institutions actually work: standing daily counts each school or office adjusts from its own login, term breaks that pause without phone calls, cook counts locked per service, and a month of meals closed with one consolidated invoice. In your currency, wherever meals are served.
The count is the contract, and the count keeps moving.
Institutional catering is won on price and kept on reliability. The margin per tray is thin, the headcount shifts with attendance, exams and field trips, and the invoice at month end is checked by an administrator whose job is to find the discrepancy.
The moving headcount.
Four hundred on Monday, three-sixty on exam day, zero on the holiday nobody told you about. Every wrong count is cooked money.
Term breaks by surprise.
A two-week break pauses everything, and the resumption date lives in someone else’s circular.
The disputed invoice.
A month of daily counts, reconstructed at billing time from delivery memory, against an administrator with their own records.
Payment at committee speed.
Institutions pay on their cycle, after their approvals, and a caterer’s cash flow carries the gap.
Their admin sets the count. Your kitchen cooks it. The invoice writes itself.
Each institution runs its own count.
Register each school, hostel or office as a business customer with its own login. Their admin holds the standing daily count, drops it for exam days and field trips, and raises it for events, all before your cutoff. The changes land in your plan, not in your phone.
Term calendars that pause cleanly.
A term break is a pause with a resume date: nothing is cooked, delivered or billed for the empty weeks, and the contract resumes on the day term does. The hostel that closes for a festival week works the same way.
Cook counts locked per service.
Lunch and any second service run as separate slots, each with its own cutoff and locked count across every institution you serve. The kitchen cooks one exact number per service, and the vans load against a printed sheet.
Every tray on the record.
Each day’s delivery is confirmed at the institution with proof of delivery, so the month is a list of facts, not memories. At month end the account closes with a statement listing every service and one consolidated, numbered tax invoice the administrator can check line by line, and approve.
Committee-speed payment, managed.
Institutions run postpaid accounts with credit limits and due dates set to their payment cycle. Dues past terms are flagged on their own, and whether service continues stays your decision, informed by an account that can never drift. Event orders, a sports day or a conference, join as one-time orders on the same account.
Built for thin margins and checked invoices.
| What you get | What it does for you |
|---|---|
| Institutional accounts | Each school, hostel or office with its own admin login |
| Admin-managed daily counts | Headcount changes made by them, before your cutoff |
| Term-aware pauses | Breaks pause everything cleanly, resume on the date |
| Per-service locked cook counts | One exact number per service, across every contract |
| Proof of delivery per day | The month as facts, not reconstructed memory |
| Monthly statements and consolidated invoices | One numbered tax invoice an administrator can approve |
| Credit limits and due-date terms | Committee payment cycles managed, dues flagged |
| One-time event orders | Sports days and conferences on the same account |
| Delivery slots | Lunch and second services, each with its own cutoff and route |
| Disputes and credits | A short delivery settled with a fair credit, on the record |
| Honest limit | Food safety, menus, nutrition standards and institutional compliance stay entirely the caterer’s responsibility. The platform keeps the counts and the money exact |
The count-and-contract trade is the same everywhere.
School midday meals, hostel messes, office cafeterias, care homes: the institutions differ, the moving headcount and the checked invoice do not. Choose your currency, set your service slots and cutoffs, and keep your catering licences on file, with a reminder before they lapse.
Built by people who plan tomorrow the night before.
Lanemi began on a round where the night’s locked plan decided the morning’s work, with no room for guessing. Contract catering is that discipline multiplied by four hundred trays, and the per-service locked count at the heart of this platform is built for exactly that arithmetic.
The things institutional caterers ask us first.
Headcounts change daily. Who keeps them current?
The institution does, from its own login, before your cutoff. Their admin owns the count; your kitchen cooks the locked number; nobody reconstructs anything at month end.
What happens during term breaks?
The contract pauses with a resume date. Nothing is cooked, delivered or billed for the break, and service resumes automatically when term does.
How does this end invoice disputes?
Every day’s delivery is confirmed on the spot, the statement lists each day’s count, and the consolidated invoice reconciles to those lines exactly. The administrator checks it once and approves it, because there is nothing left to find.
Institutions pay slowly. How is that handled?
Terms and due dates match their cycle, a credit limit bounds the exposure, and overdue accounts are flagged early. Whether to continue serving is always your call, made on facts.
Can I serve three schools and an office from one kitchen?
Yes. Each is its own account with its own counts, and your kitchen sees one locked total per service, with the per-institution split for loading.
Do you handle nutrition standards or food-safety compliance?
No, and we are plain about it. Menus, standards and compliance stay with you as the caterer. We store your licence documents and remind you before they expire; the responsibility itself is yours.
One good idea for your round, once a week.
Short, practical, and no filler. Leave any time.
Ready to bill to the tray?
Book a demo and we will set it up with your institutions, your services, your terms and your currency.