NDC

Why it matters

This concept affects how travel supply moves between systems and which state can be trusted during search. Distribution data needs more than a valid payload: it needs context, freshness and clear ownership. The same term may exist at supplier, channel-manager, OTA and metasearch layers with different semantics, so careless abstraction creates hard-to-debug mismatches.

What does it look like in practice?

A hotel rate update moving from supplier through connectivity into an OTA or metasearch should preserve entity identity, source timestamp, restrictions and version state. HTTP success alone does not prove downstream distribution state is current.

Implementation questions

• Which system is the source of truth?
• Which identifiers and versions must be preserved?
• Does state arrive by push, pull or event?
• How is stale or incomplete state detected?

Common mistakes

• Treating provider IDs as canonical IDs
• Equating HTTP success with business-state success
• Mixing full and delta update semantics

Where does it appear in the travel stack?

NDC commonly appears across distribution, flight layers. Its implementation should make source-of-truth, identity, freshness and transaction-ownership boundaries explicit.

Related terms