Try it now Login

EDI Trading Partner

Connect to Currys EDI Instantly

Join thousands of customers that connect to Currys with XEDI.

No credit card needed ✦ Free EDI mailbox included

See how XEDI connects suppliers to Currys

Currys suppliers need dependable EDI for retail orders, despatch updates and invoices. XEDI helps automate Currys trading documents and connect them with ERP, warehouse and finance systems.

Overview

Getting started with Currys EDI

Currys suppliers need dependable EDI for retail orders, despatch updates and invoices. XEDI helps automate Currys trading documents and connect them with ERP, warehouse and finance systems.

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

Currys suppliers need dependable EDI for retail orders, despatch updates and invoices. XEDI helps automate Currys trading documents and connect them with ERP, warehouse and finance systems.

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 Currys suppliers

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

Electrical goods suppliers
Consumer technology brands
Distribution teams
Warehouse teams
Finance teams

In practice

Currys EDI overview

Currys EDI is the structured exchange of commercial documents between Currys and businesses working in consumer-electronics retail, home delivery and store fulfilment. The agreed document set starts with orders and invoices, with the operational emphasis on keeping order, fulfilment and finance data aligned.

A practical Currys integration should connect the agreed document set with the systems that process it. XEDI maps the agreed EANCOM or EDIFACT 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 Currys order, despatch advice and invoice against the required format, so errors are caught before they reach your systems.

Onboarding

Currys supplier onboarding process

For Currys, 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.

01
Confirm the Currys supplier account, buyer contacts, delivery locations, identifiers and current document requirements.
02
Agree the Currys order, response and invoice scope for the trading relationship.
03
Map Currys message data to the supplier's ERP, warehouse, order-management and accounting systems.
04
Configure EANCOM or EDIFACT validation, connection routing, exception alerts and user responsibilities in XEDI.
05
Complete the agreed Currys test transactions, checking mandatory references, product data, delivery details and invoice matching.
06
Monitor initial live transactions and resolve rejected, delayed or mismatched documents with the operational and finance teams.

Ready to connect Currys?

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

Connect to Currys Book a Demo

Detail

Everything about Currys EDI

Currys EDI message types

Currys message requirements depend on the supplier account and fulfilment route. These are the common EANCOM or EDIFACT 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.	Currys to supplier
ORDRSP	Order acknowledgement or response used to confirm, reject or amend order lines before fulfilment.	Supplier to Currys
INVOIC	Invoice linked to the order, delivery and supplier references agreed with Currys.	Supplier to Currys
APERAK	Application or functional acknowledgement used to confirm receipt or identify processing errors where supported.	Either direction

Currys EDI requirements

Currys requirements should be confirmed against the current agreement and test instructions. Planning should also account for the transport and validation controls used for consumer-electronics retail, home delivery and store fulfilment.

EANCOM or EDIFACT

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

AS2 or managed connectivity

Use AS2, SFTP, a VAN or the connection method agreed with Currys, 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 Currys message set, resolve validation feedback and retain evidence that the connection is ready for live trading.

Common requirements & compliance

Common requirements

Currys 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 EANCOM or EDIFACT message set and connection method
Test evidence for the agreed order and invoice flows

Compliance notes

Currys 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 Currys orders and invoices.

Currys ERP integration

Currys EDI integration connects supplier document flows with the systems teams use to process orders, allocate stock, ship goods and create invoices. XEDI can map the agreed Currys data into ERP, accounting, warehouse, ecommerce and API workflows.

SAP

Map Currys orders, shipment data and invoices into SAP workflows.

Oracle

Connect Currys EDI with Oracle Fusion order, fulfilment and finance processes.

Sage

Automate Currys order and invoice handling for Sage users.

Microsoft Dynamics

Route Currys EDI messages into Microsoft Dynamics sales, stock and finance workflows.

NetSuite

Connect Currys EDI with NetSuite order management, fulfilment and invoicing.

QuickBooks

Support Currys invoice and accounting workflows for QuickBooks users.

Why suppliers choose XEDI for Currys

Businesses choose XEDI for Currys 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.

Currys-specific onboarding for identifiers, document scope, testing and go-live planning.
Validation for Currys orders and invoices before documents are exchanged.
EANCOM or EDIFACT 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

Currys EDI FAQs

What is Currys EDI?

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

Can XEDI connect suppliers to Currys EDI?

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

Which documents does Currys EDI support?

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

Which EDI standard is used for Currys?

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

Can Currys EDI use AS2?

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

Can Currys EDI integrate with my ERP or accounting system?

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

What should a Currys 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 Currys EDI onboarding take?

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

Can XEDI help reduce Currys order and invoice errors?

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

Do Currys supplier requirements vary?

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

Related partners