Solutions
Software for hospitality and staff meal programmes
A hospitality contract is a standing order with a moving headcount. The commercial relationship is stable; the number of people to feed changes with rosters, occupancy and shift patterns — often the evening before.
The headcount is the whole problem
Feeding a hotel’s staff canteen or a labour accommodation block is operationally simple in one way and difficult in another. The menu is settled, the delivery window is fixed, and the invoice goes to one business rather than dozens of individuals.
What moves is the number. A roster changes, a floor closes for maintenance, a shift is added, and the count for tomorrow is different from the count in the contract. The person who knows is a facilities or HR coordinator, and the way they usually tell you is a message.
That message then has to become a production number, an ingredient quantity, a pack count and a line on a monthly invoice. Done by hand, the gap between the count delivered and the count billed is where the margin on these contracts quietly disappears.
Running a programme without re-keying the count
Model the contract as a standing subscription
The account is the business, not the individual eaters. Meals per service, services per week and the delivery window live on the contract.
Take the count change through one channel
Whether it arrives by portal or by message, it has to land in one place that timestamps it and attributes it to whoever sent it. A count agreed verbally is a dispute waiting to happen.
Apply a cut-off and mean it
A count that changes after purchasing has committed is a cost you absorb. State the cut-off in the contract and enforce it in the system rather than case by case.
Let production and purchasing derive from the count
Not from last week’s number, and not from the contracted number — from the count as it stands at cut-off.
Invoice from delivered counts
The billing record should be built from what was actually produced and handed over, with the variance from contract visible rather than absorbed.
Where the money goes
| Counts tracked by hand | Counts held in the system |
|---|---|
| Change arrives by message and is applied to the production sheet only. | One change updates production, purchasing, packing and the billing record together. |
| Month-end invoice is reconstructed from memory and delivery notes. | Invoice is built from recorded delivered counts, with the contract variance shown. |
| Late changes are absorbed because nobody can prove when they arrived. | Every change is timestamped and attributed, so the cut-off is enforceable. |
| Over-production is invisible until stock runs short or waste is weighed. | Produced against delivered is a number you can look at each week. |
What this does not solve
Mealroh will not negotiate your contract, and it does not decide what your cut-off should be. It enforces the cut-off you set and records what happened around it, which is a different and more modest claim.
It also does not integrate with a hotel’s property-management or HR rostering system. Counts arrive from a person, through the customer portal or a message, not from an automated feed off the client’s roster. For most Gulf operators running a handful of contracts that is the right shape; if you are running dozens and want roster integration, say so before you buy rather than after.
Common questions
- Can one contract cover several delivery points?
- Yes — a contract can carry several stops, each with its own count and delivery window, while remaining a single billing relationship with one invoice.
- What happens when a count changes after the cut-off?
- The change is recorded with its timestamp but does not silently rewrite a committed production run. That makes the cost of a late change visible and the cut-off enforceable rather than a matter of goodwill.
- Is the invoice based on the contract or on what was delivered?
- On recorded delivered counts, with the variance against the contract visible. Reconstructing a month-end invoice from delivery notes is where margin on these contracts is usually lost.
- Does it connect to a hotel rostering or PMS system?
- No. Counts come from a person, through the portal or a message. If automated roster integration is a requirement for you, raise it before buying — it is not something we do today.
Standing contracts, moving counts
See how a count change propagates to production, purchasing, packing and the billing record in one transaction.
Related reading
- SolutionsSoftware for corporate meal providersCorporate meal programmes look like a bigger version of consumer meal plans and behave nothing like them. Three structural differences change almost every part of the operation.
- SolutionsSoftware for workplace lunch programmesA daily office lunch programme is not a corporate meal plan on a faster clock. The shorter cycle changes which parts of the operation are hard.
- SolutionsSoftware for recurring cateringCaterers moving from event work to recurring contracts discover that their existing systems model the wrong thing — and that meal-plan systems assume a fixed menu they do not have.
- GuidesSetting a meal delivery cut-off that actually holdsThe cut-off is the single most consequential number in a meal-plan operation. It is the line between a change that costs nothing and a change that costs food.
- GuidesWorking out how many customers you can actually serveMost operators estimate capacity from their kitchen equipment and then discover the real ceiling somewhere else entirely — usually in the delivery window or in the coordination workload.