CalcMenu for IT leaders: 5 questions before approval
Recipe management software touches data, integrations and compliance. Here is what a CIO or CISO checks before giving the green light.
When food service becomes an IT topic
Until recently, kitchens bought their own tools: a recipe-card app here, a labelling app there. The problem? These tools now handle sensitive data — customer allergens, dietary profiles, suppliers, costs — and must integrate with the corporate IT stack. The result: the CIO or CISO is always consulted before signing.
Here are the five questions IT rightly asks, and what CalcMenu answers.
Where is data hosted?
For any personal data, and especially health data (diets, allergies, textures), hosting is not just a performance issue. In Switzerland, the nFADP classifies health data as sensitive personal data (art. 5 let. c) and subjects it to strengthened requirements, such as express consent (art. 6 para. 7). In Europe, GDPR (art. 9) strictly regulates health data.
CalcMenu is hosted on certified clouds (AWS ISO 27001 / SOC 2). For modules that process resident health data, Blaze Tray can be deployed on Azure Switzerland North (Zurich), with data encrypted at rest (AES-256) and in transit (TLS 1.3).
Can users sign in with existing accounts?
Creating separate credentials for a kitchen tool is both a security risk and a support burden. CalcMenu supports Microsoft Entra ID (formerly Azure AD) via OIDC, with multi-factor authentication and password policy inherited from the existing Entra tenant. One account, one password policy, automatic deactivation on departure.
What integrations are available?
An isolated tool quickly creates silos. CalcMenu integrates via:
- POS connector to pull sales and refine production forecasts;
- Supplier APIs (Hogashop, etc.) to sync prices and availability;
- NiceLabel for compliant allergen label printing;
- FHIR NutritionOrder (Blaze Tray v2+) to receive diet orders from care software.
What is the audit trail?
For sanitary inspections and internal audits, knowing who changed what and when is essential. CalcMenu keeps a timestamped history of recipe, menu and — in Blaze Tray — resident profile and diet changes. This traceability is native, not reconstructed after the fact.
What SLA and support are offered?
A tool used in the kitchen cannot be down at lunch time. CalcMenu offers a 99.5 % availability SLA, email/phone support on business days, and go-live standby for critical launches. Data remains exportable at any time (JSON/CSV/PDF), with no vendor lock-in.
The right reflex: a security review upfront
A CIO does not need to become a food-service expert. They need to confirm that the software meets corporate standards for security, hosting and data governance. With the right documented answers, the tool moves from “kitchen project” to “IT-approved application”.
Does your IT team need to validate a CalcMenu project? Book a free 15-minute technical call — no commitment: Schedule a call.
Related sectors
Comments
Comments coming soon.