The messages your largest customers require, produced without a person in the middle.
CubeERP and EDI
Electronic data interchange with retailers, OEMs and distributors - orders and schedules in, despatch advices and invoices out.
- Trading
- No per-connector licence
- 01234 672 617
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.
What moves
Exactly what is synced, and which way
Being specific about this up front avoids the single most common integration disappointment - discovering after go-live that one field never travelled.
- Into CubeERP
Orders and delivery schedules
Purchase orders and rolling schedules received and turned into sales orders or call-offs, with changes highlighted rather than silently applied.
- Out of CubeERP
Despatch advices
ASN/DESADV messages produced from actual pack contents at despatch, matching the labels physically on the pallet.
- Out of CubeERP
Invoices
Invoices sent in the partner’s required format, matched to the despatch, so self-billing and remittance reconciliation work cleanly.
- Out of CubeERP
Stock and availability
Where a partner expects inventory reporting, availability is sent on their schedule from live stock rather than a manual extract.
How it behaves
The detail that decides whether it is actually useful
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.
Setting it up
Three steps, done during implementation
- 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.
Questions
What people ask about this one
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.
The common retail and automotive message types for orders, schedules, despatch advices and invoices. Partner-specific variants are configuration rather than development.
By generating labels and despatch advices from actual pack contents at the point of despatch, rather than from a separate template maintained by hand.
The mapping is configuration, so a change is a configuration update and a test cycle rather than a development project.
Yes, and you should. Onboard the largest or most demanding partner first, get it right, then repeat.
Related
Usually set up at the same time
- Adobe Commerce (Magento)Adobe Commerce and Magento Open Source connected to CubeERP stock, customer-specific pricing, order processing and fulfilment.
- Carriers & CouriersRates, labels, manifests and tracking for the main UK parcel and pallet networks, generated from the despatch record.
- CubeERP API & WebhooksA documented REST API and webhooks covering the whole system - the same interface the product itself is built on.
EDI
Check the EDI detail before you commit
Send us the specifics - your chart of accounts, your tax treatment, your product structure - and we will tell you exactly how it maps rather than promising it will be fine.