An EDI 850 purchase order lands in our WMS from the retailer's VAN (SPS Commerce, TrueCommerce, or GXS depending on the retailer). The 850 contains the PO number, line items with retailer SKU codes mapped to your internal SKU IDs, requested ship dates, must-arrive-by dates, ship-to DC address, and routing instructions. The WMS validates every field against your master compliance profile for that retailer and flags any mismatches (out-of-stock at the line level, MABD that conflicts with carrier transit time, ship-to DC not in the routing guide) before the PO enters the pick queue. Mismatches generate an EDI 855 with the exception detail, sent back to the retailer within the acknowledgment window (typically 24 hours).
Pick wave assembly for retail POs is different from DTC. Retail POs are bulk picks (typically full cases or master cartons), pre-allocated against bin location at the wave-build stage, and assembled to retailer-spec pallet patterns. The pick associate scans the SKU at the bin, scans the destination master carton, and the WMS records the assignment. Master cartons get the UCC-128 / GS1-128 carton label printed at the pack station from the retailer-specific template library. Target wants the SSCC at a specific position on the label. Walmart enforces label dimensions to the millimeter. Nordstrom enforces the human-readable text block format. We maintain a per-retailer template library and the WMS prints the correct template based on the destination retailer code on the PO.
BOL (bill of lading) generation runs against the retailer's routing guide. Every retailer publishes a routing guide that specifies which carriers handle which lanes, which booking portal to use, the BOL format, and the chargeback schedule for non-compliance. We read every routing guide for every retailer your brand ships to and enforce the routing rules in our shipping logic. When a retailer updates the routing guide (Macy's did three times in 2024, Walmart Vendor did twice), we update the rules and notify your account manager the same week. The BOL gets generated from the retailer's exact template, with the correct carrier name, BOL number format, and consignee data.
EDI 856 advance ship notice timing is the single most chargeback-prone step. The 856 has to land in the retailer's system inside a specific window before the trailer arrives at the DC. Saks: 24 hours. Nordstrom: 12 hours. Target: 1 hour on certain lanes (tightest in retail). Walmart: 2 hours. Most 3PLs send the 856 at pack-complete timestamp, which means if the trailer sits at the dock for 8 hours waiting for the carrier, the 856 is now 8 hours stale and the brand burns half the window before the trailer even moves. We time the 856 against the trailer dispatch time, not pack-complete. The WMS holds the 856 send until the dock manager confirms trailer departure, then fires it inside the retailer's window.
Dock seal capture, BOL signature, and trailer handoff happen with the dock manager present. The seal number gets photographed and logged against the manifest. The carrier driver signs the BOL on a tablet that captures timestamp, GPS coordinates, and the driver's signature. Chain-of-custody is documented from the seal photo through the carrier's first scan. When a parcel goes missing or a chargeback dispute lands, we have the documentation. Brands switching to us from a 3PL that did not run this discipline find that chargeback dispute outcomes improve materially when the audit log is complete.
EDI 810 invoice generation fires after delivery confirmation, with the line-item detail matching what shipped (not what was ordered, which can differ if a line was short or substituted). The 810 ties back to the original 850 PO number, the 856 ASN, and the delivery confirmation. Retailers can match all four documents before approving payment, which speeds the payment cycle and reduces dispute risk. The retail fulfillment dashboard in your account surfaces every active PO, the compliance status at each EDI step, the ASN-window countdown for in-flight trailers, and the chargeback exposure flag. If a chargeback hits anyway, the audit log gives you the documentation to dispute.