EDI Integration with Cin7: Why It Is an Ongoing Relationship, Not a One Time Setup
A Cin7 EDI connection does not end at setup. See how ASN timing, document mapping, and invoice authorization drive real trading partner compliance.
TL;DR
EDI with Cin7 is an ongoing operational relationship, not a one time technical switch.
Cin7 Omni includes native EDI connections. Cin7 Core requires an external EDI partner, such as SPS Commerce, Crstl, or Surpass Solutions. These are two different setup paths with different vendors and costs.
The core documents are the 850 purchase order, the 856 advance ship notice (ASN), and the 810 invoice. Each one is triggered by a specific authorization step inside Cin7.
Chargebacks most often trace back to late or missing ASNs, carton or count mismatches, label errors, and invoice discrepancies. The connection itself is rarely the culprit.
Knowing when EDI turns from a setup task into an implementation project saves real money.
This article is not saying your team did anything wrong. Three assumptions show up at this stage, and each one is reasonable. Each one also breaks down once documents flow in both directions.
Turning EDI on means the work is done.
A vendor portal login is basically the same as EDI.
If an order appears correctly in Cin7, the EDI side must be working.
Let us test each one.
Do I Have a Real EDI Connection With Cin7, or Just a Vendor Portal Login?
A true EDI connection exchanges structured documents automatically between systems. Those documents are the 850, the 856, and the 810. A vendor portal is manual entry on the retailer’s own website.
With a portal, someone can log in, view a purchase order, and even mark it fulfilled. Meanwhile, no structured document ever reaches the retailer in the format their system expects. That is a lot like waving at a train instead of boarding it.
Here is the part that trips teams up. An order appearing correctly in Cin7 does not confirm that your outbound documents were sent in the right format or at the right time. Order visibility in Cin7 and compliance confirmation from the trading partner are two separate things. They are checked in two separate places.
Why Is EDI Scoped as a One Time Project?
EDI is usually budgeted like a project with an end date. In reality, it is a live compliance relationship that needs attention every time an order moves through Cin7.
Part of the confusion starts at the platform level.
Cin7 Omni offers built in EDI connections, managed inside the platform. Cin7 lists pre built connections to major retailers such as Walmart, Target, Costco, Woolworths, and Coles.
Cin7 Core requires a partner. Cin7’s own help center documents an SPS Commerce route, and its EDI section also lists Crossfire Cloud. Other partners include Crstl and Surpass Solutions.
Different platform, different vendors, different cost structure, different owner of the problem. A team that reads the wrong product’s documentation can scope the entire project incorrectly before a single document is exchanged. If you are unsure which Cin7 plan fits your retail channel, our Cin7 implementation team can sort that out early.
SKU and unit of measure mapping is another common gap at go live. A pack size, a case quantity, or a price tier that does not map cleanly can pass through Cin7 without a complaint. It then fails on the retailer’s side. The order looks perfect in Cin7 and gets rejected anyway. Rude, but common.
How Do EDI Documents Move Through Cin7?
Every outbound compliance document your trading partner checks is triggered by a specific action inside Cin7. Nothing fires quietly in the background. Walking through the steps shows exactly where gaps open.
Step 1: The 850 purchase order arrives. It comes through the EDI partner (Cin7 Core) or the built in connection (Cin7 Omni). It maps to a sales order in Cin7, and stock is allocated against it.
Step 2: Pick, pack, and carton data. The order is picked and packed. SSCC carton data is assigned to the shipment.
Step 3: Ship authorization fires the 856 ASN. In Cin7 Core, authorizing the Ship tab does two jobs. It posts the cost of goods sold entry, and it acts as the fulfillment export trigger for the ASN. In Cin7 Omni, the trigger is completing the four dispatch criteria. Depending on your EDI partner or configuration, automated dispatch export may also require the Pack tab to be authorized and a non blank invoice number to be present. The invoice itself can stay unauthorized.
Step 4: Invoice authorization fires the 810. This is a separate trigger. It posts revenue recognition, fires the 810 invoice, and pushes the accounts receivable entry to QuickBooks Online or Xero. The 820 remittance advice then closes the loop when the retailer pays.
The Ship tab and the Invoice tab do two different financial jobs. One drives cost of goods sold. The other drives revenue recognition. Treating them as one combined click is where timing and financial accuracy start to drift apart.
The Rule That Prevents Most ASN Penalties
Never authorize the Ship tab, or mark an order dispatched, until four things are in place:
The SSCC carton number
Full dispatch quantities
The carrier
The tracking code
An ASN cannot be sent properly without them. If fulfillment goes through a 3PL, the risk gets sharper. Authorizing the Ship tab before the 3PL has passed tracking and SSCC data back into Cin7 creates an incomplete ASN. An incomplete ASN can trigger a retailer compliance penalty on its own.
Why Do Chargebacks Still Happen After Everything Is Set Up?
Because the setup is not the risk. The daily handling is. Four patterns explain most of what goes wrong once an EDI connection is technically working.
1. Ship and Invoice authorization treated as admin clicks. These steps are the compliance moments. Rushing them is how late, incomplete, or mismatched ASNs and invoices reach your trading partner.
2. Incomplete SKU and unit of measure mapping. Mapping between the retailer’s catalog and Cin7 gets left half done at go live. It surfaces weeks later as flagged or rejected orders.
3. Carton, count, and label errors. These come up most often when a 3PL is involved and carton data does not make it back into Cin7 before dispatch.
4. Financial adjustments made in the wrong place. Chargebacks, allowances, and short payments should never be entered as a generic bank feed “Spend Money” transaction or a plain expense. They need to start inside Cin7 as a Credit Note or an Additional Charge adjustment, which then syncs to QuickBooks Online or Xero. Entering them straight in the bank feed can leave orphaned balances in the customer subledger. The correction never links back to the original sales order or invoice.
Why These Patterns Are Easy to Miss
The portal gap described earlier is one reason. A portal experience can feel complete from the inside even when it is not.
The other reason is the math. Cin7 can show a clean gross revenue figure while chargebacks and penalty fees quietly erode net margin. There is no single alarming event. It is a slow leak. It can go unnoticed until someone checks the accounting side against what the trading partner actually paid. Our report accuracy and reconciliation work often starts exactly there.
When Does EDI Become an Implementation Project?
Three situations push EDI past a simple setup task.
You fulfill through a 3PL. Carton data has to pass correctly from the 3PL into Cin7 or the EDI partner.
You have multiple trading partners. Each one brings its own routing guide and document requirements.
Chargebacks or held payments already repeat. That points to a structural mapping or timing gap, not a one off mistake.
This does not mean every business needs a paid engagement just to understand what EDI is. It means these are the points where an internal team’s attention tends to run out. If your existing Cin7 setup is already causing pain, our Cin7 rescue works built for that.
What Does a Healthy, Ongoing EDI Relationship Look Like?
Clean master data mapping. SKU, unit of measure, and price tier are explicitly mapped between the retailer’s catalog and Cin7. This layer is the one most often left incomplete. It is also the cheapest to fix before go live.
An automated trigger chain. The 850 maps to a sales order. Pick, pack, and dispatch activity generates SSCC carton data. Dispatch criteria are met before the 856 fires. Invoice authorization fires the 810 and syncs cleanly to QuickBooks Online or Xero.
Reconciled financials. Retailer payouts and 820 remittances clear through dedicated clearing or control accounts. This isolates the gap between when a sale is recognized and when cash lands in the bank. Chargebacks and allowances get their own general ledger expense lines instead of hiding inside a generic revenue account.
Two firm rules:
Never manually edit an EDI generated invoice or credit note directly in QuickBooks Online or Xero. All changes, including chargeback credit notes, should start in Cin7 to protect the audit trail.
Keep your QuickBooks Online or Xero period lock dates aligned with how far back Cin7 may need to rewrite cost of goods sold journals. Locking a period too early can block a legitimate cost correction and leave a lasting variance between the general ledger and the subledger.
Where Does This Leave Your Own Setup?
Gaps between what Cin7 shows and what your trading partner receives often surface weeks after the dispatch that caused them. They rarely connect back to the accounting side on their own.
Place your setup somewhere on the trigger chain, from the 850 arriving to the 820 remittance clearing. You will know exactly what to check next.
Is Your EDI Connection Configured to Last?
If your EDI connection was set up as a one time project, it deserves a second look. A Fiskal systems review checks whether your mapping, ASN timing, and invoice reconciliation actually match what your trading partner expects. It happens before a gap becomes a chargeback.
Our Cin7 EDI mapping and integration services cover this kind of review: designing, configuring, and maintaining the connection so it holds up long after go live. This is not a replacement for your EDI partner or middleware provider. It is a review of what is configured underneath it.
