Bottom line first: when an EDI 858 shipment information message goes wrong, the format is almost never the problem. The problem is that the data the warehouse sent and the data the carrier holds describe two different shipments. The 858 has one job — to transmit detailed bill-of-lading, rating, and scheduling information in a standard format. The format is easy. The hard part is the checking that happens before you send it. My advice: run every 858 through the checklist below inside the warehouse before it goes out. Catch the mismatch yourself, because the carrier will catch it later, and by then it costs money.

I have seen this exact failure three times, and all three times the script was the same. The first was March 2024, at an auto-parts 3PL outside Los Angeles. The warehouse shipped about 40 LTL loads a day. The picker confirmed the shipment in the WMS, the system generated the 858 automatically, and everything looked fine — until the carrier started sending a weekly exception report. A few hundred dollars a week in "weight discrepancy" and "piece-count discrepancy" charges. When we finally dug in, the WMS was sending the inbound gross weight recorded at receiving. The carrier was billing on scale weight at pickup. The difference was the pallets: 18 kilos each, 12 pallets per shipment, more than 200 kilos per load, enough to push the shipment into the next rate bracket. That was not a software bug. Nobody had ever written "weigh the shipment" into the shipping process.

The second time was worse. June 2025, a Columbus, Ohio e-commerce fulfillment warehouse. The carrier reported that the bill-of-lading numbers in the 858s did not match anything in their system. Thirty-seven shipments sat in "pending confirmation" while the end customer started calling. The root cause took three days to untangle: the WMS was stuffing the internal pick-ticket number into the bill-of-lading field instead of the carrier's shipment number from booking. Two numbering schemes, neither side wrong in its own system, completely unmatchable across the interface. Since then, my go-live-night checklist has one non-negotiable line: run one real shipment end to end — order, pick, verify, weigh, label, generate the 858 — and confirm every number matches before anyone signs off.

What EDI 858 Shipment Information Actually Is — and How It Differs From 856 and 810

The EDI 858 is the Shipment Information transaction set under ASC X12. The standard defines it plainly: it transmits detailed bill-of-lading, rating, and scheduling information for a shipment, and it can also carry government bills of lading, commercial bills of lading, and transportation control and movement documents. In warehouse terms, think of it as the "shipment information packet" — the carrier uses it to know what the freight is, where it goes, what it costs, and when it moves.

It gets confused with two other transaction sets constantly, so in every implementation I start with this table:

Message Sent to Says what Warehouse touches it when
856 ASN Consignee / buyer Your goods shipped, here is what is inside After loading, at ship confirm
858 Carrier / shipper Bill of lading, rating, scheduling info At ship confirm, to the carrier
810 Customer Invoice, here is what you owe After charges are confirmed

All three draw from the same outbound record, but they go to different parties for different purposes. That is exactly why warehouses that run clean 856s still fail on 858s: the 856's data is yours to declare, while the 858's data has to match the carrier's system, and the tolerance for error is far lower.

The structure itself is not complicated. Under the X12 specification, the set opens with an ST segment, and the core is the BX segment (General Shipment Information), where BX01 is the purpose code — 00 for an original transmission. Reference numbers, dates and times, routing, measurements, and special handling follow. The warehouse never hand-writes these segments; the translation software and the WMS EDI module handle that. What the implementation consultant actually owns is the field mapping: which WMS field lands in which segment. Get that mapping table wrong once, and every shipment after it is wrong in exactly the same way.

The EDI 858 Shipment Information Pre-Send Checklist

My checklist habit is an occupational disease, but this one was paid for in real money. Before any 858 leaves the building, the shipping verification station runs through it in order:

  1. Bill-of-lading number: the number in the 858 must be the carrier's shipment number from booking — not the internal pick-ticket number, not the customer order number.
  2. Piece count and weight: actual scale weight, never the theoretical weight in the system. Whether pallet weight counts toward gross weight follows the carrier's rating rules — write that into the mapping, do not leave it to memory.
  3. Addresses: verify the consignee address character by character. One wrong digit in the ZIP code and the carrier's rating engine prices a different shipment.
  4. Service level: ground, expedited, next-day — the service in the WMS must match the service confirmed at booking.
  5. Special handling: over-length, over-weight, hazmat, appointment delivery. Miss one flag and it comes back as an accessorial charge at destination.
  6. Dates and times: pickup and estimated delivery dates in the carrier's time zone, not the warehouse's local time forced into the field.

The third failure I saw was in September 2025, at a home-goods warehouse in Dallas. Their 858s were fine. The problem was the 997. The 997 is the functional acknowledgment — the trading partner's reply saying "received" or "rejected, here is why." This warehouse's EDI module dumped 997 rejections into a log file nobody read. The carrier had rejected eleven 858s in a row; the warehouse believed they were sent, the carrier believed they were never received. Both sides waited on each other until the customer called asking where the freight was.

Four Ways the Numbers Stop Matching — and the Workaround for Each

When shipment information fails to reconcile, it is almost always one of four failures, and each needs a different workaround:

First, weight and piece count mismatch. The most common, and the most preventable. The workaround is a scale at the verification station feeding weight straight into the WMS, with no manual override. If a wrong 858 has already gone out, send a correction transaction — change the BX01 purpose code to a correction and transmit the right weight — and call the carrier's customer service by phone. Do not rely on the message alone.

Second, bill-of-lading number mismatch. The most damaging, because the carrier's system cannot find the shipment at all. The workaround is to make the carrier's shipment number a mandatory field in the WMS: blank means the shipment cannot be confirmed. If it already went wrong, send a corrected 858 immediately and ask the carrier to link it manually in their system.

Third, rating mismatch. The warehouse sent it at rate A; the carrier billed at rate B. Here is the counterintuitive part: the root cause is usually not the rate table at all. It is the address and the service level — one wrong ZIP code, one wrong service code, and the whole rate changes. Arguing about the rate table will not get you anywhere. The workaround is a monthly reconciliation: match the carrier's invoice against the 858 send log, shipment by shipment, and pull out every variance above an agreed threshold for review.

Fourth, the message never arrived. The workaround is 997 monitoring with a timeout alert: if no 997 comes back within four hours of sending an 858, the EDI owner gets an alert. Four hours is the value I use as a starting point on projects; adjust it to the carrier's service agreement.

The math makes the case for investing in this. The following is a hypothetical example: a warehouse shipping 100 LTL loads a day with a 5 percent 858 error rate has five problem shipments a day. At an average of 60 dollars per error in rework, accessorials, and re-invoicing labor, over 22 working days that is 6,600 dollars a month — before counting the hidden costs of customer complaints, strained carrier relationships, and finance reconciliation time. Two weeks spent cleaning up the mapping table and the verification checklist, pushing the error rate below 1 percent, pays for itself in the first month. I run this calculation for every client at kickoff. It works better than a hundred speeches about data quality.

One thing you can do tomorrow: pull ten shipments from last week at random, and compare the 858 send log against the carrier's invoice field by field — bill-of-lading number, piece count, weight, address, service level. All five have to match. If two or more out of ten fail, do not start by shopping for a new system. Fix the mapping table and the verification checklist first.

By Lin Xiao, WMS Implementation Consultant