Supported EDI Transactions
Last updated: June 10, 2026
RetailReady will support all transactions required by the retailer. If a transaction type is listed as optional by a retailer AND is listed below, then it can be supported! These determinations are made during setup and testing with the retailer.
Supported EDI Transactions
850 - Purchase Order
The 850 is the starting point of any EDI trading relationship. It is sent by the retailer (buyer) to the vendor (seller) to formally place an order for goods. It contains all the details the vendor needs to fulfill the order including item numbers, quantities, prices, ship-to location, and required delivery dates.
855 - Purchase Order Acknowledgment
The 855 is sent by the vendor back to the retailer in response to an 850. It tells the retailer whether the order can be fulfilled as requested. Each line item gets an ACK code indicating whether it was accepted, rejected, partially filled, or quantity changed. It is the vendor's formal confirmation that they received the PO.
856 - Advance Ship Notice (ASN)
The 856 is sent by the vendor to the retailer at the time of shipment. It provides detailed information about what is being shipped, how it is packed, and when it will arrive. It includes the shipment hierarchy along with carrier and tracking information. Retailers use it to prepare their receiving docks and reconcile what arrives against what was ordered.
810 - Invoice
The 810 is sent by the vendor to the retailer after goods have shipped and is a request for payment. It contains line item detail, quantities, prices, and the total amount owed. It is the digital equivalent of a paper invoice.
997 - Functional Acknowledgment
The 997 is an automated response sent by the receiver of any EDI transaction back to the sender confirming that the file was received and whether it was syntactically valid. It does not confirm business acceptance, only that the file was readable and structured correctly.
846 - Inventory Inquiry/Advice
The 846 is sent by the vendor to the retailer to communicate current inventory levels and stock availability. This helps the retailer understand what the vendor has available to ship.
860 - Purchase Order Change Request
The 860 is sent by the retailer to the vendor to request a change to a previously submitted 850 purchase order. Changes can include quantity adjustments, date changes, item cancellations, or price corrections. It is used when the retailer needs to modify an order after it has already been placed but before it has shipped.
852 - Product Activity Data
The 852 is sent by the retailer to the vendor to share point-of-sale and inventory activity data. It communicates how products are performing at the store or warehouse level, including information such as units sold, on-hand inventory, on-order quantities, and weeks of supply. Retailers use this transaction to give vendors visibility into how their products are moving so the vendor can make informed decisions around replenishment, forecasting, and production planning. It is essentially the retailer sharing their sales and inventory data with the vendor to support a more collaborative supply chain relationship.
820 - Payment Order/Remittance Advice
The 820 is sent by the retailer to the vendor to communicate payment details for invoices that have been paid. It serves as the electronic equivalent of a remittance advice, telling the vendor which invoices are being paid, what amounts are being applied, and what deductions if any have been taken. This allows the vendor to accurately apply payments to the correct open invoices in their accounting system and efficiently identify any discrepancies between what was invoiced and what was actually paid.