EDI Integrations (ERP, WMS, CRM)

Setting up EDI integrations means creating a direct link between the EDI platform and your internal systems — ERP, WMS, CRM, e-commerce. The goal is that an inbound EDI document lands as a real record in the system that should own it.

Where EDI usually lands

ERP — purchase orders, invoices and payments. Often the system of record for finance.
WMS — advance ship notices, inventory updates, warehouse activity confirmations.
CRM — order status updates, customer-facing acknowledgments, shipment tracking.

Two integration patterns

Most modern EDI flows use one of two patterns:

Webhook-driven — EDIFlux POSTs translated documents to a URL you provide as soon as they arrive. Your integration code decides what to do with them.
Pull-based — your application calls the EDIFlux REST API on a schedule (or in response to a user action) to fetch documents.

Mapping the two directions

Inbound: EDIFlux parses, validates, optionally enriches (e.g. resolves partner SKU → internal SKU), then hands off. Outbound: your application calls EDIFlux with a JSON document and the target partner and document type; EDIFlux generates and sends the EDI.

Idempotency keys save weekends

Integrations that retry inbound webhooks without an idempotency key end up creating duplicate orders. EDIFlux includes a stable document ID on every webhook so your integration can deduplicate.