Connect AWS to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between AWS and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with AWS EDI
XEDI exchanges trading files through S3, either on a schedule or triggered the moment an object lands, so EDI is added to the AWS estate your systems already write to.
One managed platform, no custom code
XEDI maps AWS to your trading partners and validates every document, so data flows straight into the systems your teams already use.
S3 can tell us a file has arrived, which changes the rhythm
Most file exchanges poll: look in the folder every so often and see what is there. S3 does not have to work that way, because object creation can raise a notification, and a despatch file can be picked up within seconds of your system writing it rather than at the next scheduled sweep.
That is worth having when the document is time-sensitive. A retailer's cut-off for a despatch advice does not care that your export runs at ten past the hour, and the difference between event-driven and scheduled collection is occasionally the difference between meeting it and not.
Lifecycle rules are the thing that catches people out
S3 lifecycle policies are usually written with cost in mind: move anything older than thirty days to a colder class, expire it after a year. Applied to a bucket that also carries trading files, they will do exactly that to documents somebody later needs to retrieve.
Retrieval from an archival class is not instant and sometimes not cheap, which is an unwelcome discovery during a dispute about what was sent. So the lifecycle and versioning rules touching the exchange prefixes are established up front rather than inherited from whatever the bucket already had.
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 listing a bucket.
Orders arrive and become the despatch advice raised from what is actually going, adjusted where quantities differ, carrying SSCC pallet labels where the retailer requires them, with the invoice following delivery and its arrival confirmed in the dashboard.
Nothing about how your systems write to S3 needs to change. The EDI capability is bolted onto the storage you already run, and the partner requirements behind it stay ours.
Documents you can exchange
- Order files written to a bucket for your systems
- Despatch and quantity files collected from a prefix
- Invoice data exported for downstream processing
- Stock and catalogue files exchanged with partners
- Failed documents written to an exception prefix
Built for AWS teams
Whoever owns AWS in your business, XEDI keeps EDI accurate and hands-off.
- Engineering and platform teams
- Businesses with AWS-hosted systems
- Data teams consuming trading files
- Operations relying on automated exports
- Organisations standardised on AWS
AWS EDI document types
A bucket carries objects; these are the exchanges they usually serve.
| Document | What it carries | Direction |
|---|---|---|
| Order files | Retailer demand written to a prefix your systems already read from. | XEDI to S3 |
| Despatch files | What is actually shipping, collected on write and validated before it becomes a despatch advice. | S3 to XEDI |
| Invoice data | Invoice detail written out for downstream finance or analytics processing. | XEDI to S3 |
| Catalogue and stock files | Product or availability data exchanged with partners on an agreed cycle. | Either direction |
| Processed objects | Files moved to an archive prefix once handled, so nothing is collected twice. | Within the bucket |
| Exception objects | Documents that failed validation, written with the reason attached for correction. | XEDI to S3 |
How to connect AWS with EDI using XEDI
The interesting decisions are about triggering and lifecycle rather than connectivity. The sequence below is what onboarding looks like from your side.
-
01
We agree the buckets and prefixes used, and whether collection is scheduled or event-driven.
-
02
We set up access with a role or key scoped to those prefixes rather than the account.
-
03
We fix object naming so collection is unambiguous and reprocessing is impossible.
-
04
We prove the flows, including behaviour when lifecycle rules or versioning are in play.
-
05
You get EDI running against storage your systems already use, without changing how they write.
Ready to connect AWS?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about AWS EDI
Common requirements
- Buckets, prefixes and regions in scope
- How access should be granted
- Object naming convention
- Lifecycle and versioning rules that apply
- The trading partners the files relate to
What we need from you to build it
Only what we cannot decide for you. Partner requirements stay ours; the storage conventions are agreed together.
- Buckets and prefixes
- Which locations carry exchange traffic, so access can be scoped there rather than account-wide.
- Access method
- Whether a role or a key is granted, and what your security policy permits, since that often shapes the design.
- Object naming
- How objects are named, because collection and duplicate detection depend on recognising them reliably.
- Lifecycle and versioning
- Any rules that would move or expire objects, since a trading document in an archival class is not retrievable on demand.
- The partners the files relate to
- Which relationships this serves. Their requirements are already held by us.
Why suppliers choose XEDI for AWS
- Your trading partners are very likely connected already, so the build is buckets and prefixes rather than partner onboarding.
- Collection can trigger on the object landing rather than waiting for the next sweep, which matters against a retailer cut-off.
- Lifecycle and versioning behaviour is settled before it quietly archives a document somebody needs.
- Access is scoped to the exchange prefixes rather than the wider account.
- Your systems keep writing to S3 exactly as they do now.
- Partner requirements, validation and connections remain ours whatever the storage layer does.
Can you pick files up as soon as they are written?
Yes. Object creation can trigger collection rather than waiting for a scheduled sweep, which is worth having where a retailer's cut-off is tight relative to when your export runs.
Will our lifecycle rules cause problems?
They can. A rule moving objects to an archival class will do so to trading documents, and retrieval from there is neither immediate nor free. Those rules are established at the start.
Do you need broad access to our account?
No. Access is scoped to the buckets and prefixes carrying exchange traffic, granted by whichever method your security policy prefers.
Plan your AWS EDI setup
Everything you need to scope, map and go live with AWS, in one place.