Catering Orders That Keep Pace

Orders are built and rekeyed by hand

Counts, meal choices, and special meals are pulled from separate systems and telexed, emailed, or phoned to each caterer, then re-entered on their side. Every handoff is a chance to transpose a number or miss a change.

A moving count means waste — or a delay

Provision for an early estimate and a light flight leaves meals to be thrown away. Come up short, and the fix is a last-minute van trip to the aircraft, with the departure delayed until it arrives. Without a rule that refines the order to who actually checks in, every flight is a guess, with a cost on both sides.

Special and preordered meals slip through

SPMLs, crew meals, and preselected choices are orphaned from the main count. Tracked separately, they go missing in the gap between systems, and a missing meal request is the failure a passenger remembers.

The Catering Plan sets the service every flight should carry — by route, cabin, and service offering — so Orders always builds against the plan of record instead of a rekeyed guess.

Every order line pulls its meal definition and agreed price from Specifications, so the caterer receives an unambiguous order and the amount payable is agreed up front, not argued later.

Orders generates each flight’s order automatically from your planning rules — meal counts drawn from bookings, preorders, and special meal requests — and refines every count as the flight nears departure.

It captures the caterer’s confirmation and final counts, then compares estimates against them, so you can see how accurate each station and rule really is.

The confirmed order becomes the baseline every invoice is checked against, so the quantities and line items you are billed for reflect what the flight actually took, not a supplier’s restatement of them.