Airline special meal management that catches every allergen change before the trays are loaded
Every allergen change caught before loading, and every meal traced from booking to seat.
See one case, screen by screen ↓Airline special meal management is the work of carrying every special meal request and its allergen data from the booking to the galley and the seat: the SPML and other special meal codes, the caterer's order and recipe, the load plan and the crew. Special Meal and Allergen Management covers that, and the inflight allergen management that goes with it, with eight agents that read the bookings, caterer orders, allergen sheets and change notices, catch a break before the trays are loaded, propose a safe substitute and check it twice, and write the purser's special meal list. The inflight services manager approves every change to a passenger's meal.
How to choose AI for airlines: a buyer's guide to agentic AI solutions →
Updated
A passenger who books a sesame-free meal is trusting five hand-offs owned by different teams and companies: the special service request in the booking, the order to the caterer, the caterer's recipe and its allergen matrix, the galley position in the load plan, and the purser who serves it. A food allergy outside the IATA special meal codes rides as free text on an SPML request, or sits on a loyalty profile that never reaches the booking. Nobody sees the whole chain for one passenger.
So the chain breaks quietly. A caterer swaps the bread in a shared tray template and its product change notice speaks only of the standard tray. A flight cancels and the special meal does not follow the rebooking. The aircraft changes and the tray moves to another galley, or the gate moves the passenger after the special meal list is printed. The first person to notice is the passenger, and customer relations then spends days rebuilding the record from five systems.
Estimated split for one caterer change notice on a hub's departures and one meal complaint, by hand and with the solution.
Eight agents follow every special meal from booking to seat, catch caterer changes and check each other; the inflight manager approves.
Thursday, October 15, Chicago O'Hare. Corvane Airways' caterer changes tonight's dinner roll to a sesame brioche, nine hours before CV 63 leaves for London with a sesame-allergic passenger in 14A. Here is how airline special meal management works with the agents, screen by screen, in the working solution.
Dana opens Today to a summary from the agents: they followed all 6,318 special meals on 1,112 flights from booking to galley, three caterer changes touched 11 allergen meals and 4 are already fixed. Five items wait for her, each with the agents' proposal: the sesame swap at Lakeshore, a kosher meal from a canceled flight, a late gluten-free request, a reaction on board and an aircraft change to Haneda.
“Agents propose and explain; a named person approves every change to a passenger's meal.”
Lakeshore Flight Kitchens sends PCN-LFK-2291: on templates PY-D-14 and Y-D-09, the BR-110 plain soft roll becomes a BR-214 sesame brioche roll from 15:00, October 15–18, during bakery line 2 maintenance. The Recipe watcher reads it three minutes later, compares the two allergen sheets — sesame and eggs added — and follows the change through the tray templates. Standard trays on 61 flights need no action; 7 sesame meals on 4 flights do.
“The notice speaks of the standard tray. The agent found that allergen trays inherit the template bread; nobody at the caterer flagged them.”
Iris Halloran, Premium, booking QX7RTM, asked for a special service request, SSR SPML “NO SESAME”, in the Corvane app on September 28. The trace shows five links, each with its source: booked, ordered on Lakeshore's final figures at 12:40, the recipe changed by the caterer, galley G2 cart 3 on the 787-9 N827CV, and seat 14A, where the briefing is held until approval.
“We propose BR-118 plain sourdough roll from the same kitchen, checked twice. Lakeshore needs your answer by 12:00.”
The Second check re-reads each of the 7 bookings and profiles against the substitute's sheet, its may-contain notes and its shared lines. Six pass. Lena Fischer in 44D on CV 81 to Narita declared sesame and is celiac, and the sourdough contains wheat. It rejects BR-118 for her seat, and the finder proposes BR-305, a gluten-free roll with no seeds from Lakeshore's sealed allergen room A.
The Second check can block a proposal; it cannot approve one.
The Substitute finder proposed BR-118 plain sourdough from Lakeshore's approved list: allergen sheet AS-LFK-BR118 rev 4, bakery line 3 with no sesame on the line, 140 in stock. Dana asks the agents why it is safe. The answer cites the sheet and the airline's own rules: same caterer, current sheet, and nothing the passenger declared is in it or may be.
Second check: “It is made on bakery line 3 — no sesame on the line. Iris declared sesame, so it meets rule §4.2: nothing the passenger declared is in it or may be.”
On Approvals, Dana selects the seven meals from the notice and approves them together with reason code SUB-01, “Same caterer, allergen-free component”, signing with her passkey. One signature records a separate decision for each meal. The Substitute finder then tells Lakeshore which 7 trays carry the approved roll.
“Nothing changes a passenger's meal until a person approves, edits or rejects it with a reason.”
CV 63 carries 23 special meals, 8 with an allergen, across galleys G1 to G4. 14A and 31C now show Fixed. The Request reader has two more for the team before the briefing: 22E wrote “no nuts” without saying which, so a one-line question is drafted for approval, and 40H has a milk allergy on the loyalty profile only, so adding it to the booking is proposed.
The Request reader never drops a free-text allergy, and never contacts a passenger without approval.
With the substitutes approved, the briefing goes to 11 crew tablets: the two changed meals first, then the 6 allergen meals, then the other 15. The line for 14A reads “Halloran — sesame allergy (severe). Roll changed to plain sourdough roll. Serve first, G2 · cart 3. Confirm at seat.” The crew sees seat, name, allergen and what changed, nothing more from the passenger's record.
Briefing writer: “I never tell the crew about a fix before a person has approved it.”
The crew taps “Served” on the tablet at the seat, or picks a reason. On Wednesday 6,071 of 6,104 special meals were confirmed at the seat, 99.5%. Of the 33 not served, 14 passengers did not fly and 19 were Corvane's to fix: 9 asked after the caterer's cut-off, 6 loaded short by the caterer and 4 seat changes not followed. Each has a follow-up drafted.
The Delivery confirmer never marks a meal delivered without the crew's tap or the purser's note.
Complaint CR-20418: Nadia Corwin's gluten-free meal on CV 44 from London was not served. The Case handler has already assembled the chain — booked, ordered, recipe and galley clear, seat broke — and found why: the gate moved her from 23C to 31A at 10:41 after the crew list was printed. It drafts a plain apology with 15,000 miles, inside the Customer Relations limit of 15,000 miles or $150, for a person to approve and send.
Case handler: “Corvane's fault, not the caterer's.”
The same sesame-free meal, seen by five of the people who carry it from booking to seat — what their day looked like, and what it looks like now.
Eight agents follow every special meal from booking to seat, catch caterer changes and check each other; the inflight manager approves.
Reads each booking's special service requests — SSR SPML and the other IATA special meal codes — the free text and the loyalty allergy profile; records the meal code and the declared allergens; flags unclear text such as “no nuts pls”.
Checks each request reached the right caterer's order at the right count before the cut-off, and follows rebookings, cancellations, seat changes and aircraft changes into new galley positions.
Reads caterer specifications, allergen matrices and product change notices from portals, email and PDF, and follows a component change through the tray templates to every passenger whose declared allergen it touches.
Proposes a safe substitute from the same caterer's approved list with a current allergen sheet, and checks stock and the caterer's deadline.
Re-reads every proposal against the passenger's full allergen list, may-contain notes and shared production lines, and argues against it.
Writes the purser's briefing — seat, name, allergen, what changed and where the tray is, one line per seat, changes first — and sends it to the crew tablets.
Matches the crew's taps at the seat and the galley loading checks to every request, and finds what was not served and why.
Assembles a meal's whole record for a complaint or a reaction on board, drafts the reply and goodwill within policy, and drafts the safety report.
Approves every substitute; Catering Quality accepts allergen sheets; Customer Relations signs replies. The agents propose; a named person decides.
Ask about a flight, a seat, a caterer or a change — or tell the agents what to do. Every answer points to its source, and nothing is sent until a person says so.
What changed on CV 63 tonight?
Lakeshore swapped tonight's dinner bread for a sesame brioche at 09:38. Two passengers on CV 63 declared sesame: 14A Iris Halloran and 31C Adrian Moss. The agents propose BR-118 plain sourdough, checked twice.
Why is sourdough safe for 14A?
BR-118 plain sourdough roll contains wheat and declares no “may contain”. It is made on bakery line 3, with no sesame on the line. Iris declared sesame, so it meets rule §4.2: nothing the passenger declared is in it or may be. Same caterer, current sheet, 140 in stock (§4.1).
Why did the second check change 44D on CV 81?
Lena Fischer declared sesame and is celiac. The first proposal, BR-118 sourdough, contains wheat. The Second check rejected it and the finder proposed BR-305, gluten-free and made in a sealed allergen room.
Tell Lakeshore to confirm by 11:00
Drafted for Lakeshore's portal: “Please confirm that the PY-ALG and Y-ALG trays for CV 81, CV 1406, CV 57 and CV 63 tonight will carry BR-118 (and BR-305 for CV 81 seat 44D) instead of BR-214, by 11:00 CDT.” I will not send it until you say so.
13 screens from the working solution, on its sample data. Pick one to see it large.
The clocks and rules the agents follow are the airline's settings, kept as a versioned rulebook with an owner and on the audit trail.
| Setting | Default | Choose from |
|---|---|---|
| Caterer final figures | 6 hours before departure | Hours before departure, set per airline |
| Kosher and medical meals | 48 hours before departure | Hours before departure |
| Allergen meal lock | 3 hours before departure | Hours before departure |
| Briefing sent / purser acknowledgment due | 90 / 45 minutes before departure | Minutes before departure |
| A component that “may contain” a declared allergen | Never used | Never used · A person decides |
| A component made on a shared line | A person decides | A person decides · Never used |
| A substitute from another caterer | Inflight Services Manager only | Inflight Services Manager only · Never |
| Customer Relations goodwill limit | 15,000 miles | Miles; above it, the Inflight Services Manager approves |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (FARE food allergy facts and statistics — 33 million Americans; FASTER Act of 2021 — sesame the ninth major US food allergen from January 1, 2023; PAX International with dnata, April 2024 — 53 special-meal names on 39 codes). Corvane Airways, its caterers, flights and the people named on this page are fictional — characters and sample data in the working solution.
Airline special meal management is the work of carrying every special meal request and its allergen data from the booking to the galley and the seat: the SPML and other special meal codes, the caterer's order and recipe, the load plan and the crew. Special Meal and Allergen Management covers that, and the inflight allergen management that goes with it, with eight agents that read the bookings, caterer orders, allergen sheets and change notices, catch a break before the trays are loaded, propose a safe substitute and check it twice, and write the purser's special meal list. The inflight services manager approves every change to a passenger's meal.
The Recipe watcher reads every specification, allergen sheet and product change notice from the caterers, in portals, email and PDF, and follows a component change through the tray templates to the passengers whose declared allergens it touches. In the working solution it read a caterer product change notice for a sesame brioche three minutes after it arrived and found 7 sesame meals on 4 flights, although the notice spoke only of the standard tray.
SPML is the IATA special meal code a passenger uses when no standard code fits, with the details in free text — often an allergy such as “NO SESAME”. The Request reader reads each booking's special service requests, free text and the loyalty allergy profile, and records the meal code and the declared allergens. It never drops a free-text allergy: unclear text such as “no nuts” is treated as the stricter reading and a question to the passenger is drafted for a person to approve, and an allergy on the loyalty profile but missing from the booking is flagged.
The Order checker carries the special meals to the new flight and re-maps galley positions on an aircraft change, then re-sends the briefing. It asks a person only where a cut-off or a partner stands in the way — for example, a kosher meal past the caterer's 48-hour cut-off, with one of two sealed reserve kosher meals held at JFK proposed instead.
A named person does. The agents propose and explain; a named person approves, edits or rejects every substitute, late-request option, allergen sheet, reply and safety report with a reason code and an e-signature. The agents never change a meal, contact a passenger, order after a cut-off or send a crew briefing without approval.
Every complaint or reaction opens with the meal's whole record already assembled — booking, order, tray, galley, seat and the crew's note — and the link that broke. The Case handler drafts the reply and goodwill within policy and drafts the safety report for a reaction; a person approves before anything is sent.
Yes. Caterer final figures, kosher and medical cut-offs, the allergen meal lock, briefing and acknowledgment clocks, the may-contain and shared-line policy, substitutes from another caterer and the goodwill limit are all settings, kept as a versioned rulebook on the audit trail.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your special meal rules, caterer specifications and allergen sheets, and a sample of past bookings and notices — and it goes live once every quality gate has passed. We will walk you through it on your own special meals first.
Every caterer line checked against what was loaded, and every missed penalty claimed.
1-min demoGalley PlanningEvery galley loaded to spec: no cabin short of a meal, no weight flown for nothing.
1-min demoCatering Demand ForecastingMeals ordered for the passengers who board, not the ones booked, and no cabin left short.
1-min demoWe'll run Special Meal and Allergen Management on a sample of your own bookings, caterer notices and allergen sheets.