Glossary

Who cooks and delivers. Maintains recipes, menu plans, production, stock and billing. Sees numbers only of the eaters, no names.

Who is supplied — nursery, school, after-school club, care home, staff canteen, municipality. Maintains its own structure and its people, reports headcounts, absences and closures. The controller for the eaters' personal data.

Who eats or decides for someone. Sees the menu plan, orders and cancels. For end users CateringOS is free.

An organisation above several facilities — a municipality with eight nurseries, say. The contract can cover the whole provider or only a partial scope (“the schools only”).

The answer to “which houses get the same plan?”. Three nurseries with an identical menu plan are one menu-plan group — you plan once, not three times. Not to be confused with a care group.

A group inside a facility — “Ladybirds”, “class 3b”, “ward 2”. Belongs to the facility and is maintained there.

A parallel service on the same day: standard, vegetarian, vegan, pork-free, halal, or consistency levels (soft, puréed, strained). Its own lane in the planner, its own number at serving.

Starter, main course, side dish, dessert.

A recurring plan — a four-week rhythm, for instance. Built once and then rolled out weeks in advance.

From when you supply a facility. Before this date no quantities arise, even if a plan exists.

A weekday on which you deliver. No delivery day, no demand.

The building block: a preparation with ingredients, from which allergens and nutrition are calculated (e.g. “mashed potatoes”). Maintained once, reused across many dishes.

What lands on the plate and gets planned into the menu — composed of one or more recipe building blocks (e.g. “roast beef with mashed potatoes”). Allergens, nutrition and labels are aggregated from the blocks.

A group of eaters with a factor: crèche child 0.5, school child 0.8, adult 1.0. Usually defined by an age range. That is how heads become quantities.

People multiplied by the factor of their portion group. The number you cook to — as opposed to the plain headcount.

How many people are eating. Can be reported by the facility or recorded by the kitchen over the phone; in the second case it counts as a declared target quantity and is not reduced by cancellations a second time.

A delivery address in its own right. A provider with five houses has five delivery points — this is also the unit the CateringOS plan is priced by.

Until when a cancellation still changes something — usually “up to X days in advance, by HH:MM”. Set in the contract. After that the day is billed, even if nobody eats.

What is to be cooked today, in what quantity, per menu line and course.

How what has been cooked is split across the houses — facility × portion group, printable as a picking and delivery slip.

First Expired, First Out — on withdrawal, what expires first goes out first. Not the same as FIFO (first stored).

A single goods-receipt booking with its own best-before date. Two deliveries of the same ingredient stay separate.

The legally required self-monitoring system for food businesses — control points, measurements, deviations with corrective action, export for the authority.

A day on which nothing at all is delivered — holidays, bridge day, training day, outing. Applies to a whole facility or to individual care groups.

A single person is not eating on one or more days. Deliberately without a reason: why somebody is missing has no bearing on the quantity, and a reason such as illness would be health data under Art. 9 GDPR.

The monthly summary of meals delivered per facility — the basis for invoicing. It is sent for approval and, without an objection, counts as approved after a deadline.

How detailed the statement is: day only, day × portion group (default) or day × dish × portion group. Set in the contract.

A price for a particular combination — “school child, lunch, from 1 Sep”, for instance. The most specific matching rule wins; if none applies, the contract’s flat rate applies, otherwise the kitchen’s standard price.

An end customer with no facility in between — a meals-on-wheels subscription, for instance. Managed in the organisation area.

An organisation in CateringOS — a kitchen or a facility/provider. One tenant’s data is not visible to other tenants.

Determines which application someone lands in: kitchen, facility or parent portal.

Determines what they may do there — per resource: view, create, edit, archive. Several roles are possible; the union applies.

Restricts an account to a part of the structure — one unit and everything below it.