Connect OneDrive to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between OneDrive and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with OneDrive EDI
XEDI can exchange trading files through OneDrive or SharePoint document libraries, which is usually the path of least resistance for businesses already standardised on Microsoft 365.
One managed platform, no custom code
XEDI maps OneDrive to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Staying inside the tenant is often the real reason for choosing this
For many organisations the deciding factor is not capability, it is governance. Files stay within Microsoft 365, under existing retention and compliance policy, covered by controls IT has already approved, and nobody has to justify a new service.
That is a legitimate reason and frequently the strongest one. The trade is that you inherit the tenant's behaviour too, including its sync model and its versioning, both of which matter more for automated exchange than for documents people edit.
Personal OneDrive and SharePoint are not the same thing
They are commonly spoken about interchangeably and they are not. A personal OneDrive belongs to an individual, which means it can disappear when that person leaves, and a trading exchange should not be tied to somebody's account.
A SharePoint document library belongs to the organisation and survives staff changes, which is almost always the right choice. Versioning is the other difference worth settling early: a library that keeps versions will keep them for machine-written files too, which changes retention behaviour in ways nobody intended.
What your team sees day to day
You get an EDI mailbox and a portal that behaves like an inbox, showing what has been collected and what is outstanding without anyone opening a library.
Orders arrive and become the despatch advice raised from what is actually going, adjusted where quantities moved, carrying SSCC pallet labels where required, with the invoice following delivery and its arrival confirmed in the dashboard.
The library is just the route. If you later connect a system directly, files stop flowing through Microsoft 365 and your partners notice nothing. Nothing in the tenant changes shape; EDI is added onto the document libraries you already run.
Documents you can exchange
- Order files written to a library for your system to collect
- Despatch and quantity files collected from a library
- Invoice data exported for finance
- Stock and price files exchanged with partners
- Exception files for correction
Built for OneDrive teams
Whoever owns OneDrive in your business, XEDI keeps EDI accurate and hands-off.
- Businesses standardised on Microsoft 365
- IT teams preferring to stay within the tenant
- Finance and operations staff
- Suppliers whose systems export to a network location
- Organisations with policies against outside file services
OneDrive EDI document types
A document library carries files; these are the exchanges they usually serve.
| Document | What it carries | Direction |
|---|---|---|
| Order files | Retailer demand written to a library for a system that collects rather than integrates. | XEDI to library |
| Despatch files | What is actually being sent, collected and validated before it becomes a despatch advice. | Library to XEDI |
| Invoice data | Invoice detail exported for a finance system that imports from a network location. | XEDI to library |
| Stock and price files | Availability or catalogue data exchanged on a schedule with partners expecting it. | Either direction |
| Archived files | Processed files moved aside so nothing is collected twice. | Within the library |
| Exception files | Anything failing validation, written back with the reason. | XEDI to library |
How to connect OneDrive with EDI using XEDI
Most of the decisions here are governance ones rather than technical. The sequence below is what onboarding looks like from your side.
-
01
We establish whether this is personal OneDrive or a SharePoint library, because they behave differently.
-
02
We agree the locations, naming and who else has access.
-
03
We connect with permissions scoped to those locations rather than the tenant.
-
04
We prove the flows, including behaviour under sync delays and versioning.
-
05
You get an exchange route inside the Microsoft estate your business already runs.
Ready to connect OneDrive?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about OneDrive EDI
Common requirements
- Whether OneDrive or SharePoint is being used
- Tenant and location detail
- Permission scope available to you
- Versioning and retention policy
- The trading partners the files relate to
What we need from you to build it
Only what we cannot decide for you. Partner requirements are ours; where files live is your organisation's decision.
- OneDrive or SharePoint
- Which is actually being used, since a personal OneDrive is tied to an individual and a library is not.
- Tenant and locations
- Where exchange files will live, so permissions can be scoped there rather than broadly.
- Permission scope
- What your IT policy allows to be granted, which often shapes the design more than anything technical.
- Versioning and retention
- Whether the library keeps versions, because it will do so for machine-written files too.
- The partners the files relate to
- Which relationships this serves. Their requirements are already held by us.
Why suppliers choose XEDI for OneDrive
- Partners are generally connected already, so the only real decision is where files live inside your tenant.
- Trading files stay inside your Microsoft tenant, under policies IT has already approved.
- The exchange is built on a SharePoint library rather than an individual's OneDrive, so it survives staff changes.
- Versioning and retention behaviour is settled deliberately rather than discovered at an audit.
- Collection state is visible in the platform rather than inferred from a folder.
- If a partner raises a problem, it comes to us whatever route the file took.
Should we use OneDrive or SharePoint?
A SharePoint document library, in almost every case. A personal OneDrive belongs to an individual and can disappear when they leave, which is not a sound basis for a trading exchange.
Will this satisfy our IT policy?
It is usually chosen for exactly that reason: files remain within Microsoft 365 under existing retention and compliance controls, so no new service needs approving.
Does versioning cause problems?
It can, because a library keeping versions will keep them for machine-written files too, which affects retention in ways nobody planned. It is settled during scoping.
Plan your OneDrive EDI setup
Everything you need to scope, map and go live with OneDrive, in one place.