Sign in Start free trial Book a demo

EDI orders For the retailers whose procurement system decides

Your retailer’s EDI connection, built and run for you

A chain has told you to be on EDI by a date. We build the mapping, pass their certification cycle, and keep it working when they change it. No translator, no middleware, no network contract.

Get a quote Book a 30-min demo

Bring their onboarding pack if you have one — we’ll read it on the call.

The onboarding email from a retail chain, and the connection it ends as On the left, an email from a buyer at a retail chain with the subject “Supplier EDI onboarding — action required by 1 March”, saying suppliers are moving to EDI and attaching a supplier specification. Behind it sits the specification itself, a dense document listing four mandated document types with their EDI codes and a certification requirement. On the right, a small card showing the same retailer connected and certified, with all four document types ticked, and a note that their orders now arrive in the same list as everything else. SUPPLIER EDI SPECIFICATION Version 7.2 · 41 pages 1. Trading partner identifiers 2. Transport and connectivity 3. Message specifications 4. Certification procedure MB Buyer, supplier onboarding to you · 06:41 Supplier EDI onboarding — action required by 1 March We’re moving our suppliers onto EDI this year. You’ll need to be connected and certified before we can continue placing orders. Our specification is attached. supplier-edi-spec-v7.2.pdf 41 pages Tesco Connected certified 24 Feb Purchase order ORDERS / 850 Receipt confirmation CONTRL / 997 Despatch advice DESADV / 856 Invoice INVOIC / 810 Their orders arrive in the same list as everything else.

What you get

A live connection to the chain, and nothing to run

Not software you install and operate. A working EDI channel into the retailer that mandated it — certified by them, maintained by us, and landing in the order list you already use.

Orders

Chain orders arrive in your normal order list

A purchase order from a supermarket group lands next to a storefront basket and an emailed PDF, tagged by channel, at that customer’s agreed prices. Your team does not learn a second system, and nobody logs into a supplier portal to fetch anything.

  • Checked against your catalogue and their agreed prices on arrival
  • Into your ERP with the rest — no separate EDI workflow to run
  • Their purchase order number travels with it, so their finance system matches
One order list, with the channel as a column A single list of six orders. Two arrived by EDI from retail chains, two from buyers signing in to the storefront, and two as documents read by Vision. Every row has the same columns — order number, customer, how it arrived, the reference, the time and the total — and the channel is shown as a small coloured chip rather than as a separate screen. One of the EDI orders is held for review. Orders All channels 6 of 214 ORDER CUSTOMER ARRIVED BY REFERENCE RECEIVED TOTAL #4318 Tesco EDI ORDERS · 850 18 Aug · 06:12 €18,340.00 #4317 Sundal Retail Storefront Jonas Sundal 17 Aug · 16:44 €3,211.50 #4316 Brecken Outdoor Vision PDF · email 17 Aug · 14:02 €745.86 #4315 Carrefour EDI ORDERS · 850 17 Aug · 09:30 €24,905.40 price mismatch · held #4314 Alpine Sports Co Storefront Mia Talvik 16 Aug · 11:18 €1,166.70 #4313 Havlund Retail Vision Spreadsheet 16 Aug · 08:51 €8,420.00
Two retailers on EDI, the rest ordering however they order. How an order arrived is a column you could sort by — there is no separate EDI screen to go and look at.

Compliance

Every document they require, sent automatically

“EDI compliant” means four documents moving in a fixed order, inside the retailer’s own time windows. All four go out without anyone remembering to send them — including the technical acknowledgement that quietly decides your compliance score.

  • Receipt confirmation returned inside their stated window
  • Shipping notice generated when you dispatch — contents, packing, arrival
  • Invoice matched to the order and the shipment, so it is not held
  • North American and European standards both run here
The EDI exchange between a retail chain and Turis A retail chain sends a purchase order. Turis returns three documents in sequence: a receipt confirmation, a shipping notice and an invoice. The retail chain Turis The purchase order 850 The chain sends what it wants, in the format it insists on. Receipt confirmation 997 Turis confirms the file arrived and could be read. The shipping notice 856 What is coming, in which boxes, arriving when. The invoice 810 Sent in the format their finance system will accept. Turis sends all three back. You do not build or maintain any of it.
What a retail chain sends, and the three documents it expects back.

When it goes wrong

A rejection arrives already read for you

Chains reject documents. It is normal, not a fault, and every vendor in this category shows you the working state and stops. Here the rejection is translated out of its raw code into the line it concerns, with what to do about it — and when the retailer changes their specification, the mapping is ours to fix.

  • The reason in plain words, against the order it belongs to
  • Changes to a live connection are covered by the monthly fee — new fields, revised mappings, a new version of the retailer’s specification, and the re-test cycle that follows.
  • At no extra cost — changes are not billed as change requests
