EDI Guides
Public implementation guidance for DataShift canonical EDI documents, validation, webhooks, and versioned contracts.
Guides
Start here for lifecycle, integration, and operational guidance.
Schemas
Canonical PO, POA, ASN, and INV schema documentation.
Validation
Required fields, enums, date/time, currency, tax, and extension rules.
Webhooks
Delivery lifecycle, retries, and idempotency for public events.
Errors
Public error codes with remediation guidance.
Versioning
Immutable schema releases, compatibility policy, and CDN behavior.
Document Lifecycle
The public canonical flow starts with a purchase order and carries correlation references through acknowledgement, shipment, and invoice reconciliation.
Purchase Order
Buyer creates the order and establishes the business reference.
The PO creates the correlationId and line-level uniqueLineKey values used downstream.
Purchase Order Acknowledgement
Supplier accepts, rejects, backorders, or qualifies order lines.
Acknowledgement lines should preserve the original PO uniqueLineKey.
Advance Shipping Notice
Supplier describes shipped goods before receipt.
ASN lineItems are authoritative; packages reference those lines through lineReferences.
Invoice
Supplier requests payment and supports reconciliation.
Invoice lines should reference PO or ASN lines with uniqueLineKey when available.