Cin7 exists because modern product brands sell everywhere at once — DTC site, marketplaces, wholesale, maybe a 3PL in each region — and inventory has to stay true across all of it. Retail EDI is simply the next channel in that list, with one difference: it arrives as a mandate with a routing guide attached. The good news for a Cin7 shop is that EDI's document flows map cleanly onto objects the platform already keeps accurate.
One integration shape, two Cin7s
Whether you run Cin7 Core (the product formerly known as DEAR) or Cin7 Omni, the EDI integration rides the same conceptual objects: products with SKUs, stock levels by location, sales orders, and fulfillments with tracking. The EDI layer converts each partner document into the corresponding object and listens for the events that trigger outbound documents:
- Stock levels → 846 inventory advice. Dropship partners like Wayfair and Chewy run on inventory feeds — the 846 publishes sellable positions on the partner's cadence, keeping listings live and oversells contained. Cin7's whole reason for being — one true stock picture across channels — is exactly what a dropship 846 needs to draw from.
- Inbound 850 → Cin7 sales order, with the retailer's item numbers and UPCs cross-referenced to your SKUs and the ship-to intact. Wholesale POs and dropship consumer orders both land in the same order queue your team already works.
- 855 out — automatic confirmation inside the partner's response window.
- Fulfillment → 856 ASN. When the Cin7 fulfillment exists with a tracking number, the ASN transmits. For wholesale programs requiring carton-level hierarchy, GS1-128 labels are included free with EDISQ, with SSCC-18 serials shared between label and ASN so they cannot drift apart.
- Invoice → 810, referencing the PO the way the partner's payables match demands.
The multi-channel wrinkles worth planning for
Inventory allocation. A brand selling DTC plus three dropship programs from the same stock pool has to decide what each partner may see. Feeding every partner your full free stock invites simultaneous sellouts; most teams publish channel-adjusted quantities or buffers. Decide the policy before the first 846 goes out — it is a business rule, not a mapping detail.
3PL fulfillment. Many Cin7 shops ship through 3PLs. The loop still works: the EDI order lands in Cin7, the 3PL fulfills through your existing Cin7 workflow, the tracking posts back, and the connector turns it into the partner-facing ASN. The 3PL never needs to know EDI exists — the same inheritance pattern covered in our dropship operations guide.
Item mapping across variants. Retailers order by their identifiers; Cin7 thinks in your SKU catalog. Map at the sellable-unit level, and keep the cross-reference in one maintained table rather than scattered through channel configs.
Going live
The sequence is short. Connect Cin7 (platform connectors are activated on request; CSV import/export is live for every account immediately, a practical bridge for a first partner deadline). Pick partners from the directory — 2,200+ trading partners with certified maps, so each retailer's companion-guide rules are configuration rather than research. Wire the item and location cross-references. Test in sandbox: order in, 855 back, ASN structure, invoice match, 846 cadence.
From there, scale is horizontal. The Cin7 side never changes; each new retail program is another map set on the EDISQ side. Brands routinely run one stock pool behind a DTC store, two marketplaces, and four EDI partners — which is precisely the world Cin7 was built for.
The bill
Multi-channel brands live and die on unit economics, and the EDI line should be legible: first 25 documents each month free, then from $0.50 per document, tapering with volume on marginal tiers — published openly on the pricing page. Connectivity (AS2, VAN, SFTP), maps, labels, and automatic 997s are included, signup is self-serve, and there is no monthly fee on the Self-Serve plan. Adding a retail channel should cost like adding a channel — not like buying a system.
FAQ
Does Cin7 support EDI?
Cin7 is inventory-first — stock, orders, and channels. Retail X12 EDI comes from pairing it with an EDI layer that converts partner documents into Cin7 orders and turns fulfillments into ASNs and invoices.
Which Cin7 product does EDI apply to?
Both. Cin7 Core (formerly DEAR) and Cin7 Omni handle inventory and orders; in either case the EDI layer rides the platform's order and fulfillment objects, so the integration shape is the same.
How do retailers' orders reach Cin7?
Each inbound 850 becomes a Cin7 sales order with the retailer's item identifiers cross-referenced to your SKUs and the ship-to carried through — the order joins the same queue as your other channels.
What does Cin7 EDI cost with EDISQ?
Per document: the first 25 each month are free, then from $0.50 per document, decreasing with volume. Connectivity, maps, and 997 acknowledgments are included, with no monthly fee on the Self-Serve plan.