DataShift EDI
Public documentation for DataShift canonical EDI documents, validation, operational errors, versioned contracts, and generated schema models.
What DataShift publishes
Versioned JSON Schema and OpenAPI contract artifacts, human-readable document models, validation guidance, public error codes, and release notes.
How to prepare
Validate payloads against the published schemas, preserve correlation identifiers, understand DataShift-managed fields, and store public error codes with business references.
Where to start
Implement the lifecycle in order: Purchase Order, Purchase Order Acknowledgement, Advance Shipping Notice, then Invoice.
Guides
Start here for lifecycle, integration, and operational guidance.
Documents
Canonical PO, POA, ASN, and INV pages with schemas, models, and versions.
Validation
Required fields, enums, date/time, currency, tax, and extension rules.
Errors
Public error codes with remediation guidance.
Versioning
Immutable schema releases, compatibility policy, and CDN behavior.
Document Lifecycle
The canonical lifecycle starts with a purchase order and preserves correlation references through acknowledgement, shipment, and invoice reconciliation.
Purchase Order
Buyer creates the order and establishes the business reference.
Purchase Order Acknowledgement
Supplier accepts, rejects, backorders, or qualifies order lines.
Advance Shipping Notice
Supplier describes shipped goods before receipt.
Invoice
Supplier requests payment and supports reconciliation.