IMS Platform

Cin7 Core is your
inventory hub. Let it act like one.

Cin7 Core is built to manage your inventory, orders and stock across every channel — but only delivers on that promise if every surrounding system feeds it correctly and responds in time. Supply Lens connects Cin7 Core inbound and outbound, across every storefront, warehouse and finance system you use.

Cin7 Core connects to
Shopify
WooCommerce
EDI
Mintsoft
Xero
QuickBooks
Amazon
ShipStation
How Cin7 Core fits your stack

Inbound from commerce.
Outbound to fulfilment and finance.

Cin7 Core sits in the middle of your operation. Supply Lens makes sure everything flowing into it is clean and structured, and everything flowing out reaches the right system at the right time.

Inbound flows
Orders from your storefronts and marketplaces, plus retailer purchase orders from EDI networks, land in Cin7 Core as correctly structured sales orders without manual intervention.
Shopify orders WooCommerce orders Amazon orders Retailer EDI POs
Cin7 Core as the hub
Stock levels, product data, customer records, pricing and fulfilment state all live in Cin7 Core. Supply Lens keeps every surrounding system aligned with what Cin7 Core holds as truth.
Stock sync Customer sync Product data Pricing tiers Fulfilment state
Outbound flows
Dispatch events go to storefronts. Tracking numbers reach customers. Invoices land in your finance system. Warehouse orders reach your 3PL. All triggered by events in Cin7 Core.
Dispatch to storefront 3PL order handoff Invoice to Xero ASN to retailer Stock to channels
What Supply Lens handles

Five core flows.
All the complexity handled.

The data flows that matter most for a Cin7 Core operation, and the specifics that make each one difficult to get right without the right integration layer.

Sales order creation
Shopify, WooCommerce, Amazon and EDI orders become correctly structured Cin7 Core sales orders — customer resolved, SKUs matched, tax applied and shipping handled — regardless of which channel the order came from.
Multi-sourceCustomer resolutionSKU matching
Stock sync (outbound)
Available stock from Cin7 Core updates your storefronts and marketplaces. Channel-specific availability rules applied: single or multi-warehouse, or by fulfilment method. Rate limits respected — updates batch correctly without silent failures.
Real-timeMulti-warehouseChannel rules
Fulfilment & dispatch
Cin7 Core dispatch events trigger fulfilment updates back to Shopify, WooCommerce and Amazon. Tracking numbers pushed to storefronts and customers. 3PL and shipping software order handoff handled automatically.
Tracking pushStorefront update3PL routing
Invoice to finance
Sales invoices from Cin7 Core land in Xero or QuickBooks with correct account codes, tax treatment and customer references. No re-keying. Credit notes matched to original invoices automatically.
XeroQuickBooksAccount codes
Retailer EDI flows
Retailer purchase orders become Cin7 Core sales orders. Acknowledgements, ASNs and invoices are generated and returned to the trading partner, with supplier codes, location references and cross-references all handled per retailer.
PO ingestionASN & invoice outCode mapping
Where integrations typically break

Cin7 Core is capable. The surrounding
systems don't always cooperate.

The common failure points in Cin7 Core integrations, and how Supply Lens handles them before they become operational problems.

Our Shopify product codes don't match Cin7 Core codes and the sync fails on the first order.

Supply Lens operates a cross-reference layer between Shopify variant SKUs and Cin7 Core product codes. You define the mapping once — or we build it from your data — and it persists through every order, every stock update and every fulfilment event. Mismatches are caught, logged and flagged rather than silently failing or creating incorrect records.

Stock updates from Cin7 Core keep hammering the Shopify API and we're getting throttling errors.

Supply Lens manages sync frequency intelligently. Stock changes are batched correctly, API rate limits are respected, and the sync runs reliably without throttling errors or silent failures. Where Cin7 Core holds stock across multiple warehouses, only the correct available-to-sell quantity reaches each Shopify location — not a raw total that doesn't reflect your fulfilment rules.

We sell bundles on Shopify but Cin7 Core doesn't have the same bundle SKUs — fulfilment breaks.

Bundle SKUs sold through storefronts are exploded into their component lines before the Cin7 Core order is created, so the sales order reflects the individual products Cin7 Core knows about. Stock is consumed at component level, and fulfilment confirmation returns to Shopify against the original bundle SKU. Your Cin7 Core inventory position stays accurate without any manual intervention.

We have two warehouses in Cin7 Core but Amazon FBA and our own warehouse keep showing the wrong stock.

Multi-warehouse stock logic in Cin7 Core needs explicit handling at the integration layer. Supply Lens maps each warehouse to the correct channel or fulfilment method, and only the stock available from the relevant warehouse updates each channel. FBA stock stays separate from your own warehouse stock, and each channel reflects an accurate, fulfilment-specific available quantity rather than a combined total.

Getting started

A complete Cin7 Core
integration in days.

Most Cin7 Core integration projects follow a structured onboarding path. You give us what we need, we configure and test. You go live.

What we need from you
Cin7 Core API credentials
Account ID and API key from your Cin7 Core settings panel
Source system credentials
Shopify, WooCommerce, Amazon, or EDI network details depending on your flow
Warehouse and location list
Which warehouses drive stock and fulfilment for each channel
Customer account strategy
How customers should be created or matched in Cin7 Core
Sample orders and products
To validate mapping, SKU resolution and edge case handling before go-live
How we get you live
1
Scope
Credentials, SKU mappings and a handful of sample orders collected.
2
Configure
Your connection is built and mapped in a staging environment.
3
Test
End-to-end run with real data. Edge cases confirmed, exceptions reviewed.
4
Go live
Production activated. Monitoring on from day one.

EDI flows involve additional steps for document spec review and trading partner configuration.

Ready to make Cin7 Core
the hub it's built to be?

Most Cin7 Core integrations are live in 2–3 days. No long contracts. 30-day trial available.