Racklipedia
Racklify
​
Software

What Is an EDI 855 Purchase Order Acknowledgment and How It Works

Updated October 23, 2026
Published October 23, 2026

EDI 855 Purchase Order Acknowledgment

Definition

An EDI transaction set used by a supplier to acknowledge, accept, reject, or modify a purchase order.

Overview

EDI 855 Purchase Order Acknowledgment The EDI transaction used by a supplier to acknowledge and communicate acceptance or changes to a purchase order. The 855 tells the buyer whether the supplier accepts the order as-is, accepts with changes (quantity, date, price), or rejects the order entirely. In retail supply chains the 855 is a formal electronic confirmation that replaces phone calls and e‑mails, enabling automated downstream processes in warehousing, replenishment, and invoicing.


Retailers expect consistent, machine-readable acknowledgments because their replenishment systems, warehouse management systems (WMS), and order management platforms depend on timely, structured responses. A correctly formatted 855 aligns with ANSI X12 transaction set rules but is commonly customized to meet a trading partner’s specific mapping and business rules (e.g., different segment usage for promised ship dates or split shipments).


What The 855 Covers


The 855 communicates order-level and line-level status back to the buyer. Typical data elements include:


  • Order Reference: Purchase order number and date echoed from the original PO (850).
  • Line Acknowledgement: Accepted, accepted with change, or rejected for each SKU/PO line.
  • Quantity And Dates: Confirmed ship quantity, promised ship date, and expected delivery dates.
  • Reason Codes: Codes or notes explaining changes or rejections (stockouts, lead time, cartonization).
  • Carrier/Shipment Info: When known, planned carrier, shipment ID, or instructions affecting fulfillment.


Why It Matters For Retail Operations


Retail workflows depend on accurate acknowledgments for inventory planning, store allocations, and customer promises. A fast, accurate 855 reduces overstocks and stockouts by enabling buyers to adjust allocations and rearrange replenishment when suppliers report short shipments or delayed dates. For warehouses, the 855 triggers receiving schedules and slotting adjustments; for carriers it can indicate when consolidations or routing changes are required.


How The 855 Fits With Other EDI Messages


The 855 follows the buyer’s PO (850) and precedes shipment notices (856) and invoices (810). It is not a delivery confirmation (that’s the 856) nor a functional application acknowledgment (997) — though many trading partners exchange a 997 to confirm EDI transport integrity in addition to the business-level 855.


How It Varies Across Retail Trading Partners


Implementation differences are common. Some large retailers require specific segments, extended PO line identifiers, or additional date qualifiers. Suppliers should maintain flexible mapping and translation logic in their EDI gateway or middleware to support retailer-specific requirements such as split-case acknowledgments, multiple ship-to locations, or ASN‑driven replacing of certain 855 fields.


Practical Example


Suppose a buyer issues PO 12345 for 500 units of SKU 98765 with requested ship date July 10. The supplier can send an 855 with the following common responses:


  • Accept As Requested: Line shows 500 units, ship date July 10.
  • Accept With Change: Line shows 400 units, promised ship date July 15, with reason ‘shortage’. Buyer systems can then reallocate the remaining 100 units or create a backorder.
  • Reject Line: Line rejected with reason ‘discontinued’. Buyer inventory/planning teams receive the rejection and may re-source or cancel the PO.


Tips For Suppliers And Warehouse Teams


A reliable 855 process reduces manual touch and billing discrepancies. Best practices include:


  • Automate Mapping: Use middleware to support retailer-specific maps and reduce manual edits.
  • Timely Responses: Send acknowledgments within the trading partner SLA window to avoid cancellation or replenishment errors.
  • Clear Reason Codes: Use standardized codes for shortages and lead-time changes to help buyers automate downstream decisions.
  • Sync With Inventory Systems: Ensure WMS inventory position feeds the EDI software so quantities in the 855 reflect real-time availability.


In short, the EDI 855 Purchase Order Acknowledgment is the supplier’s formal electronic response to a buyer’s PO that confirms acceptance, communicates changes, or rejects lines. Accurate, timely 855 transactions keep retail replenishment, receiving, and invoicing aligned and reduce costly manual interventions.


Sources And Additional Reading (3)

More from this term
Looking for a 3PL?

Compare warehouses on Racklify and find the right logistics partner for your business.