Acceptance, the way it should work
Scan the AWB barcode. Skidd pulls the FWB, displays the canonical model with shipper, consignee, pieces, weight, special handling codes, and any inbound MVT/FSU history. The screen shows you what the airline expects. You verify against what’s in front of you.
If pieces match, weight matches, SHC codes match — press A to accept. The FSU/RCS fires to the carrier in the same keystroke. Storage clock starts based on the airline’s configured free period for that direction.
If something doesn’t match — piece count short, weight outside tolerance, missing dangerous-goods declaration — Skidd flags it, attaches your operator id and timestamp, and routes the shipment to the supervisor approval queue. You don’t need to chase anyone; the exception is already in front of the right person.
Lanes, not lists
The Acceptance view splits your work into four lanes: Expected, On-hand, Accepted, Held. Each lane filters by status, so you’re never looking at finished work to find the next thing to do. Dock supervisors see the same lanes filtered to their dock.
Keyboard, not mouse
| Key | Action |
|---|---|
| A | Accept the current shipment |
| R | Receive (transition to RCS) |
| C | Clear security (FPS) |
| B | Build up into a ULD |
| D | Deliver |
| T | Tender (back-to-back rare cases) |
These aren’t toy shortcuts. They map to IATA state transitions, get audit-stamped with your operator id, and emit the right message to the airline.
What you stop doing
- Re-typing AWB numbers between systems
- Writing discrepancies on printouts that get lost
- Radioing the dock supervisor for status updates the system could broadcast
- Looking up the airline’s free-period rule from a shared drive