One-off events break the roster
Ongoing contracts and loose events mixed together = roster chaos. A wedding of 200 people on Sunday costs you 15 extra staff — who, where, with which qualifications?
Catering
CAO Contractcatering, event rostering, allergy tracking and a client portal with order history.
Sound familiar?
Ongoing contracts and loose events mixed together = roster chaos. A wedding of 200 people on Sunday costs you 15 extra staff — who, where, with which qualifications?
One client with a nut allergy accidentally gets a dish with pistachio — a health incident, a claim, reputational damage. An Excel list and loose messages don't forgive this.
A regular calls: "Are we doing the same as last week again?" Someone has to look it up in WhatsApp, email or Excel. 10 minutes lost per order.
CAO compliance
Corporate catering (Contractcatering) and event catering (Horeca) run side by side — Mory switches automatically to the right CAO per shift.
Configurable per organisation. CAO Contractcatering for long-term locations (corporate catering), CAO Horeca for pop-up and event catering. Mory switches in the right allowance set.
Alongside the regular roster (corporate canteen, daily lunches) you plan one-off events with their own qualification requirements and staff. Mory prevents an employee being in two places at once.
For each client you record allergies and dietary requirements. On every order Mory automatically shows warnings if a dish contains an allergen the client has. No more incidents from human error.
Clients see their order history (last 12 months), can place repeat orders, update allergies, and download invoices. Fewer calls, more client satisfaction.
Illustrative estimate
The figures below are illustrative — based on an average organisation, not a specific client. Your savings depend on team size, service mix and current way of working.
| Activity | Manual | With Mory | Saved |
|---|---|---|---|
| Event roster alongside fixed roster | 6 hrs/week | 1 hr/week | 5 hrs/week |
| Allergy check per order | 3 hrs/week | Automatic | 3 hrs/week |
| Looking up order history | 4 hrs/week | 0 hrs (portal) | 4 hrs/week |
| Client communication and reminders | 3 hrs/week | 30 min/week | 2.5 hrs/week |
| Hour admin across 2 CAOs | 4 hrs/month | Automatic | 4 hrs/month |
| Total estimated saving | ± 64 hrs/month | ||
Event roster alongside fixed roster
Allergy check per order
Looking up order history
Client communication and reminders
Hour admin across 2 CAOs
Total estimated saving
± 64 hrs/month
At an average hourly rate that illustratively comes to ± € 2.560/month in time won back.
Mory treats sector-specific CAO rules as configuration, not code: allowances, pension fund and hour norms are set per sector — so the calculation stays correct and auditable.
We expect the catering module in Q4 2026. We're building catering after cleaning, security, landscaping and home care — based on demand signals on the waitlist. Want catering sooner? Sign up; the more sign-ups, the faster we build.
Yes, both models run side by side. Corporate catering with ongoing contracts (CAO Contractcatering) and event catering with one-off jobs (CAO Horeca). Mory switches automatically between the right CAO allowances per shift.
At client level you record allergies and diets (gluten, lactose, nuts, vegan, halal, etc.). At dish level you record the allergens the dish contains. On every order Mory cross-checks these and gives a warning on a match. The employee has to confirm explicitly before the order can be scheduled.
In the catering version: yes, for repeat orders based on existing contracts. For new dishes or ad-hoc jobs a conversation is still needed. The goal is to automate standard orders, not to thin out the relationship.
Per menu item you can set price and availability periods (e.g. "only during the Christmas period" or "summer price €8.50 / winter price €9.00"). On ordering Mory shows the right price and blocks unavailable items.
Mory for catering is in early access — expected Q4 2026. Sign up and help decide which modules get built first.