How To Use Shipment Level Data In WMS And EDI For Receiving And Tracking

The ASN level containing information about the overall shipment, carrier, trailer, tracking, bill of lading, and dates.

Shipment Level is the ASN level containing information about the overall shipment, carrier, trailer, tracking, bill of lading, and dates. To get operational value from that data, warehouses must map shipment-level fields into the WMS and TMS, validate inbound transmissions, and apply processes that connect the electronic shipment record to the physical trailer at the dock.

Start by identifying the shipment-level fields your systems require: carrier identifier (SCAC), trailer or container number, BOL/PRO number, SCAC service, estimated arrival date/time, and total pallets or pieces. These items map to specific WMS and TMS fields and should be required on incoming EDI 856s or API ASN payloads. Treat these fields as primary keys for matching a physical arrival to an electronic notice — missing or malformed values are the single biggest cause of receiving delays.

Mapping Shipment-Level Fields Into Systems

Work with your EDI/IT team to ensure shipment-level segments are captured during translation:

• Carrier/SCAC: Map the carrier code to the TMS to enable rate lookups and carrier-specific rules.
• Trailer/Container ID: Store as the arrival identifier to match gate scans and trailer inspections.
• BOL/PRO: Save in the WMS for billing, claims, and audit trails.
• ETA/Ship Dates: Feed ETAs into appointment booking and alerting modules.

Receiving Workflow That Uses Shipment-Level Data

Design a receiving flow that anchors on the shipment record:

• Gate-In Scan: Scan trailer ID and update actual arrival time on the shipment record.
• Door Assignment: Use the shipment’s pallet count and ETA to auto-assign doors and resources.
• Manifest Validation: Compare shipment totals with order- or pack-level ASNs and raise exceptions if counts differ.
• Update Tracking: Push arrival event to carrier/TMS and to customers for delivery confirmation.

EDI And API Best Practices For Shipment Level

EDI 856 and modern API ASNs both support shipment-level segments but differ in structure. Ensure your translators extract and validate required shipment tags. Use the following practices:

• Schema Validation: Enforce presence of carrier, trailer ID, BOL, and ETA before accepting an ASN.
• Normalization: Standardize carrier codes and trailer formats so downstream systems can match on consistent values.
• Change Management: Treat shipment-level updates (ETA changes, trailer swaps) as discrete events and version the shipment record so audit trails show attribute history.

Handling Exceptions And Reconciliation

When shipment totals don’t match consolidated child-level counts, use a clear exception process. Common steps are:

• Auto-Flag: System flags mismatch and prevents auto-putaway.
• Gate-Hold: Place trailer on hold pending physical verification if counts are materially different.
• Notification: Alert the shipper and carrier with the shipment-level identifiers (BOL, PRO, trailer ID) so they can investigate upstream.

Integrating With TMS And Carrier Portals

Link the shipment-level record in the WMS to the TMS to centralize transport status and billing. Use the BOL/PRO and SCAC as join keys for carrier EDI messages and portal lookups. When a trailer swaps or the carrier updates the pro number, propagate the change to the WMS so receiving teams see the correct reference in their mobile devices and dashboards.

Performance And Reporting Using Shipment-Level Data

Shipment-level metrics drive operational KPIs: on-time arrivals, gate dwell time, average unload time per pallet, and discrepancy rates between shipment and order totals. Use shipment-level timestamps to measure SLA adherence and to evaluate carrier performance. Reporting at the shipment level simplifies root-cause analysis because it ties multiple POs to a single transport event.

Implementation Tips

• Make Key Fields Mandatory: Require SCAC, trailer ID, BOL/PRO, and ETA in supplier ASNs.
• Automate Gate Capture: Equip gates with barcode scanners or OCR to capture trailer IDs and immediately update the shipment record.
• Reconcile Regularly: Run nightly reconciliations between shipment totals and aggregated child-level counts and resolve exceptions before invoicing.
• Train Staff: Ensure dock teams understand which shipment-level fields to verify on physical arrival (BOL, trailer number, counts).

In short, the Shipment Level is the operational linchpin between electronic ASNs and physical freight. Accurate capture, validation, and process integration of its carrier, trailer, tracking, bill of lading, and date fields let warehouses schedule docks, reduce exceptions, and close the loop between transport and receiving.