A rejected invoice, with the retailer’s reason translated An exception in Turis. The retailer has rejected an invoice. On the left is the raw acknowledgement file the retailer sent back, a short block of EDI segments. On the right the same rejection is written as a sentence: the quantity on line 12 of the invoice does not match the quantity on the shipping notice, twenty-four against eighteen, and the invoice was not accepted. The offending line is shown with both numbers. At the foot, Turis states that it is correcting and resending, and that nothing reached the ERP. Tesco rejected an invoice Exception · order #4318 · 18 Aug, 09:14 WHAT THE CHAIN SENT BACK AK1*IN*4318~ AK2*810*000000041~ AK3*IT1*12**8~ AK4*3*380*7*24~ AK5*R*5~ AK9*R*1*1*0~ Functional acknowledgement (997). Reject code 5 on segment AK5. WHAT IT MEANS The quantity on line 12 of the invoice doesn’t match the quantity on the shipping notice you sent them. Tesco will not accept an invoice it cannot reconcile against the despatch. Nothing was posted to your ERP. Line 12 · Fell Jacket — Moss shipping notice 18 invoice 24 Turis is correcting the invoice and resending it. You do not need to do anything. If we need a decision from you, this becomes an action instead. Rejections are normal in EDI. Every one of them arrives as a file like the one on the left, and every one of them is read before it reaches you.
What a rejection looks like once someone has already read it. The retailer’s own acknowledgement on the left, in full, so you can check the translation.

Your retailer

Whichever chain sent you the onboarding pack

Their specification, their test cycle, their deadline. Some chains we have connected before; the rest are ordinary work. Either way, you send us the pack and we tell you what is involved on the first call.

A chain already in our catalogue

The mapping starts from something proven rather than a blank sheet. That shows up in the setup charge, and in how quickly their certification cycle runs.

  • Walmart
  • Tesco
  • Coop
  • Carrefour
  • REWE

Among the chains in our EDI partner catalogue.

Any other chain — the normal case

Most of the connections we build are to a retailer we have not published. It affects the setup charge and nothing else. Whether it can be done is not the question.

Get a quote for your retailer

What it costs

Priced by the connection, one retailer at a time

From €200/mo per retail partner, plus a setup charge per partner. One retailer connected is one connection; two retailers is two. You are not buying a platform licence sized for twenty and then paying per connection on top — the connection is the product, which is what makes a single retailer worth doing at all.

The connection, monthly

The live connection to that retailer, the network it runs over, and everything that keeps it working. Changes to a live connection are covered by the monthly fee — new fields, revised mappings, a new version of the retailer’s specification, and the re-test cycle that follows.

Setting it up, once per partner

Registering your GLN — the ID number a retail chain uses to identify your business in their system — building and testing the mapping between their product codes and yours, and running the retailer’s certification cycle with them until you pass it.

More than one retailer

Quoted together rather than multiplied. Most brands connect a second retailer within a year of the first, and it is both cheaper and faster than the first — your product and price data is already mapped by then.

  • No commission on what you sell through EDI
  • No per-document or per-kilocharacter fee
  • No separate VAN contract in your name
  • No charge when the retailer changes their specification

Always quoted in writing, per retailer, before you commit to anything — bring the retailer and we will price that retailer. See how the three channels price →

Before we start

What we need from your side

Four things, and none of them are EDI knowledge. Written so you can forward this section to whoever looks after your ERP without explaining it first.

Product data that matches theirs

They order using their codes or GTIN/EAN barcodes; we map those to yours. The list just has to be correct — this is the most common cause of delay, and it is fixable before we start rather than during.

A way for Turis to read and write to your ERP

Native connections to Business Central, SAP, Infor M3, Visma Net, Rackbeat and Uniconta are already built. Otherwise your ERP’s API, or a scheduled file exchange if it has none.

Agreed prices for that customer, loaded in Turis

Their order carries the price they expect. We check it against yours and hold a mismatch rather than accepting it silently — which needs the agreed list to be in Turis.

The retailer’s onboarding pack, and a named contact there

The spec tells us what they want and how. The contact runs the test cycle with us — ask your buyer if you have no name; every large chain has a supplier-onboarding team.

What we don’t need

Your own EDI software. A VAN contract in your name. A project manager on your side. Or anyone on your team who understands EDI — if you did, you would not be reading this page.

See how Turis connects to your ERP →

Someone has already done this

All three channels, into SAP Business One

To Øl, the Copenhagen craft brewery, runs B2B Storefront for the accounts that order themselves, Vision for the ones that email, and Turnkey EDI for the retailers that mandate it — all landing in SAP Business One.

