Integrations

Works with what you already use.

CleanEDI delivers clean data in the format your systems expect. D365, SAP, Business Central, CloudSuite, NetSuite, or any system that accepts a webhook or REST call. No VAN required.

See pricingTry the decoder
No VAN required

Replace your EDI VAN with an API

Traditional VANs charge per-message fees, annual platform costs, and professional services for every change. CleanEDI connects directly to your trading partners via AS2 or SFTP with flat monthly pricing. No per-message fees. No Christmas spike surcharges.

Direct AS2 and SFTP connections to trading partners
Flat monthly pricing, no per-message fees
Works alongside your existing VAN during transition
No professional services required for message type changes
Available now

Live connectors

Early AccessERP

Microsoft D365 F&O

CleanEDI delivers normalised EDIFACT data into D365 Finance and Operations via OData entities. Inbound ORDERS arrive as purchase orders, inbound INVOIC as vendor invoices, inbound DESADV as product receipts. The connector handles the EDIFACT-to-D365 mapping including partner cross-references, GLN-to-account resolution, site and warehouse mapping, and legal entity routing.

What it covers
Inbound ORDERS to D365 purchase orders via OData
Inbound INVOIC to D365 vendor invoices
Inbound DESADV to D365 product receipts
GLN to D365 account and vendor resolution
Site, warehouse, and legal entity routing
Azure AD authentication, no credentials stored
Outbound D365 invoices to EDIFACT INVOIC (in development)
Common questions
Does it create real D365 records or just deliver JSON?

Real D365 records via OData data entities. A purchase order lands in D365 as a purchase order, not as a file you need to process separately.

How are GLN numbers resolved to D365 accounts?

The CleanEDI partner registry maps GLN numbers to D365 account, vendor, and customer IDs. This is configured during onboarding and maintained by CleanEDI.

By engagementERP

Infor CloudSuite / M3

CleanEDI's EDIFACT platform already handles ORDERS, DELFOR, DESADV, INVOIC, CONTRL and RECADV end to end. CloudSuite and M3 specific data mapping, resolving partner references to your CloudSuite records, is scoped and built as part of onboarding for manufacturing and distribution businesses.

What it covers
Inbound ORDERS and DELFOR normalised to clean business data
Outbound DESADV generated from CloudSuite shipment data
CONTRL and RECADV acknowledgement handling
Delivery schedule and production planning data support
Delivered via ION, REST, or webhook depending on your environment
Partner-specific EDIFACT dialects isolated from CloudSuite customisations
Common questions
Is there a pre-built CloudSuite connector today?

The EDIFACT platform is live. The CloudSuite-specific data mapping is scoped and built per engagement rather than delivered as a self-serve connector today.

Does this cover M3 as well as CloudSuite Industrial?

Yes, the integration boundary is the same, what changes is how data is delivered into your specific environment.

By engagementWMS / SCM

Blue Yonder

CleanEDI's EDIFACT platform already handles ORDERS, DESADV, INVOIC, CONTRL and RECADV end to end. Blue Yonder specific delivery, into Blue Yonder Connect, a middleware layer, or your own APIs, is scoped and built as part of onboarding.

What it covers
Inbound ORDERS normalised to clean purchase order data
Outbound DESADV generated from shipment and pick confirmation events
CONTRL and RECADV acknowledgement handling
Delivered into Blue Yonder Connect, middleware, or your own APIs
Works alongside your existing full-service EDI provider during transition
Partner-specific EDIFACT dialects isolated from warehouse and planning logic
Common questions
Does this replace Blue Yonder Connect?

No, CleanEDI sits upstream and handles trading-partner EDIFACT specifically, then delivers clean data into Blue Yonder Connect or any integration layer you already run.

Can you generate ASNs from shipment events?

Yes, advance ship notice generation from shipment and pick confirmation data is a core outbound flow.

AvailableMessaging

Message Queues and Event Streams

CleanEDI publishes normalised business events to your message queue or event stream of choice. Azure Service Bus, Amazon SQS, Google Cloud Pub/Sub, and Kafka are all supported. Any downstream consumer picks up clean structured messages without knowing anything about EDIFACT.

