Shipment requests hold the demand.
Each request can carry many drops and item rows without exposing operators to raw IDs.
Transport Management System
Plan every drop through the real route.
Model shipment requests, hub legs, dispatch, tracking, handoff proof, and POD in one operating view.
Route plan preview
SR-202501-00042
Route tree
1
Jakarta origin warehouse
CGK-01All drops staged for trunk loading
2
Hub Cirebon
HUB-CBNSplit final-mile legs from custody transfer
3
Bandung B1 customer site
BDG-B1Final POD required before request closes
4
Bandung B2 customer site
BDG-B2Drop can be replanned under same request
Leg dispatch
Vehicle
B 9234 KXR
Driver
Agus Pranata
Leg
Leg 2
Monitoring
Drop SLAAt risk
Vehicle GPSLive
1
Parent shipment request carrying demand, schedule, and aggregate load.
12
Destination drops tracked individually from planning through POD.
4
Shipment legs assigned one vehicle and one driver per movement.
Built around how freight actually moves.
The system separates demand, route structure, execution, and final proof so operators can see the next valid action.
Dispatch belongs to one leg.
Vehicle and driver assignment happens per shipment leg, not against the whole request.
Proof follows custody.
Hub handoff proof and final POD stay attached to the drops they actually verify.
Proof chain without hidden handoffs.
Operators can follow loading, hub transfer, route progress, and final POD without guessing which document closes the work.
Loaded at origin
Recorded against the carried drop
09:20
Handoff at Hub Cirebon
Recorded against the carried drop
12:45
POD received at Bandung B1
Recorded against the carried drop
16:10
Open the workspace when the route needs action.
Invited teams sign in with Clerk and continue from the right role: operations desk for admins, driver workspace for drivers.