---
title: "How the Turkey Travel Distribution Ecosystem Works"
description: "A technical guide to how travel supply moves from PMS/CRS/PSS through GDS, NDC, bedbanks and channel managers into OTA and metasearch layers in Turkey."
slug: "turkey-travel-distribution-ecosystem"
translationKey: "learn-turkey-travel-distribution-ecosystem"
locale: "en"
type: "guide"
category: "architecture"
tags: ["turkey","travel-distribution","ota","gds","bedbank","pms","crs","channel-manager"]
publishedAt: "2026-09-26"
updatedAt: "2026-09-26"
reviewedAt: "2026-09-26"
sources:
  - title: "SiteMinder Developer Guide"
    url: "https://www.siteminder.com/developer-guide/"
  - title: "Turkish Airlines — TKCONNECT"
    url: "https://www.turkishairlines.com/en-kt/tkconnect/how-to-tkconnect/"
  - title: "Hotelbeds API Suite"
    url: "https://developer.hotelbeds.com/"
---
Turkey's travel-distribution ecosystem should not be modeled as a list of OTAs. A hotel, flight or package offer visible in search may pass through supplier systems, connectivity, wholesale/GDS and retail layers before reaching the traveler. A sound architecture keeps each layer's identity and source-of-truth responsibilities explicit.

## Problem and why it matters

The same hotel may have different identifiers in PMS, channel-manager, bedbank and OTA systems. A flight offer may originate from GDS, NDC or an airline-direct source. Flattening all of this into one generic provider record creates mapping, freshness, attribution and reconciliation failures.

## Architecture flow

```text
Travel Supply
  ↓
PMS / CRS / PSS / Supplier Extranet
  ↓
Connectivity / Channel Manager / GDS / NDC / Bedbank
  ↓
OTA / Marketplace / Metasearch / Tour Operator
  ↓
Booking Engine / Payment / Attribution
  ↓
Reconciliation
```

Each arrow is more than transport: identity translation, pricing semantics, availability state and commercial ownership can change.

## Hotel distribution

A hotel PMS may be the operational source, a CRS may orchestrate chain-level inventory and rates, and a channel manager can distribute ARI and reservation state downstream. A bedbank can re-distribute contracted or wholesale inventory. An offer reaching an OTA or metasearch service may originate from any of these layers.

## Flight distribution

Airline inventory can move from supplier/PSS state through GDS, NDC aggregators or direct APIs. Turkish Airlines TKCONNECT is a useful local example because it supports UI, aggregator and direct NDC API connection models around the same airline supplier.

## Package holidays

Tour operators can combine hotel, flight, transfer and other components into one package. Package identity is not a simple concatenation of component identities; bundle-level contracts, cancellation and pricing rules may exist.

## Trade-offs

More intermediaries increase coverage and commercial reach but also increase identity mapping, stale-state, reconciliation and tax/fee-normalization complexity. Direct connectivity can preserve richer supplier context and reduce hops, but it creates per-supplier integration and operational cost.

## Failure modes

Typical risks include wrong property/room mapping, stale ARI, duplicate hotels, lost source provenance, tax/fee errors, unsafe timeout fallback, unmatched booking/payment references and delayed cancellation state.

## Observability and KPIs

Measure update lag, mapping coverage, duplicate rate, availability mismatch, price mismatch, timeout/error rate, reconciliation drift and unresolved attribution by layer. “Search works” is not a sufficient distribution-health metric.

## Production checklist

- [ ] Preserve source/provider provenance on every offer.
- [ ] Separate supplier IDs from canonical IDs.
- [ ] Model hotel, room, rate and package identity separately.
- [ ] Preserve GDS/NDC/direct source.
- [ ] Track freshness timestamps by layer.
- [ ] Separate booking, payment and attribution references.
- [ ] Make reconciliation replayable.
- [ ] Label stale/partial fallback explicitly.

The Turkey ecosystem hub maps the entities in each layer; this guide explains why the technical boundaries between those layers matter.