Buyer resource · Readiness worksheet

Seats, bags and upgrades: ready for agent-led purchases?

An agent recommending an extra bag is different from an airline confirming that bag for the right passenger and flight. Use this airline ancillary commerce worksheet to evaluate the complete purchase: accessible inventory, accurate entitlements, consent, payment and verified fulfillment. Apply it during shopping, initial booking or an unchanged existing trip, as well as during servicing.

Define the workflow before the pilot

Choose one product, booking stage, caller and supported order population. Agree who owns exceptions and what counts as completion. Qualify each supported operation before combining a flight change, adjacent seats, existing bags and an optional upgrade. Each component needs its own evidence.

Standards inform the questions; backend evidence answers them

IATA describes New Distribution Capability (NDC) as an exchange format built around offers and orders. Its purpose includes communicating richer airline products across distribution channels. See IATA’s NDC overview. For a pilot, inspect the actual adapter, version and service operations; a standards label is not evidence of supported purchases or post-booking changes.

ONE Order aims to bring fulfillment, delivery and accounting into an integrated order record, gradually replacing separate reservation, ticket and electronic miscellaneous document (EMD) records. See IATA’s ONE Order explanation. Establish which records your airline actually uses and how a service’s identity, payment and delivery status reconcile. Do not assume this transition is complete or that a confirmed itinerary proves ancillary fulfillment.

Readiness checklist

Check an item only when the named workflow has supporting test evidence. Leave unverified items unchecked. These controls stay in your browser and are not submitted or saved by Aviark. Use your browser’s print command to keep a worksheet; do not rely on entries surviving a reload.

Product, booking stage, supported order population and owner

Evidence confirmed for this workflowAccessible ordersConfirm read and write authority for the issuing channel, airline, backend version and order population. Reject unsupported bookings before attempting a purchase.Passenger and segment entitlementsMap each seat, bag and benefit to the correct traveler and flight. Distinguish purchased, included, loyalty, cancelled and unknown services; missing data never means no entitlement.Eligible productsVerify seat availability, baggage quantity and restrictions, and upgrade eligibility. Test party seating and unavailable products. Explain exclusions before the traveler commits.Current quote and net priceShow currency, total additional cost, fees, expiry and changed conditions. An upgrade may include an already purchased bag: identify its treatment and prevent duplicate charging.Consent and airline authorizationBind the approved products, passengers, segments and price to the action. Record traveler consent separately from airline permission. Requote and reapprove material changes.Payment stateIdentify who collects payment and owns reconciliation. Test declines, authentication interruptions and payment success followed by a timeout; never assume a missing response means no charge.Fulfillment evidenceRead authoritative state after execution. Confirm the actual seat assignment, baggage entitlement or cabin, payment reference and applicable service-document status. An accepted request is insufficient.Partial completion and reversalTest a flight change succeeding while a service purchase fails. Define permitted cancellation, refund or escalation steps and an owner; do not promise automatic rollback across systems.Safe repetition and operationsRepeat requests, restart processing and revoke permission. Prove duplicate prevention, truthful pending states and reconciliation. Record support effort and handoff responsibility for unresolved cases.

Proof-of-value scorecard

Agree thresholds with the airline before collecting results. Record the baseline, pilot observation and evidence period for each measure. Use a matched cohort or controlled comparison; distinguish observed differences from evidence of causation. There is no universal pass score.

Gross sales count transaction value, not incremental value. A seat purchase that would already have happened elsewhere is not automatically uplift. Compare contribution after relevant costs and avoid counting the same benefit in both commercial value and servicing savings.

Eligible coverage

Eligible requests / assessed requests. Retain exclusion reasons and the same population definition in both cohorts.

Eligible coverage: baseline, threshold, pilot result, period and evidence

Verified fulfillment

Verified fulfilled purchases / purchase attempts. Report pending and partial outcomes separately; exclude duplicate retries from both counts.

Verified fulfillment: baseline, threshold, pilot result, period and evidence

Product attachment

Fulfilled seat, bag or upgrade purchases / eligible opportunities for that product. Compare equivalent booking stages and passenger groups.

Product attachment: baseline, threshold, pilot result, period and evidence

Entitlement integrity

Orders with verified retained services / changed orders requiring preservation. List lost, unknown and incorrectly charged services separately.

Entitlement integrity: baseline, threshold, pilot result, period and evidence

Incremental contribution

Contribution difference against the agreed baseline, adjusted for discounts, cannibalization, displacement, refunds and fulfillment costs. Document assumptions and uncertainty.

Incremental contribution: baseline, threshold, pilot result, period and evidence

Failures and reversals

Track failed, partial and unknown outcomes per purchase attempt, plus completed reversals, outstanding refunds and time to resolution. Assign an owner to unresolved cases.

Failures and reversals: baseline, threshold, pilot result, period and evidence

Operating burden

Support, reconciliation, repeat contact, model/API and delivery costs per verified outcome. Include failed attempts and human fallback effort. With no verified outcomes, report total cost and zero completions instead of a per-outcome ratio.

Operating burden: baseline, threshold, pilot result, period and evidence

Make the next decision explicit

Choose whether to continue discovery, address a failed gate or propose a limited rollout. Record missing evidence, the owner and next review. A human fallback can be appropriate, but it must be disclosed and costed rather than counted as automated completion. Keep implementation scope separate from ongoing workflow coverage, capacity and support.

Decision, unresolved gates, owner and next review

Continue with governed agent transactions or the airline commerce overview.