DataShift
EDI

EDI Guides

DataShift EDI implementation guides: how a purchase order moves through validation, mapping and acknowledgment, and what to prepare before onboarding a partner.

Public implementation guidance for DataShift canonical EDI documents, validation, errors, and versioned contracts.

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 public canonical flow starts with a purchase order and carries correlation references through acknowledgement, shipment, and invoice reconciliation. Open Documents.

PO: Purchase Order

Buyer creates the order and establishes the business reference.

The PO creates the correlationId and line-level uniqueLineKey values used downstream.

POA: Purchase Order Acknowledgement

Supplier accepts, rejects, backorders, or qualifies order lines.

Acknowledgement lines should preserve the original PO uniqueLineKey.

ASN: Advance Shipping Notice

Supplier describes shipped goods before receipt.

ASN lineItems are authoritative; packages reference those lines through lineReferences.

INV: Invoice

Supplier requests payment and supports reconciliation.

Invoice lines should reference PO or ASN lines with uniqueLineKey for automatic reconciliation.

Last updated on

DataShift EDI

Public DataShift EDI documentation for canonical documents, validation, errors, and versioned contracts.

EDI Documents

DataShift EDI document pages for PO, POA, ASN, and invoice schemas, models, and versions.

On this page

Document LifecyclePO: Purchase OrderPOA: Purchase Order AcknowledgementASN: Advance Shipping NoticeINV: Invoice