HalaBag
Platform

The orchestration layer above your existing systems

Airlines, airports and handlers already run mature systems for check-in, sortation and tracing. None of them executes the resolution of a case once it leaves the belt. HalaBag is that execution layer: it receives the case, runs the workflow, allocates the work, keeps custody, talks to the passenger, proves the outcome and closes the money.

Where it sits

Source systems
  • SITA WorldTracer
  • Airline DCS / PSS
  • Handler desks
  • Booking platforms
HalaBag orchestration layer
  • Case intake
  • Workflow
  • Allocation
  • Chain of custody
  • Passenger comms
  • SLA governance
  • Financial closure
Execution network
  • Ground handlers
  • 3PLs
  • Baggage operators
  • Warehouses

Source systems

SITA WorldTracer, airline DCS and PSS, airport BHS, handler desks, lost-property counters, partner booking flows

Raise the case. Remain the system of record for the bag's identity and tracing file.

HalaBag orchestration layer

Case intake, workflow engine, allocation, custody, passenger communication, SLA governance, financial closure

Executes the case end to end and returns status to the source system and the passenger.

Execution network

Ground handlers, 3PLs, baggage operators, airport warehouses, station teams

Perform the physical work under HalaBag's allocation, evidence and SLA measurement.

The life of a case

  1. 01

    Intake

    A case arrives from WorldTracer, a DCS event, a handler, a counter or an API. HalaBag validates it, attaches the passenger and the station, and opens one record.

  2. 02

    Workflow

    The configured workflow for that airline, station and product applies: consent, address confirmation, screening, cut-offs, documentation.

  3. 03

    Allocation

    The case is offered to the providers who cover the lane, ranked on cost and measured SLA performance. Manual override stays available, and is logged.

  4. 04

    Custody

    Every hand-off is confirmed by the receiving party with time, location and evidence. The chain of custody is complete or the case is flagged.

  5. 05

    Passenger

    Status, ETA, delivery windows and proof go to the passenger in their language under your brand, by the channels you allow.

  6. 06

    Closure

    Provider cost, airline charge and any passenger fee are captured on the case, reconciled and invoiced. The record is closed and reportable.

Capabilities

Multi-tenant by design

Each airline, handler or operator sees its own cases, providers, rules and reports. A handler serving five airlines runs one system with five tenancies.

Configurable workflows

Products, stations, cut-offs, documents and steps are configuration, not code. Turning a station on for a new product is an operational task.

Provider scorecards

On-time rate, proof completeness, exceptions and cost per case, per provider and per lane, feeding allocation automatically.

Chain of custody

Timestamped, geolocated hand-offs with photo and signature evidence, exportable for claims and audits.

Passenger communication

Templated, bilingual, brand-controlled messages across SMS, WhatsApp Business, email and tracking pages.

Financial closure

Cost, charge and fee on every case. Invoices and credit notes issued to ZATCA requirements in Saudi Arabia, with reconciliation against provider statements.

APIs and webhooks

Create cases, receive status, push proof and pull reports from your own systems. One integration surface for airlines, platforms and providers.

Operational control

Live station views, exception queues, SLA countdowns and escalation rules for operations teams.

Illustration of the Chain-of-custody timeline view, with fictional data. A capture from the demo tenant replaces it.
Illustration of the Proof of handover and delivery view, with fictional data. A capture from the demo tenant replaces it.
Illustration of the Passenger communication flow view, with fictional data. A capture from the demo tenant replaces it.
Illustration of the Reporting and financial closure view, with fictional data. A capture from the demo tenant replaces it.
Illustration of the Field operations mobile app view, with fictional data. A capture from the demo tenant replaces it.

What HalaBag is not

Not a tracing system

WorldTracer remains the system of record for the tracing file. HalaBag reads it and writes status back.

Not a baggage handling system

HalaBag does not sort or screen bags. It orchestrates what happens once a case exists.

Not a courier

Physical movement is performed by integrated handlers, 3PLs and operators. HalaBag allocates, measures and settles that work.

Deployment

Standard implementation

Tenant setup, station configuration, source-system connection, provider onboarding and go-live checks follow a repeatable model. New stations are configuration.

Hosting and data

Cloud-hosted with data residency options. Role-based access, audit logs and per-tenant isolation.

Languages

Operations consoles and passenger channels in Arabic and English, with further languages on request.

How it is bought

Platform licence

A recurring fee scaled to operational size. This is software.

Per-case platform fee

A usage fee per case or item processed through the platform. This is software.

Technology-enabled orchestration

Where HalaBag also manages the operation on your behalf, coordinating providers and outcomes, that is a managed service and priced as one, with physical delivery passed through at cost.

Distribution

Where partner services are sold through the platform, HalaBag earns a distribution margin. Described as such.

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.

Request a demo