EDI Trading Partner

Connect to Dunnes EDI Instantly

Join thousands of customers that connect to Dunnes with XEDI.

No credit card needed Free EDI mailbox included

See how XEDI connects suppliers to Dunnes

Overview

Getting started with Dunnes EDI

Dunnes suppliers need dependable EDI for retail orders, delivery updates and invoices. XEDI helps automate Dunnes EDI document exchange and connect it with internal order, warehouse and finance systems.

Purchase orders Order acknowledgements and responses Invoices Credit notes or adjustments where required Product, catalogue or stock data where required

Explore XEDI for Dunnes

Documents you can exchange

  • Purchase orders
  • Order acknowledgements and responses
  • Invoices
  • Credit notes or adjustments where required
  • Product, catalogue or stock data where required
Who it's for

Built for Dunnes suppliers

Whether you send a handful of orders a week or thousands a day, XEDI keeps your Dunnes trading accurate and hands-off.

  • Retail suppliers
  • Food and grocery suppliers
  • Consumer goods brands
  • Order processing teams
  • Accounts receivable teams
In practice

Dunnes EDI overview

Dunnes EDI is the structured exchange of commercial documents between Dunnes and businesses working in Irish grocery, clothing and homewares supply. The agreed document set starts with orders and invoices, with the operational emphasis on keeping order, fulfilment and finance data aligned.

A practical Dunnes integration should connect the agreed document set with the systems that process it. XEDI maps the agreed EDIFACT or EANCOM messages into ERP, warehouse, accounting or API workflows, while validation and alerts help teams deal with exceptions before they affect delivery or payment.

Every document validated before it moves

XEDI checks each Dunnes order, despatch advice and invoice against the required format, so errors are caught before they reach your systems.

Onboarding

Dunnes supplier onboarding process

For Dunnes, onboarding starts with confirming the supplier relationship, document scope and connection route. XEDI then maps, tests and monitors the agreed workflow so teams can move from first order to stable live trading with clear ownership of exceptions.

  1. 01

    Confirm the Dunnes supplier account, buyer contacts, delivery locations, identifiers and current document requirements.

  2. 02

    Agree the Dunnes order, response and invoice scope for the trading relationship.

  3. 03

    Map Dunnes message data to the supplier's ERP, warehouse, order-management and accounting systems.

  4. 04

    Configure EDIFACT or EANCOM validation, connection routing, exception alerts and user responsibilities in XEDI.

  5. 05

    Complete the agreed Dunnes test transactions, checking mandatory references, product data, delivery details and invoice matching.

  6. 06

    Monitor initial live transactions and resolve rejected, delayed or mismatched documents with the operational and finance teams.

Ready to connect Dunnes?

Talk through documents, standards, testing and system integration with XEDI.

Detail

Everything about Dunnes EDI

Dunnes EDI message types

Dunnes message requirements depend on the supplier account and fulfilment route. These are the common EDIFACT or EANCOM equivalents used to plan the order-to-invoice workflow; the shipping message is included when the agreed route requires it.

Message Purpose Direction
ORDERS Purchase order with item, quantity, price, delivery location and requested delivery details. Dunnes to supplier
ORDRSP Order acknowledgement or response used to confirm, reject or amend order lines before fulfilment. Supplier to Dunnes
INVOIC Invoice linked to the order, delivery and supplier references agreed with Dunnes. Supplier to Dunnes
APERAK Application or functional acknowledgement used to confirm receipt or identify processing errors where supported. Either direction
Dunnes EDI requirements

Dunnes requirements should be confirmed against the current agreement and test instructions. Planning should also account for the transport and validation controls used for Irish grocery, clothing and homewares supply.

EDIFACT or EANCOM

Map the agreed Dunnes order, response and invoice messages in the EDIFACT or EANCOM format used by the trading setup.

AS2 or managed connectivity

Use AS2, SFTP, a VAN or the connection method agreed with Dunnes, with secure routing and delivery-status monitoring.

Product and location references

Validate agreed product identifiers, pack data, ship-to or depot locations and supplier references before a document is sent.

Testing and go-live

Test the agreed Dunnes message set, resolve validation feedback and retain evidence that the connection is ready for live trading.

Common requirements & compliance

Common requirements

  • Dunnes supplier account, trading partner and buyer identifiers
  • Product identifiers, SKUs, GTINs, pack sizes and agreed item descriptions
  • Delivery, depot, warehouse or ship-to references
  • Invoice, tax, payment and remittance references
  • Agreed EDIFACT or EANCOM message set and connection method
  • Test evidence for the agreed order and invoice flows

Compliance notes

  • Dunnes document requirements can vary by category, region, delivery route and fulfilment model.
  • Supplier, product, location and invoice references must match the trading agreement and test data.
  • Use pre-send validation and exception monitoring to reduce rejected Dunnes orders and invoices.
Dunnes ERP integration
Why suppliers choose XEDI for Dunnes

Businesses choose XEDI for Dunnes EDI when they need a managed connection focused on keeping order, fulfilment and finance data aligned, with the agreed documents, validation rules, integrations and exceptions visible in one workflow.

  • Dunnes-specific onboarding for identifiers, document scope, testing and go-live planning.
  • Validation for Dunnes orders and invoices before documents are exchanged.
  • EDIFACT or EANCOM mapping with ERP, accounting, warehouse, API, AS2 and VAN connectivity options.
  • Exception alerts and monitoring for failed, delayed or rejected documents.
  • A managed workflow that reduces manual re-keying while keeping procurement, operations and finance teams informed.
Supplier FAQ

Dunnes EDI FAQs

What is Dunnes EDI?

Dunnes EDI is the structured exchange of documents between Dunnes and its suppliers. It supports agreed workflows for orders, order responses, delivery information, invoices and related acknowledgements.

Can XEDI connect suppliers to Dunnes EDI?

Yes. XEDI can connect Dunnes EDI flows with supplier systems and automate the agreed EDIFACT or EANCOM messages, subject to the account's document scope and testing process.

Which documents does Dunnes EDI support?

Every enriched XEDI partner page covers purchase orders and invoices. The wider Dunnes workflow can include order responses, credit notes, product information and acknowledgements where agreed.

Which EDI standard is used for Dunnes?

This Dunnes page is planned around EDIFACT or EANCOM. The exact version, subsets and message rules should be confirmed from the current trading agreement and test pack.

Can Dunnes EDI use AS2?

XEDI can support AS2 where it is the agreed Dunnes connection route, including certificates, encryption, signatures and delivery-status monitoring.

Can Dunnes EDI integrate with my ERP or accounting system?

Yes. XEDI can map Dunnes documents into supported ERP, accounting, warehouse, ecommerce and API workflows, including SAP, Oracle, Sage, Microsoft Dynamics, NetSuite and QuickBooks.

What should a Dunnes supplier prepare before onboarding?

Prepare supplier and product identifiers, delivery locations, tax and invoice details, the agreed message list, connection details and any testing instructions supplied for the account.

How long does Dunnes EDI onboarding take?

Timing depends on the supplier systems, agreed message set, data quality, testing scope and Dunnes onboarding process. Confirming scope early helps prevent avoidable delays.

Can XEDI help reduce Dunnes order and invoice errors?

Yes. XEDI can validate mandatory fields, map references consistently and surface exceptions before documents are exchanged, reducing avoidable corrections in Dunnes order and invoice workflows.

Do Dunnes supplier requirements vary?

They can vary by category, region, fulfilment model and delivery route. The current Dunnes agreement and test instructions should always take priority over a general integration plan.

Next steps

Plan your Dunnes EDI setup

Everything you need to scope, map and go live with Dunnes, in one place.