LTL tracking goes quiet because a less-than-truckload shipment is scanned only at physical handoffs: pickup, the origin terminal, any transfer terminal, the destination terminal, out for delivery and delivery. Nothing is recorded while it rides a linehaul trailer between those points, over a weekend, or while it waits at the destination terminal for a delivery appointment. Realistically you can get the PRO number before pickup, pickup confirmation, terminal arrivals and departures, an estimated delivery date, appointment events, delivered status and a delivery receipt image. Silence becomes a problem only when it outlasts the next scan you should have seen.
The rest of this field note explains the LTL event model scan by scan and maps it to X12 214 status codes. It then sets out what to ask carriers for and gives starting rules for telling a normal gap from a real stall.
How an LTL shipment actually moves
An LTL shipment shares trailers with other shippers’ freight and changes trailers at terminals. Each change is a scan; the driving in between is not. Once you see the route as a chain of handoffs, the quiet stretches stop being mysterious.
Old Dominion’s glossary gives the vocabulary. “Line haul” is “the transporting of freight between cities or service centers”. A shipment that is “closed out” is “loaded on a trailer and awaiting driver assignment”. P&D means pickup and delivery, the local trucks that run between customers and the terminal.
A typical shipment passes through these steps:
- Pickup. A local P&D driver collects the freight, often with several other pickups on the same route, and brings it back to the origin terminal (carriers call terminals service centers).
- Origin dock. The freight is unloaded, matched to its bill of lading and loaded onto a linehaul trailer headed toward its destination.
- Linehaul. The trailer travels to the destination terminal or to an interim terminal, where freight from many origins is sorted onto new trailers.
- Destination terminal. The freight is unloaded and loaded onto a P&D trailer for a local delivery route, or held if delivery needs an appointment.
- Delivery. The driver delivers, and the consignee signs the delivery receipt, noting any shortage or damage.
An Old Dominion transportation executive described the network on the carrier’s blog in May 2026. There, trucks are “partially loaded at every stop”, and loads are “reconfigured, recombined, and rebalanced” at distribution centers. Shipments cross the country “in a day or two, often on several different trailers along the way”.
That design explains the tracking pattern. Between scans, a shipment is either moving on a trailer or waiting on a dock for the next scheduled departure, and neither produces a scan.
What a terminal scan records
Scans happen when freight crosses a dock: unloaded from one trailer, loaded onto another, or held. Each scan ties the PRO number to a place and a time. XPO’s LTL tracking API guide (release 1.0, 2018) reports an origin, current and destination service center for each shipment, and its sample event history includes entries such as “Unloaded from trailer - Emptied”.
Truckload freight can be followed by the truck’s location because one truck carries one load. An LTL pallet has no position of its own; it inherits the location of whatever trailer it is on. XPO’s tracking API, for example, reports the current service center, not a map position. Plan your tracking around scans, not maps.
Which events LTL carriers record
The events below cover most of what an LTL carrier can tell you. The wording varies by carrier, so map each carrier’s statuses to your own milestone names rather than showing raw text to customers.
| Physical event | Example carrier wording | X12 214 status code (004010) |
|---|---|---|
| Driver arrives at the shipper | Varies by carrier | X3 Arrived at Pick-up Location |
| Freight picked up | “Pickup Completed” (Old Dominion); “Picked up” (XPO) | AF Carrier Departed Pick-up Location with Shipment |
| Freight on the origin dock | “Received at Dock”, “Arrived at Origin SVC” (Old Dominion); “At origin” (XPO) | X4 Arrived at Terminal Location |
| Leaves a terminal on linehaul | “En route to interim” or “En route to destination” (XPO) | P1 Departed Terminal Location |
| Reaches an interim terminal | “Arrived at interim”, “At interim” (XPO) | X4 Arrived at Terminal Location |
| Reaches the destination terminal | “Arrived at Destination SVC” (Old Dominion); “Arrived at destination” (XPO) | X4 Arrived at Terminal Location |
| Estimated delivery date set or changed | Estimated delivery field | AG Estimated Delivery |
| Loaded for local delivery | “Out for Delivery” | X6 En Route to Delivery Location |
| Delivered | “Delivered” | D1 Completed Unloading at Delivery Location |
| Delivery attempted, not completed | “Appointment Attempted”, “Returned to Dock” (Old Dominion); “Attempted delivery” (XPO) | AH Attempted Delivery; AP Delivery Not Completed |
| Delay reported | “Delayed” | SD Shipment Delayed |
Old Dominion’s wording comes from the customer notification options on its trace page, checked November 2026. XPO’s comes from the status appendix of its API guide. The X12 codes come from the 004010 release as published in Stedi’s X12 reference, a secondary source.
Notice what is missing from Old Dominion’s notification list. Its transit group has three options: arrived at origin service center, arrived at destination service center, and delayed. Between origin and destination, a customer who relies on those notices hears nothing unless something is late.
What the 214 status, reason and appointment fields mean
X12 describes the 214 as the message a carrier uses “to provide shippers, consignees, and their agents with the status of shipments in terms of dates, times, locations, route, identifying numbers, and conveyance” (X12, 214). Each status sits in an AT7 segment with up to seven fields:
- Status code (AT701), such as X4 or D1 in the table above.
- Status reason code (AT702). In 004010, NS means “Normal Status”. Others explain a problem, such as A1 “Missed Delivery”, AG “Consignee Related”, AN “Holiday - Closed”, AO “Weather or Natural Disaster Related” and HB “Held Pending Appointment”.
- Appointment status code (AT703), used instead of a shipment status when the message is about an appointment. AB means “Delivery Appointment Date and/or Time” and X9 means “Delivery Appointment Secured on This Date and/or Time”.
- Appointment reason code (AT704), from the same reason list.
- Date, time and time code (AT705 to AT707). The time code tells you which time zone the time is in.
A 214 with status SD and reason AG tells you far more than “Delayed” on a web page: the carrier says the delay is the consignee’s. Ask each carrier which status and reason codes it actually sends. Our note on EDI 214 versus carrier APIs covers how to normalize them when you have several carriers.
When the PRO number exists, and why it matters
You cannot track an LTL shipment until you have its PRO number, and on a paper bill of lading you may not have it until after pickup. Old Dominion’s glossary defines the PRO as “a sequential number assigned to a shipment for unique identity purposes”. The pro label is “a pre-numbered gummed label that is attached to the bill of lading and the articles being shipped”.
With a paper BOL and the carrier’s pro labels, the PRO is attached to the paperwork and the freight at pickup. Your system learns it only when someone keys it in, the carrier sends a 214, or the carrier’s portal shows the shipment. That gap at the very start produces “no tracking” calls that have nothing to do with the freight.
The eBOL fixes the first gap
The NMFTA’s Digital LTL Council publishes an electronic bill of lading (eBOL) API standard, at version 2.1 on the council’s API standards page. Its FAQ on the Digital LTL site answers the tracking question directly: “The Pro Number will be returned for reference once the eBOL is sent.” The same FAQ says the request can carry “the shipper’s pre-assigned PRO number for the requested carrier. If one is not provided in the request, one is automatically assigned by the carrier.”
In practice, then, a shipper that creates bills of lading through a carrier’s eBOL API has the PRO before the truck arrives. Old Dominion’s Shipping API Integrations page describes its eBOL API as compliant with NMFTA v2.1.0, and says users “can receive a PRO number or provide one that they already possess”. Its pickup API returns a pickup number and pre-pro IDs for each shipment in the request.
Pre-assigned PROs and reference numbers
If a carrier does not offer an eBOL API, ask for a range of pre-assigned PRO numbers and print the pro labels yourself. Your shipping system then records the PRO at the moment it prints the BOL. Either way, send your own references on the BOL as well: order number, PO number and BOL number.
Those references matter for matching. XPO’s API guide accepts “either a PRO number or any reference number used to identify the shipment” as the lookup. It also treats the PRO as the first part of a shipment’s unique identifier and the pickup date as the second, so store the pickup date alongside the PRO.
Six normal reasons for a quiet day
Most LTL silences have an ordinary cause. Knowing which one applies tells you whether to wait, chase the carrier or call your own customer.
1. The freight is on a linehaul trailer
A shipment loaded onto a linehaul trailer produces no events until that trailer is unloaded. On a long lane, or with a stop at an interim terminal, that can mean a day or more between scans. XPO’s status list includes “En route to interim” and “En route to destination”, and those statuses can stand unchanged for many hours while the trailer is driven.
2. It is a weekend or a carrier holiday
At Old Dominion, for example, pickup and delivery are business-day services. Its rules tariff ODFL 100-Q (effective April 14, 2025, updated October 5, 2026) defines a business day as “a weekday, Monday through Friday, excluding holidays”. It says the carrier “is not obligated to pick up or deliver shipments on Saturdays, Sundays or holidays” (Item 752-3).
Its holiday definition lists New Year’s Day, Memorial Day, Independence Day, Labor Day, Thanksgiving, the day after Thanksgiving, Christmas Eve and Christmas Day. It also covers any day the carrier generally observes as a holiday at the point where service is performed. A shipment that reaches the destination terminal on a Friday afternoon may show nothing new until it goes out for delivery on Monday.
3. Delivery is waiting for an appointment
If a receiver requires a delivery appointment, the freight sits at the destination terminal until one is set. XPO’s status “Appointment required at destination” means the shipment “is being held at the destination service center until an appointment for delivery has been set or met at the request of the receipient”. In a 214, look for reason code HB, “Held Pending Appointment”.
Old Dominion’s tariff treats a request to schedule an appointment, or a BOL note such as “call before arrival”, as a chargeable service (Item 647). Under its storage rule, appointment freight gets 24 hours of free time before storage charges apply (Item 910). If the appointment requirement is not on the BOL, the carrier may discover it only at the destination terminal, and the shipment waits there while the appointment is arranged.
4. The freight is being reweighed or inspected
If the BOL looks wrong, the carrier checks. Old Dominion’s tariff (Item 367) says that when the description or other BOL information “is incomplete or is believed to be incorrect”, the carrier may reweigh, inspect the product or recompute density. The carrier’s glossary names a “Weight and Inspection” department responsible for this.
Classification changes raise the stakes. The NMFTA says new National Motor Freight Classification changes took effect July 19, 2025, including more detailed classification criteria for density. Accurate weights and dimensions on the BOL reduce the chance of a stop for inspection; our freight density calculator helps check them before the freight leaves. Old Dominion’s May 2026 blog post adds that freight found “longer or heavier than expected” at pickup can upset load plans and “create ripple effects that cause delays”.
5. The clock started later than you think
Transit time is counted in the carrier’s days, from the carrier’s start point. XPO’s guide says that for an after-hours pickup, “delivery date calculations begin the next business day rather than on the pickup date”. Its estimated delivery date is the date “within the standard number of days established for XPO Logistics’ transit time between the origin and destination points”. Old Dominion’s transit time tools likewise show “the number of in-transit days between your origin and destination”.
A shipment picked up late on Friday on a three-day lane is therefore not late on Tuesday, even if your customer expected it then. Compare against the carrier’s own estimated delivery date first, and against your customer’s promise date second.
6. Another carrier is making the delivery
Not every LTL carrier serves every ZIP code directly. When it does not, it hands the freight to a partner for the final miles. Old Dominion’s glossary defines an agent as a “carrier that delivers your freight to a direct point” and a beyond carrier as one “which moves a shipment beyond a point of interchange with another carrier”. XPO’s guide describes “SCAC deliveries” to locations it “does not service directly; therefore, we must forward them to a carrier who will deliver the shipment”.
After the handoff, the delivering carrier may scan the freight under its own number, and the original carrier’s tracking can stall at the interchange. In a 214, the handoff can appear as status J1, “Delivered to Connecting Line”. Ask the original carrier for the partner’s name and PRO. Before you ship, check the carrier’s route guide for the points it serves, and ask how it handles the rest.
How to tell a real stall from a normal gap
A real stall is a shipment that has missed the next event it should have produced. The test is not “how long since the last update” but “which event should have happened by now, given the lane, the calendar and the appointment”. That needs three inputs: the carrier’s transit days for the lane, a business-day calendar with the carrier’s holidays, and the shipment’s appointment status.
| Last event seen | Next event expected | Treat as a stall when | First action |
|---|---|---|---|
| BOL created, PRO known | Pickup completed | No pickup event by the end of the requested pickup day | Check the pickup request; call the origin terminal |
| Picked up | Arrived at origin terminal | No origin terminal event by the next business morning | Ask the carrier to trace the pickup |
| At origin terminal | Departed on linehaul | No departure or en-route status by the end of the next business day | Ask whether it is held for inspection or space |
| En route or at an interim terminal | Arrived at destination terminal | Estimated delivery date reached and no destination terminal arrival | Ask for the trailer's location and a new estimated delivery date |
| At destination terminal | Out for delivery, or an appointment event | One business day with neither | Check for an appointment hold; contact the receiver |
| Out for delivery | Delivered, or attempted | No event by the end of the delivery day | Ask for the driver's status and any attempt reason |
| Delivered | Delivery receipt image available | No image within two business days | Request the delivery receipt through the carrier's document service |
When the PRO stops but the freight does not
A frozen status can also mean the shipment was split. XPO’s status list includes a “Non-Movement PRO (parent)” for a shipment that “has been split and loaded onto more than one trailer due to either space availability or as directed by the shipping documents”. The original PRO “acts as the ‘parent’”, and each portion gets “an additional freight bill number”.
If you track only the parent PRO, you may see no movement while the pieces travel on other numbers. When a multi-pallet shipment goes quiet at a terminal, ask the carrier whether it was split, and record the child numbers against your shipment. Your system should hold one shipment with several PROs, not assume one PRO per shipment.
Calibrating thresholds from your own scan history
The thresholds in the table are a starting point. Your own history will show what is normal for each carrier and lane, and it costs little to measure.
- Export three months of delivered LTL shipments with every event and its timestamp, from the carrier’s API history, your 214 archive or a platform export.
- For each shipment, compute the hours between consecutive events, and label each gap by the segment it covers: pickup to origin terminal, origin dwell, linehaul, destination dwell, out for delivery to delivered.
- For each carrier, lane and segment, find the gap that 90 percent of shipments stay within. Use business hours for segments that depend on pickup and delivery days.
- Set the stall threshold a little above that figure, and review the shipments that exceed it. If most were real problems, keep the threshold; if most were normal, widen it.
Repeat the exercise when a carrier changes its network or service standards, and after peak season. A rule tuned to last spring’s network will drift.
Statuses that mean act now
Some statuses are stalls by definition, whatever the clock says. Act on these the day they appear:
- “All short.” In XPO’s list, the destination service center reports the shipment all short “because it has not arrived there as scheduled”. Something did not make the trailer it was planned on.
- “Delayed” or 214 status SD, especially with a reason other than NS. The reason code tells you who owns the delay.
- “Returned to dock, no attempt to deliver.” XPO says the shipment “will go back out for delivery the next business day”, so your customer’s date has moved.
- “Undeliverable” or “Refused”. XPO says undeliverable freight stays at the destination service center until the shipper contacts the carrier with instructions. Storage clocks may start.
- “Delivered part short.” Only part of the shipment was delivered. This becomes an OS&D case; see our note on shipment exception management for owners and response times.
Why “days since last update” alerts fail
A single rule such as “alert if no update in 24 hours” fires every weekend and on every long linehaul, and misses a shipment stuck one day past its estimated delivery date on a short lane. Alerts that fire on normal gaps teach people to ignore alerts. Expected-next-event rules produce fewer alerts, and each one carries a reason a person can act on.
A worked example: one shipment, three quiet stretches
The example below follows one fictional shipment through a normal week. It shows how a customer can see “in transit” for days while every step is on schedule except one.
Example (fictional). A distributor ships four pallets of item EX-20118 on PRO EX-77310 from its Kansas City warehouse to a customer’s distribution center in North Carolina. The carrier’s transit time for the lane is three business days. The bill of lading does not mention that the customer requires delivery appointments.
- Wednesday 4:40 p.m. Picked up. 7:15 p.m.: arrived at the origin terminal. 11:30 p.m.: departed, en route to an interim terminal.
- Thursday. No events. The trailer is on linehaul.
- Friday 3:10 a.m. Arrived at the interim terminal. 9:05 p.m.: departed, en route to destination.
- Saturday and Sunday. No events.
- Monday 4:50 a.m. Arrived at the destination terminal. No out-for-delivery event follows.
- Tuesday 10:20 a.m. Status: appointment required at destination. The carrier calls the receiver, who offers Wednesday at 8:00 a.m.
- Wednesday 8:35 a.m. Delivered. The delivery receipt image appears on Thursday.
The customer’s portal showed “in transit” from Thursday to Monday and called twice. Under the expected-next-event rules, nothing was late until Monday evening, when one business day passed at the destination terminal with neither an out-for-delivery event nor an appointment event. That single alert pointed to the real cause: the missing appointment note on the BOL. Adding the customer’s appointment requirement to the order and the BOL would likely have saved a day.
What tracking data you can realistically get
From the carriers cited here you can get a defined set of milestones, but not continuous location. The table sets out what is realistic by channel, so you can stop asking for data that does not exist and start asking for data that does.
| Channel | What it gives you | Limits to plan for |
|---|---|---|
| Carrier website and email or text notices | Current status, estimated delivery date, origin and destination terminals; notices at chosen milestones | Manual; Old Dominion’s tracker accepts up to 25 numbers at a time |
| Carrier tracking API | Current status and, on some carriers, full event history, estimated delivery date and appointment details | Per-shipment calls; your system must poll and respect usage rules |
| EDI 214 | Status, reason and appointment codes, pushed by the carrier | Trading partner setup per carrier; codes and timeliness vary |
| eBOL and pickup APIs | PRO number at BOL creation, pickup confirmation | Carrier must support the standard; your BOL data must be complete |
| Document retrieval | Bill of lading, delivery receipt and, on some carriers, delivery photos | Available after the event, not live |
| Visibility platform feed | The same carrier events, normalized across carriers | The platform cannot create scans the carrier does not make |
XPO’s guide documents what a carrier API can hold. It has separate operations for current status, reference numbers and full event history, and it says to use the history operation “when investigating a possible exception to a shipment”. Its status response carries an estimated delivery date, a delivery appointment with start and end times, and service exception records with reason and resolution codes.
Old Dominion’s API page lists a Document Retrieval API for “bills of lading, delivery receipts or delivery photos” by PRO. A delivery receipt is the signed document on which the consignee notes any discrepancies. It is the closing evidence in a delivery dispute, so collect it automatically.
What the NMFTA standards may add
The council’s API page lists an In-Transit Visibility API standard at version 1.0.0. Its listed features include terminal updates at origin, intermediate and delivery terminals, exception notifications for delays, damages and reweighs, and reasons for missed deliveries. The council’s LTL page still labels it “In Development” (both checked November 2026). Ask your carriers whether and when they plan to support it; until then, plan on each carrier’s own API or 214.
What you will not get
You will not get a GPS position for an LTL pallet, an exact time of arrival at an interim terminal in advance, or a promise that weekend linehaul events will appear. Some carriers publish more than others. If a customer contract promises live location for LTL freight, rewrite the promise before you try to build it.
What to ask your LTL carriers for
Put these requests to each LTL carrier you use regularly, and keep the answers in your carrier file. They turn vague “better tracking” into specific data you can test.
- The PRO before pickup. Through an eBOL API, a pickup API that returns pre-pro IDs, or a pre-assigned PRO range for your own labels.
- A status feed. API access with event history, or a 214, with the list of status codes, reason codes and appointment codes the carrier actually sends.
- Timeliness. How soon after a scan the event reaches the API or 214, and whether weekend events are sent as they happen or in a batch.
- The estimated delivery date. Which field carries it, when it is recalculated, and whether it counts from the next business day for late pickups.
- Appointment events. Whether the carrier sends an event when a shipment is held for an appointment, when an appointment is set, and when one is missed.
- Exception reasons. The carrier’s reason list for delays, attempts, refusals and shortages, mapped to your own exception types.
- Documents. Automatic access to delivery receipts and any delivery photos by PRO, and how soon after delivery they are available.
- Time zones. Whether event times are local to the terminal or in UTC. XPO’s guide, for example, returns all timestamps in UTC.
- Reference numbers. Which of your references (PO, order, BOL) the carrier stores and returns, so you can match events without keying PROs.
Record the answers per carrier with the tracking milestone map, one row per milestone, with its source and expected timing. That sheet becomes the rule set for stall detection.
What to fix on your own side
Some gaps start at your dock. Check these before blaming the carrier:
- The BOL carries complete weight, dimensions, piece count and class, so the freight is not stopped for inspection.
- Delivery appointment requirements and receiving hours are on the order and printed on the BOL.
- Pallets carry the pro label and your own shipping label, both readable.
- The PRO is recorded in your system at the time of shipping, not keyed later from the carrier’s portal.
Setting expectations with customers and your own team
When a quiet LTL shipment triggers a “where is my freight” call, the call is usually about the gap between what the screen shows and what the customer expected. Close that gap by showing what the carrier can actually know, in plain words.
Show these items on any customer-facing tracking view or email:
- Milestone, not raw status. “At the carrier’s terminal near Charlotte” reads better than “X4” or “At interim”.
- The carrier’s estimated delivery date, labeled as the carrier’s estimate, and your promise date if it differs.
- The next expected update. For example: “Next update expected when the shipment reaches the destination terminal, estimated Monday.”
- Appointment state for receivers who require appointments: requested, set, or missed.
Give customer service a short script for quiet stretches. It should say where the shipment was last scanned, what the next scan will be, when it is expected, and whether anything is actually late. That answer works because it reflects how the network runs. It also keeps your team from opening carrier traces on shipments that are on schedule.
Answers for the questions customers ask most
Customer service can answer the common LTL tracking questions with the same few facts. A shared pattern keeps answers consistent across the team:
| Customer question | What to check | How to answer |
|---|---|---|
| “It has said in transit for two days.” | Last terminal event, lane transit days, calendar | Where it was last scanned, the next scan expected and when, and whether it is on time against the carrier’s estimate |
| “Why wasn’t it delivered today?” | Appointment state, attempt or reason codes | Whether it is held for an appointment, was attempted, or is simply due another day |
| “Can you give me a delivery time?” | Appointment status | A time only if an appointment is set; otherwise the estimated delivery date |
| “It shows delivered, but we don’t have it.” | Delivery receipt, signature, delivery address, partner carrier | Who signed and where; then open a trace with the carrier the same day |
Inside your own operation
The transportation desk needs the opposite view: only shipments that missed an expected event, ordered by how close they are to a customer deadline. Build that queue from the stall rules above, and give each alert an owner and a response time. A delivered shipment with no delivery receipt belongs to a different person than a shipment held for an appointment.
Building the rules into your tracking
Stall detection needs a little data you may not hold yet, but none of it is exotic. Much of it comes from your carriers’ own transit time tools and rules tariffs.
- Lane transit days. Load each carrier’s transit days for your main lanes from its transit time tool, and refresh them when the carrier changes its service standards.
- A business-day calendar per carrier. Include weekends and the carrier’s holidays as listed in its rules tariff. Old Dominion’s, for example, includes the day after Thanksgiving and Christmas Eve.
- Expected next event per milestone. Write the expected next event and its deadline for every status, as in the thresholds table above.
- Appointment state. Hold the receiver’s appointment requirement on the customer record and track whether the appointment is requested, set or missed.
- Two timestamps per event. When it happened and when you received it, so a late-arriving scan does not look like a stall that cleared itself.
- Reason-code mapping. Map each carrier’s reason codes to your exception owners: carrier, shipper, consignee or weather.
If you already run a visibility platform or a TMS that receives 214s, these rules may be able to sit on top of the feed you have. If you are deciding whether to buy a platform for this, our note on how to choose a shipment visibility platform sets out the criteria. Where the rules need data from your ERP or WMS, such as appointments and promise dates, the work is the kind of tracking layer described on our shipment tracking software page.
Testing the rules before go-live
Before the rules send alerts to real people, replay past events through them. Take a month of closed shipments, run their events through the rules in time order, and list every alert the rules would have raised.
Then check three things. The number of alerts per day should be one the desk can work. Each alert should match a shipment someone would have wanted to know about. And no shipment that caused a customer complaint should have passed without an alert. Adjust thresholds until all three hold, and keep the replay as a regression test for later rule changes.
What to do next
Start with the shipments that generate calls, and work backward to the missing scan or the missing data. A review of recent LTL inquiries will show which of the six causes you see most.
- Pull last month’s LTL shipments that triggered a customer call, and note the last event before each call.
- For each, decide whether the gap was linehaul, a weekend or holiday, an appointment hold, an inspection, a late start or a handoff to a partner carrier.
- Move every carrier that does not provide the PRO before pickup onto an eBOL, a pickup API or pre-assigned PRO labels.
- Replace “no update in 24 hours” alerts with expected-next-event rules, using the thresholds table as a starting point.
- Ask each carrier the nine questions above and record the answers in the tracking milestone map.
- Put appointment requirements and full weight and dimensions on every BOL.
If you want help turning those rules into software that reads your carriers’ feeds and writes alerts to the right person, tell us about your carriers and systems.
