Airline retailing is moving from PNRs and tickets to a single Order record, with Offer, Order, Delivery and Settlement as separate, connectable components. Showing that works across independent vendors, with real data flowing between systems, is a different problem. Turkish Technology, Ink Innovation and Sutherland solved it. The same Order flows across three independent systems, from offer creation to airport delivery to revenue recognition, as one coherent journey.

Three vendors. One architecture.

Turkish Technology is the technology arm of Turkish Airlines, building and owning the airline's commercial systems: Offer and Order management, product catalogue, stock keeper, and Dual Mode Adapter. All built to IATA standards and exposed through open APIs.

Sutherland connects settlement and revenue recognition directly to operational delivery events, replacing assumption-driven accounting with real fulfilment data.

Ink Innovation runs the airport service delivery: check-in, bag drop, boarding, built to speak Order as a first language.

The project was developed as a proof of concept within the IATA Multivendor Demo Day programme, 2025.

Challenge

The industry has the model. The question is whether it actually connects.

Most airline systems still communicate through legacy documents: PNRs, tickets, EMDs, requiring constant translation between commercial, operational and finance layers. Modernising one domain usually means negotiating with all the others.

The harder problem is showing that different vendors, building independently, can consume the same Order and behave as a single system.

Implementation

One Order. Three systems. Four domains.

Offer. Turkish Technology builds the product and the price. A contextual offer, flights, bags, sports equipment, lounge access, bundles, built from a live product catalogue with airline-controlled pricing and rules. No dependency on airport systems or accounting.

Order. Turkish Technology turns acceptance into a single record. Each service becomes an explicit entitlement: flights, ancillaries, passenger linkages, held in one place and shared via API. Partners read the Order directly. Nothing is reconstructed from tickets.

Delivery. Ink executes the airport operation against the Order. Agents see the passengers, their pre-purchased services, and optional ancillaries still available at the airport. Check-in, bag drop, boarding pass and bag tag printing, boarding: each step updates the delivery status in real time. Status moves from "planned" to "ready" to "in progress" to "delivered." Commercial, operational and customer channels stay aligned on the same Order state.

Settlement. Sutherland recognises revenue from delivery events. Each order line carries its contract price and recognition status. Revenue moves from "deferred" to "recognised" as delivery events confirm fulfilment, driven by what actually happened, not schedule assumptions or coupon logic.

No translation layer between systems. Alignment is structural.

Results

Partner voice

"Working with Ink allows us to connect digitally with anybody through APIs. That's the idea, modularity guiding us." — Ozbek Erdem Yetgin, Product Manager of Order Management System, Turkish Technology

What's next

The proof of concept demonstrates something beyond this partnership. Any airline running its own Offer and Order management can connect Ink's Delivery layer without switching providers or rebuilding its stack. The integration requires no shared codebase, no common PSS, just aligned standards and open APIs. For airlines moving toward OOSD, the path to delivery is already there.