Getting Cin7 Core and Shopify talking to each other properly is one of the highest-leverage moves a growing ecommerce brand can make but only when the integration is configured correctly from the start.
Key Takeaways
Getting Cin7 Core and Shopify talking to each other properly is one of the highest-leverage moves a growing ecommerce brand can make but only when the integration is configured correctly from the start.
- Map your SKUs before you connect anything: Shopify allows duplicate SKUs; Cin7 Core does not. Resolving this before the integration goes live prevents the most common cause of sync failures.
- Decide on your fulfilment trigger: Whether orders push from Shopify to Cin7 Core on creation, payment, or fulfilment makes a significant operational difference that needs to be agreed upfront.
- Set a single inventory master: Designate Cin7 Core as the authoritative source for stock levels and push to Shopify, not the other way around. Bi-directional inventory sync almost always creates problems.
- Test with a live order in staging first: A small pilot using real product data exposes mapping gaps and tax configuration issues before they hit your actual customers.
- Plan for location complexity early: If you hold stock across multiple warehouses or use a 3PL, your Shopify location setup needs to reflect this before the integration is activated.
Done right, a Cin7 Core and Shopify integration removes the manual reconciliation work that quietly consumes hours every week, and gives you the real-time stock visibility that makes scaling across channels significantly less chaotic.
Connecting Cin7 Core to Shopify sounds straightforward on paper. In practice, it is one of those integrations that rewards careful preparation and punishes shortcuts.
For product-based businesses running their ecommerce through Shopify, Cin7 Core is typically the natural choice for inventory and order management as order volumes grow. The two platforms are built to work together, and when the integration is set up correctly, it genuinely transforms operations orders flow automatically from Shopify into Cin7 Core for picking, packing and fulfilment, and stock levels update in real time so you are never overselling or chasing phantom inventory figures.
But getting there requires more than clicking “connect” in the app settings. The businesses that struggle with this integration almost always hit the same handful of issues: SKU mismatches, tax configuration gaps, location mapping errors, and fulfilment workflow decisions that nobody made before the integration went live.
Understanding How the Cin7 Core and Shopify Integration Actually Works
Before configuring anything, it helps to understand what the integration actually does and, just as importantly, what it does not do. A lot of the problems we see during onboarding come from mismatched expectations about data flow direction.
What the Integration Covers
At its core, the Cin7 Core and Shopify integration handles four things: order sync, inventory sync, product sync, and fulfilment updates. Orders placed in Shopify are pushed into Cin7 Core as sales orders. Inventory levels adjusted in Cin7 Core through receipts, adjustments, or fulfilments are pushed back to Shopify to keep your storefront accurate. Product data can be managed in either platform and synced across. And when a Cin7 Core sales order is fulfilled, that fulfilment status and tracking information can be pushed back to Shopify to update the customer.
Each of these flows has its own configuration options, and the decisions you make about each one need to align with how your business actually operates.
Where the Integration Reaches Its Limits
The integration does not automatically resolve data conflicts. If a product exists in Shopify with a SKU that does not match the corresponding product in Cin7 Core, the sync will fail silently or create duplicate records neither of which you want to discover mid-peak-season.
It also does not replace the need for a well-structured Cin7 Core setup. If your inventory module is not configured correctly, locations not mapped, costing methods inconsistent, product variants not structured properly those issues will surface the moment Shopify orders start flowing through. A Cin7 Core system review before connecting Shopify can save a significant amount of remediation time later.
Preparing Your Systems Before You Connect
The most reliable integrations are built on clean foundations. Rushing to connect before your data is in order is the single most common reason businesses end up re-doing the integration three months later.
Audit Your Product Data in Both Platforms
Export your full product catalogue from both Shopify and Cin7 Core and compare them side by side. You are looking for SKU consistency above everything else. Every variant in Shopify needs a corresponding SKU in Cin7 Core that is identical same format, same capitalisation, no trailing spaces.
Shopify allows products to exist without SKUs. Cin7 Core does not operate that way. Any Shopify product variant without a SKU will either fail to sync or create a new product record in Cin7 Core, which then creates inventory tracking problems downstream.
Product titles and variant structures do not need to be identical between the two platforms, but they do need to be logically consistent. A product with three colour variants in Shopify should have the same three variants in Cin7 Core not two, not four.
Resolve Your Location Structure
If you fulfil from a single warehouse, your location setup is simple. If you hold stock in multiple locations a main warehouse, a 3PL partner, a retail location you need to decide how Shopify locations map to Cin7 Core bin locations or warehouses before connecting the integration.
Shopify’s multi-location inventory feature is often the source of stock discrepancy problems after integration. When Cin7 Core pushes a stock update, it needs to know which Shopify location to update. If that mapping is not explicit, updates either fail or go to the wrong location entirely.
Check Your Tax Configuration
Tax mismatches between Shopify and Cin7 Core are one of the most persistent causes of order sync failures. Shopify calculates and collects tax at checkout based on your Shopify tax settings. Cin7 Core needs its own tax rules configured correctly for the same products.
If a product in Cin7 Core has no tax rule assigned, or has a tax rule that conflicts with what Shopify is applying, the order either fails to import or imports with incorrect tax values. Given the compliance implications of incorrect tax records, this is worth resolving carefully before go-live rather than correcting retrospectively.
The same logic applies to your Xero connection if you are running a three-way integration. Misaligned tax codes between Cin7 Core and Xero compound quickly once order volumes increase a topic covered in more detail in our guide on connecting your warehouse and accounting in real time.
Step-by-Step: Configuring the Cin7 Core and Shopify Integration
Step 1: Connect the Integration from the Cin7 Core Side
The integration is managed from within Cin7 Core, not Shopify. Navigate to the Integrations section in Cin7 Core and locate the Shopify connector. You will need your Shopify store URL and will be prompted to authorise the connection via Shopify’s OAuth process.
Once authorised, the integration will attempt an initial product sync. Do not assume this sync has gone cleanly check it manually. Look at a sample of ten to fifteen products across different product types and variants to confirm that SKUs have matched correctly and that no duplicate product records have been created.
Step 2: Configure Order Import Settings
This is where most of the meaningful operational decisions happen. Cin7 Core gives you control over several key settings.
Order import trigger. You can choose to import Shopify orders when they are created, when payment is confirmed, or when they are marked as paid. For most ecommerce businesses, importing on payment confirmation is the right choice it prevents unpaid or abandoned orders from generating sales order records in Cin7 Core. If you offer payment terms or have a high proportion of orders paid on account, you may need a different approach.
Customer record handling. Cin7 Core can create new customer records for each Shopify order or map orders to a default guest customer record. For B2C businesses with high order volumes and one-time buyers, using a default customer record is often cleaner. For businesses with returning wholesale customers who also order through Shopify, mapping to individual customer records gives you better reporting visibility.
Product mapping behaviour. If a Shopify order contains a product that Cin7 Core cannot match to an existing SKU, you need to decide whether the integration should create a new product record automatically or flag the order for manual review. Auto-creation sounds efficient but creates catalogue sprawl quickly. Manual review adds a step but keeps your product data clean.
Step 3: Set Up Inventory Sync
Designate Cin7 Core as the inventory master. This is not a configuration toggle so much as a disciplinary principle your team needs to understand stock levels are managed in Cin7 Core and pushed to Shopify, not managed in Shopify and reflected back.
Set the sync frequency based on your order volumes and operational requirements. For most businesses, an hourly sync strikes the right balance between real-time accuracy and system load. If you run flash sales or operate in a category where stock accuracy is genuinely critical limited edition products, perishables, anything with tight quantities you may want a more frequent sync schedule and should test that it performs reliably under load.
Enable low stock alerts within Cin7 Core rather than relying on Shopify’s built-in notifications. Cin7 Core has a more complete picture of incoming stock, reserved quantities, and fulfilment pipeline, so its alerts are more accurate.
Step 4: Configure Fulfilment Feedback
When a sales order in Cin7 Core is fulfilled and dispatched, that information can be pushed back to Shopify to update the order status and send tracking information to the customer.
This closes the loop operationally and removes the need for anyone to manually update Shopify orders after dispatch.
Configure this carefully if you use a 3PL, as the fulfilment trigger in Cin7 Core needs to align with when your 3PL confirms despatch rather than when the pick is generated. Sending premature fulfilment notifications to customers is a customer experience problem that is easy to create and harder to undo.
For businesses using ShipTheory or a similar shipping platform connected to Cin7 Core, the fulfilment data flows through that integration first. Understanding the full order-to-despatch workflow before configuring this step is important our piece on syncing orders, inventory and finance using Cin7 Core integrations covers this workflow in more depth.
Step 5: Run a Full Pilot Before Going Live
Before processing real customer orders through the integration, run a controlled pilot. Place test orders in Shopify covering your main product types simple products, products with variants, any bundled or kit products and trace each one through the full workflow in Cin7 Core.
Check that the sales order has been created with the correct products, quantities, pricing, and customer information. Check that the inventory has been reserved correctly. Process the fulfilment and confirm that the tracking update pushes back to Shopify. If you are connected to Xero, check that the invoice has been generated correctly.
This testing phase is where mapping gaps and configuration errors surface in a controlled environment rather than in front of real customers. The data integration issues that commonly appear here are documented in our step-by-step fix guide for Cin7 Core implementation challenges.
Step 6: Brief Your Operations Team
An integration that nobody understands is an integration that gets worked around. Before going live, walk your fulfilment, customer service, and finance teams through how the new workflow operates.
Specifically, make sure everyone understands that Shopify is no longer where stock levels are managed, that orders should not be manually duplicated, and that any exception handling returns, cancellations, partial fulfilments follows a defined process rather than ad hoc edits in either platform.
Handling Common Integration Problems After Go-Live
Even well-configured integrations encounter issues as your catalogue and order patterns evolve. Knowing which problems to look for makes them much faster to resolve.
Inventory Discrepancies Between Shopify and Cin7 Core
If stock levels in Shopify and Cin7 Core drift apart over time, the most common cause is inventory adjustments being made directly in Shopify rather than in Cin7 Core. This bypasses the integration logic and creates a divergence that grows with each manual adjustment.
The fix is a combination of a one-time stock reconciliation and a team process change to ensure all inventory adjustments happen in Cin7 Core. Cin7 Core’s system optimisation service can help identify where adjustments are being made incorrectly and put the right process controls in place.
Orders Not Importing
When Shopify orders fail to appear in Cin7 Core, the cause is almost always one of three things: a SKU on the order that has no match in Cin7 Core, a tax configuration mismatch, or a Shopify location that is not mapped to a Cin7 Core location. Check the integration error log in Cin7 Core first it will flag which orders have failed and give a reason.
Shopify’s own integration documentation provides useful context on how their inventory and order APIs structure data, which can help when diagnosing mapping issues at the field level.
Duplicate Customer Records
If Cin7 Core is creating new customer records for returning Shopify customers rather than matching them to existing records, check whether your customer matching logic is set to email address. Name-based matching is unreliable because minor formatting differences between orders “Ltd” versus “Limited”, for example are treated as distinct entities.
Post-Integration Maintenance
A Cin7 Core and Shopify integration is not a set-and-forget configuration. As your product catalogue grows, as you add new sales channels, and as Shopify and Cin7 Core release updates, the integration needs periodic attention.
Review Mapping After Platform Updates
Both Shopify and Cin7 Core update their APIs and data structures regularly. After significant platform updates on either side, check that field mappings are still correct and that any custom fields you are using are still being passed through correctly. The official Cin7 Core release notes are worth monitoring so you are not caught out by changes.
Monitor Sync Errors Weekly
Build a habit of checking the integration error log at least once a week, even when operations feel smooth. Errors that go unnoticed for weeks compound into larger reconciliation problems. A quick review of failed syncs is far less disruptive than a quarterly stock reconciliation caused by months of ignored errors.
Expand the Integration as You Scale
The Cin7 Core and Shopify integration is a foundation, not a ceiling. As your business scales, there are natural points at which to extend it adding a second Shopify store for a new brand, connecting a B2B wholesale portal, bringing in a 3PL partner, or extending the integration to Xero for automated financial reporting. Each extension is easier when the core integration is clean and well-documented.
If you are uncertain whether your current setup is well-positioned for that kind of growth, a structured review of your integration architecture is often the most efficient starting point. Our integration service is designed exactly for that.
Conclusion
Integrating Cin7 Core with Shopify for automated order and inventory sync is one of the most impactful operational improvements a product-based ecommerce business can make but it requires careful preparation, deliberate configuration, and clear ownership of the data flows involved. Businesses that invest the time upfront to audit their product data, resolve their SKU inconsistencies, and define their fulfilment logic before connecting the integration avoid the problems that force others to rebuild it from scratch six months later.
The goal is an integration that runs quietly in the background orders flowing in, stock updating, fulfilments confirming while your team focuses on the work that actually moves the business forward. That outcome is entirely achievable with the right setup.
Frequently Asked Questions
- Can I connect multiple Shopify stores to a single Cin7 Core account?
Yes, Cin7 Core supports multiple Shopify connections from a single account, which is useful for businesses operating separate brands or regional storefronts. Each connection has its own configuration settings, so you can define different order import rules, inventory locations, and fulfilment workflows per store. The key consideration is keeping your product catalogue and SKU structure consistent across all connected stores to avoid mapping conflicts. - What happens to existing Shopify orders when I first connect the integration?
By default, the Cin7 Core and Shopify integration only imports orders created after the connection is activated. Historical orders are not imported retroactively. If you need historical order data in Cin7 Core for reporting purposes, this typically needs to be handled through a separate data migration process rather than the live integration. - How does the integration handle Shopify refunds and cancellations?
Refunds and cancellations initiated in Shopify can be configured to trigger corresponding actions in Cin7 Core cancelling the sales order and returning stock to inventory. The exact behaviour depends on how far the order has progressed through fulfilment. Orders that have already been picked or dispatched require a returns or credit note process in Cin7 Core rather than a simple cancellation, which needs to be defined as part of your integration setup. - Will the integration handle products with multiple variants correctly?
Yes, provided your Shopify variant SKUs match the corresponding product variants in Cin7 Core exactly. Each Shopify variant for example, a t-shirt in size M, colour blue needs its own unique SKU that matches a specific product variant in Cin7 Core. Problems arise when variants exist in one platform but not the other, or when SKU formats differ between platforms. - How long does a typical Cin7 Core and Shopify integration take to set up properly?
For a business with a clean product catalogue and straightforward fulfilment workflow, a basic integration can be configured and tested within a few days. For businesses with complex variant structures, multiple warehouse locations, 3PL involvement, or an existing Xero integration to maintain, the setup process typically takes one to three weeks to complete properly including testing, staff briefing, and the first post-go-live review. Rushing this timeline is one of the most reliable ways to create problems that take significantly longer to fix than the time you saved. If you want a structured approach to getting this right, our implementation service walks you through the full process.
