GenFrontier homeScope a project
Menu
Filed under
Deliver toTransportation, receiving and customer service leads who answer "where is it?"

Shipment tracking software, from PO to delivery

One milestone model for every shipment, fed by the events your carriers, suppliers and warehouse already produce, with rules that alert a named person when a shipment goes off plan.

Map your tracking milestones
services / shipment-tracking-software
A paper airplane folded from a blank lined form flies across the page, leaving a dotted red trail marked with small evenly spaced ticks

Most tracking problems are not a missing map. They are a missing agreement about what “shipped” means, and status data that arrives from five places in five formats. Purchasing watches the supplier’s email, transportation watches the carrier portal, receiving watches the yard, and customer service calls all three. We build a tracking layer that collects those events, puts them on one milestone model and tells the right person when a shipment goes off plan.

The milestone model

A milestone is a point in a shipment’s life that someone cares about and that some event can prove. We write the model with your team before anything is built, one row per milestone, so that “in transit” means the same thing on every screen and in every report.

Milestone Event that proves it Typical source
Ordered Purchase order released ERP, or an X12 850 Purchase Order from a customer
Confirmed Supplier confirms quantities and ship date X12 855 Purchase Order Acknowledgment, supplier portal, or keyed from email
Ship notice received Cartons, pallets and SSCCs listed X12 856 Ship Notice/Manifest
Tendered Load offered to and accepted by a carrier X12 204 and 990, or your TMS
Picked up Carrier pickup status X12 214, carrier API
In transit Location, terminal or delay updates X12 214, carrier API, visibility-platform feed
Arrived Gate check-in or dock door assigned Yard or gate scan
Received Receipt posted against the PO WMS receipt
Delivered Proof of delivery on an outbound order Carrier API, X12 214, driver app

Each row also records when you expect the milestone, which system owns it and what happens if it is late. You can draft your own version with the tracking milestone map.

Where the events come from

We build the interface to each source you already have. There is no connector catalog here: each interface is built for your carriers, partners and systems, and listed in the integration inventory.

  • EDI from carriers and suppliers. The X12 214 Transportation Carrier Shipment Status Message carries carrier milestones. The 856 tells you what is coming before it ships.
  • Carrier APIs. Many parcel and LTL carriers offer tracking APIs. We handle credentials, polling or webhooks, and the carrier’s rate limits.
  • Visibility-platform feeds. If you already subscribe to a visibility platform, its feed becomes one more source. We connect to it rather than replace it.
  • Yard and gate scans. Check-in at the gate and the dock door assignment close the gap between “delivered” in the carrier’s system and “on our dock”.
  • WMS receipts. The receipt is the event that closes an inbound shipment and starts put-away.
  • A manual entry screen for the events nobody sends, such as the supplier who confirms ship dates by email.

Events arrive late, twice and out of order. The tracking layer keeps both the time an event happened and the time it was received, never lets an older event overwrite a later milestone, and flags conflicts instead of guessing. Two carriers can report the same delivery with different status and reason codes, so a mapping table from each source’s codes to your milestones is part of the deliverable.

ETA and exception rules

The ETA starts from the planned dates on the PO or tender. It updates when a carrier sends its own estimate and when a milestone lands early or late against the lane’s usual transit time, which the system measures from your own history. The rules are written down in plain language, so a planner can see why an ETA moved.

Exceptions are conditions with an owner and a queue, for example:

  • No pickup status two hours after the pickup appointment.
  • Ship notice quantity differs from the PO by more than the agreed tolerance.
  • ETA moves past the receiving appointment or the customer’s must-arrive-by date.
  • No status update for a set number of hours while in transit.
  • Delivered by the carrier, but no WMS receipt by the end of the shift.

Each exception closes with a reason code, so you can see later which suppliers, carriers and lanes cause the most work.

Example (fictional). A distributor orders 24 pallets of item EX-20118 on PO EX-4471. The supplier’s 856 lists 22 pallets. The tracking layer opens a short-ship exception for the buyer before the truck leaves the supplier, and the receiving screen shows 22 expected SSCCs instead of 24. When the carrier’s 214 reports a delay, the ETA moves past the receiving appointment and the dock scheduler gets a second exception to rebook the door.

Customer-facing status

Customers and your own customer service team see milestone names in plain language, not carrier codes. You decide which milestones and fields each audience sees. Lookups work by the references people actually have: order number, PO number, bill of lading or PRO number. Depending on the customer, we build a status page, email notices on chosen milestones, or an outbound 214 or API feed for customers who want the data in their own systems.

Master data that tracking depends on

Tracking is only as good as the references that tie events together. During requirements analysis we name the system of record for each of these:

  • PO and order numbers carried on the ship notice, bill of lading and carrier tender.
  • Carrier identifiers and service levels.
  • Location identifiers for ship-from, ship-to and dock, ideally GS1 Global Location Numbers (GLNs).
  • SSCCs on pallet labels that match the SSCCs in the 856. Our barcode and labeling work covers the label side.
  • Items and units of measure, so that 22 pallets and 1,320 cases describe the same shipment.

In our view, any tool placed on top, including the AI features now sold with visibility platforms, depends on these same references being right in your own systems first.

What you receive

  • The milestone model, exception rules and status code mapping tables, signed off by your team.
  • Interfaces to each event source, tested with each carrier and partner.
  • Exception queues, ETA logic and the customer-facing status views.
  • Source code and configuration, delivered at handover. Ownership and licensing terms are set out in each statement of work.
  • An integration runbook and role guides from our documentation service.

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.