What it covers
Azure Service Bus topics and queues
Amazon SQS and SNS
Google Cloud Pub/Sub
Apache Kafka (managed or self-hosted)
Clean JSON, XML, or CSV payload
Dead-letter handling included
Works with Azure Functions, Lambda, Cloud Run
Managed identity and IAM authentication supported
Always availableUniversal

Webhook / REST

Every CleanEDI plan includes webhook and REST delivery as standard. If your system can receive an HTTP POST or call an API, it can connect to CleanEDI with no additional connector required. JSON, XML, and CSV payloads are all supported out of the box.

What it covers
HTTP POST to any endpoint you specify
JSON, XML, or CSV payload
HMAC signature verification included
Retry with exponential backoff
Dead-letter queue for failed deliveries
Works with any language or framework
No connector installation required
Coming soon

More connectors in progress

If you need one urgently, get in touch and we will prioritise it.

ERP

Microsoft D365 Business Central

Separate connector for Business Central covering purchase orders, invoices, and fulfilment. Targeted at mid-market businesses on the Business Central stack.

ERP

SAP ECC / S4HANA

SAP connector for inbound and outbound EDIFACT. Targeted at large enterprise customers in manufacturing, logistics, and retail.

ERP

NetSuite

Mid-market connector for NetSuite covering purchase orders, invoices, and fulfilment flows for growing businesses.

Microsoft

Power Platform

Custom connector for Power Automate and Power Apps. Non-developer teams can build EDIFACT-connected workflows without writing code.

E-commerce

Adobe Commerce

B2B and retail connector for Adobe Commerce and Magento. Covers supplier order flows, inventory updates, and invoice reconciliation.

E-commerce

Shopify

Connector for Shopify merchants receiving EDIFACT purchase orders from large retail or wholesale buyers.

Accounting

MYOB

APAC-focused connector for MYOB Business and MYOB Advanced. Covers supplier invoices and purchase orders for Australian and New Zealand businesses.

Accounting

Xero

Connector for Xero covering inbound supplier invoices and outbound purchase order confirmations for APAC SMB suppliers.

EDI without a VAN

Common questions about replacing your VAN

Do I need a VAN to use CleanEDI?

No. CleanEDI connects directly to your trading partners via AS2 or SFTP without requiring a value-added network. You pay for the integration capability, not per-message fees to a VAN. For trading partners who require a VAN connection, CleanEDI can sit behind your existing VAN and handle everything from there.

How much do businesses typically save by replacing their VAN?

VAN costs vary widely but per-message fees, annual platform fees, and professional services often add up to tens of thousands of dollars per year for active trading partners. CleanEDI's flat monthly pricing means you know your cost regardless of message volume. No Christmas spike surcharges.

Can CleanEDI work alongside our existing VAN?

Yes. Many customers start by routing new trading partner connections through CleanEDI while keeping existing VAN connections in place. Over time they migrate existing connections as VAN contracts expire.

What trading partners does CleanEDI support?

CleanEDI works with any trading partner that communicates via EDIFACT regardless of which platform or VAN they use. This includes MessageXchange, SPS Commerce, GXS, TrueCommerce, and direct AS2 connections. CleanEDI handles the EDIFACT parsing, validation, and transformation into clean business data for your systems.

Universal compatibility

Connect anything via REST or webhook

If your system is not on the list, it can almost certainly still connect to CleanEDI. Any system that can receive an HTTP POST can connect with no additional setup.

Talk to us
Any language or framework
Python, .NET, Java, Node, Go. We send HTTP, you handle it your way.
Any cloud
Azure, AWS, GCP, or on-premise. CleanEDI is not tied to any cloud provider.
JSON, XML, or CSV
We deliver in the format your system already expects.
Your APIs stay as-is
You do not need to rebuild your APIs to work with CleanEDI.
We handle the trading partner side
AS2, SFTP, EANCOM, GS1 all stay on our side. You never see it.

Ready to connect?

Tell us what systems you are working with and we will map out exactly how CleanEDI would fit. No commitment required.

Get in touchSee pricing