Integrate once, serve many: three live provider integrations

Context

Allocation across competing providers only works if the providers are integrated to the same case model: order creation, status events and proof. Each provider's API is paced by its own release cycle.

Challenge

Normalise three different provider APIs into one allocation, custody and proof model without losing what each does best, including Aramex's rate calculation for cost-based allocation.

Approach

1. 1

   One provider model

   Orders, status and proof mapped to a common case model with provider-specific adapters.

2. 2

   Resilience

   Retries, idempotency and failure handling per provider, so a provider outage queues rather than loses work.

3. 3

   Rate-aware allocation

   Aramex rate calculation used for cost-based ranking; contracted rates configured for the others.

4. 4

   Available to every tenant

   Once integrated, each provider is offered to every airline and programme on the platform.