What pricing does Cin7 Core actually hold?
Cin7 Core has three separate pricing mechanisms and they stack, which matters because only one of them travels to a storefront natively.
The first is price tiers. Cin7 states that Cin7 Core “lets you set up to 10 price points for each individual product”, tier names are editable under Settings, then General Settings, then Price Tier Names, and tier amounts can be set manually or calculated with markup rules that follow supplier pricing. A customer is assigned a tier, and “the sale order price tier takes priority over the customer price tier”.
The second is custom pricing. Cin7 says “you can set custom prices for the products in your inventory for selected customers” and that “custom prices take precedence over regular product prices set by price tiers”. This is where real Contract pricing is a price that applies to one customer or one group of customers rather than to everyone. In B2B it is normal for the same product to have a different price for every account on the book. usually lives for a Cin7 Core seller, because a negotiated number for one account does not fit inside a ten-band tier structure.
The third is discounts, applied by product, by customer group or by individual customer, including a blanket percentage discount across everything a customer buys.
Checked against: Cin7 Core: Pricing and price tiers, Cin7 Core: How can I use different prices for a customer
Which of those prices reaches Shopify natively?
One tier. Cin7 Core’s Shopify settings screen has a Sale price tier, and Cin7 documents that tier as the default price used when products are downloaded from and updated in Shopify. You can change which tier a product uses when you list or update it, but a Shopify product carries one price at a time, so the storefront shows one band to everybody who is not being handled by something else.
The second half of the answer is the part that surprises people more. Cin7 Core states that “product information must be manually updated to be exported to Shopify, it will never be updated automatically”. Price is part of that product information. So a Cin7 Core price change does not walk over to Shopify on its own: somebody lists or updates the product, individually or in bulk, up to 50,000 at a time.
That is a different failure mode from a connector that syncs the wrong price. Here the storefront simply keeps showing yesterday’s price until a human pushes it, and nothing errors while it does.
Cin7 Core does hold customer records and does sync customers to Shopify. SparkLayer, which builds on that sync, documents it as “the integration is one way (cin7 core to shopify)”, with “all customer data managed via cin7 and any amends made directly in shopify will not synchronise back to cin7”. Knowing which side owns the customer is half of knowing which side owns the price.
Checked against: Cin7 Core: Shopify settings, Cin7 Core: List or update products in Shopify, Cin7 Core: Introduction to Shopify, SparkLayer: Cin7 Core integration docs
What makes the trip from Cin7 Core to a storefront, and what does not?
One row per pricing mechanism, with the destination platform named, because the answer differs between Shopify and BigCommerce. All of it read on 20 August 2026.
| Criterion | Native Shopify integration | Native BigCommerce integration |
|---|---|---|
| Price tier for everyone | Yes. One nominated Sale price tier becomes the Shopify price on list or update. | Yes, two of them. Cin7 maps a regular price tier and a sale price tier to BigCommerce, defaulting to tier 1 and tier 2. |
| A second and third price band | Not natively. A Shopify product holds one price per market, so extra bands need Shopify B2B catalogues or an app. | Only as the sale price. The third band onwards has no documented native destination. |
| Per-customer custom priceThis is the row that decides most Cin7 B2B projects. If your real prices are custom prices, the native integration is not going to carry them. | No documented native path. Cin7 Core’s Shopify settings describe a tier, not a customer-resolved price. | No documented native path. |
| Customer discount percentages | Not documented as a synced field. Treat it as untested rather than as confirmed missing. | Not documented as a synced field. |
| Automatic price refresh | No. “Product information must be manually updated to be exported to Shopify, it will never be updated automatically.” | Cin7 documents category and product family option changes as blocked after listing because of BigCommerce API limits, and does not document automatic price refresh either. |
| Customers, so a price can be aimed at oneThe direction reverses between the two platforms. Any design that assumes Cin7 Core seeds your BigCommerce customer list is wrong from the first sprint. | One way, Cin7 Core to Shopify, per SparkLayer’s integration documentation. | The other way. Cin7 states “uploading customers from Cin7 Core to BigCommerce is not possible”; customers come from BigCommerce into Cin7 Core. |
Checked against: Cin7 Core: Shopify settings, Cin7 Core: List or update products in Shopify, Cin7 Core: BigCommerce, SparkLayer: Cin7 Core integration docs
What does a third-party B2B app change, and what does it not?
SparkLayer is the best-documented route from Cin7 Core price lists to a Shopify storefront, and its own documentation is unusually honest about the edges, which is why we cite it. It describes displaying “customer-specific B2B pricing on your existing store using the price lists you’ve already set up in Cin7 Core”, keeping customer records in sync, and sending B2B orders back into Cin7 Core.
Two limits from that same documentation are worth knowing before you assume the problem is solved. First, on tiers: “in cin7, you can utilise up to 10 price lists”, and although you can rename them in Cin7 Core, SparkLayer “does not support the custom names meaning they will show in sparklayer as sell price tier x”. Your carefully named Gold and National Account tiers arrive with their internal names.
Second, on customers. Customer tags must match group names exactly and be comma separated with no spaces. Changing a customer’s email address “will create an additional customer in shopify”, changing a default contact means you “manually disable the account in shopify”, and “a customer that is removed by removing the tag will not be disabled within shopify”. Addresses are one way from Cin7 Core into Shopify, and SparkLayer recommends not letting buyers edit addresses because new ones will not appear in Cin7.
Credit is a display, not a control. SparkLayer maps credit limit “to the customer account through a shopify metafield called payment on account”. A metafield shows a number on a page. It does not stop an order, so if you need a A credit limit is the amount a customer may owe at any one time. Buying on account, often on thirty-day terms, is standard in B2B and the limit is enforced by the ERP. enforced at checkout, that is still yours to build.
Checked against: SparkLayer: Cin7 Core integration docs, SparkLayer: Cin7 integration overview
What are the four routes to customer pricing on Cin7, and what does each cost?
Nobody gets everything Cin7 Core’s pricing engine can express onto a public storefront. The decision is which property you give up: the number of bands, the freshness, the per-customer precision, or the maintenance you take on.
| Criterion | How it works | What it costs you |
|---|---|---|
| 1. Keep contract accounts on the Cin7 Core B2B portal | Trade accounts order through the portal, where they see their Cin7 Core tier, while the public storefront sells at one tier. | You are running two channels with two price answers, and you own the rule for which customer belongs where. Cheap, honest, and it works until a contract customer finds the storefront. |
| 2. Model tiers as Shopify B2B catalogues | Turn Cin7 Core tiers into Shopify B2B catalogues attached to companies, maintained by an app or by hand. | Shopify B2B requires the plan that carries it, and catalogue counts are capped by plan. Nothing in Cin7 Core’s documentation creates or maintains Shopify catalogues, so the maintenance is somebody’s job by name. |
| 3. Use a documented B2B app such as SparkLayer | The app reads Cin7 Core price lists and customer tags and renders the right price to the logged-in buyer. | Up to 10 price lists, internal tier names on display, and a set of customer-sync edges you have to operate around, including duplicate Shopify customers when an email changes. |
| 4. Resolve the price at runtime through middleware | The storefront asks a service you own for this customer’s price, and that service reads Cin7 Core, including custom prices. | Budget it as development, not configuration. You take a dependency on Cin7 Core’s API on your most performance-sensitive pages, and Cin7 Core throttles: its own Shopify FAQ documents the error “you may have reached the API calls limit”. |
Checked against: Cin7 Core: Shopify Integration FAQs, SparkLayer: Cin7 Core integration docs, Cin7 Core: Set up B2B Portal
What could we not verify about Cin7 pricing?
Four things, stated plainly, because a page that pretends to certainty it does not have is worth less than one that marks its own edges.
If any of these four decide your project, they are the first thing to prove in a sandbox rather than the last. That is exactly the kind of question the Celeste diagnostic is built to put in front of you before you sign.
Whether a Cin7 Core custom price for one customer renders for that customer in the Cin7 Core B2B portal. The pricing article says custom prices take precedence in Cin7 Core; the portal settings article does not address it.
Whether quantity or volume price breaks exist in Cin7 Core in a form a storefront can read. The pricing and price tiers article does not mention volume discounts at all.
Whether Cin7 Omni has a price tier ceiling. Its Price and cost tiers article states no maximum, which is not the same as stating there is none.
How often anything actually syncs. SparkLayer says its automatic customer sync runs every hour, Cin7 Omni’s Shopify settings offer order download every two hours, and Cin7 Core product data does not sync automatically at all. There is no single Cin7 sync interval to quote.
Checked against: Cin7 Core: Pricing and price tiers, Cin7 Omni: Price and cost tiers, Cin7 Omni: Shopify settings
The wider picture
This page answers one narrow question. Acro Commerce covers the strategy around it.
Common questions
- How many price tiers does Cin7 Core support?
- Ten. Cin7’s documentation states that Cin7 Core “lets you set up to 10 price points for each individual product”, and those tiers can be renamed under Settings, then General Settings, then Price Tier Names. Beyond tiers, Cin7 Core also supports custom prices for selected customers, which take precedence over tier prices, so the ten-band ceiling limits your published bands rather than your total number of negotiated prices.
- Does Cin7 Core push price changes to Shopify automatically?
- No. Cin7 states that “product information must be manually updated to be exported to Shopify, it will never be updated automatically”. Price sits inside that product information, so a price change in Cin7 Core stays in Cin7 Core until somebody lists or updates the product, individually or in bulk. Nothing errors in the meantime, which is why this one usually surfaces as a customer complaint rather than as an alert.
- Why do my Cin7 price tier names show as “sell price tier 3” on the storefront?
- Because the downstream system is reading Cin7 Core’s internal tier naming rather than the display names you set. SparkLayer’s Cin7 Core documentation says exactly this: you can rename tiers in Cin7, but SparkLayer “does not support the custom names meaning they will show in sparklayer as sell price tier x”. Plan your tier numbering so the internal names are at least tolerable, because the friendly name may not travel.
- Does Cin7 Core sync credit limits to Shopify?
- Through SparkLayer, a credit limit is “assigned to the customer account through a shopify metafield called payment on account”. A metafield is stored data you can display, so the buyer can see their limit, and nothing about that stops an order that would exceed it. If you need the limit enforced at checkout, treat enforcement as custom work and not as a synced field.
- How many price tiers reach BigCommerce from Cin7 Core?
- Two. Cin7’s BigCommerce article describes mapping a regular price tier and a sale price tier to BigCommerce, defaulting to Cin7 Core price tier 1 and price tier 2. The other eight tiers have no documented native destination. The same article also states that “uploading customers from Cin7 Core to BigCommerce is not possible”, so customer records flow the opposite way from the Shopify integration.
Last updated 2026-08-20. Facts on this page last checked against source 2026-08-20.