Verified transaction set reference
Amazon EDI 850 Purchase Order Validation
A supplier can parse a structurally clean 850 and still ship the wrong revision, process a duplicate, substitute an unrecognized item, or ignore a cancellation. The preflight boundary therefore includes document structure plus stateful order ingestion and a clear newest-version rule.
Direct answer
Direct answer
An 850 starts the procurement chain, but syntax alone cannot prove it is the newest actionable order. Validate its envelope and purchase-order identity, ingest it idempotently, compare revisions and cancellations, preserve every buyer item identifier, and retain the accepted source snapshot that later 855, 856 and 810 documents must reference.
What to check
- Confirm ST01 identifies the configured transaction set and controls reconcile.
- Require a stable purchase-order number and issue date.
- Detect duplicate deliveries without duplicating the ERP order.
- Compare changed or cancelled order state before fulfilment.
- Preserve buyer, vendor and product identifiers exactly.
- Store the accepted order snapshot for downstream reconciliation.
Accepted shape
ST*850*0001~
BEG*00*SA*PO1001**20260717~
PO1*1*12*EA*19.99**VN*SKU100~Rejected shape
The same PO is imported twice, or an older PO revision overwrites a later cancellation.How to fix it
Use the trading partner plus purchase-order identity and revision metadata as an idempotency key. Quarantine unknown item identifiers, process changes as state transitions, and make downstream documents read from the accepted immutable snapshot instead of reparsing arbitrary files.
Evidence boundary
Shipment Sentry currently publishes educational and reconciliation guidance for 850; production validation remains limited to the formats explicitly listed on the validator. Obtain the appropriate X12 commercial-use licence before embedding licensed X12 metadata.
Sources