What does 'both directions' mean?
CleanEDI handles EDIFACT in both directions. Inbound: your trading partner sends raw EDIFACT, we deliver clean JSON to your webhook or API. Outbound: your system POSTs JSON to us, we generate valid EDIFACT and deliver it to your trading partner via AS2 or SFTP. Your team never writes or reads a single EDIFACT segment either way.
Do you only support JSON? What if my system uses XML or another format?
JSON, XML, and CSV are all supported out of the box. If your system already produces or consumes any of these, CleanEDI will work with it directly with no extra configuration. If you are working with X12 (the North American EDI standard), fixed-width flat files, or another format, talk to us during onboarding and we will sort it out. The goal is always that your team keeps using whatever format they already work with.
Do I need to know anything about EDIFACT to get started?
No. That is the whole point. You tell us what data you want to send or receive in plain business terms, we handle everything EDIFACT-related on your behalf. Your developers work with JSON, XML, or CSV. They never need to open an EDIFACT specification document.
How long does onboarding take?
Most Foundation customers are live with their first trading partner within two to three weeks. Scale customers with multiple partners typically take four to six weeks depending on the number of partners and message types. Enterprise timelines depend on scope and are agreed during the proof-of-concept engagement. We do not go live until we have tested end to end with your first partner.
Do I need to change anything on my trading partner's side?
No. Your trading partner continues sending and receiving EDIFACT exactly as they do today. From their perspective nothing changes. CleanEDI sits on your side of the boundary and handles the translation. You do not need to go back to your trading partners and ask them to change anything.
Does CleanEDI send functional acknowledgements automatically?
Yes. When an inbound EDIFACT message is received, CleanEDI automatically generates and sends a CONTRL acknowledgement back to the trading partner. This is standard behaviour on all plans and satisfies requirements from platforms like SPS Commerce and other EDI networks.
What happens if a message fails?
You are notified immediately via webhook or email depending on your configuration. Every message is logged with its full status, error detail, and the raw content so you can see exactly what happened. Messages can be replayed once the issue is resolved, 30 days on Foundation and 90 days on Scale and Enterprise. Nothing is silently dropped.
Are there per-message fees?
No. Your plan covers everything within your partner and message type limits. No charges per message, no surprise bills at month-end.
What counts as a trading partner?
Each organisation you exchange EDIFACT messages with counts as one trading partner. Multiple message types with the same partner still count as one.
What happens if I exceed my partner limit?
We will talk to you before anything breaks. Additional partners can be added at a prorated rate or we move you to the next tier, whichever makes more sense.
What if my trading partner is not on a supported list?
There is no fixed supported list. CleanEDI works with any trading partner that communicates via EDIFACT regardless of which platform or VAN they use, MessageXchange, SPS Commerce, GXS, Orderful, or a direct AS2 connection. If your partner sends or receives EDIFACT, we can work with them.
Do you support AS2 and SFTP?
Yes, both. We handle the transport layer so your systems connect to us via REST or webhook and we deal with AS2 and SFTP on the trading partner side.
Is my data secure? Where is it stored?
All data is encrypted in transit and at rest. We store message data in Azure data centres in Australia by default, keeping your data in-region for APAC customers. Enterprise customers can request dedicated deployments with custom data residency requirements. We are working toward ISO 27001 certification and can provide a security overview on request.
Can I trial it before committing to an annual contract?
Yes. We offer a proof-of-concept engagement before any contract is signed. We configure a real end-to-end flow with one of your actual trading partners so you can see exactly how CleanEDI works with your specific setup before you commit to anything.
What is included in onboarding?
We configure your partner profiles, message mappings, transport connections (AS2 or SFTP), and webhook or API delivery. We test end to end with your first partner before you go live. Foundation and Scale plans include this as standard. You do not pay separately for onboarding.
Can I start with one direction and add the other later?
Yes. Some customers start with inbound only (partner sends EDIFACT, you receive JSON) and add outbound (you send JSON, partner receives EDIFACT) later. Your plan covers both from day one regardless.
What support do I get?
All plans include email support with a 24-hour response commitment on business days. Scale plans include priority support with a 4-hour response target. Enterprise plans include a named customer success engineer and negotiated response SLAs. During onboarding every customer has a direct line to the team regardless of plan.
What is your disaster recovery and business continuity policy?
CleanEDI runs on Azure infrastructure with built-in redundancy, geo-redundant storage, and automatic failover for core services. All messages are persisted before processing so nothing is lost if a service restarts. Message replay is available for 30 days on Foundation and 90 days on Scale and Enterprise plans. We are working toward formal DR documentation and ISO 27001 certification. Enterprise customers can request our current security and infrastructure overview before committing to a contract.