Connect Zynk to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Zynk and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Zynk EDI
XEDI works alongside Zynk Workflow, which already automates a great deal around Sage, adding the retailer relationships and their compliance rather than another file-moving job for workflows you maintain.
One managed platform, no custom code
XEDI maps Zynk to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Zynk already solved the Sage half, which is the harder half to buy
Businesses running Zynk have generally been automating for a while: orders from a webstore into Sage, invoices out, stock updated, all on a schedule that works. That is real capability and there is no sense replacing it.
What Zynk gives you is a reliable route into and out of Sage in formats it understands. What it does not give you is a relationship with Tesco. Those are complementary rather than competing, and the sensible arrangement uses each for what it is.
Partner compliance is a different kind of ongoing work
A workflow that imports orders into Sage is stable once it is right. The file layout does not change because somebody at your webstore decided it should, and if it does you control both ends.
Retail trading is not like that. Each retailer specifies identifiers, documents, labelling and timing, enforces them with deductions, and revises them when it suits. That is not a workflow problem, it is continuous relationship maintenance, and it is what we do so that your Zynk workflows can stay the stable things they are.
What your team sees day to day
You get an EDI mailbox and a portal that behaves like an inbox, and your workflows receive retailer documents in a format they already handle.
A retailer's order arrives, what actually ships becomes the despatch advice with SSCC labels where required, and the invoice follows delivery with its arrival confirmed in the dashboard.
Your existing automation is untouched. The EDI capability is bolted onto the workflows you already run, with the retailer side staying ours to maintain.
Documents you can exchange
- Retailer orders delivered for your workflows to consume
- Acknowledgements and despatch advice submitted from Zynk
- Invoices raised through the workflows already in place
- Product and stock data exchanged with retailers
- Exceptions surfaced where your workflows already report
Built for Zynk teams
Whoever owns Zynk in your business, XEDI keeps EDI accurate and hands-off.
- Sage users running Zynk Workflow
- UK distributors and wholesalers
- Operations teams automating order entry
- Finance teams importing to Sage
- Businesses already automating ecommerce to Sage
Zynk EDI document types
These arrive in formats your workflows already handle rather than as partner-specific work.
| Document | What it carries | Direction |
|---|---|---|
| Retailer orders | Demand delivered in a format your workflow already imports into Sage. | XEDI to Zynk |
| Acknowledgements | Confirmation of what will be supplied, produced from Sage data via your workflow. | Zynk to XEDI |
| Despatch advice | Shipment detail from your despatch process, labelled to each retailer's standard. | Zynk to XEDI |
| Invoices | Billing exported by your existing workflow and validated before it reaches the retailer. | Zynk to XEDI |
| Product and stock data | Catalogue and availability figures published to retailers expecting them. | Either direction |
| Exceptions | Retailer rejections reported where your workflows already surface problems. | XEDI to Zynk |
How to connect Zynk with EDI using XEDI
The division is straightforward: Zynk owns Sage, we own the retailers. The sequence below is what onboarding looks like from your side.
-
01
We establish what your Zynk workflows already move and who maintains them.
-
02
We agree the file formats and locations those workflows are comfortable with.
-
03
We connect so retailer documents arrive as a source your workflows already know how to handle.
-
04
We prove the flows, including how a retailer rejection is reported.
-
05
You get retail trading without another set of partner-specific workflows to look after.
Ready to connect Zynk?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Zynk EDI
Common requirements
- What your Zynk workflows currently do
- Which Sage product is behind them
- File formats and locations in use
- Who maintains the workflows
- The retailers you supply
What we need from you to build it
Only what we cannot decide for you. Retailer requirements and their changes stay entirely with us.
- Current workflows
- What Zynk already moves, so retail fits alongside rather than duplicating it.
- Which Sage product
- Since Sage 50, 200 and X3 differ in what they can carry and how much can be automated.
- Formats and locations
- What your workflows import and export comfortably, so retailer documents arrive as a familiar source.
- Who maintains them
- Whether that is internal or a partner, since it decides who we coordinate with.
- The retailers you supply
- Which relationships this covers. Their requirements are already held by us.
Why suppliers choose XEDI for Zynk
- Your retailers are almost certainly connected already, so nothing waits on a new workflow being written.
- Your Zynk workflows stay stable because retailer variance never reaches them.
- Retailer compliance is continuous relationship work, and it is ours rather than an addition to your automation.
- Documents arrive in formats your workflows already import, not partner-specific layouts.
- Adding a retailer needs no new workflow.
- If a retailer raises a problem, it comes to us rather than to whoever maintains your automation.
Does this replace Zynk?
No. Zynk continues to own the route into and out of Sage, which it does well. What it adds is the retailer relationships, their compliance and their changes, which is a different kind of work.
Could our Zynk workflows handle EDI files directly?
They could move the files. What they cannot do is hold each retailer's specification, notice when it changes or answer for a rejected delivery, and that is the part that does not end.
Which Sage products does this suit?
All of them, though how much can be automated differs. Sage 200 and X3 can carry the order itself; with Sage 50 the invoice is usually the useful part.
Plan your Zynk EDI setup
Everything you need to scope, map and go live with Zynk, in one place.