Outcome and prerequisites
When a diner declares a serious nut allergy or dietary need during booking, the goal is to communicate the relevant requirement safely to the appropriate team without compromising privacy. This does not automatically guarantee allergen-free food.
1. Collect the declaration through a structured field
Rezervem's supported allergy/dietary flow uses structured `DietaryNeedsJson` data for relevant channels. Reported allergens, severe reactions and intolerances should not be treated like unrestricted staff notes. Verify the specific field and venue configuration.
Legacy free-text `Allergens` information or a booking note should not be assumed to be complete, current structured dietary data.
2. Verify explicit consent and other processing conditions
The relevant Rezervem API workflow uses t36 consent records for health-related allergen data and t37 for dietary preferences that may reveal beliefs. Missing valid consent or other applicable conditions must activate the intended safeguards.
A privacy notice, consent and booking contract are different concepts; a booking does not permit unrestricted health-data processing or marketing. Apply current Turkish KVKK requirements.
3. Share only what the service team needs
Before service, only authorised hosts and the relevant kitchen or service team should access information needed for the task. Do not circulate medical diagnoses, speculative notes or irrelevant family details.
Confirm whether the requirement belongs to the booking holder, a child or another diner, and whether it changed before service.
4. Confirm the kitchen's actual ability to respond
A 'gluten-free' request does not by itself mean the kitchen can prevent cross-contact. Kitchen staff must verify ingredients, equipment, preparation areas and alternatives.
Be transparent where a requirement cannot be safely fulfilled. Do not make medical diagnoses on behalf of guests.
5. Handle changes and withdrawal of consent
Guests may update some booking notes or permitted tags through supported screens. Updates or deletion of sensitive dietary declarations must use their specific secure data-management and consent workflow, not an ordinary staff note.
Pre-service dietary request checklist
Use one clear handoff across teams.
- Was the requirement stored against the correct reservation and channel?
- Have relevant consent or processing conditions and access rights been verified?
- Is it clear which diner the requirement concerns?
- Has the kitchen assessed preparation and cross-contact risk?
- Have actual options and limitations been explained to the guest?
- Did the team review any booking or dietary changes?
- Was unnecessary reuse and retention of personal information avoided?
How Rezervem supports the workflow
Rezervem API keeps allergy/dietary declarations and dedicated consent records in a separate flow. Manager supports booking operations; Experience presents catalogue information but is not medical verification or a food-safety guarantee.
See tasting menu allergen information for public menu communication; this guide concerns secure booking-to-service handoff.
Frequently asked questions
Is an allergy declaration an ordinary occasion tag? — No, health-related data requires a separate workflow.
Does gluten-free always mean safe? — No, kitchen conditions must be verified.
What if the guest withdraws consent? — Follow the appropriate processing-stop and deletion/management rules.