A customer calls to ask where an order is. Someone in customer service opens the ERP, then messages the warehouse, then emails or calls the carrier, and finally answers from whatever was learned last.
This guide answers one executive question: what information must connect shipment planning, carriers, freight execution, delivery events, and customer commitments? The answer below is a set of recommendations for defining that information, not a report of how any particular manufacturer or system works. The only external research we cite concerns courier delivery planning, and we use it only to illustrate the difference between a plan and what actually happens.
The problem: plans, events, and promises live in different places
The plan says what should move, when, and how. Execution events say what a carrier or warehouse did. The customer commitment says what the manufacturer told the buyer.
In a study of a courier delivery problem, University of Southern California researchers describe a setting where delivery requests become available each morning, and where the locations of customers are known but not whether a particular customer will request delivery on a given day. The same report notes that vehicles may wait if they arrive early, which might cause an earliness penalty, and that arriving after the latest start time may incur a lateness penalty. The study is a routing model for one courier operation, not a standard for manufacturers.
We recommend treating three consequences as diagnostic questions, not as findings about your business. Does customer service spend time asking carriers for status? Can a partner see more than it should, or can your team not see what a partner knows? Do decisions about expediting, rebooking, or notifying the customer wait on someone assembling the facts?
What makes this hard
Several constraints shape any answer.
- Data ownership. The manufacturer, the carrier, and the customer may each hold part of the record. Decide who is the source of each fact, who stewards the record, and who may change it.
- Access control. Decide which records each outside party needs to see, and define those permissions before opening any exchange.
- Integration capacity. Your team and your partners can support only so many connections. Confirm what each carrier can send.
- Operating change. Dispatchers, customer service staff, and billing clerks will need to work from the shared record instead of their own side channels.
The systems that may be involved include the ERP, the warehouse management system (WMS), a transportation management system (TMS), carrier systems, electronic data interchange (EDI) or application programming interface (API) connections, telematics, and a customer portal. Identify where each fact originates in your own environment.
We recommend defining the following in plain business terms before choosing any technology.
Stages of transportation work. Separate planning, tendering (offering the load to a carrier), execution, tracking, freight settlement, and proof of delivery. Each stage may produce different records and may have a different owner; decide who owns each.
Identifiers. Define shipment, load, stop, package, carrier, appointment, and event identifiers, and say which one links to the customer order. If a carrier's reference cannot be mapped to your shipment, no integration can place its events on the right commitment.
States. Agree what planned, estimated, tendered, accepted, departed, delivered, and exception mean, who may set each one, and what evidence moves a shipment from one to the next. Keep an estimate separate from a confirmed event, so that a promised time and an observed time can be compared. We recommend recording the plan and the events that follow it separately.
Downstream use. Decide how carrier evidence feeds customer service answers, invoicing, claims, and carrier performance management. A delivery event that reaches only the tracking screen leaves billing and claims to rebuild it.
Approaches to compare
Compare these against the identifiers and states above.
- Extend existing systems. Add fields, statuses, or workflows to the ERP, WMS, or TMS you already run. This keeps your team within familiar tools, but the extension is only as good as the partner data that reaches it.
- Targeted integration. Connect specific carriers or customers by EDI, API, or files for the events that matter most. Each connection adds a link someone must monitor and support.
- Reporting or portal patterns. Give customer service and partners a permissioned view of shipment status.
- No platform change. Tighten definitions, ownership, and exception routines with the tools you have. Software effort may be lower while process effort remains.
- Governed transformation or modernization. Consider a broader program only if the assessment shows that your records, systems, and ownership cannot support the commitments you make.
Tradeoffs to weigh
The choice turns on effort, data quality, ownership, permissions, adoption, and support. A portal adds a permission surface you must govern. Extending existing systems avoids new tools but inherits their limits. A narrow integration covers only the carriers it connects; others may remain on manual follow-up. We recommend checking whether undefined states or unclear ownership are the main defect before deciding that a technical change is needed.
Plan variability also has a cost. In the courier study, researchers found in simulation that their approach improved route similarity and lateness penalty at the expense of increased total time spent when compared with scheduling each day independently. That result describes one routing method on one courier problem. It does illustrate a general design point: a stable plan and a responsive plan pull against each other, so decide which matters more for your commitments. The same report observes that similar daily schedules can minimize the cost of re-planning every day, which is one reason to separate a standing plan from daily adjustments.
Next steps and applying this to your operation
Use a short sequence with your leadership and operations team.
- Trace one late shipment. This may help locate where the connection is missing.
- Write the state definitions. For planned, estimated, tendered, accepted, departed, delivered, and exception, record who sets the state and what evidence is required.
- Fix the identifiers. Confirm which identifier ties a carrier event to a customer order, and test whether your top carriers can supply it.
- Assign decisions. Name who can act on an exception, who may speak to the customer, and who approves access for outside parties. These may be different people.
- Choose the smallest sound response. Match the gaps you found to the approaches above. If definitions and ownership are the gap, start there before any integration.
- Connect the back end. Check that delivery evidence reaches invoicing, claims, and carrier performance review.
These steps are our recommendations, so test them against your own records, partners, and systems.
