Industry analysis · 9 October 2026 · Neerej Sasikumar

ATPCO Product Catalog: Why Airline Product Interoperability Is Bigger Than Fare Filing

In brief: ATPCO outlined at Elevate 2026 a vision in which airline product information can flow through a shared exchange to airline partners, travel sellers and aggregators. The key architectural distinction is that an airline can retain ownership of its catalog while using an exchange layer for distribution. This is a vision described by ATPCO, not evidence that every airline, NDC channel or interline scenario already supports it.

What ATPCO actually said

In his opening Elevate 2026 remarks, CEO Brett Burgess described extending ATPCO's data-exchange role from pricing toward product information. Airlines, he explained, would primarily manage their own catalogs within their offer systems; a shared product catalog exchange could help distribute descriptions of products to interline partners, joint ventures, sellers and aggregators. He presented this as a way to reduce point-to-point integrations while keeping airline control over product information.

Primary source: ATPCO Elevate 2026 opening session, official transcript. The discussion is in the Product Catalog portion of the keynote. It describes a direction of travel, not a universal production capability or implementation timetable.

Product catalog versus offer engine versus order management

These three concepts are related, but they are not interchangeable. The product catalog describes a sellable product and its attributes: for example, checked-baggage allowance, eligibility, inclusions, display labels and fulfilment requirements. The offer engine decides which products and prices to propose for a particular shopping context, including inventory and commercial constraints. The order management layer records the customer's accepted purchase and supports servicing and delivery. A shared product-data exchange need not make the offer or fulfilment decisions on behalf of airlines.

IATA's NDC guidance describes Offer and Order message exchange for distribution, while its ONE Order guidance discusses the downstream order and fulfilment lifecycle. These are useful reference points, but neither means a product exchange automatically solves airline-specific business rules.

Example: distributing the meaning of a checked bag

Consider an airline defining a 23 kg checked-baggage product. A partner seller needs a reliably interpretable product name, allowance, applicable journey or passenger conditions, effective dates, refundability and customer-facing text. The offer engine still needs to determine whether the baggage item can be offered on the requested itinerary and at what price. After purchase, the parties still need a deliverable entitlement and accurate order/service status.

A coherent catalog identifier and version can help partners avoid displaying stale or contradictory attributes. But a catalog entry alone does not guarantee the bag is accepted by every operating airline, at every airport, or in every disruption scenario. Those checks belong to eligibility, agreement and delivery logic.

Five practical implementation questions

Who owns the source of truth? Is the canonical definition maintained by the airline, an offer platform, a merchandising system or another master-data service?
How are versions and effective dates enforced? A seller must know whether a product definition changes before pricing, booking or servicing.
What must a partner understand? Common identifiers are insufficient without compatible attribute meanings, units, restrictions and localisation.
Where is eligibility resolved? Product content, commercial pricing rules, operating-carrier constraints and order-delivery obligations should not be collapsed into one field.
How can the exchange be audited? Teams need traceable product revisions, partner acknowledgements, distribution latency and exception management.

Interline and joint ventures: where the difficulty sits

Across carriers, product interoperability has two separate layers. First, airline A must communicate what a product is. Second, airlines A and B must agree what can be sold, which party is responsible for delivery and how changes, refunds or settlement will be handled. The first problem benefits from a common product-data model. The second requires processes and commercial agreements beyond data publication. For retailer/supplier interline patterns, see our SRSIA explainer and interline knowledge hub.

How airlines should measure progress

Useful measures include time to distribute a revised product definition, percentage of channel displays with complete and current attributes, product-eligibility rejection rates at OfferPrice, mismatches between sold entitlements and delivery systems, and partner onboarding effort. These are proposed engineering KPIs, not reported ATPCO performance figures. Measure the full path from product definition to offer presentation and delivery rather than counting catalog records alone.

Why this matters now

ATPCO's keynote also discussed the role of richer shopping signals, Routehappy attributes and AI. The larger lesson is that more dynamic offers depend on products being represented consistently enough for both human shoppers and connected systems to interpret. That makes product semantics, ownership and governance an architectural concern, not merely a merchandising copy exercise. This interpretation is independent analysis based on ATPCO's published remarks.