Custom EDI integration for retail-chain suppliers
Orders, despatch advices and invoices exchanged electronically with retail chains such as Kaufland, Albert or Lidl — wired straight into POHODA ERP via ORiON EDI, EDITEL and GS1 standards.
We usually reply within 24 hours
We connect your POHODA ERP to the EDI network the retail chains use to trade with you. Incoming orders (EDIFACT ORDERS) are created automatically as sales orders in POHODA; from the shipped delivery and issued invoice the system builds the electronic DESADV and INVOIC messages in GS1 EANCOM format and sends them back through your EDI provider — ORiON EDI by GRiT or EDITEL. No re-typing orders from a chain portal, and a much lower risk of penalties for a late or incorrect despatch advice.
Trading with chains runs on portals and manual re-typing
Retail chains require their suppliers to exchange documents electronically over EDI. Without an ERP connection that means logging into each chain's portal, re-typing orders into POHODA by hand and confirming deliveries manually — and every late or incorrectly filled despatch advice risks a penalty. The chain's item numbers may not match your catalogue either, so GTIN and GLN mapping ends up being done by hand.
- Orders from chains are re-typed from a portal into POHODA, risking typos in quantity and price
- The delivery note and invoice are filled in separately for each chain's own format
- A late or incomplete despatch advice (DESADV) leads to a penalty from the chain
- Mapping your stock items to GTIN and customers to GLN is handled manually
- The EDI provider runs separately from the ERP, with documents moved by e-mail or by hand
What the EDI integration does
We connect POHODA to your EDI provider and translate every message between the chain's format and your ERP — both ways, with no manual step in between.
Automatic order intake (ORDERS)
An electronic order from the chain in EDIFACT ORDERS format is pulled from the EDI network and created automatically as a sales order in POHODA — with matched stock items, quantities, prices and delivery date. Your sales clerk no longer copies anything from a portal.
Despatch advice and invoice back (DESADV, INVOIC)
From the shipped delivery and the issued invoice the system builds the electronic DESADV (despatch advice) and INVOIC (invoice) messages in GS1 EANCOM format and sends them back to the chain via ORiON EDI or EDITEL — within the deadline and in the structure the chain requires.
Works with ORiON EDI and EDITEL
The integration works with the EDI provider you already use — ORiON EDI by GRiT as well as EDITEL's eXite platform. Documents flow directly between POHODA and the provider's network, without moving files by e-mail or a shared drive.
GS1 standards — GLN, GTIN, SSCC
Customers are identified by a GLN location number, items by a GTIN and logistic units by an SSCC. The system keeps the mapping between your POHODA catalogue and the chain's numbers, so messages conform to the GS1 EANCOM standard.
Validation and matching before sending
Before a message goes out it is checked against the chain's expected structure, and any unmatched items or customers are flagged for review. Errors surface before the chain rejects or penalises them.
Message overview and statuses
Every inbound and outbound message has a status and history — you see what arrived, what was sent and what is pending. Technical acknowledgements (CONTRL / APERAK) from the provider are matched to documents, so you know a message went through.
How the rollout works
We build the integration between your existing POHODA and the EDI provider the chains require. We don't replace the ERP or the EDI network — we connect them.
Analyse chains and messages
We map which chains you supply, which EDI messages they require (ORDERS, DESADV, INVOIC, and optionally ORDRSP, RECADV) and which provider you already use — ORiON EDI, EDITEL, or another.
Connect POHODA and the provider
We link the integration to orders, invoices and stock items in POHODA and to your EDI provider's interface for receiving and sending messages.
GS1 mapping and message setup
We set up the mapping of stock items to GTIN and customers to GLN, and map the structure of the EANCOM messages onto the data in POHODA for each chain.
Test run and go-live
We validate messages on test documents with the chain and the provider, then take the integration live — including status monitoring and technical acknowledgements.
What your company gains
EDI stops being an extra manual chore and becomes an automatic flow of documents between the chains and your ERP.
Manual order re-typing
Orders from chains drop straight into POHODA matched to stock — no logging into portals and no typos in quantity or price.
Fewer despatch-advice penalties
DESADV and INVOIC go out automatically in the right format and deadline, so the risk of fines for late or incorrect electronic documents drops.
Data entered once, correctly
Catalogue and customers are matched to GTIN and GLN once; every subsequent message simply reuses that mapping.
Ready for the next chain
Connecting a new chain is a matter of configuring its messages and mapping, not a new system — you grow without more manual work.
Our own team, turnkey and on schedule
- years of team experience
- 15+
- completed projects
- 150+
- of agreed deadlines met
- 99%
- orders processed per year
- 1M+
- shortest time to launch an integration
- 7 days
- typical reply time
- 24 h
What our clients say
“We've been working with Adaptis IT for over 4 years. Response times are always hours, not days. They solved an integration that two previous vendors declared impossible. It's been running flawlessly ever since.”
Built on your ERP and EDI provider
The integration needs no new system — it connects POHODA to the EDI network the chains require, through the provider you already have.
Frequently asked questions
More solutions that fit together
Ready to start?
A free, no-obligation consultation. Tell us what you need to connect or automate — we deliver it turnkey with our own team, no subcontractors.
Contact us