Planning & Execution Interfaces
6 min
once your master data is in place, you're ready to begin transport operations this stage involves creating orders, planning and grouping them into loads, attaching invoices, and then tracking those shipments from dispatch through to final delivery in transportone, this lifecycle is divided into two phases planning your erp sends transport orders and invoice details to transportone tms then prepares loads, assigns transporters, and gets loads ready for dispatch execution after dispatch, tms tracks real time progress and sends updates back to your erp once delivered, your system confirms completion by submitting proof of delivery your erp’s role is to send us complete and accurate order data provide invoice details (if needed) share proof of delivery back once the shipment is completed in return, tms will send back real time updates about the shipment status, so your team stays informed without needing to chase anyone the apis in this section are used daily to keep your erp and logistics operations in sync these apis form the core integration between your erp and transportone — keeping both systems in sync throughout the transport journey initiate planning planning apis are used to prepare loads before dispatch your erp pushes order data, initiates load creation, and shares invoice documents this ensures that transportone has all required information to plan and allocate transport effectively order order api send transport order data from your erp to transportone https //docs1 getos1 com/explore all apps/order creation material invoice api material invoice api send material level invoice data from erp to transportone before dispatch learn more execution execution starts once a load is prepared or dispatched this phase ensures that loads are tracked, delivery is confirmed, and order statuses are updated in your erp this includes both pre dispatch execution (such as transporter assignment and vehicle allocation) and post dispatch tracking (such as delivery confirmation and pod) load updates api load updates api stay updated as your load moves through events like dispatch, facility arrival, unloading, and delivery transportone automatically sends live updates to your erp whenever these events occur https //docs1 getos1 com/explore all apps/load updates proof of delivery api proof of delivery api after goods are delivered, your erp or transporter submits a delivery confirmation and related documents https //docs1 getos1 com/explore all apps/submit pod order updates api order updates api receive notifications when the status of an order changes in transportone, such as reassignment, delay, or removal from a load https //docs1 getos1 com/explore all apps/order updates see also https //docs1 getos1 com/tms api ref/list plan orders view the complete api reference file including required endpoints, requests, responses, parameters what’s next? after delivery is complete, sync freight invoices and payment statuses to close the transport lifecycle
