Ce contenu n’est pas encore disponible dans votre langue.
Overview
:::info The Recipes module is a standalone module and is required by the Calculation & Inventory Management module. When both modules are active, recipes can be built directly from the goods master and drive automatic allergen propagation, cost calculation, and POS article population. :::
The Recipes module provides a structured, team-shared recipe library for kitchen and bar — covering everything from cocktails to plated dishes. Recipes are built with step-by-step preparation instructions, photos per step, plating hints, mise-en-place lists, and equipment requirements. They are stored in a shared directory with role-based read and write access, searchable by name, ingredient, or tag, and linked directly to POS articles and the KDS so that staff always work from the current, approved version. All recipe data is tenant-scoped.
Core Recipes Features
Feature | Description |
Recipe creation | Create recipes manually or — when the Calculation & Inventory Management module is active — build them directly from the goods master with quantities and units |
Recipe types | Distinct recipe types for Food, Cocktail, and (future) Barista/Coffee — type-specific fields (glassware, garnish, ice type) appear only where relevant |
Structured preparation steps | Step-by-step instructions with per-step timing and timers — no free-text block |
Per-step photos | A photo or image can be attached to each preparation step — visual guidance especially valuable for temporary staff and new hires |
Plating & presentation notes | Separate plating/garnish section distinct from preparation steps — documents the expected final appearance for consistent service |
Mise-en-place list | Dedicated mise-en-place section for prep items that must be ready before service — kept separate from the live preparation steps |
Equipment list | Required equipment and specialist tools documented per recipe (e.g. sous-vide circulator, specific glassware) — supports kitchen planning and onboarding |
Allergen management | Allergens entered manually or, when the Calculation module is active, propagated automatically from linked goods |
POS article link | Linking a recipe to a POS article triggers automatic allergen updates on the article whenever the recipe changes |
KDS integration | When a linked POS article is ordered, the recipe is accessible directly on the KDS ticket — kitchen always has the current version at hand |
Bond-printer recipe print | Per recipe: configurable to auto-print the recipe on the relevant receipt printer when the linked POS article is ordered — for kitchens without KDS |
Allergen highlight on KDS | If a guest has allergies stored (via CRM guest profile or session-level entry), allergen warnings are prominently highlighted on the KDS ticket for the affected recipe |
Shared recipe directory | All recipes are stored in a shared team directory with folders and sub-folders; individual users are granted read or write access per folder |
Version history | Every change to a recipe's content (instructions, photos, plating notes) is versioned with a timestamp and the name of the editor — independent of calculation versioning |
Approval workflow | Optional: recipe changes require sign-off from an authorized user (e.g. Head Chef) before the updated version becomes live on the KDS |
Tags & categories | Recipes tagged with dietary attributes (vegan, vegetarian, gluten-free), operational labels (Signature Dish, seasonal), and custom categories — used as filters in the shared directory |
Full-text search | Search the entire recipe library by name, ingredient, or tag |
Recipe duplication | Any recipe can be duplicated as a starting point for a variant — e.g. "Burger" → "Burger Vegan" — without affecting the original |
Branded recipe sheet export | Export individual recipes as a branded PDF sheet |
Training bundle export | Export multiple recipes as a single bundled PDF — e.g. an onboarding recipe book for new staff; integrates with the HR Onboarding Checklist |
Multilingual recipe sheets | Recipe sheet exports available in multiple languages (DE / EN / further languages) — relevant for international kitchen teams |
Daily Menu integration | The shared dish library is used by both the Recipes module and the Daily Menu module — no duplicate maintenance required |
Allergen print configuration | Receipt printer templates for linked articles can be configured to include allergen notices on the guest receipt — independently of whether the recipe itself is printed |
Recipe Types & Type-Specific Fields
Recipes are created with a type that controls which fields are shown:
Type | Type-specific fields |
|---|---|
Food | Plating notes, mise-en-place list, equipment list |
Cocktail | Glassware specification, garnish field, ice type and quantity |
Barista | (Planned — type-specific fields to be defined) |
Fields that are not relevant to a recipe type are hidden — the form stays clean and does not show cocktail-specific fields on a food recipe or vice versa.
Recipe Structure
Preparation Steps
Each recipe is built from an ordered list of preparation steps. Every step has:
A description of the action
An optional time duration or active timer (e.g. "Reduce for 8 minutes")
An optional photo or image for visual guidance
Steps can be reordered at any time. The structured format prevents the recipe from degrading into an unstructured text block and makes it directly usable on the KDS without reformatting.
Mise-en-Place List
The mise-en-place section is kept entirely separate from the preparation steps. It lists everything that must be prepared or portioned before service begins — stocks reduced, garnishes prepped, proteins tempered. This separation reflects actual kitchen workflow and prevents the live steps from being cluttered with pre-service prep.
Plating & Presentation Notes
A dedicated plating section documents how the finished dish or cocktail should look when it leaves the pass — garnish placement, sauce application, glassware fill level. This is separate from the preparation steps and from the mise-en-place list. It is the reference for visual consistency across shifts and staff.
Equipment List
Each recipe carries an explicit list of required equipment and specialist tools. This allows kitchen managers to plan procurement, identify bottlenecks, and include equipment checks in onboarding checklists.
Allergen Management
Manual Entry
Allergens can be entered directly on the recipe. All standard EU allergen groups are supported.
Automatic Propagation (requires Calculation & Inventory Management module)
When the Calculation module is active:
Allergens flow from goods → recipe → linked POS article automatically
Any goods-level allergen change propagates through to the POS article without manual steps
The link between recipe and POS article is the single source of truth for allergen data on the menu
Allergen Highlight on the KDS
If a guest has allergen information on file — stored either in their CRM guest profile or entered at the table session level — the KDS highlights the relevant allergen warnings prominently on any affected recipe ticket. This gives kitchen staff an immediate, unmissable alert before preparing the dish.
Allergen Notices on Receipt Printer
Allergen data can be included in the configured print template for the guest receipt — independently of whether the recipe itself is printed. This is configured per article and per printer in the print template settings.
Shared Recipe Directory
Team Access & Permissions
All recipes are stored in a shared directory that is visible to the entire team. The directory supports folders and sub-folders for organizing recipes by section (kitchen, bar, pastry, etc.), occasion, or any internal structure.
Access is controlled per folder:
Access level | Capability |
|---|---|
Read | View recipe, view preparation steps, view photos |
Write | Create, edit, and delete recipes in the folder |
Permissions are assigned per user, allowing operators to give bar staff write access to the cocktail folder while restricting them to read-only on kitchen recipes.
Full-Text Search
The recipe directory is fully searchable across all recipes — by dish name, any ingredient listed, or any tag assigned. Search results update as the user types.
Tags & Filters
Tags mark dietary attributes (vegan, vegetarian, gluten-free), operational labels (Signature Dish, seasonal, event-only), and any custom category the team defines. Tags are used as filter criteria in the shared directory — a bar manager can filter to show only Signature cocktails, a head chef to show only vegan mains.
POS Article & KDS Integration
POS Article Link
A recipe is linked to a POS article in the article master. Once linked:
The recipe's allergen data is pushed to the POS article automatically
Any future change to the recipe's allergens updates the article without manual action
The link is the authoritative source of allergen data for that article
Recipe on the KDS
When a linked POS article is ordered and the KDS module is active, the recipe is accessible directly from the KDS ticket. Kitchen staff can open the current recipe — with steps, photos, and plating notes — without leaving the KDS display.
Recipe Print on Bon Printer
For operations without a KDS, individual recipes can be configured to auto-print on the relevant receipt printer when the linked POS article is ordered. This is configured per recipe and activates only when the KDS module is not booked.
Version History & Approval Workflow
Version History
Every content change to a recipe — preparation steps, photos, plating notes, mise-en-place list, equipment list — is recorded with:
Timestamp of the change
Name of the user who made the change
A diff of what changed
The version history is independent of the Calculation module's recipe versioning (which tracks ingredient cost changes). Recipe version history tracks operational content and preparation instructions.
Approval Workflow
An optional approval workflow can be activated per recipe or per folder. When active:
A user with write access edits the recipe and submits the change for review
An authorized approver (e.g. Head Chef, Bar Manager) is notified
The approver reviews the change and either approves or rejects it
Only approved versions are pushed live to the KDS and visible to staff
This ensures that no unreviewed recipe change goes live during service without a senior sign-off.
Export & Training Materials
Branded Recipe Sheet
Any recipe can be exported as a branded PDF sheet — formatted with the tenant's corporate design. Suitable for printing and posting in the kitchen or bar area.
Training Bundle Export
Multiple recipes can be selected and exported as a single bundled PDF — for example, an onboarding recipe book for a new employee cohort. This bundle can be referenced in the HR Onboarding Checklist, creating a direct link between recipe content and staff onboarding.
Multilingual Recipe Sheets
Recipe sheets can be exported in multiple languages (German, English, and additional languages). This is relevant for international kitchen and bar teams where not all staff read the primary operating language fluently.
Daily Menu Integration
The dish library used by the Daily Menu module and the recipe library in the Recipes module share the same underlying data. A dish defined in the Recipes module appears in the Daily Menu dish picker without re-entry — one record, two use cases.
Dashboard Metrics
The Recipes module provides always-current key figures at a glance:
Total recipes in the shared directory
Recipes with pending approval (awaiting sign-off before going live)
Recipes modified in the last 7 days and by whom
Recipes with no linked POS article (allergen data not yet propagated)
Most recently created or updated recipes per type (Food / Cocktail)
:::danger Pricing
DO NOT QUOTE FROM THIS PAGE Quotable pricing information can be found only at Pricing & Packages :::
:::info Known Issues