Operations · 7 min read
Designing Restaurant Delivery Orders for Allergy Requests
Write restaurant delivery app food allergy instructions that connect guest requests with kitchen checks, clear tickets, and packaging reviews.
Key takeaways
- An allergy note isn't confirmation that a request can be accommodated.
- Guests should tell staff about allergies, and staff should confirm every order with the kitchen.
- Don't release an order with unresolved ingredient, preparation, or packing questions.
Design delivery allergy orders around a written request, direct guest communication, and kitchen confirmation before preparation begins. Guests should tell staff about allergies, and staff should confirm every order with the kitchen. Your workflow should carry that confirmed request through the ticket, preparation, packaging, and pickup, with a clear stopping point when something can't be verified.
What should restaurant delivery app food allergy instructions say?
Start with instructions that explain what the guest needs to do and what your team needs to check. A comment box shouldn't be treated as confirmation that the restaurant can accommodate a request.
Food allergies deserve a defined process. A research review describes their substantial health and quality-of-life burden across age groups. That context supports treating an allergy request as a service responsibility, rather than an ordinary preference modifier. Read the food allergy research review.
Suggested wording for your delivery menu:
Have a food allergy? Please call the restaurant to discuss it before ordering, and identify the allergy and affected dish in your order instructions. Our staff will check ingredients and preparation with the kitchen. An order note alone doesn't confirm that we can accommodate your request.
Adapt that message to a contact method your team actually monitors. Don't promise a callback if nobody owns the phone during the rush.
Ask guests to identify the specific food they're avoiding. A note such as “allergy, no sauce” leaves the team with unanswered questions. “Milk allergy, chicken bowl for Alex” gives staff a starting point, but the kitchen still needs to review the whole dish.
Keep the message visible near ordering information. Don't bury the only allergy instructions in a long restaurant description.
How do you check whether allergy notes reach the kitchen?
Before relying on any delivery ordering channel, trace a test request from checkout to the station that prepares the food. Use an authorized test order and inspect what your team actually receives.
Check these points:
- Can the guest enter an allergy request for a specific dish?
- Does the full note appear on the restaurant's order screen?
- Does it print or display on the kitchen ticket without being cut off?
- Can the expediter see the same information during packing?
- Who contacts the guest if clarification is needed?
Include an order with several dishes and different modifications. That's where you can see whether a note remains attached to the intended item or becomes an ambiguous instruction for the whole bag.
Document any gap and assign a manual step to cover it. For example, if an order-level note doesn't appear on individual station tickets, require the shift lead to communicate it and obtain a read-back before preparation.
Repeat the check after changing printers, ticket layouts, or ordering settings. Your process should depend on an observed result, not an assumption about what the app sends.
Who should confirm a delivery allergy request?
Assign one person per shift to own the request from receipt through release. During a busy service, that might be the manager or expediter. Name a backup so the process doesn't disappear when the lead steps away.
Use a simple sequence:
| Stage | Required action | Reason to pause |
|---|---|---|
| Request received | Identify the allergy, affected dish, and guest contact route | The note is unclear |
| Kitchen review | Check current ingredients and preparation conditions | An ingredient or method can't be verified |
| Guest conversation | Explain the kitchen's findings and any proposed change | The guest hasn't agreed to the change |
| Preparation release | Record the confirmed instructions on the ticket | The ticket doesn't match the conversation |
| Packing release | Match the dish, label, and order | Something differs from the confirmed request |
Consider this service scenario: at 7:10 p.m., a four-item delivery order arrives with “sesame allergy” in the general notes. The shift lead doesn't guess which diner or dish it concerns. They contact the guest, identify the affected item, and ask the kitchen to review it.
A useful opening is: “I'll check with the kitchen. Which dish is for the person with the sesame allergy?”
If the guest can't be reached and the request remains unclear, keep the affected item on hold. Follow your platform's process for resolving or canceling the order instead of sending an unconfirmed substitution.
Give staff a consistent approach to these conversations with your guide to handling guest allergy questions.
What should chefs check before accepting an allergy modification?
Build the review around the complete dish. Ask the chef to check the current recipe, purchased components, cooking oils, and preparation equipment. Include the sauce, garnish, dressing, and any side packed with the order.
Don't let “leave it off” become an automatic approval. First establish whether the ingredient is added separately, already mixed into a component, or involved elsewhere in preparation.
For example, imagine a guest requests a bowl without its finishing sauce. The chef should still check the marinade and base ingredients before confirming the modification. Removing one visible component doesn't answer every ingredient question.
Review shared fryers, grills, and prep stations separately from recipe ingredients. Make the equipment check explicit on your review sheet so staff don't stop after reading the recipe.
Use your written cross-contact procedures for preparation, including appropriate equipment, cleaning, handwashing, and glove changes. Don't describe a quick wipe or a glove change as proof that every concern has been addressed. A restaurant cross-contact checklist can help structure the team's review.
When a supplier label or preparation detail isn't available, say so. “We can't verify that ingredient tonight” gives the guest information they need. Guessing creates an answer your team can't support.
How should allergy orders be flagged and packaged?
Make the allergy visible in plain text wherever the order is handled. Don't rely only on a color, an abbreviation, or someone remembering a verbal message.
A hypothetical ticket could read:
ALLERGY: MILK. Alex's chicken bowl. Hold for kitchen review. Check all components and preparation before release.
After review, record the specific confirmed modification and who checked it. Keep the original allergy visible. A change from “milk allergy” to “no dressing” would lose the reason for the request.
For more ticket examples, use how to flag allergy tickets and kitchen chits.
At packing, give one person responsibility for the final comparison:
- Match the finished item to the confirmed ticket.
- Check sides, garnishes, sauces, and any automatic additions.
- Package the affected dish separately from other dishes and label it clearly.
- Match the containers to the correct order before closing the bag.
Use a guest name or item identifier to distinguish similar containers. A label should identify the request and dish without making a claim the restaurant can't support.
If an unexpected garnish appears at the pass, stop the item and return the issue to the kitchen lead. Don't let the packer decide that removing the garnish resolves the concern.
Keep sealed orders together for handoff. Ingredient questions and changes belong with restaurant staff, rather than becoming decisions for the delivery driver.
How can allergen menu information support the workflow?
Keep delivery descriptions aligned with the recipes and supplier information your kitchen uses. Assign someone to review affected descriptions whenever a component changes. Your process for updating allergen information after recipe or supplier changes should include every ordering channel you maintain.
Menu information helps staff prepare for a conversation, but it doesn't confirm an individual delivery order. Keep that confirmation step in your service procedure.
For restaurants that also want dine-in guests to filter the menu themselves, Can I Dine?™ is one practical option. The restaurant uploads its own menu, reviews dishes, ingredients, cooking oils, and shared fryer, grill, or prep station groups before publishing. Guests scan the restaurant's QR code at the table and see results sorted into suggested, may need a modification, and avoid.
The product tour shows that menu workflow. It organizes restaurant-provided information; it doesn't inspect kitchens or replace staff confirmation. Guests still tell staff about allergies, and staff confirm every order with the kitchen. Keep delivery request handling as an explicit operational process.
For disclosure requirements, consult the restaurant allergy laws by state resource when reviewing your menus and packaging.
How do you train the team to handle allergy orders during a rush?
Put the workflow into a short written procedure and rehearse it before service. Include who owns the request, who reviews ingredients, how staff contact the guest, and who releases the packed order.
Run a practical drill: two identical bowls, one allergy request, an unavailable ingredient label, and a driver waiting at pickup. Ask each team member to show their next action. The missing label should trigger a pause and clarification, even when the line is in the weeds.
Check whether staff can explain uncertainty without making promises. “I'll check with the kitchen” should lead to a real check and a specific response.
Review missed notes, remakes, and packing discrepancies with the team. Look for the point where information was lost, then change that step. Before the next rush, everyone should know who can stop an allergy order and what must be confirmed before it leaves.
Frequently asked questions
What should restaurant delivery app food allergy instructions include?
Include a request to contact the restaurant, identify the specific allergy, and name the affected dish. Explain that entering a note doesn't confirm the restaurant can accommodate it. Guests should tell staff about allergies, and staff should confirm ingredients and preparation with the kitchen before releasing the order for preparation.
What should a restaurant do if a delivery allergy note is unclear?
Put the affected item on hold and have the assigned staff member contact the guest. Clarify the allergy and which dish it concerns, then confirm with the kitchen. If the guest can't be reached or the kitchen can't verify a necessary detail, follow the ordering channel's resolution or cancellation process instead of guessing.
How should restaurants label delivery orders with allergy requests?
Use plain text to identify the allergy and affected dish on the ticket. Record the kitchen-confirmed modification and distinguish the finished container with a guest name or item identifier. Don't use labels that promise an outcome. The packer should compare the dish, accompanying items, and label against the confirmed ticket before closing the bag.
Does removing an ingredient complete an allergy request?
No. Staff shouldn't assume that removing a visible ingredient answers the whole request. The kitchen needs to review the current recipe, components, cooking oils, and relevant shared equipment before confirming what it can do. Guests should tell staff about allergies, and staff should explain any uncertainty or preparation limitation before proceeding.
How can managers test their delivery allergy workflow?
Trace an authorized test order from the guest's instructions through the restaurant screen, kitchen ticket, preparation review, and packing check. Include multiple dishes so you can check whether the request stays attached to the right item. Assign responsibility for any manual handoff, and repeat the check when ordering settings or ticket layouts change.
Sources
Can I Dine?™ organizes the information a restaurant provides so guests and staff can have a clearer conversation. It doesn't inspect kitchens or certify allergen-free preparation. Always tell your server about your allergies before ordering.