CalcMenu
Blog
HospitalityAugust 15, 2026 · 6 min

CalcMenu vs JAMIX: the closest comparison in collective catering

Two long-established kitchen management systems aimed at almost the same buyer — schools, hospitals, care homes, universities. They overlap more than any other pair in this category, so the decision comes down to volume patterns, variant depth and language.

The short version

This is the closest comparison in the category, and any honest answer has to start there. JAMIX and CalcMenu have both been at this for around three decades, both sell to schools, hospitals, care homes and universities, and both connect menus to recipes, allergens, nutrition, costing, production and purchasing in one system.

Where they part company is what each optimised for on the way here. JAMIX optimised for cycle menus at institutional volume. CalcMenu optimised for variant depth per meal. Neither is a deficiency; they are different bets about where the difficulty lies.

Where they genuinely overlap

More than anywhere else in this comparison set. Both: menus connected directly to recipes, allergens and nutrition; automatic purchase orders generated from the menu plan; nutritional analysis that can be held against published recommendations; costing; food labels; production sheets; multi-site or chain management.

If a feature checklist is how you are choosing, these two will tie. The decision has to come from somewhere else.

Where JAMIX is stronger

Volume. Over 2,500 kitchens producing more than a million meals a day is not a marketing figure so much as a design constraint, and it shows in how the system handles high-volume cycle menu planning and the reporting around it.

Standards compliance as a named module. Nutritional Recommendations ships as a standard feature alongside Nutrition Analysis, framed exactly as public-sector caterers are asked to demonstrate it. CalcMenu holds menus against published standards too — the DGE-Qualitätsstandard in German clinical catering being the clearest example — so this is a difference in packaging and workflow rather than in whether the capability exists. But if your tender language mirrors a named standard, JAMIX presents against it very cleanly.

Sales and leftovers tracking as a standard module, plus Food Bank and Production Requisitions as options — a module list that reads like a public catering specification because it was built against one.

Strongest fit: schools, universities, military and large public-sector caterers running high-volume cycle menus against published nutritional standards.

Where CalcMenu is stronger

Variant depth. One master recipe carrying diet and IDDSI texture variants as first-class objects that inherit changes from the base. Where an operation’s difficulty is not a thousand identical meals but sixty meals in eleven versions each — a care home, a rehabilitation clinic, a psychiatric unit — this is the structural advantage.

Languages inside the recipe card. Several languages on the same card simultaneously, for brigades that do not share one. This is a Swiss and wider European problem that Nordic-origin products have had less need to solve.

Airline and specialist catering. Airline catering brings requirements — IATA special meal codes, galley and trolley constraints, per-flight manifests — that general collective catering systems are not usually shaped around.

The surrounding stack. FoodOps for ERP-level stock, patient and staff ordering, kitchen labelling and electronic shelf labels all read from the same recipe rather than integrating with it.

Strongest fit: healthcare and care operations with deep per-meal variant requirements, multilingual teams, and a need for the recipe to drive ordering, labelling and stock as well as menus.

The question that usually decides it

Count two numbers about your own operation before the demos.

Meals per day — and versions per meal.

If the first number is very large and the second is small (a school authority producing 8,000 near-identical lunches), the difficulty is volume and cycle planning, and JAMIX was built against exactly that. If the second number is what hurts (a 90-bed care home where every dish exists in a normal, three diet and three texture versions, and the diet list changes with the residents), the difficulty is variant management, and that is what CalcMenu was built against.

Most operations know which number is the painful one the moment they are asked. Ask it before you sit through two feature demos that will otherwise look nearly identical.

Sources

Explore CalcMenu's recipe and menu software for nursing homes to see how it applies to your kitchen.

Comments

Comments coming soon.