Six B2B freight exceptions are worth a rule: a missed pickup, a rejected tender, an ETA that moves past the receiver’s appointment, dwell beyond free time, over, short or damaged (OS&D) freight at delivery, and a missing proof of delivery. Each needs a detection signal, a threshold, one owning role, a response time and closing evidence. You set most response times from your own customer commitments, but some clocks are set by others. Old Dominion’s rules tariff requires notice of concealed damage within five business days of delivery, and federal law bars the carriers it covers from allowing less than nine months to file a claim.
This field note is written for truckload and LTL freight between businesses, not parcel deliveries to homes. It gives the catalogue, ties each exception to X12 214 status codes, and sets out owners, response times and the evidence that closes each case.
What counts as a shipment exception in B2B freight
A shipment exception is a deviation from the shipment plan that needs a decision from a named person within a set time. A status update is not an exception. A notification is not an exception either, unless someone owns the decision it triggers.
The distinction matters because tracking systems generate far more events than people can read. A load that departs the pickup on time produces several status messages, none of which needs a person. A load that is still at the shipper two hours after its pickup appointment produces no message at all, and that silence is the exception.
Why parcel exception advice does not fit freight
Much of the published advice on delivery exceptions is written for parcels to consumers: failed delivery attempts, wrong addresses and “where is my order” emails. B2B freight differs in four ways:
- Appointments. Distribution centers and plants receive by appointment, so a late truck can lose its slot and wait a day.
- Tenders. Truckload freight is offered to a carrier, which can decline. A rejected tender is an exception before the freight moves.
- Dwell and detention. Time at the dock costs money under carrier tariffs and contracts, on both sides of the shipment.
- Claims. OS&D on a pallet of goods has formal notice and filing clocks, and the evidence collected at the dock decides the outcome.
The five fields every exception rule needs
Write each rule with the same five fields, and refuse to switch on any rule that lacks one:
- Detection signal: the event, or the missing event, that triggers it.
- Threshold: the time or quantity at which it becomes an exception.
- Owner: one role per shift, not a shared inbox.
- Response time: how fast the owner must acknowledge, and how fast the case must be resolved.
- Closing evidence: the record that proves the case is closed, with a reason code.
Most exceptions are missing events
Four of the six exceptions are triggered by something that did not happen: no pickup event, no 990, no departure from the dock, no delivery receipt. A system can only detect a missing event if it knows when the event was due. That means the exception rules depend on reference data that often lives outside the TMS:
- Pickup and delivery appointments, from your dock scheduling tool or the customer’s portal.
- The tender response window, from your routing guide.
- Free time for each carrier and each facility, from tariffs, contracts and rate confirmations.
- The carrier’s estimated delivery date, and the customer’s must-arrive-by date from the order.
Collect that data before switching on the rules. A rule with no due time will either never fire or fire on everything.
The six exceptions at a glance
The catalogue below is a starting set for shippers and 3PLs moving truckload and LTL freight. Thresholds and response times are starting points to adjust after a month of data, not industry standards.
| Exception | Detection signal (214 codes, 004010) | Starting threshold | Owner | Response time | Closing evidence |
|---|---|---|---|---|---|
| Missed pickup | No AF (departed pickup with shipment); reason AY (missed pick-up) | Truckload: 2 hours after the pickup appointment. LTL: end of the pickup day | Transportation planner | Acknowledge in 30 minutes; new pickup time the same day | Pickup event, or a rebooked pickup with reason code |
| Tender rejection | 990 with an action code other than A (accepted), or no 990 within the routing-guide window | On receipt, or at the end of the response window | Transportation planner | Re-tender within 1 hour | Accepted 990 from the next carrier |
| ETA past the appointment | New estimate (AG or X2) later than the appointment (AB or X9) | ETA beyond the appointment's grace window | Dock scheduler (inbound); customer service (outbound) | Rebook or notify within 1 hour | Rebooked appointment or customer acknowledgment |
| Dwell beyond free time | Arrival (X3, X1) with no departure (AF, CD) or completion (D1) | The free time in the contract or tariff | Facility manager at that dock | Act before free time ends | In and out times, and a detention charge approved or disputed |
| OS&D at delivery | A9 (damaged), A7 (refused), reason S1 (delivery shortage); receiving count differs | Any discrepancy noted at delivery or found later | Receiving lead (inbound); customer service (outbound) | Notice to carrier the same day; concealed damage within the carrier's limit | Annotated delivery receipt, photos, claim number |
| Missing proof of delivery | D1 (completed unloading) with no delivery receipt on file | 2 business days after delivery | Billing or accounts receivable | Request within 1 business day of the threshold | Signed and dated delivery receipt stored on the order |
Pre-shipment supplier milestones, such as a missing purchase order acknowledgment or a late ship notice, are a separate catalogue. Our note on inbound PO visibility covers them.
Exceptions to add once the six are working
The six above are a starting set. Once they run cleanly, these are the usual next additions, each with its own five fields:
- Attempted or refused delivery. 214 status AH, “Attempted Delivery”, or A7, “Refused by Consignee”, sometimes with reason B1, “Consignee Closed”. The owner is customer service, because the fix is often at the receiver.
- Held pending appointment. Reason HB, “Held Pending Appointment”, on LTL freight at the destination terminal. It can arise when the receiver’s appointment rule is not on the bill of lading.
- Stale data feed. No events at all from a carrier’s API or 214 connection for longer than normal. This is an integration exception, owned by whoever supports the interface, and it should fire before the shipment exceptions that depend on it go quiet.
- Reconsignment or address change. A changed destination after pickup, which may change the delivery date and the charges.
Add them one at a time, and only when someone has the time to own them.
Missed pickups and rejected tenders
These two exceptions happen before the freight moves, so they are the cheapest to fix. A same-day response can still protect the delivery date; a next-day response may not.
Missed pickup
The detection signal for a missed pickup is the absence of a pickup event. In a 214, the X12 shipment status message, the carrier reports pickup as status AF, “Carrier Departed Pick-up Location with Shipment”. It may first send X3, “Arrived at Pick-up Location”. When a carrier reports a missed pickup itself, the 004010 reason code is AY, “Missed Pick-up” (code meanings from Stedi’s X12 reference, a secondary source). The later release 8010 adds finer reasons, such as NF, “No Freight Available At Time Of Pickup”, and SN, “Shipment Not Ready”.
Those reason codes matter because a missed pickup is not always the carrier’s fault. If your own dock was not ready, the fix is in the warehouse, not the carrier scorecard. Record which side caused it every time.
Set the threshold by mode. When a truckload pickup is booked to an appointment, two hours past the appointment without a pickup event is a sensible start. An LTL pickup booked for a window during the day is better judged at the end of the pickup day. The owner is the transportation planner who booked the load, and the action is to get a confirmed new pickup time or move the load to another carrier.
Tender rejection
A tender rejection is a carrier declining a load offered to it. In EDI, the shipper sends a 204 Motor Carrier Load Tender and the carrier replies with a 990 Response to a Load Tender (X12 transaction set list). The 990’s B1 segment carries a reservation action code. In the 004010 release, A means “Reservation Accepted”. Other codes include B, “Conditional Acceptance”, and D, “Reservation Cancelled”. Each carrier’s 990 guide says which code it sends to decline, but any code other than A needs a look.
Two signals trigger this exception: a 990 with any action code other than A, and no 990 at all within the response window in your routing guide. The second is easy to miss, because nothing arrives. Your TMS or tracking layer has to start a clock when the 204 is sent.
The owner is the planner, and the response is to re-tender to the next carrier in the routing guide. Close the case when an accepted 990 arrives. Track rejections by carrier and lane; repeated rejections on one lane can point to a rate or schedule problem on that lane rather than a problem with one carrier.
Example (fictional). A 3PL tenders load EX-5521 to its primary carrier at 9:00 a.m. for a 2:00 p.m. pickup the same day. Its routing guide allows two hours for a response. At 11:00 a.m. no 990 has arrived, so the rule opens a tender exception for the planner on shift. She calls the carrier, learns the tender was never processed, and re-tenders to the backup carrier, which accepts at 11:40 a.m. The case closes with reason code “no response from carrier” and the accepted 990 attached.
ETAs that slip past the receiving appointment
An ETA exception fires when the latest estimate of arrival moves past the receiver’s appointment by more than the grace the receiver allows. The point is to act while there is still time to rebook the slot or warn the customer, not after the truck is turned away.
In a 214, estimates arrive as status AG, “Estimated Delivery”, or X2, “Estimated Date and/or Time of Arrival at Consignee’s Location”. Appointments arrive as appointment status AB, “Delivery Appointment Date and/or Time”, or X9, “Delivery Appointment Secured on This Date and/or Time”. A visibility platform may supply its own predicted ETA as well. Compare them against the appointment held in your own dock schedule or order system, because that is the time that matters.
Why truckload ETAs jump by ten hours or more
Truckload ETAs can jump rather than drift, and the hours-of-service rules are a common reason. Under 49 CFR 395.3, a property-carrying driver may not drive without first taking 10 consecutive hours off duty. The driver may then drive up to 11 hours, but not after the 14th hour since coming on duty. A 30-minute break is required after 8 hours of driving.
So a driver who loses two hours waiting at a shipper can run out of driving time short of the destination. The ETA then moves by at least the 10-hour rest. Under 49 CFR 395.1(b), a driver who meets adverse driving conditions, such as snow, fog or unusual road conditions not known before the trip, may drive up to two extra hours to complete the run. That allowance is narrow, and it cannot be planned on.
Example (fictional). A truckload of item EX-20118 has a receiving appointment at 6:00 a.m. Tuesday, about 600 miles from the shipper, or roughly 11 hours of driving. The driver came on duty at 6:00 a.m. Monday, drove an hour to the shipper, waited three hours and left at 10:00 a.m.
The 14-hour window ends at 8:00 p.m. Monday. Between 10:00 a.m. and 8:00 p.m. the driver can drive about 9.5 hours, with a 30-minute break, and is still roughly 80 miles out when the window closes. After a 10-hour rest, the driver can leave at about 6:00 a.m. Tuesday and arrive near 7:30 a.m. The ETA exception fires Monday afternoon, when the platform’s prediction crosses 6:00 a.m. The dock scheduler moves the appointment to 8:30 a.m. before the receiving crew is planned.
Grace windows and the receiver’s rules
Receivers decide how late a truck can be before it loses its appointment, and that grace window is the threshold for this exception. Hold it per facility, not as one company-wide number. A plant that unloads by appointment with a 30-minute grace window needs an earlier alert than a cross-dock that works trucks as they arrive.
When a carrier sends an appointment status with X9, the appointment has been secured, and that time should replace any earlier planned time in your records. Keep the history, because a dispute about a missed appointment often turns on which time each side was working to.
Who owns an ETA exception
Ownership depends on direction. On inbound loads, the dock scheduler owns it, because the decision is whether to rebook the door and move labor. On outbound loads, customer service owns it, because the decision is whether and how to tell the customer and whether the order’s must-arrive-by date is at risk. The planner supports both when a recovery option exists, such as a team driver or a different carrier for the rest of the trip.
Dwell beyond free time at pickup and delivery
Dwell is the time a truck spends at a facility from arrival to departure. It becomes an exception when it approaches the free time allowed before detention charges start. The useful alert fires before free time ends, while someone can still get the truck loaded or unloaded.
The 214 can supply arrival and departure times: X3 “Arrived at Pick-up Location”, X8 “Arrived at Pick-up Location Loading Dock”, AF for departure from pickup, X1 “Arrived at Delivery Location”, X5 “Arrived at Delivery Location Loading Dock”, D1 “Completed Unloading at Delivery Location” and CD “Carrier Departed Delivery Location”. Release 8010 adds reason codes UG, “Driver Waiting to Pick Up”, and UH, “Driver Waiting to Unload”. At your own docks, your gate and yard records are better evidence than the carrier’s events.
How a carrier tariff defines free time
Free time is set by contract or tariff, so read yours. Old Dominion’s rules tariff ODFL 100-Q (effective April 14, 2025, updated October 5, 2026) shows how precise the rules can be. Under Item 502, for a trailer with tractor, time “will begin when the vehicle arrives at the Customer’s property”. It ends when loading or unloading is complete and the customer hands over a signed bill of lading or delivery receipt.
If an appointment was made, the clock starts at the appointment time, not before. If the carrier is more than 30 minutes late, one minute of free time is added for each minute it is late. Free time is set per vehicle by the number of shipments at the stop: 20 minutes for one shipment, rising by five minutes per shipment to 60 minutes for nine or more. Truckload contracts and broker rate confirmations set their own terms.
Example (fictional). A truck arrives at a distributor’s own dock at 7:40 a.m. for an 8:00 a.m. live unload. The carrier’s contract allows two hours of free time from the appointment. At 9:30 a.m. the yard system shows the truck still waiting for a door, and the dwell rule alerts the receiving supervisor with 30 minutes of free time left. She moves the load to the next open door, unloading finishes at 9:55 a.m., and the case closes with gate times attached and no detention due.
Owners and evidence for dwell
The facility manager at the dock where the truck is waiting owns the exception. At your own docks that is your shipping or receiving supervisor. At a customer’s or supplier’s dock, customer service or the buyer owns the conversation with that facility, because you cannot direct their labor.
Close each case with the in and out times from both sides and the decision on any detention charge: approved, disputed with evidence, or charged back to the party that caused it. Our note on detention and dwell time tracking covers how to measure dwell at your own docks well enough to settle disputes.
Over, short and damaged freight at delivery
OS&D means freight that arrives over the billed quantity, short of it, or damaged. It is the exception with the strictest outside deadlines, and the one where evidence gathered in the first hour decides the outcome months later.
Old Dominion’s glossary draws the key distinction. Noted damage is “damage discovered before or at the time of delivery of a shipment”. Concealed damage is “a damage to the contents of a package which is apparently in good condition externally”. A shortage is “when quantity received is less than that shown on the Bill of Lading”. The delivery receipt is the “document signed by the consignee verifying receipt of freight with any noted discrepancies”.
In a 214, OS&D may show up as status A9, “Shipment Damaged”, or A7, “Refused by Consignee”, or with reason S1, “Delivery Shortage”, or AK, “Damaged, Rewrapped in Hub”. More often your own receiving count is the first signal.
The clocks that start at delivery
Several deadlines start when the freight is delivered. Some come from federal law and regulation, and others from the carrier’s tariff. Check the tariff of every carrier you use, because the carrier’s limits can be shorter than you expect.
- Concealed damage notice. Old Dominion’s tariff requires notice of concealed loss or damage “within five (5) business days from the date of delivery”, and the carrier “must be allowed to perform a proper inspection”. Its claims FAQ adds that packaging must be kept until the claim is concluded.
- Claim filing. Under 49 U.S.C. 14706(e), a carrier may not allow less than 9 months for filing a claim, or less than 2 years for a civil action after it disallows a claim in writing. Old Dominion’s tariff uses nine months from delivery, or from the anticipated delivery date if the freight is lost.
- What a claim must contain. Under 49 CFR 370.3, a claim is a written communication that identifies the shipment, asserts the carrier’s liability and claims a specified or determinable amount of money.
- Carrier acknowledgment. Under 49 CFR 370.5, the carrier must acknowledge a claim in writing within 30 days of receiving it, unless it pays or declines within that time.
- Carrier decision. Under 49 CFR 370.9, the carrier must pay, decline or make a firm compromise offer within 120 days. If it cannot, it must report the claim’s status then and every 60 days after that.
What to record at the dock
A claim rests on the evidence gathered in the receiving lead’s first minutes with the freight. A short, fixed checklist helps every shift collect the same evidence:
- Photograph the trailer doors, the seal and its number before unloading, and the load as first seen.
- Count pallets and pieces against the bill of lading and the ship notice before signing.
- Write the specific discrepancy on the delivery receipt: how many pieces short or damaged, and what the damage looks like.
- Photograph each damaged pallet and its labels, then the damaged contents once opened.
- Keep the damaged goods and the packaging apart from good stock until the claim is settled.
- Record the carrier’s PRO or load number, the driver’s name if given, and the time, in the OS&D case.
The same checklist works for your customers. Sending it to them with outbound orders makes outbound claims easier to support.
Owners, response times and evidence for OS&D
On inbound freight, the receiving lead owns OS&D, because the evidence is on the dock. The response is immediate: note the shortage or damage on the delivery receipt before signing, photograph the freight and packaging, and quarantine the goods. If damage is found after the driver leaves, notify the carrier the same day where you can, and in any case inside the carrier’s concealed-damage limit.
On outbound freight, customer service owns the case, because the customer holds the evidence. Ask the customer for the annotated delivery receipt and photos on the day of delivery, and confirm who files the claim under your sales terms.
The case closes when the claim is filed with its claim number, or when the discrepancy is resolved without a claim (for example, a shortage found in a split shipment). Keep the claim open in your system until the carrier pays, declines or settles.
Missing proof of delivery
A missing proof of delivery is a delivered shipment with no signed delivery receipt on file. It looks minor until a customer disputes the delivery, short-pays the invoice or files a claim. Old Dominion’s glossary defines proof of delivery as “a properly signed and dated delivery receipt”.
The signal is a delivered event (D1, or “Delivered” in a carrier API) with no document attached after a set time. Two business days is a workable start. Carriers that expose documents by API make this easy to automate. Old Dominion’s Shipping API Integrations page, for example, lists a Document Retrieval API for “bills of lading, delivery receipts or delivery photos” by PRO number.
Dropped trailers need special handling. Old Dominion’s tariff (Item 784) makes the consignee responsible for returning delivery receipts within 72 hours of the trailer being spotted or 48 hours of unloading, whichever comes first. If they are not returned, the carrier may prove delivery from its own records. If you or your customers receive on dropped trailers, your POD rule needs that window built in.
The cost of a missing POD shows up later, in accounts receivable. When a customer short-pays an invoice and says the freight never arrived, the signed delivery receipt settles the question. Without it, the dispute turns into a trace with the carrier weeks after the event, when memories and photos are gone.
The owner is billing or accounts receivable, because the document protects the invoice. The case closes when the signed and dated delivery receipt is stored against the order, with any noted exceptions copied into the OS&D queue.
Who owns each exception
Ownership is the field easiest to leave vague, and the one that decides whether a rule helps. Assign each exception to a role, on each shift, with a named backup. Never assign it to a group mailbox.
| Exception | Owner | Supports | Escalates to |
|---|---|---|---|
| Missed pickup | Transportation planner | Shipping supervisor, when the cause is the dock | Transportation manager |
| Tender rejection | Transportation planner | Carrier sales contact | Transportation manager |
| ETA past appointment, inbound | Dock scheduler | Planner, for recovery options | Receiving or warehouse manager |
| ETA past appointment, outbound | Customer service | Planner, for recovery options | Customer service lead |
| Dwell beyond free time, own dock | Shipping or receiving supervisor | Yard or gate staff | Warehouse manager |
| Dwell beyond free time, other dock | Customer service or buyer | Planner | Account or purchasing manager |
| OS&D, inbound | Receiving lead | Inventory control | Warehouse manager |
| OS&D, outbound | Customer service | Claims administrator | Customer service lead |
| Missing proof of delivery | Billing or accounts receivable | Customer service | Finance lead |
Three rules keep ownership clear. First, one owner per exception at any moment, even when several people help. Second, the owner can close the case without permission, but must record the reason code. Third, if a case passes its response time without acknowledgment, it escalates automatically to the next role, not to everyone.
Handing a case from one owner to another
Some exceptions change hands. An inbound ETA exception owned by the dock scheduler may become an OS&D case for the receiving lead when the truck finally arrives with damage. Transfer the case with its history rather than closing one and opening another, so the timeline stays in one place. Never leave two open cases for the same problem with different owners; each will assume the other is acting.
Night shifts and weekends
Trucks move at night and on weekends, so some exceptions arise outside office hours. Decide which exceptions need a response outside office hours and who covers them. A dwell exception at your own dock at 2:00 a.m. belongs to the night shift supervisor; a missing POD can wait until Monday.
Setting response times you can meet
A response time is a promise from your operation to itself. Set it from the consequence of a late response, then check that your staffing can keep it. A response time that is missed every day teaches people that response times do not matter.
Use two clocks for every exception. Time to acknowledge is how long until the owner opens the case and takes it. Time to resolve is how long until the closing evidence is in place. Measure both from the moment the rule fires, not from when someone first noticed.
Group exceptions by what is at risk:
| Tier | What is at risk | Typical exceptions | Starting acknowledge time | Starting resolve time |
|---|---|---|---|---|
| 1 | A same-day pickup, appointment or customer commitment | Missed pickup, tender rejection, ETA past appointment, dwell near free time | 30 minutes | Same shift |
| 2 | Money with a hard deadline | OS&D, concealed damage | Same day | Within the carrier’s notice period |
| 3 | Money without an immediate deadline | Missing proof of delivery, detention invoice review | 1 business day | 5 business days |
These are starting figures for this article, not benchmarks. Review them after a month: count how many cases met each clock, and why the rest did not. If one exception type misses its clock every week, either the staffing, the threshold or the owner is wrong.
Measuring the exception process
Four numbers, reported monthly by exception type, show whether the process works:
- Exceptions per 100 shipments, by carrier, lane and customer.
- The share acknowledged within the response time.
- The share resolved within the response time.
- The split of cause codes: carrier, shipper, consignee or outside event.
Act on the cause split first. It tells you whether to talk to a carrier, change a dock process, or renegotiate a customer’s receiving rules.
Link response times to delivery performance
Exceptions exist to protect delivery performance. If you measure on-time in-full delivery, report it alongside exception response times. A falling OTIF score with good response times points to upstream causes; a falling score with slow responses points to the exception process itself. Our OTIF and fill rate calculator shows how the measures are calculated.
Building the exception queue
An exception queue is a list of open cases, each with an owner, a clock and a reason. It can live in a TMS, a visibility platform or a tracking layer you own. What matters is that every rule writes to it in the same format and that nobody has to watch raw status feeds.
Each exception record should hold at least these fields:
- Exception type, and the rule version that raised it.
- Shipment references: load or PRO number, BOL, PO or order, carrier.
- The triggering event, or the missing event and when it was expected.
- Owner role, the person who acknowledged it, and both timestamps.
- Reason code, chosen from a list, plus free-text notes.
- Closing evidence: a document, an event or a record ID.
- Cost, where one applies: detention, redelivery, claim amount.
Where the queue should live
Put the queue where the owners already work, and where the data for every rule can reach it. Three common homes each have a limit:
- The TMS sees tenders, 990s and carrier status, but often not dock appointments, receiving counts or delivery receipts. Dwell, OS&D and POD rules may need data it does not hold.
- A visibility platform sees carrier events and predicted ETAs across carriers, but usually not your orders, appointments or invoices unless you send them.
- A tracking layer you own can join all of these, but someone has to build and support it.
Whichever you choose, list each rule’s data sources first. If a rule needs data from three systems, the queue belongs in the place that can read all three; otherwise the rule fires on incomplete data.
Map carrier reason codes to your own
Carriers explain problems in their own codes. The 214 reason list in 004010 includes NS “Normal Status”, AG “Consignee Related”, AH “Driver Related”, AI “Mechanical Breakdown”, AM “Shipper Related”, AO “Weather or Natural Disaster Related” and B1 “Consignee Closed”. Map each carrier’s codes to a short list of your own that says who caused the exception: carrier, shipper, consignee or outside event. That single field lets you report which carriers, lanes and customers generate the work.
Close cases automatically where the evidence arrives by itself
Some cases close themselves. A missed-pickup case closes when the pickup event arrives, with the delay recorded. A missing-POD case closes when the document appears. Let the system close these, but keep the record, because the delay itself is data. Cases that need a decision, such as a detention dispute or an OS&D claim, should close only by a person.
Example (fictional). A distributor switches on the six rules for its outbound freight. In the first week, the queue holds 140 cases: 60 missing-POD cases that close by themselves once documents arrive, 35 ETA cases, 20 missed pickups, 15 dwell cases, 6 tender rejections and 4 OS&D cases. Reviewing the reason codes, the team finds that 12 of the 20 missed pickups were “shipment not ready” at its own dock. The fix goes to the warehouse’s wave planning, not to the carriers.
The milestone and exception rows you write for this queue are the same ones you would draft in our tracking milestone map: milestone, source, owner, expected time and exception rule. If you are adding the queue to systems you already run, the shipment tracking software page describes the parts such a build includes.
What to do next
Start small and measurable. Two or three well-owned rules beat a dashboard of unowned alerts.
- Pick the two exceptions that cost you most today and write their five fields: signal, threshold, owner, response time and closing evidence.
- Read the claims and detention items in the rules tariffs of your main carriers, and record their notice periods and free time.
- Map each carrier’s 214 status and reason codes to your milestones and your own cause codes.
- Assign an owner role per shift for each exception, with a backup and an escalation path.
- Run the rules for a month, measure time to acknowledge and time to resolve, then adjust thresholds.
- For LTL shipments, use expected-next-event rules rather than “no update” alerts; our note on why LTL tracking goes quiet explains why.
If you want help writing the catalogue for your own lanes and building the queue around your ERP, WMS and TMS, tell us how your freight moves today.
