Ground Handlers

Flight manifest to cargo release in seconds

Parse flight manifests, match Delivery Orders to AWBs, and populate your WMS instantly — before the cargo is offloaded.

The Problem

35+ minutes delay between arrival and WMS entry

Before: Manual Manifest Processing

  • Flight manifests with 20+ HAWB lines manually keyed into WMS — piece count, weight, shipper/consignee, SPH codes all entered by hand
  • SPH codes like EAP (perishable), DG (dangerous goods), and AVI (live animals) are missed in manual reading
  • Each airline uses a different manifest format — staff must recognize 8+ layouts
  • Delivery Orders pile up during peak hours — consignees wait for cargo even though shipments have already arrived
  • DG (dangerous goods) shipments missed in manual reading cause regulatory violations and safety incidents
35 min
average delay per flight between arrival and WMS entry

After: KabyTech Automation

  • Flight manifest parsed instantly — all HAWB lines extracted with shipper, consignee, pieces, weight, and SPH codes
  • Delivery Orders auto-matched to parent AWBs — cargo release authorized immediately
  • WMS populated before forklifts reach the cargo — zero gap between arrival and system visibility
  • DG shipments auto-flagged — EAP, DGR, AVI, and all SPH codes trigger correct handling protocols
  • ULD breakdown data captured in real time — piece-level tracking from aircraft to warehouse bay
<2 sec
per manifest line processed
Flight TG0671 — Manifest Pipeline
Step 1 — Flight Arrival
TG0671 BKK→NRT
42 HAWB lines · 3 ULDs · 2,840 KG
RECEIVED
▼
Step 2 — Manifest Parse
42 shipments extracted
SHP, CNE, PCS, WGT, SPH — all lines parsed
PARSING
▼
Step 3 — D/O Matching
39 matched ✓ 3 DG hold
Cargo release authorized for 39 shipments
MATCHED
▼
Step 4 — WMS Populated
BAY A3-A7 ASSIGNED
Forklifts dispatched · consignees notified
DONE
The Solution

Flight manifest to cargo release in seconds

KabyTech reads the entire flight cargo manifest the moment it arrives — every HAWB line is extracted with piece count, weight, shipper/consignee, goods description, and special handling codes.

Delivery Orders are auto-matched to parent AWBs. When the D/O and manifest data align, cargo release is authorized automatically. DG shipments and special cargo are flagged for handler review.

Manifest parsingD/O matchingSPH code extractionULD breakdown trackingDG auto-flagging8 carrier formats
Cargo Release Status
FlightTG0671✓
Total Shipments42✓
Released39 shipments✓
DG Hold2 (DGR review)✓
SPH: EAPCold Chain → Bay C1✓
SPH: DGRDangerous Goods → Hold✓
SPH: AVILive Animals → Bay D2✓
WMS StatusALL POPULATED✓
42 shipments processed · 0 SPH codes missed
Key Capabilities

Never miss a special handling code again

KabyTech extracts every SPH code from the AWB and manifest — EAP, PIL, DRY, AVI, DGR, VAL, and more. Each code triggers the correct handling protocol in your WMS automatically.

Delivery Orders are auto-matched to their parent AWBs. When the D/O and manifest data align, cargo release is authorized automatically. DG shipments and special cargo are flagged for handler review.

EAP cold chainDGR dangerous goodsAuto WMS routingCargo release authDG flagging24/7 operation
Results

Impact at Suvarnabhumi cargo terminal

A ground handling agent at Don Mueang International Airport deployed KabyTech for manifest and D/O processing and achieved these results within 45 days.

1,200+
Shipments processed per day
Zero
Manual WMS entries
8
Carrier formats supported
<2s
Per manifest line

Ready to automate your cargo dock operations?

Book a demo with your actual flight manifests. See parsed data populate your WMS in real time — with SPH codes flagged automatically.

Book a DemoView API Docs