HalaBag
Manage recovery

Left-behind baggage

A bag missed the flight. HalaBag is your technology for getting it to the passenger: it plans the next uplift, tracks the bag across stations, delivers it with proof and tells the passenger at every step.

Operational recovery for bags that missed the flight

How it works with your airline

Where the case starts, where HalaBag sits, and what your team sees.

  1. Offload event from DCS1
  2. Case opened with onward itinerary2
  3. Next uplift planned3
  4. Destination provider allocated4
  5. Custody and proof5
  6. Passenger updated6
  7. Closed and invoiced7
Illustration of the Left-behind baggage workflow view, with demonstration data.
  • Operational today

    Console or offload-list intake; reroute, destination allocation, custody, updates, closure.

  • Practical route before the integration

    Origin station records the offload; destination case opens automatically.

  • Requires further integration

    Automated DCS offload events.

  • Cross-station visibility
  • Passenger updates at each step
  • Cause tracking
  • Faster reunification
  • Fewer duplicate calls between stations
  • Root causes measured
  • Compensation exposure reduced
Why this matters

Left-behind bags cross stations and handlers. Origin knows the bag was offloaded; destination knows the passenger is waiting; nobody owns the recovery. Transfers cause 39% of mishandling, and the fix depends on coordination that today happens by phone.

How it works, in six steps
  1. 1Offload event to case. An offload or short-shipped event from the DCS or handler raises the case with the onward itinerary attached.
  2. 2Rush and reroute. The workflow plans the next available uplift, notifies the destination station and the passenger, and tracks the bag across the reroute.
  3. 3Destination delivery. On arrival the case allocates to a provider for final delivery, with custody and proof as for any mishandled bag.
  4. 4Closure. Status written back to the tracing file, cost captured, case closed.
Capabilities
  • Cross-station visibility. Origin, transfer and destination see the same case and the same clock.
  • Passenger updates at each step. Offload, uplift, arrival and delivery communicated automatically.
  • Cause tracking. Weight, security, connection or handling cause recorded per case for root-cause reporting.

Related integrations

  • SITA WorldTracer

    In progress

    The source system for mishandled-baggage files. HalaBag receives the case and writes status back.

  • Aramex

    Live

    Integrated logistics provider for allocation, status and proof, with rate calculation and international reach.

  • SPL (Saudi Post Logistics)

    Live

    Integrated national logistics provider for domestic allocation, status and proof.

  • Airline DCS and PSS

    In progress

    Departure-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

The workflow plans and records it; the booking itself is made in your baggage or DCS system and its confirmation is captured on the case.

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.