EDI Dataflow From The 3PL Standpoint: Scenario One

There are many scenarios related to the 3PL, supplier, and trading partner’s EDI dataflow. In an effort to satisfy ship windows, ensure delivery of goods (and do so in a timely manner), from 3PL to the trading partner, careful considerations must be placed on full-cycle flow of each transaction. To provide more insight on how this data flow works, we’re going to present you a scenario in how it might function. Below, is a legend to help distinguish the purpose of each EDI transaction code.

3PL Shipping

850: retail purchase order
856: retail advanced shipment notice
940: Warehouse Shipping Order
945: Warehouse Shipping Advice
943: Warehouse Stock Transfer Shipping Advice
944: Warehouse Stock Transfer Receipt Advice
810: invoice (not discussed in the article)


To begin with, the trading partner creates a purchase order in their ERP and exports into a specified data format. Their EDI system translates to an 850. The 850 is sent to the supplier’s 3rd party EDI provider via VAN, SFTP, AS2, etc. The supplier’s 3rd party EDI provider translates the 850 to a specified data format and provides it to the supplier, which is imported into the supplier’s ERP. The 850 is also translated to a 940 and sent to the 3PL via VAN, SFTP, AS2, etc.

The 3PL EDI system translates this 940 to a specified data format and loads into their warehouse management system (wms). In their wms, a Warehouse Shipping Advice is created against this order. Also, a UCC-128/GS1 label is generated and placed on a shipping carton. Carrier info, consignee, consignor, warehouse, ship and delivery dates are examples of possible information contained on the shipping advice. This transaction is exported from the wms into a specified data format and is translated to a 945 by the 3PL’s EDI system. This 945 is communicated to the supplier’s 3rd party EDI provider.

The EDI provider then translates the 945 to an 856 and sends to the trading partner. Optionally, depending on the agreement, the supplier can create the ASNs in their ERP and upload to their 3rd party system. There it is translated to an 856 and sent to the trading partner, via VAN, SFTP, AS2, etc.

Keep in mind, the 856 must be received by the trading partner, before the shipment is received. This concludes the breakdown of of the first scenario related to EDI dataflow between 3PL, supplier and trading partner. Check back on our blog for two more possible scenarios.