Offer & Order Management,
in the open.
An exploration. A proposal. Not a roadmap commitment.
Read on if you'd like to help shape what an open Offer & Order Management System for airlines could look like — once the three pillars below it have landed.
ProposalThe thesis
Once airlines have open infrastructure for documents, taxes, and schedules, the Offer & Order layer above them becomes a tractable community project — instead of a multi-year vendor lock-in.
We've sketched a data model for an IATA Modern Airline Retailing compatible Offer & Order Management System — bundles, products, orders, services, settlement, fulfilment — built on top of the Open Order Database Engine. It is, today, a sketch. It moves forward only if an airline community forms around it.
Bundles & products
A clean naming model — our own, not pinned to NDC vocabulary. Products at the catalogue layer, bundles at the offer layer.
Flow-DSL rules engine
Typed node sockets. Rules compose graphs, not procedural code. Built on the Open Rules Engine — RuleForge — same DSL as the Tax Engine.
Append-only orders
Order history as an event log. Servicing, ops, and finance all read the same authoritative timeline.
Source-available
Airlines run, inspect, modify. Commercial redistribution reserved. The compromise that lets us spend years on it.
Catalogue → Delivery
The full retail spine: Catalogue → Offer → Order → Servicing → Settlement → Delivery, with the rules engine at the core.
After the pillars. Not before.
We're disciplined about scope. The Open Order Database Engine, Open Tax Engine, and Open OAG Studio come first. They're the foundations. An OOMS is the cathedral you build once the foundations are laid — not the other way around.
No deadline. We'll start when the contributor base is real.
Tell us what you'd build.
Or what you'd break.
Sketches, RFCs, war stories from your last OOMS migration — we want them all. Email us if you have skin in the game, operationally or technically.
Stay close
RFCs land in this inbox first.
RFC = Request for Comments. When we're shaping a new spec, we publish a draft for the community to read, critique, and shape before it ships. Subscribe to read them as they drop.
Note: AeroToys is free and community-built. We don't do RFTs (Request for Tender) — there's nothing to bid on, just code to contribute to.
Or email info@aerotoys.io