Before Turis, their reps spent about half of each day keying orders into SAP Business One. The dedicated EDI providers they looked at carried a high upfront cost that was difficult to justify against a small number of retailer connections — which is the arithmetic this page exists to change.

  • 90% of orders now placed by the customer directly, against a starting point where every order was keyed in by a sales rep
  • ~20 hrs a week back per sales rep, and the equivalent of one full-time admin role

To Øl reports these figures — Eric Gilham, Chief Digital Officer. They are their own account of the result rather than something we measured. Read the full story →

Before you ask us

The questions a supplier under a mandate asks

If yours isn’t here, thirty minutes with the retailer’s onboarding pack in front of us answers it faster than another page will.

How is this different from buying EDI the normal way?

The normal way is four purchases: a translator to convert the retailer’s file format, middleware to move files into your ERP, a network contract billed per document, and an implementation project to map the fields. You assemble and own all four. Here it is one line on the invoice you already have, and the assembling is not your problem.

Which documents and standards do you support?

The four a retail chain expects: the purchase order (850 in North America, ORDERS in Europe), the technical receipt confirmation (997 / CONTRL), the shipping notice (856 / DESADV) and the invoice (810 / INVOIC). Both the North American and European standards run here. You never have to use the codes — they are what the retailer’s specification will call them.

What happens when the retailer changes their specification?

We change the mapping and run their re-test cycle. Changes to a live connection are covered by the monthly fee — new fields, revised mappings, a new version of the retailer’s specification, and the re-test cycle that follows. There is no change-request rate and no separate quote — the point of a managed connection is that a chain moving its own goalposts is our problem rather than yours.

We have never done EDI. What is it, exactly?

A way for two companies’ systems to exchange orders as structured files instead of emails between two people. The retailer’s system produces the order, it travels over a private network, and it arrives already formatted — customer, delivery date, product codes, quantities, prices — with nobody retyping it at either end. Being “on EDI” means your side does four things automatically: take their order, confirm you got it, send a shipping notice before the goods arrive, and send the invoice. You do not need to learn any of it; that is what we are for.

A retailer has told us we need EDI by a date. Can you make it?

Often, yes — and the part neither of us controls is the retailer’s own certification queue, which is usually the longest single wait. Bring the deadline and the retailer’s onboarding pack to the first call and we will tell you honestly whether it is reachable, including if it is not.

We’re trying to win a retailer we don’t supply yet. Does this still apply?

More so. A great many large retailers require EDI of any supplier they list, so being unable to accept their orders can end the conversation before the buyer has finished considering the product. Getting connected first turns it from a reason to say no into a box already ticked — and a connection can be built before you have won the listing.

Do we need to understand EDI to use this?

No. You need to know which retailers you sell to and what your product data looks like. The specification, the mapping and the test cycle are ours.

We only have one retailer on EDI. Is it worth it?

That is the case this is priced for. You buy one connection, from €200/mo per retail partner plus its setup, rather than a platform licence sized for twenty. If a single retailer is a meaningful share of your revenue, the arithmetic is usually not close — and we will put a real number on your retailer on the first call.

Do you charge per document?

No. Flat per retail partner per month, whatever the volume goes through that connection. No per-kilocharacter fee either, which is how traditional network contracts bill.

Who owns the VAN contract?

We do. A VAN is the private network EDI orders travel over, and normally the supplier signs for one themselves. You do not sign a network agreement and there is no per-document network charge on your side.

What if the retailer changes their specification?

We rebuild the mapping and re-run their test cycle, and it is covered by the monthly fee. There is no change-request rate.

What happens when an order comes in with the wrong price?

It stops as an exception with the line flagged, and someone on your side decides. It does not reach your ERP as an accepted order — silently accepting the retailer’s price is how a margin problem gets found a quarter late.

Do we need B2B Storefront or Vision as well?

No. EDI can be bought on its own. Most brands who buy it already run one of the others, because the retailers mandating EDI are rarely the whole customer base — but it is not a requirement.

Our ERP isn’t one of the ones you list.

Then we look at what it can expose — an API, or a scheduled file exchange. On the first call we will tell you whether yours is straightforward, a project, or a bad fit. See the integrations →

How is this different from our ERP’s own EDI module?

If your ERP has one and it is live, you may not need this. The difference is who does the mapping and who handles the retailer when the specification changes — an ERP module gives you the capability and leaves the work with you or your ERP partner. Worth a call rather than a page.

Three ways an order arrives. One place it lands.
They’d order themselves, if there were somewhere to do it B2B Storefront from €299/mo
They’ll always email a PDF or spreadsheet Vision from €199/mo
Their procurement team mandates EDI Turnkey EDI from €200/mo per partner

Tippy AI, Pulse and Reports included with every plan. No commission on your sales.

See it with one of your own orders

Send us a real purchase order — a messy one, ideally — and we’ll show you what Turis does with it on the call.

Book a 30-min demo

Live product, your order flow, no slide deck.  ·  No commission on your sales, ever.