Procure-to-Pay (P2P) Services from Retail EDI

The procurement and regular replenishment of goods and supply chain processes have grown increasingly complex. Companies share information, documents and plans with hundreds, sometimes even thousands of suppliers. Business integration across companies and applications, is challenging and costly.

Retail EDI enables buying organizations to optimize procurement processes.  The same strategies used to improve business process automation, and availability of data for analytics often go hand-in-hand with increasing onboarding, and adoption tempos.  Our experts can assist with project management, data model and canonical development through to hands-on integration with LoB applications and data warehouse platforms while supporting your community.

Retail EDI cost-effectively integrates and collaborates with all partners in the supply chain and all messages used across the Procure-to-Pay and Order-to-Cash processes.

Managed Services – Retail EDI stands ready to support your project with VAN, AS2, and other managed services as well.

Integration enables the exchange of information included in purchase orders and related messages across systems, applications and enterprises. No matter what EDI or procurement system you or your customers, partners or suppliers are using, Retail EDI is here to help you send and receive documents and data in the format you need.

Optimize Order-to-Cash, Procure-to-Pay, and other systems with Retail EDI data integration:

  • Transformation: API/JSON,  EDI, cXML, more.
  • Eliminate redundant data entry
  • Use data to surface insight


Whether you need EDI a new data services to transform to REST for integration across applications for your iPaaS to consume, or just a new trading partner added to an existing service, we’re here to help.

EDI for Procure-to-Pay Scenarios

Procure to Pay is the conventional ordering process organizations work with to acquire goods and services from one another (Addressed from a Buyer’s perspective).  The majority of retail EDI traffic goes across VAN networks, while AS2, SFTP and finally JSON/REST is primarily used closer to LoB applications.  Many of the efficiencies found in leveraging the value of B2B data results from automating across silos, and the ability to easily analyze data (Not to replace, removal of duplicate data entry).  Therefore, the B2B data, and all the other values used benefit from automation.


Functional  Message EDI ANSI ASC EDIFACT


Sales Forecast Planning Schedule w/Release (830) DELFOR Product Activity Message
Purchase Order Purchase Order (850)/Grocery (875) ORDERS

Purchase Requisition

Confirmation Purchase Order Confirmation (855) ORDRSP

Confirmation Request

Shipment Advice Advanced Shipment Notification DESADV

Shipment Notification

Product Activity Product Activity Data (852) SLRPT

Product Activity Message

Invoicing Invoice (810) INVOIC






The Common Procure-to-Pay EDI Transactions

P2Prelationships  differ by industry, design, and there are quite a few documents which can be incorporated.  Only the most common are shown here.

The Purchase Order – Retailers issue Purchase Orders to vendors as a means of officially requesting goods or services electronically.

Purchase Order Change – Retailers use this to alter existing orders.  The EDI transaction is the 860.

Purchase Order Confirmation – This document is sent by a Supplier to the customer in response to an EDI 850.  The document conveys information such as; acceptance, freight, packing method and more optionally.  Transaction type and relationship requirements usually dictate the level of detail needed.

Shipment Advice – This is sent by suppliers.  Most will relate the ASN (Advanced Shipment Notification) to this message.  The ASN follows the EDI 855 (In ASNI ASC messaging parlance…), and specifically details how the order was packed, carrier (Seen this term: “SCAC”?), and other information.  Accurate and easy to understand shipments means to the extent possible – shipments with item level serialization.  This not only helps in downstream data management, but it also helps align the transaction with other documentation such as BOL, manifest (gov), GS1-128 (UCC-128) labels and more.

Invoice – This document is sent by a Supplier in response to an order, but normally after the shipment notification is sent.  They can be sent per store, per item, consolidated or not, etc.

Let’s talk about how we can help increase efficiencies for your organization.  Use the Retail EDI Value Added Network as your supply chain partner to manage the actual EDI e.g. Orders and ASNs etc. across retail and other EDI-based channels.  Use our advisory and integration services to deliver automation and insight to the rest of your supply chain.