Shipment tracking milestone map template
Map each inbound shipment milestone from purchase order to put-away, with its source, EDI message or event, owner, deadline and exception rule.
Plan a tracking project
Worksheet
The rows are a fictional example. Edit any cell, add or remove rows, then download a CSV to share with your team. Nothing leaves your browser.
| Milestone | Source system or party | Message or event | Owner | Expected by | Exception rule | Remove |
|---|---|---|---|---|---|---|
Shipment tracking software is only as useful as the list of events it is told to expect. A milestone map writes that list down: each step a shipment passes through, where the signal for it comes from, who is responsible, when it is due and what counts as a problem. The template above starts with a fictional inbound purchase order, from release to stock available in the warehouse.
How to use the template in a project
- Pick one flow. Inbound purchase orders, transfers between sites and outbound customer orders have different milestones. Map each separately.
- List the milestones in order. Each must be an event that someone or something records. “In transit” is a state; “picked up by carrier” is an event.
- Name the source: the system or party the signal comes from.
- Name the message or event: the EDI transaction set, API event, scan or portal action that carries it.
- Assign an owner by role, not by team.
- Set the expected time relative to a reference point, such as Day 0, the ship date or the dock appointment, so one rule works for every shipment.
- Write the exception rule as a condition a system can test.
- Review the map with the people who would receive each alert, then download the CSV and attach it to the requirements.
The example, row by row
The first four rows use X12 EDI transaction sets. Their names, as X12 lists them:
| Set | X12 name | Role in the example |
|---|---|---|
| 850 | Purchase Order | The buyer releases the order to the supplier |
| 855 | Purchase Order Acknowledgment | The supplier confirms or changes quantity and date |
| 856 | Ship Notice/Manifest | The supplier’s advance ship notice before pickup |
| 214 | Transportation Carrier Shipment Status Message | Pickup and in-transit status from the carrier |
Many suppliers and carriers send these through a portal or an API instead, which is why each row says “or”. The remaining rows come from your own operation: an estimated arrival from the carrier or a visibility feed, a check-in scan at the gate, the receipt against the ASN in the WMS, and the put-away confirmation that makes stock available.
Look at the exception rules. “No acknowledgment in 2 business days” has a reference point (order release), a time limit and a missing event. “Quantity or date changed” is a different kind of exception: the message arrived, but its content differs from the order. Good maps need both kinds. “Not available after 24 hours” catches stock that was received but never put away, which is invisible to most carrier tracking.
What good looks like
- Every source exists today, or there is a decision to create it. If only some suppliers send an 856, record the share and the fallback for the rest.
- Every exception rule names a condition, a time limit and an owner. “Late shipment” is not a rule. “No pickup event by end of ship date, alert the logistics coordinator” is.
- Manual events are included, such as gate check-in, not only electronic messages.
- Fewer milestones with clear rules beat many milestones no one watches.
- Timings are tested against history. Check a month of real shipments before you set alert thresholds, or the first week will produce hundreds of false alarms.
Who should fill it in
- The logistics coordinator drafts the flow and the timing.
- The buyer and the receiving lead confirm the purchase order and dock steps.
- The EDI or IT contact confirms which partners send which messages, and in which version.
- The operations manager signs off the owners and the alert rules.
From map to software
The finished map becomes the milestone model and exception rules in the requirements. Each source becomes a row in the integration inventory worksheet, and each exception rule becomes a test in the UAT test plan. The example project follows one fictional inbound shipment through the same steps, and shipment tracking software describes how the tracking itself is built around your ERP, WMS and TMS.
Scope your project.
Tell us what you need to track, which systems you run and when it has to work. We reply with questions or a time to talk.