53 cards in the blueprint's section Ancillaries, seats and bundles: 43 are in Lean, 11 are open questions and 10 need a business decision.
Each with the number of cards that depend on it, directly or through other cards, most first. Click one to see what it
depends on and what builds on it.
On a given flight, no seat is assigned to two passengers at once. A seat assignment holds a seat and the passenger segment it applies to, and the seat map marks each seat available or occupied. The model checks that a seat request keeps this true when it held before and the seat maps mark no held seat available. Case to check: The seat worked example selects 12B for PAX01 and 12C for PAX02. Nothing in the described rules refuses a request selecting 12B for both on SEG1. A segment flown on two legs with a change of aircraft has two seat maps, so one seat per segment is ambiguous.
Counterexample: two passengers on SEG1 hold no seats, and the seat map marks 12B available. One request chooses 12B for PAX01 and for PAX02. Both choices pass the seat map, and both passengers hold 12B (Lean example sameSeatTwice).
Open point: The source states no uniqueness rule. The business must decide whether uniqueness is checked within one order or across every order on the flight. It must also decide whether the unit is the passenger segment or the operating leg, since an assigned seat sits on a leg while referencing a segment.
10 cards depend on it, directly or through other cards, in 2 areas.
A bundle is a set of services sold together at one price that the customer cannot take apart. Conditions set on the offer item apply to every service in it. Case to check: Under the ARMI reading a flight item and a mandatory meal item form one bundle, yet the cancellation page lets a seller delete the meal order item alone as a partial cancellation.
Open point: The EASD bundle page places a bundle inside one offer item, while the ARMI bundle capability treats it as the mandatory offer items of an offer, each with its own price. The business must pick one, because it decides whether removing a bundled ancillary later is a change to one item or a cancellation of a separate item.
7 cards depend on it, directly or through other cards, in 2 areas.
checks ONE-603.6!Open questionAn order item whose conditions allow cancellation can be cancelled by some request that names it.
Counterexample: in the same order, under the reading where a cancellation is refused until the seller names the dependents too, naming the flight alone is refused for the bag, and naming the flight and the bag is refused by the bag's conditions (Lean example refuseUntilNamedBlocks). The flight cannot be cancelled at all.
Open point: Should a dependent's conditions be able to stop its flight from being cancelled?
1 card depends on it, directly or through other cards, in 1 area.
checks ONE-603.5!Open questionA live service of an item whose conditions do not allow cancellation stays as it was.
Counterexample: in the same order, the extra bag's conditions do not allow cancellation. Under the reading where dependents are cancelled with the flight, cancelling the flight item cancels the bag (Lean example cancelFlightWithBag).
Open point: Whose conditions govern a dependent cancelled with its flight, and its refund: the dependent's own or the flight's?
1 card depends on it, directly or through other cards, in 1 area.
checks ONE-603.4!Open questionAfter a seller cancels a flight, no live service depends on it.
Counterexample: the add bag worked example as an order, a flight for PAX-1 and an extra bag on it in its own item. The seller cancels the flight item alone. Under the reading where dependents stay in place, the flight is cancelled and the bag stays confirmed (Lean example cancelFlightWithBag).
Open point: Should cancelling a flight cancel its bag and seat, be refused until the seller names them, or leave them in place?
1 card depends on it, directly or through other cards, in 1 area.
A baggage allowance associated with several passengers together is shared among them, and one associated with each passenger separately limits that passenger alone. Under a sum reading, any bags that fit the separate allowances also fit the pooled one. Case to check: Two passengers pool 2 pieces each with a 46 kg total. Under the sum reading they may check 4 bags up to 92 kg. Under the stated totals reading they may check 2 bags up to 46 kg, less than they had separately.
Open point: The pooled example gives each passenger two pieces of 23 kg with a 46 kg total. The business must decide whether the pooled limit is the sum over passengers or the stated totals once, and whether the per-piece maximum still applies to each bag.
1 card depends on it, directly or through other cards, in 1 area.
checks ONE-607.3!Open questionRemoving services from a bundle returns no more than the bundle price, under every reading.
Counterexample: the seat worked example's bundle, one order item at 1,000.00 EUR holding both passengers' flights and bags. Under stand-alone prices of 470.00 EUR a flight and 60.00 EUR a bag, removing every service returns 1,060.00 EUR (Lean example bundleShares).
Open point: How does a bundle price split among its services: by stated component prices, by stand-alone prices, or not at all?
No card depends on it yet.
A flight-related ancillary enters an order only together with a flight service for the same passenger and segment, either in the same acceptance or already in the order. A seat map requested for an offer requires the offer to hold a flight and be unexpired. The model proves the first sentence when services are added, under every reading of flight related. This node checks the stronger claim that it stays true for the life of the order: a paid change to an order item keeps a live flight for every live flight-related ancillary. The seat map request is not modelled.
Counterexample: an order holds a paid flight for PAX-1 on SEG-OUT and a paid bag for the same passenger and segment, each in its own item. A paid change moves PAX-1 to a flight on SEG-NEW. The old flight is cancelled and the bag stays confirmed on SEG-OUT with no flight (Lean example bagLeftByFlightChange).
Open point: The source states this as a purchase precondition and never defines flight related. The taxonomy tree gives one answer: codes under Flight (0064) are flight related and codes under Journey (319C), such as insurance, are not. The business must confirm that and say whether the rule holds for the life of the order or only at purchase.
No card depends on it yet.
For a customer-initiated change, every reshop offer that would affect a dependent service says so and states the effect. The customer either accepts or reshops with the affected service included, so no dependent service changes without a stated effect the customer accepted.
Open point: The source does not define when a dependent service counts as impacted or what the stated effect must contain. The business must decide whether a change of price, seat number or delivery status counts. It must also decide whether the seller must pass the disclosure to the customer before acceptance, since the source says only that it should.
No card depends on it yet.
When an airline-initiated change affects a dependent service, the airline notifies the seller with any follow-up actions, a time limit and the consequence of no action. The customer accepts the change, or declines and cancels or reshops, and the reshop may cost more. Case to check: A customer paid 50.00 for seat 12C. The airline swaps the aircraft and 12C no longer exists. With no automatic refund and Auto-acceptance as the consequence of inaction, a customer who does nothing loses the 50.00, and one who reshops may pay again for a seat.
Open point: The business must decide what the customer is owed when an airline change removes a paid ancillary: an automatic refund, a free replacement, or a reshop at the customer's cost. The source allows extra payment on reshop and sets no limit.
No card depends on it yet.
checks ONE-601.4!Open questionAn ancillary of the order for the same passenger and segment as a flight service is counted as dependent on it, under either reading of the link.
Counterexample: in the seat example order, flights for PAX01 and PAX02 on SEG1, a bag for PAX01 that names its flight, and seats 12B and 12C that name no flight. By reference only the bag depends on PAX01's flight; through passenger and segment the bag and seat 12B do (Lean example seatWithoutReference). Under the reference reading a change to the flight reports no impact on the seat.
Open point: Which link defines the dependency: a reference to the parent, or the shared passenger and segment? And may an ancillary depend on another ancillary, such as a lounge pass on a premium seat?
No card depends on it yet.
Buying extra weight as quantity q of a unit-weight bag service yields one extra allowance of q times the unit weight. The airline returns it as a single extra bag allowance. Case to check: A passenger with one 23 kg bag buys 5 kg extra and checks one 28 kg bag. The bag is allowed if the extra raises the existing limit and refused if the extra is a separate 5 kg piece.
Open point: The source describes the extra weight as added on top of an existing allowance, but its example returns a separate one-piece allowance with its own maximum. The business must decide whether extra weight raises an existing bag's limit or adds a separate piece.
No card depends on it yet.
Assigning a free seat creates its own order item priced at zero, as a paid seat does. The payment step covers the free seat with a commitment and charges nothing.
Open point: The two pages of the seat worked example disagree: one says payment is processed for free and paid seats alike, the other says a free seat is only committed. The business must decide which, which ties to C-12.
No card depends on it yet.
Taxonomy codes form a tree rooted at code 0000, and a service tagged with a code is also described by every ancestor of that code. A seller's service criterion is Required, Exclude or Preferred, and a criterion with no level counts as Preferred. Case to check: A seller excludes Checked Baggage (13EC). An offer with a service tagged Bag (1450), a child of 13EC, passes an exact-code filter and fails a tree filter.
Open point: The source does not say whether a criterion matches descendants of its code. It also does not say whether Required and Exclude bind the airline, since both capability pages say the airline may consider them and taxonomy use is not mandated. The business must settle both before any filtering guarantee can hold.
No card depends on it yet.
checks ONE-604.4!Open questionNo seat moved by a flight replacement lands on a seat another passenger holds on the new flight.
Counterexample: PAX-1 holds a paid flight on SEG-1, paid seat 12C and a bag. The airline replaces the flight with one on SEG-2, where PAX-9 already holds 12C. Where every dependent moves, seat 12C moves and lands on PAX-9's seat; where seats are reshopped, only the bag moves (Lean example seatMovedOntoTakenSeat).
Open point: What happens to a seat when its flight is replaced: does it move, and to which seat, or is it refunded, stored or reshopped?
No card depends on it yet.
checks ONE-606.5!Open questionAn a-la-carte offer item becomes exactly one order item, as every offer item does when an offer is accepted (C-02).
Counterexample: the add bag worked example's extra bag at 50.00 EUR a unit, chosen for PAX-1 on the outbound and inbound journeys at quantity 1. The one offer item becomes two order items of 50.00 EUR, and the bag costs 100.00 EUR (Lean example bagOverTwoJourneys).
Open point: Does one offer item become one order item, as the order structure says, or one per passenger and segment, as the worked example shows? And what is the unit of the unit price?
No card depends on it yet.
A passenger holds at most one active seat assignment on each segment of an order. The model checks that a seat request keeps this true when it held before and the seat maps mark no held seat available. Case to check: A seller adds 14A for PAX01 on SEG1 through a second quote while 12B is still confirmed. Both seat items are ACTIVE, and the passenger holds two seats on one segment.
Counterexample: PAX01 holds 12B on SEG1, and the seat map marks 12C and 14A available. A second request chooses 14A for PAX01. It passes the seat map, and PAX01 holds 12B and 14A, each in its own order item (Lean example secondSeatSamePassenger).
Open point: The business must decide whether a passenger may hold extra seats, for comfort or for a large instrument, and how such a seat is represented. It must also decide whether choosing a new seat cancels the old seat item and with what refund.
No card depends on it yet.
In a pick M of N offer item, the customer chooses at most M of the N listed services. The price is the same whatever the choice. Case to check: Under the fixed price reading a customer who picks no service still pays the full price of the item.
Open point: The source gives a maximum and no minimum. The business must decide whether choosing fewer than M, or none, still costs the full price, and whether unused picks can be claimed after the order exists.
No card depends on it yet.
Removing a passenger from an order cancels every service of that passenger, ancillaries included, and keeps every service of the other passengers. Case to check: Removing adult PAX-1 leaves an infant that references PAX-1 with no accompanying adult, and leaves PAX-2 holding a pooled allowance sized for two.
Open point: The source is silent on what depends on the removed passenger through another passenger. The business must decide what happens to an infant on lap whose record references the removed adult, and to a baggage allowance pooled with the removed passenger.
No card depends on it yet.
checks ONE-607.4!Open questionRemoving every service of a bundle, all of them live, returns the whole bundle price, under every reading.
Counterexample: the same bundle. Under a reading that gives no share to any service, removing PAX02's flight and bag returns nothing, and so does removing every service (Lean example bundleShares).
Open point: Does removing part of a bundle return part of its price, and does removing all of it return all of it?
No card depends on it yet.
A seat is assigned to a passenger on a segment only through the price point offer item that the seat references on the seat map, and only if that item lists the passenger and segment as eligible. The seat is available when chosen.
Open point: The source attaches price points to available seats and lists eligible passengers on each price point, and never says a selection is checked against either. The business must decide whether an available seat without a price point can be chosen, and who enforces eligibility such as exit row restrictions.
No card depends on it yet.
An open guarantee fails under some reading of the sources. For these, Lean proves a version under one reading, named
with _of_. The model leaves the choice of reading to the business.
The requirements whose rules or guarantees are on this area's cards. Each opens its chapter in the review document.
The capabilities of IATA's Airline Retailing Maturity Index that this area's candidate cards belong to. The codes and
names are IATA's.