Named systems, and what each integration does
HalaBag connects to the systems that raise cases and to the providers that execute them. Every integration below is labelled live, in progress or planned, and the labels are reviewed monthly.
Source systems
- In progress
SITA WorldTracer
The source system for mishandled-baggage files. HalaBag receives the case and writes status back.
WorldTracer is the tracing system of record for more than 500 airlines at 2,800 airports. HalaBag treats it as the source: AHL and OHD files raise cases, and resolution status is returned to the file. Connection is through SITA's Bag Delivery Service, a commercial membership process HalaBag is completing. Until then, cases are raised from DCS events, handler consoles or file feeds.
Data flow: Inbound cases; outbound status
- AHL and OHD case intake
- Delivery order receipt
- Status write-back
- File reference on every case
Logistics providers
- Live
Aramex
Integrated logistics provider for allocation, status and proof, with rate calculation and international reach.
Aramex operates directly in 70 countries and 600+ cities and leads a global alliance reaching 240+ countries. The integration supports order creation, rate calculation, status events and proof of delivery, which makes cost-based allocation and multi-country coverage possible from one connection.
Data flow: Outbound orders; inbound status and proof
- Order creation
- Rate calculation
- Status webhooks
- Proof of delivery
- International lanes
- Live
SPL (Saudi Post Logistics)
Integrated national logistics provider for domestic allocation, status and proof.
SPL is the Kingdom's national postal and logistics operator and a named participant in the 2026 Hajj programme. The integration covers order creation, status events and proof of delivery across SPL's domestic network.
Data flow: Outbound orders; inbound status and proof
- Order creation
- Status events
- Proof of delivery
- Domestic coverage
- Live
Saaml
Integrated last-mile and city logistics provider for allocation, dispatch, status and proof.
Saaml provides city and last-mile logistics, including the dispatch and rider operations used for collection and delivery within Saudi cities. The integration covers order creation, dispatch status and proof of hand-off and delivery.
Data flow: Outbound orders; inbound status and proof
- Order creation
- Dispatch status
- Proof of hand-off and delivery
- City coverage
Airline systems
- In progress
Airline DCS and PSS
Departure-control and passenger-service events that raise cases and confirm acceptance.
Offload, short-shipped and acceptance events from the airline's DCS raise left-behind and off-airport cases and confirm that an off-airport bag has become a checked bag in the airline's own system. Integration is per airline and follows the airline's DCS vendor and release cycle; the first connections are in progress with airline partners.
Data flow: Inbound events; outbound acceptance confirmation
- Offload and short-shipped events
- Bag acceptance confirmation
- Passenger and itinerary lookup
Commerce and partner platforms
- In progress
HalaBag Partner API
One REST integration for platforms and providers: quotes, orders, status, proof and webhooks.
The Partner API is the single integration surface for travel platforms, super apps, corporate travel tools and baggage operators. It exposes quoting, order creation, status, proof and coverage, with webhooks for status changes. The API is being published with sandbox credentials and a reference implementation for partner product teams.
Data flow: Inbound orders; outbound status, proof and coverage
- Quote and order endpoints
- Status and proof retrieval
- Webhooks
- Coverage query
- Sandbox and reference client
- In progress
Booking and travel platforms
Off-airport and group baggage orders from OTAs, corporate travel platforms and aggregators.
Travel platforms connect through the Partner API to sell home check-in, land-and-leave and delivery inside their booking flow, with status returned to their interface. Integrations with the first booking and corporate travel platforms are in progress.
Data flow: Inbound orders; outbound status and proof
- Booking-flow merchandising
- Order push to handlers
- Status in the seller's UI
- Corporate billing
- Live
ERP and ZATCA-compliant invoicing
Financial closure: invoices, credit notes and payment matching for every case.
Cost, charge and fee on each case flow to the group ERP, where invoices and credit notes are issued to ZATCA e-invoicing requirements in Saudi Arabia and matched against payments and provider statements. Financial closure is part of the record, not a month-end exercise.
Data flow: Outbound invoicing events; inbound payment and document status
- Invoice and credit-note issue
- ZATCA compliance
- Payment matching
- Provider statement reconciliation
Airport and handler systems
- Planned
Airport and handler systems
Baggage handling, screening and handler task systems at the station.
Connections to airport BHS, screening and handler task systems to confirm acceptance windows, sequence off-airport arrivals and exchange custody events at the station. Scoped per airport programme.
Data flow: Bidirectional station events
- Acceptance windows
- Arrival sequencing
- Custody events at the station
Status labels are reviewed monthly. In progress and planned are not delivered.