Cin7 to Shopify Integration

Stock shows available on Shopify. A customer orders it. Only then does anyone find out it sold out in the warehouse two days ago, because Cin7 and Shopify weren't syncing on a schedule tight enough to catch it. A working Shopify Cin7 integration is supposed to prevent exactly that, and when it's configured correctly, it does. When it isn't, the sync becomes the thing everyone blames instead of the setup underneath it.

This guide covers how the integration actually works, what data moves between the two systems, how to set it up, and what changes once a Shopify store is running B2B or multi-warehouse operations.

Yes, though the setup depends on which Cin7 product you're running. Cin7 operates two distinct systems: Cin7 Core (formerly DEAR Systems) and Cin7 Omni. Both connect to Shopify, but through separate apps with separate configuration, Cin7 Core Shopify integration and Cin7 Omni Shopify integration are not interchangeable setups, and mixing up which documentation or which app applies to your account is a common early mistake.

Confirm which Cin7 product your business runs before starting setup. The rest of this guide covers the general integration pattern both share, with notes on where Core and Omni diverge.

Once connected, both Cin7 Core and Cin7 Omni sync these core data types with Shopify:

• Inventory levels. Stock counts sync from Cin7 to Shopify so the storefront reflects real availability, and Shopify order activity reduces Cin7 stock in return.
• Orders. Shopify orders download into Cin7 for picking, packing, invoicing, and fulfillment tracking.
• Product catalog. Products, SKUs, and pricing sync between the two systems, avoiding duplicate manual entry.
• Customer records. Customer data from Shopify orders downloads into Cin7 for order history and reporting.
• Order status updates. As orders move through fulfillment in Cin7, status changes can sync back to Shopify and, from there, to the customer.

What typically needs extra configuration: multi-warehouse stock allocation, customer-specific B2B pricing, and Shopify order types like draft orders that don't move through a standard checkout.

The mechanics differ slightly depending on which Cin7 product is connected.

• Cin7 Core. Connects to Shopify through its own integration module, configured from within Cin7 Core's Integrations menu. Sync runs on a schedule you configure, covering inventory, orders, and product data.
• Cin7 Omni. Connects through the Cin7 Omni Shopify app, available in the Shopify App Store, with its own settings panel for sync configuration inside Cin7 Omni.

Both are two-way integrations: inventory and product changes in Cin7 push to Shopify, and order activity in Shopify pushes back to Cin7. The sync isn't instantaneous by default in either system. It runs on a scheduled interval, which is worth understanding clearly before assuming stock counts update the moment something sells.

1. Confirm your Cin7 product. Check whether your account runs Cin7 Core or Cin7 Omni before following setup steps, since the two use different apps and settings locations.
2. Connect your Shopify store. From Cin7's Integrations menu, select Shopify and authenticate your store, granting Cin7 access to orders, inventory, and product data.
3. Configure your sync settings. Set how often inventory syncs, and whether historical orders download or only new activity going forward.
4. Map your product catalog. Match Shopify products to their Cin7 counterparts, typically by SKU, so orders and stock updates apply to the correct item on both sides.
5. Set warehouse and location rules, if applicable. For businesses running more than one warehouse in Cin7, confirm which location's stock feeds Shopify's available inventory.
6. Run a test order. Place one order and confirm it downloads into Cin7 correctly, right customer, right product, right quantity, before turning on full sync.
7. Monitor the first sync cycles closely. Stock mismatches, duplicate orders, and mapping errors tend to surface within the first few days. Check both systems' logs until the pattern looks clean.

It's a fair question to ask directly rather than sidestep. Search around this integration and you'll find real frustration from some operators, sync delays, orders that download incorrectly, stock counts that drift out of alignment. That frustration is real, and it's worth taking seriously rather than waving away with a generic reassurance.

What the complaints usually trace back to, in practice, is configuration rather than a fundamentally broken connection. A sync interval set too wide for order volume, a multi-warehouse setup that was never explicitly configured for how stock should route, or an integration that was connected without a documented testing phase before go-live. Cin7's own troubleshooting documentation covers a real, recurring list of these issues, which is itself a signal that the integration works as designed when it's configured deliberately, and causes real problems when it isn't.

The honest takeaway: this integration can run reliably, but it's not a connect-and-forget setup for a business with real order volume or more than one warehouse. Treating it that way is where the frustration tends to start.

• Stock levels drifting out of sync. Usually caused by a sync interval that's too slow for order volume, or by inventory adjustments made directly in Cin7 without triggering a push to Shopify. Fix: tighten the sync interval to match order velocity and confirm manual adjustments are configured to sync automatically.

• Duplicate order downloads. Happens when the sync retries after a connectivity gap without checking whether the order already downloaded. Fix: review the order log for duplicates regularly during the first weeks and confirm your Cin7 product's duplicate-handling setting is enabled.

