Connect Adobe Commerce to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Adobe Commerce and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Adobe Commerce EDI
XEDI connects Adobe Commerce, formerly Magento, with retailer EDI so wholesale orders arrive against the right accounts and prices, and despatch confirmations and invoices go back out without manual handling.
One managed platform, no custom code
XEDI maps Adobe Commerce to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Adobe Commerce is a platform you have built on, which is the complication
Two Adobe Commerce stores are rarely alike. Attribute sets, SKU conventions, customer groups and extensions differ by build, and a great deal of behaviour lives in code somebody wrote for you rather than in the platform itself.
An EDI integration therefore cannot be scoped against Adobe Commerce generally. It is scoped against your store, because where a wholesale order should be created and what it must carry depends on decisions made during your build.
B2B capability exists, but the estate decides whether it is used
Adobe Commerce offers company accounts, shared catalogues and tier pricing, and some builds use them thoroughly while others handle wholesale entirely through customer groups and price rules. Neither is wrong, but they map differently.
We establish which you are actually using before mapping, because an order priced through a shared catalogue and an order priced through a customer group arrive at the same number by different routes, and only one of them will still be right after your next price change.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox, so retailer orders arrive separately from consumer traffic and are handled to the retailer's requirements.
The order becomes the despatch advice from what was actually shipped, amended where the delivery differs, with SSCC labels for the pallets, and becomes the invoice on delivery, whose arrival is confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders are created in Adobe Commerce and shipments raise the outbound documents. Larger estates often add our API alongside for finer granularity.
Documents you can exchange
- Retailer orders landing as Adobe Commerce orders
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages from shipment
- Invoices raised against the shipment
- Catalogue and tier price data where a retailer requires it
Built for Adobe Commerce teams
Whoever owns Adobe Commerce in your business, XEDI keeps EDI accurate and hands-off.
- Brands running direct and wholesale on one platform
- Ecommerce managers and developers
- Operations and fulfilment teams
- Finance teams handling wholesale terms
- Agencies supporting Adobe Commerce builds
Adobe Commerce EDI document types
These are the wholesale flows; your consumer storefront continues as it does now.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand creating an Adobe Commerce order against the right customer, website and price. | Retailer to Adobe Commerce |
| Order acknowledgements | What will be supplied once stock is committed, including short and substituted lines. | Adobe Commerce to retailer |
| Advanced shipping notices | Pallet and carton detail from the shipment record, with SSCC labels for the retailer's goods-in. | Adobe Commerce to retailer |
| Invoices | Raised against the shipment and referenced so the retailer can match them automatically. | Adobe Commerce to retailer |
| Credit notes | Credit memos against the invoice being corrected, where a delivery is short or rejected. | Adobe Commerce to retailer |
| Catalogue and tier prices | Product, pack and price data published where a retailer maintains a catalogue against your range. | Adobe Commerce to retailer |
How to connect Adobe Commerce with EDI using XEDI
The build is scoped against your store rather than the platform, because that is where the decisions live. The sequence below is what onboarding looks like from your side.
-
01
We scope which websites, store views and customer groups carry wholesale in your Adobe Commerce estate.
-
02
We build the mapping between each retailer's documents and your customers, products, attribute sets and tier prices.
-
03
We configure validation so the retailer's terms are enforced before an Adobe Commerce order is raised.
-
04
We prove the order, shipment and invoice flows against what each retailer requires and against how your store is built.
-
05
You get wholesale arriving correctly priced, and we keep it right through upgrades and extension changes.
Ready to connect Adobe Commerce?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Adobe Commerce EDI
Common requirements
- Adobe Commerce version and hosting arrangement
- Website, store view and customer group structure
- Product attribute and SKU conventions
- Tier price and B2B configuration
- The trading partners you deal with, or plan to
What we need from you to build it
Only what we cannot hold for you. Retailer requirements are already ours; what we need is how your store was built.
- Version and hosting
- Which Adobe Commerce version you run and where, including whether extensions affect order creation or pricing.
- Website and customer group structure
- Which websites and groups carry wholesale, since price and tax resolution follow them.
- SKU and attribute conventions
- How your SKUs are constructed and which attributes carry pack and barcode data for retailer identifiers.
- How wholesale is priced
- Whether through B2B shared catalogues, customer groups or price rules, because they map differently and age differently.
- Which retailers you supply
- The wholesale accounts in play, now and later. Their requirements sit with us.
Why suppliers choose XEDI for Adobe Commerce
- Retailers are generally connected already, so wholesale can begin before your store build is understood in detail.
- The build is scoped against the store you actually have rather than a standard Adobe Commerce install.
- How wholesale is priced is established first, so an order does not arrive correct today and wrong after your next price change.
- Retailer requirements sit with us, so a platform upgrade or extension change does not put trading at risk.
- A new wholesale customer is our work rather than a development ticket for your agency.
- If a retailer raises a problem, it comes to us and we correct it on your behalf.
Does this work with Adobe Commerce B2B?
Yes, and where you use company accounts and shared catalogues an order can land against them directly. Where wholesale is handled through customer groups and price rules instead, that is mapped as it is, because both are common.
Will an upgrade break the integration?
Retailer-specific rules sit with us rather than inside your store, so an upgrade affects one interface rather than every retailer arrangement. We monitor the flows and adjust as the platform and your extensions change.
Is this Magento?
Yes. Magento Commerce became Adobe Commerce, and Magento Open Source remains. Which you run affects what is available, and it is confirmed at the start.
Plan your Adobe Commerce EDI setup
Everything you need to scope, map and go live with Adobe Commerce, in one place.