Do you support Cin7 Core or Cin7 Omni?

Both. They are separate products with different API surfaces, so which one you run is confirmed against your tenant in scoping and the workflow is built for it specifically.

Why not just use Cin7's own Shopify connection?

For a single store on a clean catalogue it is often the right answer, and we will tell you so. Managed integration earns its place with several stores, bundles or kits, multiple sellable warehouses, or exception handling that has to be owned by someone.

How is stock published to the storefront?

From the Cin7 warehouses you designate as sellable, on an agreed cadence, with any buffers applied by rule. A failed read retains the last known quantity rather than publishing zero.

Who works the exceptions?

APIWORX works the queue and escalates to your named contacts when a business decision is needed.

Order and inventory · Operations

Cin7

Shopify

Connect Cin7 + Shopify

Automate order, product mapping, available stock, fulfilment and tracking, customer record between Cin7 and Shopify — with monitoring and managed support from APIWORX.

See How It Works

APIWORX connects the systems your business already uses and takes responsibility for the agreed integration workflows after go-live. The exact objects, direction and cadence are fixed in writing during scoping.

ERP + eCommerce Specialists

Managed & Monitored Integrations

Expert Integration Team

APIWORX Provides the Service

Yes. APIWORX connects Cin7 and Shopify.

But connecting the applications is only the beginning. The work that costs you time sits in the process running between them.

APIWORX automates that process end to end — the objects moving between Cin7 and Shopify, the ownership rules that decide which system wins, the exceptions when a record will not post, and the monitoring that tells someone before your team finds out from a customer.

Order-to-cash automation Inventory synchronization

How it works

From requirements to a managed integration

Tell Us What You’re Connecting

Provide the systems, workflow and business requirements.

We Design the Integration

APIWORX recommends the integration architecture, mappings and implementation approach.

We Build, Monitor & Support It

APIWORX implements the integration and provides ongoing monitoring and support as applicable.

Who this is for

This page is for operations teams running Cin7 — Core or Omni — as the inventory system of record behind one or more Shopify stores.

What needs to be in place

Cin7 Core or Cin7 Omni with API access and a service account permitted to read stock and write orders.
One or more Shopify stores with API credentials and an agreed order status that means ready to process.
An agreed product mapping key — SKU, barcode or Cin7 product code — and the warehouses treated as sellable.
A named operations contact for stock, bundle and exception decisions.

When you may not need this

Cin7 ships its own Shopify connection, and for a single store on a clean catalogue that is often enough. Managed integration earns its place when several stores, bundles or kits, multiple sellable warehouses or exception handling put it beyond what a point connector is designed to hold.

What is out of scope

Cin7 Core and Cin7 Omni are different products with different API surfaces and behaviours. Which one you run — and therefore what is available — is confirmed against your tenant before build.
Where Cin7's own Shopify connection already meets the need, we will say so rather than replace it for the sake of it.
Bundle, kit and assembly behaviour differs by Cin7 product and configuration; how they are represented on the storefront is agreed before build.
APIWORX does not change how Cin7 costs inventory or how Shopify calculates tax.

What actually moves, and who owns it

A representative scope. Exact objects, mapping key and warehouse rules are confirmed against your Cin7 product before build.

Cin7APIWORX (mapping, retries, exception queue)Shopify

Objects exchanged between Cin7 and Shopify, with system of record, trigger, failure handling and owner
Object	From	To	System of record	Trigger	If it fails	Owner
Order	Shopify	Cin7	Shopify	Order reaches the agreed ready-to-process status	Held in exception queue with the validation error	APIWORX
Product mapping	Agreed key — SKU, barcode or Cin7 code	Both systems	Cin7	At order and stock sync	Unmapped items reported; nothing created on a guess	APIWORX
Available stock	Cin7	Shopify	Cin7	On the agreed cadence or on stock change	Last known quantity retained; gap reported	APIWORX
Fulfilment and tracking	Cin7	Shopify	Cin7	Shipment recorded in Cin7	Retried, then queued for review	APIWORX
Customer record	Shopify	Cin7	Agreed in scoping	At order creation	Matched or queued rather than duplicated	APIWORX
Refund or cancellation	Shopify	Cin7	Shopify	Refund or cancellation recorded	Raised as an exception for a decision	APIWORX

Three decisions that make or break this integration

Storefront stock is wrong on the fast movers

Oversells happen where the sellable position is assembled from more than one warehouse. Which Cin7 warehouses count as sellable, and how buffers apply, is agreed once and then applied consistently on an agreed cadence.

Sellable locations defined explicitly, not inferred.
Buffers applied by rule rather than by memory.
A failed read never publishes a zero.

Bundles and kits do not line up

Cin7 Core and Omni handle assemblies differently. How a storefront bundle maps to Cin7 components is decided in scoping so orders decrement the right items rather than the wrapper.

Bundle representation agreed per product type.
Component decrementing confirmed against your Cin7 product.
Unmapped bundles held rather than partially processed.

Several stores, one inventory position

Multiple Shopify stores — regions, brands, B2B — each need their own mapping and price rules against the same Cin7 stock. Each store's rules are held as configuration inside one monitored process.

Per-store mapping and sellable rules.
One exception queue across all stores.
Adding a store is a change request, not a rebuild.

Reliability and ownership

The operating rules that apply to this workflow after go-live.

Every run is logged with the source record reference so an order can be traced end to end.
Failed messages are retried on a defined schedule; anything still failing lands in an exception queue rather than being dropped silently.
Duplicate prevention keys on the source system's own identifier so a replayed message cannot create a second order or a second fulfilment request.
Exceptions are worked by the APIWORX team and escalated to your named contacts when a business decision is needed.
Mapping changes — new SKUs, new warehouses, new channels — are handled inside the ongoing engagement.
Support windows and response commitments live in your agreement; this page does not state an SLA.

How an order is traced

Illustrative — not customer data

An illustrative reference trace from Shopify order to Cin7 and back.

How an order is traced
Shopify order number	Cin7 sale reference
Agreed mapping key	Cin7 product code
Cin7 shipment	Shopify fulfilment record
Unmapped SKU	Exception queue entry

Scope and questions

Do you support Cin7 Core or Cin7 Omni?: Both. They are separate products with different API surfaces, so which one you run is confirmed against your tenant in scoping and the workflow is built for it specifically.
Why not just use Cin7's own Shopify connection?: For a single store on a clean catalogue it is often the right answer, and we will tell you so. Managed integration earns its place with several stores, bundles or kits, multiple sellable warehouses, or exception handling that has to be owned by someone.
How is stock published to the storefront?: From the Cin7 warehouses you designate as sellable, on an agreed cadence, with any buffers applied by rule. A failed read retains the last known quantity rather than publishing zero.
Who works the exceptions?: APIWORX works the queue and escalates to your named contacts when a business decision is needed.