Purchase Order Acknowledgement EDI Schema
Supplier confirmation or change response for a purchase order. Follows PO receipt and precedes shipment, giving the buyer an explicit supplier response.
POA · PurchaseOrderAcknowledgement
Supplier confirmation or change response for a purchase order.
A Purchase Order Acknowledgement records the supplier's response to a buyer order. It can accept, reject, backorder, or qualify order lines, and it carries expected delivery, quantity, price, substitution, and comment details that help the buyer resolve exceptions before shipment.
View releases · View model · View example · View guides · Versioning policy · Error catalogue
Lifecycle And Correlation
Lifecycle Position
Follows PO receipt and precedes shipment, giving the buyer an explicit supplier response.
Correlation Guidance
Each acknowledgement should identify the original data.poNumber and preserve data.lineItems[].uniqueLineKey from the PO. Sender intent belongs in supplierLineStatus; system-calculated status belongs in statusType. Lines without a known uniqueLineKey require manual review rather than automatic fallback matching.
Validation Notes
- Require poaNumber, poNumber, noticeDate, and lineItems before applying acknowledgement logic.
- Validate confirmationType and supplierLineStatus as separate concepts.
- For updates, include documentReference so the previous confirmation can be identified.
- When requireAllLines is enabled, completeness is evaluated by uniqueLineKey only.
- Keep quantity values numeric and use the same unit of measure context as the source order when applicable.
Mapping Notes
- Map supplier response intent to supplierLineStatus and allow DataShift to calculate statusType.
- Preserve the PO uniqueLineKey on every line that is acknowledged.
- Represent backorders with quantityBackordered and dates instead of free-text only.
- Use substitution only when the supplier is offering a different item.
Operational Notes
- Use poaNumber for duplicate detection when the supplier resends the same acknowledgement.
- Route missing or unknown uniqueLineKey values to manual review instead of guessing from line order.
Implementation Pitfalls
- Do not expect POA lines without uniqueLineKey to auto-match by lineNumber or item details.
- Do not acknowledge a line without preserving its correlation reference.
- Do not map sender intent into statusType; use supplierLineStatus.
- Do not treat an order-level accept as proof that every line is unchanged when line details are present.
Key Fields
data.poNumber: Original purchase order number.data.lineItems[].uniqueLineKey: Line correlation key from the PO.
Field Groups
Envelope
Identifies the acknowledgement document and traces it against the original order lifecycle.
docType: Always POA for purchase order acknowledgement payloads.correlationId: Stable UUID used to trace the acknowledgement against the PO.metadata.sourceLanguage: Source format retained for public troubleshooting context.
Acknowledgement Header
Captures supplier acknowledgement identity, operation, and order-level outcome.
data.poaNumber: Supplier-assigned acknowledgement identifier for duplicate detection and support.data.confirmationType: Order-level acknowledgement outcome.data.noticeDate: Date and time the supplier created the acknowledgement.data.poNumber: Purchase order number being acknowledged.
Line Responses
Describes how each ordered line is accepted, rejected, changed, or backordered.
data.lineItems[].lineNumber: Line number from the original purchase order.data.lineItems[].uniqueLineKey: Stable line key copied from the original PO.data.lineItems[].supplierLineStatus: Supplier-provided line acknowledgement intent.data.lineItems[].confirmedQuantity: Quantity the supplier confirms for this line.
Adjustments And Context
Provides delivery dates, shipping, tax, contact, address, substitution, and note context.
data.deliveryDate: Expected delivery date for the acknowledged order.data.shipping: Shipping cost, carrier, route, and delivery terms.data.lineItems[].substitution: Alternative item offered by the supplier.data.comments: Human-readable notes about the confirmation.
Endpoints
The current JSON Schema is served at /edi/schemas/v1/purchase-order-acknowledgement. Every published version, with its immutable download path, is on the releases page.
/edi/schemas/v1/purchase-order-acknowledgementModel
Generated from the published purchase-order-acknowledgement.schema.json (version 1.0.13). Fields marked managed are populated by DataShift.
$
Prop
Type
$.metadata
Prop
Type
$.data
Prop
Type
$.data.orderReference
Prop
Type
$.data.documentReference
Prop
Type
$.data.shipping
Prop
Type
$.data.subtotal
Prop
Type
$.data.tax
Prop
Type
$.data.total
Prop
Type
$.data.contacts[]
Prop
Type
$.data.billTo
Prop
Type
$.data.shipTo
Prop
Type
$.data.lineItems[]
Prop
Type
$.data.lineItems[].substitution
Prop
Type
Last updated on
Purchase Order EDI Schema
Buyer order request sent to a supplier. Starts the order lifecycle and creates the references used by POA, ASN, and INV documents.
Advance Shipping Notice EDI Schema
Supplier shipment notice describing dispatched goods. Follows PO acknowledgement and precedes receipt, giving the buyer shipment detail before goods arrive.