Try it now Login

EDI Trading Partner

Connect to Tor2 EDI Instantly

Join thousands of customers that connect to Tor2 with XEDI.

No credit card needed ✦ Free EDI mailbox included

See how XEDI connects suppliers to Tor2

XEDI helps Tor2 teams manage the order, fulfilment and invoice information used in retail, wholesale or marketplace supply. The connection reduces manual re-keying while keeping document status and exceptions visible to the people responsible for delivery and payment.

Overview

Getting started with Tor2 EDI

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

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

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

Suppliers and manufacturers
Commercial and order-processing teams
Warehouse and fulfilment teams
Customer-service teams
Finance and accounts receivable teams

In practice

Tor2 EDI overview

Tor2 EDI is the structured exchange of commercial documents between Tor2 and businesses working in retail, wholesale or marketplace supply. The agreed document set starts with orders and invoices, with the operational emphasis on keeping order and invoice records aligned across operational teams.

A practical Tor2 integration should connect orders and invoices with the systems responsible for processing them. XEDI maps the agreed Agreed EDI format 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 Tor2 order, despatch advice and invoice against the required format, so errors are caught before they reach your systems.

Onboarding

Tor2 supplier onboarding process

For Tor2, onboarding starts with the account identifiers, document scope and connection route used by the relationship. 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 Tor2 supplier account, buyer contacts, delivery locations, identifiers and current document requirements.
02
Agree the Tor2 order, response and invoice scope for the trading relationship.
03
Map Tor2 message data to the supplier's ERP, warehouse, order-management and accounting systems.
04
Configure Agreed EDI format validation, connection routing, exception alerts and user responsibilities in XEDI.
05
Complete the agreed Tor2 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 Tor2?

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

Connect to Tor2 Book a Demo

Detail

Everything about Tor2 EDI

Tor2 EDI message types

Tor2 document requirements depend on the commercial relationship and fulfilment route. The following business documents are reviewed when planning the order-to-invoice workflow.

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

Tor2 EDI requirements

Requirements planning should confirm the account identifiers, document scope and connection route used by Tor2. Planning should also account for the transport and validation controls used for retail, wholesale or marketplace supply.

Agreed EDI format

Map the agreed Tor2 order, response and invoice messages in the Agreed EDI format format used by the trading setup.

AS2 or managed connectivity

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

Common requirements & compliance

Common requirements

Tor2 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 Agreed EDI format message set and connection method
Test evidence for the agreed order and invoice flows

Compliance notes

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

Tor2 ERP integration

Tor2 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 Tor2 data into ERP, accounting, warehouse, ecommerce and API workflows.

SAP

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

Oracle

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

Sage

Automate Tor2 order and invoice handling for Sage users.

Microsoft Dynamics

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

NetSuite

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

QuickBooks

Support Tor2 invoice and accounting workflows for QuickBooks users.

Why suppliers choose XEDI for Tor2

Businesses choose XEDI for Tor2 EDI when they need a managed connection focused on keeping order and invoice records aligned across operational teams, with the agreed documents, validation rules, integrations and exceptions visible in one workflow.

Tor2-specific onboarding for identifiers, document scope, testing and go-live planning.
Validation for Tor2 orders and invoices before documents are exchanged.
Agreed EDI format 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

Tor2 EDI FAQs

What is Tor2 EDI?

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

Can XEDI connect suppliers to Tor2 EDI?

Yes. XEDI can connect Tor2 EDI flows with supplier systems and automate the agreed Agreed EDI format messages, subject to the account's document scope and testing process.

Which documents does Tor2 EDI support?

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

Which EDI standard is used for Tor2?

The exact Tor2 standard, version, message subset and connection route should be confirmed from the current trading agreement and test pack. XEDI can map the agreed format without assuming a universal specification.

Can Tor2 EDI use AS2?

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

Can Tor2 EDI integrate with my ERP or accounting system?

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

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

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

Can XEDI help reduce Tor2 order and invoice errors?

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

Do Tor2 supplier requirements vary?

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

Related partners