Connect SYSPRO to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between SYSPRO and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with SYSPRO EDI
XEDI connects SYSPRO with retailers, wholesalers and logistics providers so EDI orders, acknowledgements, dispatch notes and invoices move between SYSPRO and your trading partners without manual entry.
One managed platform, no custom code
XEDI maps SYSPRO to your trading partners and validates every document, so data flows straight into the systems your teams already use.
SYSPRO's business objects make the connection straightforward
SYSPRO exposes its functions as business objects rather than expecting anyone to write against tables, and an EDI integration uses that. A retailer's order becomes a sales order against the right customer, stock code and warehouse; a despatch raises the dispatch note; the invoice run produces the invoice.
Because those objects are documented and stable, the connection itself is rarely where a project struggles. The work is that a retailer describes the same physical item completely differently from your stock file, and that has to resolve every time without a human adjudicating.
Stock codes are where a retail programme meets reality
Manufacturers running SYSPRO often carry stock codes that encode something internal: a revision, a plant, a customer-specific variant. A retailer sends a GTIN. Neither side is going to change, so the mapping between them is the integration, and it has to survive a stock code being superseded.
Unit of measure sits alongside it. A retailer ordering in cases against an item held in eaches produces a quantity that passes every check and invoices at the wrong value, which is typically found at reconciliation rather than at the order.
What your team sees day to day
You get an EDI mailbox and a portal that behaves like an inbox: retailer orders arrive, your team is notified, and trading can begin before the SYSPRO work is signed off.
The order then becomes the despatch advice rather than being re-keyed as one, amended where you are shipping differently from what was ordered, 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 land as SYSPRO sales orders and despatches raise the outbound documents. Smaller operations run the portal alone; our API serves enterprises wanting finer granularity; a SYSPRO site normally wants the integration.
Documents you can exchange
- Purchase orders landing as SYSPRO sales orders
- Order acknowledgements returned to trading partners
- Dispatch notes and ASN messages from SYSPRO despatch
- Invoices raised from SYSPRO
- Stock and price data where a partner maintains a catalogue
Built for SYSPRO teams
Whoever owns SYSPRO in your business, XEDI keeps EDI accurate and hands-off.
- SYSPRO administrators
- Manufacturers supplying retail and wholesale
- Distributors
- Despatch and warehouse teams
- Finance teams handling invoice runs
SYSPRO EDI document types
The set varies by retailer, but a SYSPRO supplier programme is usually built from these flows.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a SYSPRO sales order against the right customer, stock codes, price and warehouse. | Partner to SYSPRO |
| Order acknowledgements | What SYSPRO confirms it will supply after allocation, including amended and refused lines. | SYSPRO to partner |
| Advanced shipping notices | Pack detail raised from the SYSPRO dispatch note, to carton or pallet level where the retailer requires it. | SYSPRO to partner |
| Invoices | Produced by the SYSPRO invoice run and referenced to the order and despatch so the retailer can match them. | SYSPRO to partner |
| Credit notes | Credits raised against the invoice they adjust, sent with a credit document code. | SYSPRO to partner |
| Stock and price data | Stock code, pack and price data published to retailers maintaining a catalogue against your range. | SYSPRO to partner |
How to connect SYSPRO with EDI using XEDI
SYSPRO's business object layer means the build is mapping rather than development. The sequence below is what onboarding looks like from your side.
-
01
We scope the SYSPRO company, warehouses and trading partners involved in each flow.
-
02
We build the mapping between each partner's documents and your SYSPRO customers, stock codes and warehouses, through its business object layer.
-
03
We configure validation so a document is checked against the partner's rules before it reaches SYSPRO.
-
04
We prove the order, despatch and invoice flows against what each partner requires and against how your SYSPRO company is configured.
-
05
You get orders landing as sales orders without anyone typing them, and we keep it working as your stock file changes.
Ready to connect SYSPRO?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about SYSPRO EDI
Common requirements
- SYSPRO company and integration account details
- Customer, stock code and warehouse structure
- Unit of measure and pack conversions
- Despatch and part-shipment rules
- 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 SYSPRO company is set up.
- SYSPRO access
- A company and integration account with rights to the sales order, dispatch and invoice business objects in scope.
- Customer and warehouse records
- Each retailer mapped to a SYSPRO customer, and each delivery point resolvable to the warehouse that will service it.
- Stock code mapping
- How each retailer's item identifier resolves to your stock code, including what should happen when a code is superseded.
- Unit and pack conversions
- The unit a retailer orders in against the unit you hold, and the conversion between them at each packaging level.
- Which retailers you supply
- The partners in scope now and next. What each of them requires is already ours.
Why suppliers choose XEDI for SYSPRO
- The retailers you supply are usually connected already, so orders can start arriving before the SYSPRO work finishes.
- The stock code mapping is maintained by us, so a superseded code does not quietly stop a retailer's orders landing.
- Unit conversions are validated before a document is sent, which is what stops a case-versus-each error invoicing at the wrong value.
- A new retailer is not a SYSPRO project. We build and verify the connection before it carries live documents.
- One connection covers the retailers you supply now and every one you take on, each onboarded by us.
- If a retailer raises a problem it comes to us, and we put it right before it becomes a delivery or payment issue.
Can XEDI connect SYSPRO to EDI trading partners?
Yes. XEDI maps each retailer's EDI documents to SYSPRO sales orders, dispatch notes and invoices through its business object layer, and returns acknowledgements, despatch advice and invoices in the format each retailer requires.
How are our stock codes matched to a retailer's item numbers?
The mapping between your stock codes and each retailer's identifiers is held and maintained by us, including GTINs at each packaging level, so a code being superseded does not silently break the flow.
Does it handle part shipments and back orders?
Yes. How SYSPRO treats a part shipment and what the retailer expects to see are agreed during scoping, so the despatch advice and invoice reflect what actually shipped.
Plan your SYSPRO EDI setup
Everything you need to scope, map and go live with SYSPRO, in one place.