Connect Make to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Make and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Make EDI
XEDI works alongside Make, formerly Integromat, which is capable enough to build a passable trading integration and therefore capable enough to leave you owning one. The sensible division is worth thinking about before you start.
One managed platform, no custom code
XEDI maps Make to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Make is powerful enough to be a trap here
Make can parse structured data, branch on conditions, loop, transform and call APIs. Somebody competent could put together something that receives a retailer's file, reshapes it and posts it onward, and it would work.
That is the difficulty rather than the recommendation. A scenario that mostly works becomes load-bearing quickly, and the person who built it becomes the only one who understands why a particular step exists. The failure is rarely dramatic; it is that a retailer changes a requirement and nobody notices until a deduction arrives.
Compliance is what you would actually be taking on
The reshaping is the easy part and it is what makes building look attractive. What you would also be adopting is knowing each retailer's current specification, noticing when it changes, handling the acknowledgement they expect within their window, retrying properly, and being able to prove a year later what was sent.
None of that is scenario logic, and none of it is visible when you start. Keeping it with us means Make continues doing what it is genuinely good at while nobody in your business becomes the person who owns retailer compliance by accident.
What your team sees day to day
You get an EDI mailbox and a portal that behaves like an inbox, with Make handling the automations around it that suit your way of working.
Demand arrives, the despatch advice reflects what genuinely shipped with SSCC labels where a retailer needs them, and the invoice follows delivery with confirmation it landed.
Make is bolted on around the edges rather than carrying the documents. Your scenarios stay yours and the retailer relationship stays ours.
Documents you can exchange
- Notifications and alerts into the tools your team uses
- Data pushed to dashboards and internal systems
- Light automations around the trading workflow
- Retailer orders handled in the portal or an integration
- Invoices and despatch advice produced from real shipment data
Built for Make teams
Whoever owns Make in your business, XEDI keeps EDI accurate and hands-off.
- Operations teams building their own automations
- Technically confident small businesses
- Agencies running client workflows
- Teams that outgrew simpler automation tools
- Anyone weighing building EDI themselves
Make EDI document types
Make carries data and signals around the workflow rather than the trading documents themselves.
| Document | What it carries | Direction |
|---|---|---|
| Order notifications | Signals into the tools your team uses when a retailer order needs attention. | XEDI to Make |
| Rejection alerts | Immediate notice of a partner rejection, routed by whatever logic you prefer. | XEDI to Make |
| Internal data pushes | Trading data reshaped into dashboards, sheets or internal systems. | XEDI to Make |
| Workflow automations | Scenario-driven steps around the trading process rather than within it. | Within Make |
| Delivery confirmations | Notice that an invoice or despatch advice reached the partner. | XEDI to Make |
| Trading documents | Carried by the platform rather than by a scenario, deliberately. | Not via Make |
How to connect Make with EDI using XEDI
The decision worth making early is what you are willing to own. The sequence below is what onboarding looks like from your side.
-
01
We look at what your existing scenarios already do.
-
02
We agree which parts of the workflow Make is genuinely well suited to.
-
03
We set the portal or an integration up to carry the trading documents themselves.
-
04
We connect Make for the automations around it, and prove nothing critical depends on a scenario.
-
05
You keep the flexibility you like without inheriting partner compliance.
Ready to connect Make?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Make EDI
Common requirements
- Existing scenarios in use
- Where your team wants data pushed
- What should trigger a person
- How orders are handled today
- The retailers you supply
What we need from you to build it
Only what we cannot decide for you. Retailer compliance is ours, which is the part that does not end.
- Existing scenarios
- What you already automate, so the division of labour fits how you work.
- Where data should go
- Which internal tools and dashboards want trading data pushed to them.
- What needs a person
- Which events should interrupt somebody rather than being recorded quietly.
- How orders are handled now
- Whether the portal or an integration will carry the documents themselves.
- The retailers you supply
- Which relationships this covers. Their requirements are already ours.
Why suppliers choose XEDI for Make
- Partners are usually connected already, which removes the main reason anybody starts building this themselves.
- Nobody in your business ends up owning retailer compliance because they once built a scenario.
- Make keeps the flexibility you chose it for, around a trading chain that does not depend on it.
- Retailer specification changes are noticed and handled by us rather than discovered at a deduction.
- A broken scenario costs you an automation, not a delivery.
- If a retailer raises a problem, it comes to us regardless of what your scenarios do.
Could we build EDI in Make?
Something that mostly works, yes, and that is the risk. It becomes load-bearing, only one person understands it, and a retailer changing a requirement surfaces as a deduction rather than an alert.
So what should Make do?
What it is good at: pushing data into your dashboards and internal systems, and automating the steps around the trading process according to logic you control.
Is this the same as the Zapier arrangement?
Similar division, different reasoning. Zapier is not capable enough to be tempting; Make is, which makes the decision about what you are willing to own rather than about what is possible.
Plan your Make EDI setup
Everything you need to scope, map and go live with Make, in one place.