Integration
TenKites integration
Creventa syncs your menu data from TenKites, including modifiers and the allergens held against them. Once your menus are set up, a guest who declares an allergy is not offered the dishes that contain it.
Talk to us about this integration
Creventa integrates with TenKites. Menu data, including modifiers and the allergens held against them, syncs from TenKites using an API key set per venue in Venue Configuration. With menus set up correctly, items containing an allergen a guest has declared are disabled before that guest can order them, and a standard menu and a gluten free menu can run on the same booking.
What connects
Menu data flows from TenKites into Creventa, including modifiers and the allergen and dietary information held against each item. You set a TenKites API key per venue in Venue Configuration, and your menus stay in step without anyone retyping them.
Allergen options are removed, not just flagged
With menus set up correctly, Creventa uses the allergen data synced from TenKites to disable menu items a guest has declared an allergy to, with an explanation of why the option is unavailable. The guest cannot select it. That is a different thing from printing a warning beside a dish and hoping it is read.
Modifiers carry their own allergens and dietaries, so a choice inside a dish is checked the same way the dish itself is.
Standard and gluten free menus together
A standard menu and a gluten free menu can run alongside each other on the same booking. Both are counted correctly in every report, and each has its own section on the chef sheet and the guest grid, so the kitchen sees the split without working it out.
Why venues ask for this
Allergen data is usually maintained in one system and used in another. Every time it is copied across, it can be mistyped, and the consequence lands on the plate. Syncing from TenKites removes the copying step, so what a guest sees when they order is what your menu team maintains.
Related workflows
Guest pre-orders, allergen and dietary tracking, chef reports and the food pass.
TenKites is a third party platform. More about it on the TenKites website.
Frequently asked questions
What is TenKites?
TenKites is a menu and allergen management platform used by hospitality operators to hold dish, recipe and allergen data in one place.
How does Creventa work with TenKites?
Creventa syncs menu data from TenKites, including modifiers and their allergens, using a TenKites API key set per venue in Venue Configuration.
Can a guest order a dish containing an allergen they have declared?
Not from the menu. With menus set up correctly, items containing a declared allergen are disabled at the point of ordering, with an explanation of why. It supports your kitchen and service checks rather than replacing them.
Does it support gluten free menus?
Yes. A standard menu and a gluten free menu can run on the same booking, counted separately in reports and shown in their own sections on the chef sheet and guest grid.
Do modifiers carry allergen information?
Yes. Modifiers hold their own allergen and dietary data, so a choice within a dish is checked in the same way.
What do we need to set it up?
A TenKites account and an API key, entered per venue in Venue Configuration, plus your menus mapped so the allergen data lines up.