Connect Cin7 Core to EDI instantly
Join thousands of businesses moving EDI orders, invoices and fulfilment updates between Cin7 Core and their trading partners on XEDI, no manual re-keying.
No credit card needed ✦ Free EDI mailbox included
Getting started with Cin7 Core EDI
XEDI connects Cin7 Core, formerly DEAR Systems, with retailer EDI so wholesale orders arrive against the right customers and products, and despatch confirmations and invoices go back out without manual handling.
One managed platform, no custom code
XEDI maps Cin7 Core to your trading partners and validates every document, so data flows straight into the systems your teams already use.
Wholesale is a different discipline from the channels Cin7 Core already runs
Cin7 Core is usually carrying several channels at once: a website, marketplaces, maybe retail of your own. Wholesale looks superficially similar and behaves nothing like them. The retailer sets the terms, the pack configuration, the delivery window and the document formats, and none of it is negotiable.
What that means practically is that a wholesale order cannot be handled the way a marketplace order is. It carries obligations about how the goods are presented and described, and failing those costs money in ways a consumer channel never does.
The rename is not just cosmetic for an integration
DEAR Systems became Cin7 Core, and the Cin7 range includes more than one product. Work scoped against the wrong one, or against documentation for the other, surfaces late and awkwardly.
We establish which product and plan you are actually on before anything is built, because the available endpoints and the fields behind them differ, and a mapping is only as good as the assumption it was built on.
What your team sees day to day
You get an EDI mailbox and a portal that works like an inbox, so a retailer order does not arrive in the same place as your consumer traffic.
The order becomes the despatch advice rather than a re-entered one, amended where the delivery differs from the order, with SSCC labels for the pallets, and becomes the invoice on delivery, whose arrival is confirmed in the dashboard.
The integration sits over that workflow and automates it, so orders land as Cin7 Core sales orders and fulfilment raises the outbound documents. Smaller brands run the portal alone; our API suits businesses needing finer granularity; wholesale volume is usually what makes the integration worth having.
Documents you can exchange
- Retailer orders landing as Cin7 Core sales orders
- Order acknowledgements returned to the retailer
- Despatch advice and ASN messages from fulfilment
- Invoices raised from Cin7 Core
- Stock availability where a retailer requires it
Built for Cin7 Core teams
Whoever owns Cin7 Core in your business, XEDI keeps EDI accurate and hands-off.
- Multi-channel consumer brands
- Wholesale and distribution teams
- Operations managers across several sales channels
- Finance teams handling wholesale invoicing
- Brands adding retail alongside direct to consumer
Cin7 Core EDI document types
The set varies by retailer, but a brand supplying retail through Cin7 Core normally runs these.
| Document | What it carries | Direction |
|---|---|---|
| Purchase orders | Retailer demand landing as a Cin7 Core sales order against the right customer, products, price tier and location. | Retailer to Cin7 Core |
| Order acknowledgements | What can be committed from available stock, including short and substituted lines. | Cin7 Core to retailer |
| Advanced shipping notices | Pallet and carton detail from fulfilment, with SSCC labels the retailer's goods-in will scan. | Cin7 Core to retailer |
| Invoices | Raised from Cin7 Core and referenced to the order and despatch so the retailer can match them. | Cin7 Core to retailer |
| Credit notes | Credits against the invoice they adjust, carried with a credit document code. | Cin7 Core to retailer |
| Stock availability | Available quantity by location where a retailer plans against your figures. | Cin7 Core to retailer |
How to connect Cin7 Core with EDI using XEDI
The build starts by confirming which Cin7 product you are on, then mapping your products to each retailer's identifiers. The sequence below is what onboarding looks like from your side.
-
01
We scope which Cin7 Core locations, customers and price tiers the wholesale relationships use.
-
02
We build the mapping between each retailer's documents and your Cin7 Core customers, products and units.
-
03
We configure validation so an order is checked against the retailer's rules before it becomes a sales order.
-
04
We prove the order, fulfilment and invoice flows against what each retailer requires and against how your account is set up.
-
05
You get retail orders arriving without re-entry, and we keep the mapping right as your range and channels change.
Ready to connect Cin7 Core?
Talk through documents, mapping, testing and go-live with XEDI.
Everything about Cin7 Core EDI
Common requirements
- Cin7 Core account and API access
- Customer, location and price tier structure
- Product codes, barcodes and units
- Fulfilment and part-shipment rules
- The trading partners you deal with, or plan to
What we need from you to build it
Only what we cannot hold for you. Retailer requirements are already ours; what we need is which Cin7 product you run and how it is set up.
- Cin7 Core access
- API credentials and confirmation of which Cin7 product and plan you are on, since the endpoints and fields differ.
- Customer and location records
- Each retailer mapped to a customer with the right price tier, and delivery points resolvable to a location.
- Product and barcode data
- Product codes against retailer GTINs at each packaging level, and the unit a retailer orders in.
- Fulfilment rules
- How part shipments, back orders and substitutions should be represented to the retailer.
- Which retailers you supply
- The listings in scope now and next. Their requirements are already ours.
Why suppliers choose XEDI for Cin7 Core
- Retailers are usually connected already, so a new listing does not wait on confirming which Cin7 product you run.
- Wholesale orders arrive separately from consumer channels rather than being handled the same way and costing you at goods-in.
- Which Cin7 product you are on is established before anything is built, rather than discovered during testing.
- Product and pack translation is maintained by us as your range and channels change.
- A new retailer listing is our build, not a project for a team already running several channels.
- If a retailer raises a problem, it comes to us, and we resolve it before it becomes a deduction.
Is this DEAR Systems or Cin7 Core?
The same product: DEAR Systems was renamed Cin7 Core. The Cin7 range includes more than one product, so which one you are on is confirmed before anything is built, because the endpoints and fields differ.
Can we run wholesale EDI alongside our other channels?
Yes, and that is the usual case. Wholesale arrives separately from consumer traffic so it can be handled to the retailer's requirements rather than being treated like a marketplace order.
How are part shipments handled?
How you want short supply and back orders represented is agreed during scoping, and the despatch advice and invoice then reflect what actually shipped rather than what was ordered.
Plan your Cin7 Core EDI setup
Everything you need to scope, map and go live with Cin7 Core, in one place.