• Orders stuck in a pending or unprocessed state. Often tied to a product mapping gap, an order containing a SKU that doesn't exist in Cin7 will stall rather than download cleanly. Fix: audit product mapping before go-live rather than discovering the gap mid-order.

• Multi-warehouse stock showing incorrectly. A standard setup often doesn't route Shopify to the correct warehouse automatically, or combines stock across locations without checking which one can actually fulfill a given order. Fix: this needs explicit configuration, covered in the next section.

Cin7's own documentation and most setup guides, including the steps above, are written for a standard retail operation: one warehouse, one price per product, orders through a normal checkout. If that's your business, the guide above is what you need.

If your Shopify store runs wholesale accounts, multiple warehouses, or both, a few real gaps show up.

Multi-warehouse allocation needs explicit setup, not a default assumption. Cin7 supports multiple locations natively, but a standard Shopify integration isn't automatically configured to show combined, accurate availability across every warehouse, or to route an order to the location that can actually fulfill it fastest. Left unconfigured, this is exactly the kind of gap that produces the stock-mismatch complaints covered above.

A rep-built order isn't a checkout event, and the integration needs to know that. When a sales rep assembles a draft order in Shopify, revises it, and only then sends it for payment, Cin7's default sync logic can miss it entirely, since it's watching for a completed checkout, not a multi-step revision that finishes somewhere else in the process.

Whatever price the customer actually agreed to has to be the price that lands in Cin7. Shopify B2B accounts pay negotiated, not catalog, pricing, and if that negotiated number doesn't carry through to the order record on the Cin7 side, every margin report built on top of it is wrong from the start.

None of this means Cin7 is the wrong system for a B2B or multi-warehouse operation. It means the default setup needs real configuration on top of it, the same conclusion Cin7's own troubleshooting documentation points to, just applied specifically to B2B order types their standard guide doesn't cover.

Full and honest: platforms like NetSuite bundle their own storefront, SuiteCommerce, directly on top of the ERP, so inventory, orders, and commerce all run through one system without a Cin7-to-Shopify style connection to maintain. That's a legitimate option for some operations, and it's worth stating before making the case for keeping them separate.

Architecture and system of record. A bundled ERP-commerce platform makes the ERP the system of record for everything, including the storefront itself. Shopify plus Cin7 splits that: Cin7 stays the system of record for inventory and warehouse operations, Shopify owns the buyer-facing transaction layer, and the two sync rather than share one database. That split adds a sync layer to maintain, but it also means neither system compromises its core strength to also handle the other's job.

ERP integration approach. An all-in-one platform's commerce module is built by the ERP vendor specifically for that ERP, so most of the integration risk this guide has spent its length covering, sync timing, draft orders, multi-warehouse routing, disappears by design. What replaces it is a different constraint: the storefront itself inherits the ERP platform's development framework and release cycle instead of Shopify's.

B2B feature depth and developer dependency. Cin7 plus Shopify gets B2B ordering depth from Shopify's native company accounts and price lists, while Cin7 handles inventory and warehouse complexity a general-purpose ERP's built-in commerce module doesn't always match feature for feature. The tradeoff is a smaller, more specialized developer pool for deep customization of an all-in-one platform's storefront, versus Shopify's considerably larger Liquid and app-development talent pool.

Which approach wins depends on whether an operation is already committed to a specific ERP's commerce module, or values storefront speed and design flexibility enough to maintain a sync layer between two best-of-breed systems.

For a single-warehouse, standard retail setup, connecting Cin7 to Shopify through the native integration is a reasonable DIY project. That's an honest answer, not a lead-in to a pitch.

The calculation changes with real order volume, multiple warehouses, or B2B order types. At that point, the default sync settings stop matching how the business actually operates, and that gap is where sync problems tend to originate, not from the platforms being fundamentally incompatible.

Uncap has been a Shopify Platinum Partner since 2013, with over 380 B2B commerce projects built for manufacturers, distributors, and wholesalers. Cin7, Fishbowl, a full ERP, a CRM, the specific system on the other end of the connection changes less than most people expect. The sync itself is rarely what breaks. What breaks is the configuration work nobody scoped: multi-location inventory routing, wholesale pricing that has to carry through correctly, and order types that don't fit a standard checkout, all of which need deliberate setup the moment an operation outgrows a single warehouse.

Uncap Connect treats inventory and warehouse system connections as part of one architecture rather than a default app install, so multi-warehouse allocation, wholesale pricing, and draft orders sync correctly from the start. If you want to think through the right setup before committing to an integration path, the Blueprint process is where that conversation starts.

A properly configured Shopify Cin7 sync keeps stock accurate and orders flowing without manual double-checking. Getting multi-warehouse allocation, wholesale pricing, and draft orders right is where most standard setups need real configuration for growing B2B operations.

Book a demo to see how Uncap approaches Shopify systems integration for manufacturers, distributors, and wholesalers.