Cin7 Core B2B portal vs Shopify B2B: which one should a Cin7 wholesaler run?

The Cin7 Core B2B portal is an ordering surface that runs off Cin7 Core records directly. Cin7 describes it as enabling "your customers to browse and order from your catalog 24/7", and there is no connector, no sync schedule and no second copy of the catalogue to keep true. It ships more than most people expect: CSV quick order by product code and quantity, matrix bulk ordering across a product family, reorder from history, order history with carrier and tracking, invoice download as PDF, backorders, a minimum order value, sales rep ordering on behalf of a customer, and a custom domain pointed with a CNAME and an SSL certificate you supply.

Shopify B2B is a commerce platform with a B2B layer on top of the same store that serves the public. It models a company with company locations, assigns pricing catalogues to them, supports payment terms of net 7 through net 90, and gives you the whole Shopify content, search and theme stack. It knows nothing about Cin7 Core until something tells it.

That something is the part to understand before you compare features. Cin7 Core’s Shopify settings screen has a Sale price tier, and that nominated tier becomes the Shopify price when products are listed or updated. One tier, one price on the product. And Cin7 states that "product information must be manually updated to be exported to Shopify, it will never be updated automatically", which includes price. A Cin7 Core price change does not walk over to Shopify on its own, and nothing errors while it does not.

So the honest framing is not portal versus platform. It is: a surface that is always right about Cin7 Core and cannot be found, against a surface that can be found and is only as right as the last time somebody pushed it.

Every claim below is from Cin7 or Shopify documentation, or from SparkLayer’s Cin7 Core integration documentation, read on 20 August 2026. Where a row says the documentation does not cover something, that is an absence rather than a disproof, and it is a reason to test.

Neither column wins the table. Read the rows that match how you actually sell and ignore the rest.

When your buyers already know what they want. A portal serves a known buyer with a known catalogue very well, and it has nothing to offer a buyer who is still deciding. That single sentence resolves this comparison for most Cin7 Core wholesalers.

The structural advantage is the one nobody puts on a slide: the portal cannot show a price your order desk disagrees with, because it is reading the same records. Every Shopify path in this Library spends money defending that property, and the portal has it by construction. If your pricing is where your risk sits, that is worth more than a better product page.

Note also that several portals with different product lists is a real design rather than a workaround. If you sell into distinct trade segments with different catalogues, you get catalogue separation without building entitlement rules, at the cost of one add-on per portal. That scales with segments rather than with revenue, which suits some businesses and not others.

When a real share of your growth has to come from buyers who do not know you yet. That is the one thing the portal structurally cannot do, and no amount of settings work changes it, because the portal is built around invitation.

It is also the answer when the site has to sell rather than only take orders. Technical content, comparison pages, application guides, campaign landing pages and a search a buyer would recognize all live on the platform side. So does running one storefront for both trade and direct-to-consumer, which matters if you are currently maintaining two catalogues that have started producing two answers.

Go in knowing what you are taking on, because the Cin7 Core to Shopify path has specific, documented edges. Prices move only when somebody lists or updates products. Customer sync runs one way, Cin7 Core to Shopify, so amendments made in Shopify do not come back. SparkLayer notes that customer tags must match group names exactly and be comma separated with no spaces, that changing a customer’s email address "will create an additional customer in shopify", and that removing a customer by removing the tag does not disable the Shopify account. And your carefully named price tiers may arrive with their internal names: SparkLayer "does not support the custom names meaning they will show in sparklayer as sell price tier x".

None of those is a reason not to do it. All of them are reasons to budget an operator rather than only a build.

Three Cin7 sellers should not be choosing between these two, and one of them has a deadline.

If you are on Cin7 Omni rather than Cin7 Core, this comparison is the wrong one. Cin7’s end-of-life article lists Legacy B2B (v1) at 23 November 2026 and says "Legacy B2B uses technology that is no longer supported or compatible with the Cin7 Omni platform". That move is forced, and the replacement B2B online store is a different product from the Core portal, with Cin7 noting it is built for wholesale in particular so "you may find some of the B2C functionality you would expect missing from it". Deal with the date first.

If your customers need punchoutPunchout is a way for a buyer to shop on a supplier’s website from inside their own procurement system. The buyer clicks out, builds a cart, and the cart is returned to their system as a requisition for approval. into Ariba or Coupa, neither Cin7 help centre documents it and Shopify reaches it through third parties, so that requirement belongs at the top of the shortlist rather than at the bottom. And if your buyers inside one customer need genuinely different rights, with a clerk who orders and a manager who approves, neither option here models that: Shopify B2B has two permission levels and no approver, and the Cin7 portal documentation does not describe roles at all. Shopware B2B Components is the platform in this band with a documented order approval module.

Two things would change the comparison above. BigCommerce is the other native Cin7 Core destination, and it behaves differently enough to matter: Cin7 maps a regular price tier and a sale price tier, defaulting to tier 1 and tier 2, and states that "uploading customers from Cin7 Core to BigCommerce is not possible", so the customer direction reverses. And any change to Cin7 Core’s Shopify integration that made product updates automatic would remove the sharpest edge on the Shopify path, so re-check that sentence in Cin7’s documentation before you design a workaround for it.