Connect Epicor to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Epicor and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Epicor EDI
XEDI connects Epicor ERP workflows with EDI trading partners, helping manufacturers, distributors and suppliers automate order, fulfilment and invoice documents while keeping partner-specific compliance rules outside the ERP team’s daily workload.
One managed platform, no custom code
XEDI maps Epicor to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Demand Management is a starting point, not the whole job
Epicor ships EDI capability through Demand Management, which handles the shape of a demand record well. What it does not do is absorb the variation between trading partners: the document sets, identifiers, validation rules and connection routes that differ for every retailer you supply.
That variation is where an integration earns its keep. Each new retailer is a build we take on, against their specification, rather than another mapping project landing with your team.
Demand entries, releases and the reconciliation problem
Epicor models retailer demand as demand contracts and releases rather than as discrete orders. Retailers do not, and a purchase order that maps cleanly to a release one week can conflict the next when a partner revises quantities against the same reference.
Deciding up front how revisions, cancellations and partial acceptance are represented in Epicor prevents the common outcome where the demand record and the retailer's order file disagree and nobody can say which is right.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox. Orders arrive, your team is notified, and nothing waits on the Epicor integration being complete.
The order then becomes the despatch advice rather than being re-entered as one, amended if the delivery differs, with SSCC labels for the pallets, and becomes the invoice on delivery. Delivery of that invoice is confirmed in the dashboard rather than assumed.
The integration sits over that workflow and automates it, so demand lands in Epicor and fulfilment raises the outbound documents rather than someone confirming each one. Smaller teams run on the portal alone; enterprises with finer requirements go to our API. An Epicor integration is the middle: planners see partner demand where they already work.
Documents you can exchange
- Purchase orders
- Order acknowledgements
- Advance shipping notices
- Invoices
- Inventory or product updates where required
Built for Epicor teams
Whoever owns Epicor in your business, XEDI keeps EDI accurate and hands-off.
- Manufacturers using Epicor
- Wholesale distributors
- Supply chain teams
- EDI coordinators
- Finance and order processing teams
Epicor EDI document types
Epicor supplier programmes usually run these flows, with the exact set fixed by the retailer.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a demand entry or sales order, against the right customer, part and ship-to. | Partner to Epicor |
| Order acknowledgements | Confirmation of accepted, amended and rejected lines back to the partner. | Epicor to partner |
| Advanced shipping notices | Despatch advice raised from the Epicor shipment, including pack structure where required. | Epicor to partner |
| Invoices | Invoices referenced to the order and delivery so the partner can match them automatically. | Epicor to partner |
| Credit notes | Credits and adjustments against a previously sent invoice. | Epicor to partner |
| Delivery forecasts | Scheduled demand from partners that forecast rather than order line by line. | Partner to Epicor |
How to connect Epicor with EDI using XEDI
Epicor connections are normally staged one partner at a time so demand mapping issues stay contained.
-
01
We scope the Epicor environment, document flows and trading partners in play.
-
02
We build the mapping between each partner's documents and your Epicor records, parts, customers and fulfilment rules.
-
03
We configure validation and exception handling so partner rules are enforced before anything reaches Epicor.
-
04
We prove each document flow against what the partner requires and against your own process.
-
05
You get demand landing in Epicor the way your planners expect, and we keep it aligned as partners change.
Ready to connect Epicor?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Epicor EDI
Common requirements
- Epicor access method and export/import format
- Customer, item and warehouse references
- The trading partners you deal with, or plan to
- ASN, packaging and shipment rules
- Invoice and tax mapping requirements
What we need from you to build it
Only the things we cannot hold for you. What each retailer requires is already ours, so nobody has to chase a specification.
- Epicor access
- Permission to read and write the demand, shipment and invoice records in scope, in the company and site being traded from.
- Customer and ship-to mapping
- Each partner mapped to a customer, each delivery point mapped to the GLN the partner uses.
- Part and pack data
- GTINs per packaging level and the conversion between the retailer's ordering unit and your stocking unit.
- Revision handling
- An agreed rule for how amendments, cancellations and partial acceptance are represented against an existing demand.
- Which partners you trade with
- The retailers in scope, now and next. Their document set, standard and connection route are already on our side.
Why suppliers choose XEDI for Epicor
- Most retailers are already on our network, so trading can begin before the Epicor work is signed off.
- Retailer variation is handled in the platform rather than inside Epicor, so Demand Management stays as configured.
- Documents are validated against partner rules before sending, so rejections do not arrive as payment problems.
- Taking on a retailer costs your team nothing: the mapping, testing and sign-off are ours.
- One connection carries EDIFACT, TRADACOMS and X12.
- If a retailer raises an issue, it comes to us. We are notified on your behalf and put it right before it becomes a delivery problem.
Can XEDI connect Epicor to retailer EDI requirements?
Yes. XEDI can manage retailer-specific EDI requirements and connect the mapped data to Epicor workflows.
Which Epicor EDI documents are usually supported?
Common flows include purchase orders, acknowledgements, ASN messages, invoices and inventory updates depending on the trading partner.
Plan your Epicor EDI setup
Everything you need to scope, map and go live with Epicor, in one place.