# EDI

> Electronic data interchange with retailers, OEMs and distributors - orders and schedules in, despatch advices and invoices out.

**URL:** https://cubeerp.co.uk/integrations/edi

The messages your largest customers require, produced without a person in the middle.

EDI is rarely optional. If you supply a supermarket, an OEM or a large distributor, their message formats and labelling requirements are a condition of trading, and getting them wrong produces chargebacks. CubeERP receives orders and delivery schedules, and produces despatch advices and invoices in the formats your trading partners require, with each partner configured separately because they all want something slightly different.

## Details

- **Category:** Trading
- **Licence cost:** included, no per-connector charge
- **Platform:** CubeERP (https://cubeerp.co.uk/platform)

## What syncs

- **Orders and delivery schedules** (Into CubeERP): Purchase orders and rolling schedules received and turned into sales orders or call-offs, with changes highlighted rather than silently applied.
- **Despatch advices** (Out of CubeERP): ASN/DESADV messages produced from actual pack contents at despatch, matching the labels physically on the pallet.
- **Invoices** (Out of CubeERP): Invoices sent in the partner’s required format, matched to the despatch, so self-billing and remittance reconciliation work cleanly.
- **Stock and availability** (Out of CubeERP): Where a partner expects inventory reporting, availability is sent on their schedule from live stock rather than a manual extract.

## How it behaves

- **Per-partner configuration:** Message formats, identifiers, tolerances and labelling configured per trading partner, because no two of them are the same.
- **Labelling that matches:** Customer-specific pallet and carton labels generated from actual pack contents, which is where most chargebacks originate.
- **Exceptions to a human:** Messages that cannot be processed - unknown codes, price mismatches, unexpected quantities - are queued and reported rather than rejected silently.
- **Full message audit:** Every message in and out retained with timestamps, so a dispute about what was sent and when is settled by evidence.

## Setup

1. Collect each trading partner’s specification and labelling requirements - usually the longest part of the exercise.
2. Configure the mapping and run test messages through their conformance process before going live.
3. Onboard partners one at a time. Doing several at once means you cannot tell which change caused which problem.

## Frequently asked questions

**Do we need a separate EDI provider?**

Not necessarily. Where you already use a VAN or EDI broker, CubeERP integrates with it; where you do not, messages can be exchanged directly with the partner.

**Which message standards do you support?**

The common retail and automotive message types for orders, schedules, despatch advices and invoices. Partner-specific variants are configuration rather than development.

**How are chargebacks avoided?**

By generating labels and despatch advices from actual pack contents at the point of despatch, rather than from a separate template maintained by hand.

**What happens when a partner changes their spec?**

The mapping is configuration, so a change is a configuration update and a test cycle rather than a development project.

**Can we start with one customer?**

Yes, and you should. Onboard the largest or most demanding partner first, get it right, then repeat.

## Related integrations

- **Adobe Commerce (Magento)** - Adobe Commerce and Magento Open Source connected to CubeERP stock, customer-specific pricing, order processing and fulfilment. https://cubeerp.co.uk/integrations/magento
- **Carriers & Couriers** - Rates, labels, manifests and tracking for the main UK parcel and pallet networks, generated from the despatch record. https://cubeerp.co.uk/integrations/couriers
- **CubeERP API & Webhooks** - A documented REST API and webhooks covering the whole system - the same interface the product itself is built on. https://cubeerp.co.uk/integrations/rest-api

## Contact

- **Product:** CubeERP
- **Trading name of:** Cube Systems Limited (company number 17220899, ICO registration number ZC216972)
- **Email:** hello@cubeerp.co.uk
- **Sales:** sales@cubeerp.co.uk
- **Support:** support@cubeerp.co.uk
- **Telephone:** 01234 672 617 (+441234672617)
- **Address:** Unit 11, Olney Business Park, Osier Way, Olney, Buckinghamshire, MK46 5FP
- **Opening hours:** Monday to Friday, 9am to 5.30pm
- **Part of:** Crushed Ice Group (https://crushedicegroup.co.uk)