Not every sync needs to be real-time
Scheduled or event-driven updates can be safer, cheaper and easier to recover.
CI
ERP & Accounting
Cin7 Integration for eCommerce & Custom Websites
Cin7 Core and Cin7 Omni connected to your storefront, with the stock and pricing sync that inventory-led businesses actually need.
Cin7 is built around inventory, which is exactly why the integration has to be right: get the stock sync wrong and customers buy things you cannot ship. Cin7 Core and Cin7 Omni are two different products under one brand, with different APIs and different strengths, and the correct approach depends on which one you run. We connect Cin7 to Shopify, Adobe Commerce, WooCommerce, and custom platforms with retries, idempotency, and monitoring, so stock levels, orders, and pricing stay in step even under load.
Discuss Cin7 integration
Works with
& custom builds
& custom builds
Our integration track record
We run inventory and ERP syncs in production across Options ERP, NetSuite, MYOB, and Xero, including a nightly sync of around ten million rows at 100% success. Cin7 is an inventory-led system, and it needs exactly that: a sync you can trust when stock is moving fast.
Capabilities
What we build with Cin7
The Cin7 integration work our senior team most often takes on.
Real-time Stock Sync
Stock levels kept accurate across your storefront and any other channels, so customers cannot buy what you cannot ship. Multi-location and multi-channel stock handled properly rather than flattened into one misleading number.
Core vs Omni
Cin7 Core (formerly DEAR) and Cin7 Omni are genuinely different products with different APIs. They are not interchangeable, and you get a straight answer on which one you are on and what that means for the build.
Orders & B2B Pricing
Website orders into Cin7 ready to pick and dispatch, and customer-specific or tiered pricing surfaced to your B2B storefront. For wholesalers this pricing sync is usually the whole reason a real integration is worth it.
Rate Limits & Reliability
Cin7 has API rate limits that a naive integration hits and then starts dropping updates. Batching, queueing, retries, and monitoring are designed in so the sync stays accurate as your order volume grows.
How it works
A Cin7 integration built to last
The same approach behind every integration we deliver, from the first conversation to the years of maintenance that follow.
Scope & map
We define the data, events, responsibilities, source of truth, and failure cases across Cin7 and the systems around it.
Build for failure
We design around real failure modes with appropriate retries, idempotent writes, validation, and reconciliation so a temporary outage does not become silent data loss.
Test & reconcile
We test representative data in a safe environment, verify each data path, and reconcile the expected outcomes before go-live.
Monitor & maintain
Monitoring and alerting start at launch. Our senior team keeps the project context and remains responsible for changes, incidents, and long-term operation.
Related services
Where Cin7 fits in
The services and platforms a Cin7 integration most often plugs into.
Business Software Integrations
For organisations that need websites, ERPs, finance, CRM, fulfilment, or identity systems to exchange data reliably.
D2C eCommerce Web Development
For established consumer brands that need a faster storefront, better merchandising, and commerce systems that can handle growth.
B2B eCommerce Web Development
For wholesalers and distributors that need contract pricing, account workflows, approvals, and reliable ERP-connected ordering.
Shopify & Shopify Plus Development
A good fit for consumer brands that want a managed commerce platform and need senior help with complex storefronts, migrations, or integrations.
Laravel Development
A good fit for custom applications, complex business rules, APIs, and integrations that need a maintainable long-term codebase.
Straight advice
The simplest reliable integration usually wins.
The right design depends on volume, timing, ownership and what must happen when either system is unavailable.
Choose a source of truth
Each field and business rule needs one accountable owner across the connected systems.
Design the failure path
Retries, logs, alerts and reconciliation are part of the integration—not optional support work.
The Difference
Get the stock sync wrong and everything downstream breaks.
With an inventory system like Cin7, the integration is not a nice-to-have bolted onto the storefront. It is the thing that decides whether your customers can trust what your website tells them about stock. That is worth building carefully.
A common shortcut
Integration as plumbing.
-
Stock sync runs on a naive schedule, hits Cin7 rate limits, and silently starts dropping updates so the storefront drifts out of date.
-
Nobody checks whether you are on Cin7 Core or Omni until the API turns out to work differently mid-build.
-
A failed order sync means an order sits on the website and never reaches the warehouse.
Our senior-team model
Integration is the specialism.
-
Batched, queued, and rate-aware, with reconciliation confirming the storefront and Cin7 agree.
-
We establish which Cin7 product you run up front, because Core and Omni need different approaches.
-
Failures are retried and alerted. An order that genuinely cannot sync is flagged that day, not discovered by an angry customer.
“ Digital Bird has had a huge influence on our business providing many solutions besides just a fantastic reliable website. Jonathan is great to work with and has a solution to every challenge. Jonathan also has the ability to “dumb it down” and provide timely advice and assistance if something goes astray. With Jonathan we have in excess of 99% uptime on all three websites. ”
Jeff Ross
· Director, Impact Office Supplies
Other integrations
FAQ
Common Cin7 Integration Questions
Common questions our team is asked about integrating Cin7.
Yes. Stock levels, orders, and pricing can all sync between Cin7 and Shopify, and equally between Cin7 and Adobe Commerce or a custom storefront. Cin7 does have an existing Shopify connector, and for simple setups it may be all you need. A custom integration earns its place when you have multi-location stock, customer-specific pricing, multiple sales channels, or volume that pushes against Cin7's API limits.
Cin7 Core (previously DEAR Systems) and Cin7 Omni are two different products that Cin7 brought under one brand. They have different APIs, different strengths, and different pricing. Core is often the better fit for product-based SMBs, while Omni leans towards larger, more channel-heavy operations. An integration built for one does not simply transfer to the other, so knowing which you are on is step one.
The built-in connector is fine for straightforward stock and order syncing. It starts to hurt when your business is not straightforward: customer-specific trade pricing, complex multi-location stock rules, several sales channels that must stay consistent, or bespoke workflows the connector does not support. At that point a custom integration does exactly what your business does instead of what the connector assumes.
By respecting Cin7's rate limits rather than ignoring them. That means batching updates, queueing work so a burst of orders does not overwhelm the API, retrying failures with backoff, and running reconciliation to confirm the storefront and Cin7 actually agree. A sync that looks fine in testing and drifts in production is almost always one that was written without regard for those limits.