Skip to content 
EDI, PunchOut and the Retail Onboarding Packet a Small Tissue Importer Must Actually Ship
Short answer: when a European chain tells you to be “EDI capable,” they almost never expect you to install an EDI system. They expect their purchase orders, acknowledgements, despatch notices and invoices to flow through a translation layer, usually a cloud EDI provider or a network like Peppol, with your admin handling exceptions rather than messages. The onboarding packet underneath is identifiers and master data first, GS1 company prefix, GLN for your locations, GTIN per item, then a defined set of documents mapped to your actual order flow. A small brand that budgets for a hosted service and answers the onboarding questionnaire truthfully clears this gate in weeks; one that improvises PDF emails collides with invoice rejection in month two.
Getting listed is the dream; getting paid is the plumbing. Modern retail onboarding in Europe increasingly asks suppliers to exchange documents electronically: orders arrive as structured data instead of emails, you confirm quantities and dates, you advise despatch before goods move, you invoice in a machine-readable form referencing the order. For a private-label tissue importer with a warehouse, a bank and one part-time admin, this sounds like enterprise infrastructure. It is not, and the most expensive mistake at this stage is believing the word “EDI” describes a technology you must own rather than a workflow your data must satisfy.
What the Retailer Is Actually Requesting, Document by Document
Read the onboarding pack for the document list hiding inside it. The retailer wants a catalogue of items keyed to their numbers: your GTIN, their article number, pack hierarchy, inner pack and case and pallet counts, units of measure, net weight and dimensions, country of origin, price, and validity dates. It wants purchase orders delivered electronically and answered, not forwarded to a mailbox: a confirmed acknowledgement with ship date, a despatch advice listing what actually left, and an invoice quoting the order reference and goods received where the chain uses it. It wants the identifiers to resolve: a GLN for the ship-from location, SSCC labels on pallets if the DC scans inbound. This is the same master-data backbone you maintain when verifying sheet counts and case quantities on arrival; EDI is the retailer reading your housekeeping aloud.
Note the shape: orders, acknowledgements, despatch, invoices, and the reference data binding them. That is a procure-to-pay cycle, and the reason chains mandate it is not paperless virtue but three-way match automation. An invoice that cannot auto-match to a purchase order and a receipt becomes a manual exception, and manual exceptions are where supplier payment delays and chargebacks are born. Your goal in onboarding is to be auto-matchable from the first live order.
EDI Is Not One Thing, and the Vocabulary Matters
The questionnaire will use several terms that describe different obligations. Traditional EDI is system-to-system document exchange in standards like EDIFACT or X12, run through a VAN, a value-added network that translates and routes messages between trading partners. Peppol is the European public-network model: you connect once through an accredited access point and exchange structured documents, above all e-invoices and orders, with every other participant; the network is governed around the Peppol open framework and is now the default answer to “how will you invoice us” across government and much of retail in the Benelux, Nordics, Italy and Germany corridors. PunchOut and cXML describe the catalogue route: your product data loads into the retailer’s portal so buyers order against a live catalogue rather than sending you a PO at all. And the plain truth is that a chain with any maturity will ask for identifiers first, because a GS1 company prefix, GTINs you control and GLNs for your sites are prerequisites for every one of those three rails. The barcode you already print on retail cartons has an ID lineage, and launch guides to private-label tissue usually stop at the artwork, while onboarding stops at nothing: the barcode you own today is the key your order data hangs from later.
How a Small Importer Really Runs This in 2026
The provider model exists for your exact situation. A cloud EDI or access-point service gives you a mailbox with translation: purchase orders land converted into readable documents and, ideally, into your spreadsheet or simple order desk, while your replies are turned back into standard messages. You are not building software; you are subscribing to a translator and agreeing who presses send. The workable division of labor for a small team is: the provider or the retailer’s supplier portal carries the message mechanics, your admin owns exceptions, unknown item numbers, quantity conflicts, date slips, price mismatches, and keeps a one-page runbook for what to do with each. That runbook is a day of writing and it prevents the second-month chaos where acknowledgements are missed because nobody knew who presses the button while staff were on holiday.
Budget honestly: hosted EDI participation costs real money per trading partner or per message volume, usually far below the cost of a single invoice-payment cycle lost to mismatched references, and dramatically below the cost of a delisting for “system non-compliance.” When you negotiate the listing, treat onboarding as a line in the cost model alongside artwork and pallet labels, because it is exactly that.
The Data You Already Have, Polished
Every field the onboarding pack requests exists somewhere in your operation already. Pack quantities live in your carton spec; weights in the pallet plan your forwarder uses; origin on your certificates; prices in the quotation file. EDI punishes drift more than paperwork does, a case pack that quietly changes between containers breaks auto-match every time after, which is the same data hygiene lesson as auditing sheet counts against linear footage. So before you sign the integration, freeze a master data sheet per item with versioning: dimensions, weights, pack hierarchy, GTIN, and a named approver, and require the factory to notify you of change, the same clause pattern you already use for furnish and film. Retail onboarding then becomes data entry you half-own already, and the three-way match becomes boring, which is precisely the financial outcome a small importer is buying.
Two final clauses protect you. First, the acknowledgement clock: know the retailer’s required response window for orders, set a calendar alert, and treat missed acknowledgements as the emergency they are, because unacknowledged POs become assumed acceptance, then become penalty events. Second, invoice hygiene: reference the order number, match quantities to the despatch advice and the actual receipt, and never let a freight surcharge or FX adjustment float a price variance, because variances route straight to manual review and delay; the discipline behind lead-time management and the tissue forecasting routine is what keeps those fields true.
The Pilot Order Is the Real Onboarding
Every integration ends in the same moment, a live purchase order whose messages must actually flow. Treat the pilot as a test with three pass criteria and no mercy. First, does a purchase order arrive complete, with the retailer’s item number mapped to your GTIN and pack hierarchy, or does it arrive as a reference nobody can resolve because the master data went out with a typo; unknown article numbers are the most common first-week failure and the cheapest to prevent by double-keying the catalogue. Second, does your acknowledgement go out inside the required window, does a despatch advice land before the truck, and does the distribution center receive pallets whose SSCC matches your ASN line for line; a despatch advice that lists the wrong batch turns a clean delivery into a receiving exception. Third, does the invoice three-way match automatically, the true proof that your data and your logistics agree. Run the pilot with a real small order, watch every step with the provider’s dashboard open, and log each exception with the fix you applied, because chains re-score new suppliers on how the first orders behave and because that log becomes your onboarding report card. A supplier that clears a pilot in two weeks and sends the exception log as evidence arrives at the next chain already trusted.
Frequently Asked Questions
We are tiny. Can we really just say no to EDI?
Some chains will work through their own supplier portal with manual entry, which is their system, not yours, and is survivable at low order volume. Beyond that, the honest choice is a hosted provider or declining a retailer whose payment engine requires automation you refuse to buy; pretending capability you do not have converts a slow onboarding into a fast delisting.
What is the difference between Peppol and a VAN?
A VAN is a private mailbox between you and one trading partner running classic EDI formats; Peppol is a connected public network where one access point lets you exchange structured documents with every participant. Many European chains now accept or prefer Peppol for invoicing; ask which, because you buy the connection once either way, and the retailer’s answer shapes the quote.
Who owns our GTINs, us or the factory?
You do, when they are issued from your own GS1 company prefix against your brand’s items. A barcode the converter registered for its own product is its identifier, not yours, and the onboarding pack, and eventually the recall trail, both run on the question of who holds the keys to the numbers printed on your carton.
