Which Cin7 are you on, and which integration does this page describe?
This page describes Cin7 Core’s native Shopify integration. Cin7 Core is the product that used to be DEAR Systems, documented at help.core.cin7.com. Cin7 Omni is a separate product with its own help centre, its own Shopify integration and its own vocabulary, where stock lives in branches that you link to Shopify locations and route orders from. If you are on Omni, roughly half of what follows describes a system you do not run.
Getting this wrong is expensive rather than embarrassing. The parts that differ between Core and Omni are exactly the parts a B2B seller cares about: which price reaches the storefront, how stock is split across locations, and what the built-in B2B module can do. Cin7 Omni also retires its Legacy B2B module on 23 November 2026, which changes the calculus for an Omni seller considering Shopify B2B.
The integration itself is first-party, built and documented by Cin7, with no separate connector licence and no middleware in the default path. That is a genuine advantage over the ERP connectors elsewhere in this Library. The limits below are all limits of scope, not of reliability.
Checked against: Cin7 Core: Introduction to Shopify, read 20 August 2026, Cin7 Omni: Shopify settings, read 20 August 2026, Cin7: Core or Omni, which one is right for your business
What actually syncs between Cin7 Core and Shopify B2B, mechanic by mechanic?
The same eight mechanics as the Acumatica pages, so you can compare pairings directly. Cin7 documents this integration unusually well, and most rows below are Cin7’s own sentences rather than our inference.
One structural rule explains half the table: stock moves by itself and product data does not. Anyone who assumes a single rule covers both will be wrong about half their catalogue within a month of launch.
| Criterion | What actually crosses | Direction | Trigger, and the catch |
|---|---|---|---|
| Products and variantsOn a 5,000 item catalogue this is the row that decides who on your team owns product data, and how their week looks. | Products and variants, downloaded from Shopify or uploaded from Cin7 Core, matched on SKU. | Both ways, chosen per action. | Manual only. Cin7 states product information "must be manually updated to be exported to Shopify, it will never be updated automatically", controlled by the Load Products and Publish Product options. Importing from Shopify also requires SKUs to already exist: "It is not possible to auto-generate SKUs in Cin7 Core for Shopify products without an SKU." |
| PricingA Shopify product carries one price, so everyone who is not handled by a Shopify B2B catalogue sees the same band. | One nominated price tier becomes the Shopify price. Cin7 Core itself holds up to 10 price points per product plus custom prices per customer. | Cin7 Core to Shopify. | Only when you list or update a product, on the same manual trigger as product data. Custom prices, which Cin7 says "take precedence over regular product prices set by price tiers" inside Cin7 Core, are not documented as reaching Shopify at all. |
| InventoryThis is the strongest row in the table. A clearly stated The source of truth is the system that gets to be right when two systems disagree. For price, stock and customer terms in an ERP-run business, that is almost always the ERP. is worth more than a feature list. | Available quantity, computed for each Shopify location from the Cin7 Core locations that product is mapped to. | One way, and Cin7 says so: "stock levels are always pushed from Cin7 Core to Shopify, never from Shopify to Cin7 Core." | Automatic. Cin7 pushes stock "every time there is a change in the product stock level in Cin7 Core", plus a manual update button. Finished-goods availability for manufactured items ignores raw material and component availability, so it can overstate. |
| Customers and companiesIf your B2B model needs multiple buyers under one account with different permissions, that lives entirely in Shopify B2B. | Shopify customers, created or matched in Cin7 Core when orders are captured. Shopify B2B companies and company locations are not a Cin7 Core concept. | Shopify to Cin7 Core, one-directional. | Automatically when capturing unconsolidated orders, and manually on demand. Changing a customer’s email creates a duplicate Shopify account that has to be disabled by hand, and removing tags does not disable the account. |
| Orders | Shopify orders download into Cin7 Core as sales, with fulfilment status and tracking shared back when Ship is authorized. | Shopify to Cin7 Core, fulfilment both ways. | Automatic when an order is created, fulfilled, paid, cancelled or deleted, plus an automatic sweep at midnight daily. For a B2B site Cin7 recommends capturing at Created, because "a Shopify site which is more B2B focused may not collect payment at the time of sale". |
| Credit and termsIf a credit hold has to block a checkout, that is development on the Shopify side reading a value nobody is enforcing. | Nothing enforceable. Credit limits reach Shopify as metafields, which are visible to code and not enforced at checkout. | Cin7 Core to Shopify, as data. | On customer sync. Shopify B2B also has no native credit limit enforcement and no dunning of its own, so nothing on either side stops an over-limit order. |
| TaxThis is the one row on this page we would not put in a proposal without checking it in your own account first. | The tax Shopify charged arrives with the downloaded order. | Shopify to Cin7 Core. | At order download. We could not find a Cin7 Core help-centre statement documenting whether Cin7 Core ever recalculates that figure, so we are calling this unverified rather than guessing. Test it with one taxable order before go-live. |
| Returns and refunds | Shopify cancellations and returns are captured. Cin7 Core-side activity does not travel back: "Cancellations, refunds, or restocks in Cin7 Core are not sent to Shopify." | Shopify to Cin7 Core only. | At the Shopify event. Cin7 creates the credit note from a Shopify restock "only if you haven’t done it beforehand manually", which is how duplicate restock transactions appear. Shopify order editing is not supported at all, because it changes an order without creating a new order or credit note. |
Checked against: Cin7 Core: Shopify Integration FAQs, read 20 August 2026, Cin7 Core: Introduction to Shopify, read 20 August 2026, Cin7 Core: Stock levels in Shopify, Cin7 Core: Pricing and price tiers, Cin7 Core: How can I use different prices for a customer, SparkLayer documentation for Cin7 Core, read 20 August 2026, Shopify B2B limitations, LiquidLab, read 20 August 2026
If Cin7 Core only sends one price tier, where does contract pricing come from?
This is the question that decides the pairing, so answer it before anything else. Cin7 Core sends one nominated tier as the Shopify price. Every negotiated number beyond that has to be created somewhere else, and there are three places it can come from.
The first is Shopify B2B catalogues. You restructure Cin7 Core price tiers as Shopify catalogues assigned to companies, and accept that the catalogue is now maintained in Shopify rather than in Cin7 Core. Shopify allows up to three active catalogues across all B2B markets on Basic, Grow and Advanced, and an unlimited number on Plus, so the tier count decides the plan.
The second is a third-party B2B app such as SparkLayer, which publishes its own Cin7 Core documentation and reads Cin7 Core price tiers and customer records directly. That is a real path used by real Cin7 sellers, and it moves the pricing logic into a third vendor you now depend on.
The third is Middleware is a layer of software that sits between the ERP and the storefront, translating and enforcing rules that neither system holds on its own. It can be a hosted integration platform or a custom service. you own, pushing resolved prices into Shopify B2B catalogues on a schedule or answering price requests at runtime. It costs the most and it is the only option that carries Cin7 Core custom prices faithfully, because those prices exist per customer and per product and nothing native moves them.
Checked against: Cin7 Core: Pricing and price tiers, Shopify Help Centre: customizing B2B pricing using catalogs, read 20 August 2026, SparkLayer documentation for Cin7 Core, read 20 August 2026
What is not covered by the Cin7 Core Shopify integration at all?
Seven gaps with no setting behind them. Each is either a manual process you staff or a piece of development you buy.
The first two are the ones that shape day-to-day work rather than the launch. A catalogue that only updates when somebody clicks Publish Product needs an owner and a routine, and an integration that cannot accept a Shopify order edit needs a returns policy that uses credit notes instead.
Automatic product and price updates. Every catalogue change needs Load Products or Publish Product to be run.
Shopify order editing, which Cin7 states is not supported because it changes an order without creating a new order or credit note.
Per-customer custom prices reaching the storefront. They take precedence inside Cin7 Core and are not documented as syncing.
Credit limit enforcement. The limit arrives in Shopify as a metafield, visible and not enforced.
Shipment confirmation emails, which Cin7 describes as "not currently available in Cin7 Core".
Cin7 Core-side cancellations, refunds and restocks reaching Shopify. That direction does not exist.
Shopify B2B companies, locations, catalogues and payment terms as Cin7 Core objects. Your B2B account structure lives in Shopify.
Checked against: Cin7 Core: Shopify Integration FAQs, read 20 August 2026, Cin7 Core: Introduction to Shopify, read 20 August 2026
Who should not put Shopify B2B on Cin7 Core?
Shopify B2B on Cin7 Core is a strong pairing for a wholesaler with tiered pricing, a catalogue that changes at a human pace, and a business that already treats Cin7 Core as the stock authority. Five situations where it will fight you.
The first one is the common one. A distributor with hundreds of individually negotiated prices is asking a ten-tier structure and a one-price-per-product storefront to carry something neither was built for.
You hold negotiated prices per account rather than tiers. Cin7 Core custom prices do not reach Shopify, and 10 price points is the tier ceiling anyway.
Your catalogue changes daily and nobody can own a manual publish routine. Nothing about product data moves on its own here.
Exchanges and order edits are a normal part of your service. Shopify order editing is not supported by Cin7 Core, at all.
Finance needs credit limits enforced at checkout rather than reported afterwards. Neither system enforces them.
You manufacture to order and expect the storefront to reflect what you can actually build. Cin7 Core availability for manufactured items is drawn from finished-goods stock and ignores raw materials.
Checked against: Cin7 Core: Pricing and price tiers, Cin7 Core: Shopify Integration FAQs, read 20 August 2026
What should you test before you commit?
Five checks, all doable in a trial or a sandbox store, and all cheaper than finding out in month three.
Change a price on one product in Cin7 Core and wait. If it has not reached Shopify, you have confirmed the manual publish rule on your own account.
Pick a customer with a negotiated custom price in Cin7 Core, sign in as them on the storefront, and see which number appears.
Adjust stock in a secondary Cin7 Core location and watch which Shopify location moves, and by how much.
Place a Shopify B2B order with a payment term, then look at how it lands in Cin7 Core and whether it is treated as paid.
Refund one order in Shopify with a restock, then check Cin7 Core for a single credit note rather than two.
The wider picture
This page answers one narrow question. Acro Commerce covers the strategy around it.
Common questions
- Does Cin7 Core sync customer-specific prices to Shopify?
- No. Cin7 Core’s Shopify integration sends one nominated price tier as the Shopify price when you list or update a product. Cin7 Core does hold custom prices per customer, and says they "take precedence over regular product prices set by price tiers" inside Cin7 Core, but no Cin7 documentation describes them syncing to Shopify. Per-customer pricing on the storefront comes from Shopify B2B catalogues, a third-party app such as SparkLayer, or middleware you own.
- Does Cin7 Core update Shopify products automatically?
- No, and this is the most consequential sentence in Cin7’s own documentation: product information "must be manually updated to be exported to Shopify, it will never be updated automatically". The Load Products and Publish Product controls decide which way an edit moves, for individual products or in bulk. Stock is the exception, and it does push automatically whenever a Cin7 Core stock level changes.
- Which system owns stock, Cin7 Core or Shopify?
- Cin7 Core, unambiguously. Cin7 states that "stock levels are always pushed from Cin7 Core to Shopify, never from Shopify to Cin7 Core", and computes each Shopify location’s quantity from the Cin7 Core locations that product is mapped to. Two exceptions are worth knowing: availability for manufactured items is drawn from finished-goods stock and ignores raw materials, and buffer inventory deliberately publishes a number that is not the real one.
- Can we edit a Shopify order after Cin7 Core has downloaded it?
- Cin7 Core does not support Shopify order editing at all, and gives a clear reason: editing an order in Shopify changes it without creating a new order or a credit note, which Cin7 Core has nowhere to record. Plan your exchange and partial-cancellation processes around cancelling and re-ordering, or around credit notes raised in Cin7 Core. Note that Cin7 Core cancellations, refunds and restocks are not sent back to Shopify.
- Does this page apply to Cin7 Omni?
- No. Cin7 Omni is a different product with its own Shopify integration, documented separately, where branches are linked to Shopify locations and branch routing decides which one fulfils. Omni also ships EDI and 3PL connections natively and retires its Legacy B2B module on 23 November 2026. If you are on Omni, read the Core versus Omni page first and treat every claim on this page as unconfirmed for your system.
- Do we still need the Cin7 Core B2B portal if we build on Shopify B2B?
- Not usually, and running both means maintaining two catalogues and two customer experiences. The Cin7 Core B2B portal is genuinely capable for a wholesaler whose buyers know their part numbers, with CSV quick order, matrix bulk ordering and reorder from history, and it needs no integration work. Shopify B2B is the answer when you need a public storefront, richer merchandising, or company structures the portal does not model.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.