Mishandled and delayed baggage
A bag did not arrive with its passenger. HalaBag is your technology for what happens next: it takes the case from WorldTracer, finds the best provider, keeps the passenger informed, proves the delivery and closes the cost.
AHL and OHD recovery and delivery, governed end to end
How it works with your airline
Where the case starts, where HalaBag sits, and what your team sees.
- Case raised in WorldTracer or DCS1
- Into HalaBag, one record2
- Your workflow applied3
- 3PL allocated on performance4
- Custody tracked, proof captured5
- Passenger notified6
- SLA measured, invoiced7
- Operational today
Console or file-feed intake; allocation across Aramex, SPL, Saaml; custody, messaging, proof, reconciliation.
- Practical route before the integration
Station team raises the case; everything downstream runs automatically.
- Requires further integration
WorldTracer and DCS automated intake.
- SLA countdowns
- Multi-provider
- Delay-related exposure
- Claims-ready evidence
- Lower cost per resolved case
- Day-one delivery measured by station
- Fewer complaints and escalations
- Provider performance visible and enforced
Why this matters
Mishandled bags are fewer than they were, and each one costs more: US$260 on SITA's 2026 benchmark, about 70% of it in recovery, rerouting and delivery. That layer is executed today by whichever handler or courier is local, on its own process, with visibility that stops at the station. Head office sees the complaint, not the case.
How it works, in six steps
- 1Case intake from your source system. AHL and OHD files are received from WorldTracer, DCS events or the handler desk. The passenger, flight, station and bag details attach to one case.
- 2Consent and address. The passenger confirms delivery address and window in their language, under your brand, on the channels you allow.
- 3Allocation. The case is offered to providers covering that lane, ranked by cost and measured SLA performance. The best available takes it, or operations override with a logged reason.
- 4Custody and delivery. Each hand-off is confirmed with time, location and evidence. Delivery is proven with photo and signature.
- 5Status back to source. Progress and closure are written back to the tracing file and to the passenger.
- 6Cost closure. Provider cost and airline charge are captured, reconciled and invoiced on the case.
Capabilities
- SLA countdowns. Every case carries its contracted service level and the clock against it. Exceptions surface before the deadline, not after the complaint.
- Multi-provider. Own fleet, handler, courier or 3PL on the same case model, with the same evidence standard.
- Delay-related exposure. In Saudi Arabia, GACA sets compensation for baggage delay from the first day. Faster recovery reduces additional delay-related costs and exposure, subject to the applicable rules; the platform reports day-one delivery by station so you can see it.
- Claims-ready evidence. Custody chain, messages and proof exportable per case for claims and audits.
Related integrations
SITA WorldTracer
In progressThe source system for mishandled-baggage files. HalaBag receives the case and writes status back.
Aramex
LiveIntegrated logistics provider for allocation, status and proof, with rate calculation and international reach.
SPL (Saudi Post Logistics)
LiveIntegrated national logistics provider for domestic allocation, status and proof.
Saaml
LiveIntegrated last-mile and city logistics provider for allocation, dispatch, status and proof.
Airline DCS and PSS
In progressDeparture-control and passenger-service events that raise cases and confirm acceptance.
Status labels are reviewed monthly. In progress and planned are not delivered. Integrations
Frequently asked questions
See the platform on your own baggage cases
A 45-minute working session with our solutions team: your stations, your providers, your source systems. No slides.