Transport Order
A transport order is a system task that says move this load from a source location to a destination. In ERP and warehouse stacks it often appears as a warehouse task, transfer order, or drive order created from WMS, EWM, production, or inventory postings. A classic forklift guidance system sits on that pool: it prioritizes orders and shows them on a forklift terminal until the driver confirms pickup and drop with a scan or status tap.
Plant teams care because a closed transport order proves the booking chain, not the meters (feet) the truck actually drove. Without continuous location, empty loops between confirmations stay invisible. An IoT material call-off into twinzo AOS can create a claimable job from a floor event, and tracked movers can add travel time and distance to the same story.
Key Components
Source and destination: Named bins, staging points, or production stations in master data.
Material and quantity: What must move for the posting to close.
Priority and due time: How the guidance pool ranks the job.
Confirmation: Pickup and drop acknowledgements that close the ERP or WMS state.
Applications in Manufacturing and Logistics
Warehouses use transport orders for putaway, picking, and replenishment. Factories use them for production supply when ERP knows the requirement. Empties, scrap, and ad-hoc hops often never become transport orders at all, which is why radio still runs beside the system.
Benefits and Challenges
The benefit is auditable inventory movement. The challenge is mistaking order status for floor truth. Vendors themselves note that SAP-side guidance can run without localization, using planned path networks and confirmations. Measured travel needs a location stream on the vehicle.
Related Terms
Forklift guidance system, WMS, AOS, material call-off, RTLS.
Frequently Asked Questions
Is every AOS work order a transport order? Not in the SAP sense. AOS work orders are claimable floor jobs. They may later post into ERP, but they can start from IoT or human events that never waited for a warehouse task.
Does confirming a transport order prove empty travel was low? No. Confirmation proves the booking. Empty share needs path history.
Can FGS and AOS coexist? Yes, if scopes stay clear: ERP-state warehouse moves versus event-driven hall pull with tracked movers.