Commerce on Cin7: what it runs, what it doesn't, and how a storefront connects

Cin7 holds products, stock, and orders, and a storefront connects to it through one of Cin7's own native connectors to Shopify, BigCommerce, Adobe Commerce, WooCommerce, or Amazon. Cin7 is the right backbone when you sell product across channels and need one accurate stock and order position without a full ERP's financial and manufacturing depth. It's the wrong backbone when you need that depth, for example revenue recognition rules or consolidation across legal entities.

Not in the sense most people mean. Cin7 Core is an inventory management platform and Cin7 Omni adds order management, and both pair with an accounting system such as Xero or QuickBooks Online for the financial ledger. Cin7 markets Core as an ERP for small business, which is fair for operations, but it does not replace the finance and manufacturing depth of a system like NetSuite.

Core is the inventory platform most product sellers use, and it does a lot without configuration. Omni is more configurable and aimed at higher-volume multichannel retail and wholesale, with deeper EDI and 3PL support. In our own capability grading Omni covers meaningfully more ground than Core, and the gap is widest in exactly those areas.

On Cin7 Core, yes. Each connected store consumes one integration add-on on your subscription, with two included on the Standard plan, four on Pro, and six on Advanced, and more available to purchase. Check that count before scoping a multi-storefront build, because the licence count is a real line item, not a technical detail.

An accounting ledger, for a start: Cin7 pairs with Xero or QuickBooks Online instead of replacing them, so invoicing, tax, and reporting live there. The storefront is its own platform, and if you recognize revenue over time you'll need billing software such as Chargebee or Stripe Billing, because that isn't something Cin7 or a small-business ledger does well. Third-party logistics and EDI connections sit alongside too. Cin7 is the operational core, not the whole stack.

When the commerce scope crosses into territory the standard connector does not carry cleanly: multi-storefront brands that need a common business-rule layer across DTC, wholesale, and marketplace channels; multi-tier customer-specific pricing with effective dates; configurator-to-quote workflows; real-time inventory orchestration across multiple warehouses; or multi-currency, multi-language storefronts that read live Cin7 truth. The pattern Acro Commerce recommends is that the Cin7 partner keeps the customer relationship and the inventory scope, and the architecture partner takes the commerce build. Both sides bill for what they do best.

Cin7 fits product-making manufacturers with multi-channel sales (DTC plus wholesale, often with marketplaces) better than it fits traditional discrete or process manufacturers with deep ERP needs. Cin7 Core suits brands in the eight-figure range running multiple channels through inventory orchestration; Cin7 Omni suits mid-market manufacturers with EDI and 3PL complexity. Manufacturers with traditional ERP scope (multi-entity accounting, deep MRP, complex production scheduling) typically use Cin7 alongside an ERP rather than instead of one.

A focused B2B or DTC build on top of a stable Cin7 deployment typically runs three to seven months from discovery to first production release, with phased releases continuing after launch. Single-channel native-connector builds run on the shorter end; multi-channel decoupled builds with custom business-rule layers run on the longer end. The cheapest accelerator is discovery: a few weeks of structured work that prevents the integration from being designed against a moving target.

Often, yes. If the storefront already carries the buyer experience your customers expect and the integration to your current inventory platform is brittle, the highest-leverage work is on the integration layer rather than a replatform. Discovery should always test the keep-and-improve path before recommending replacement, because the cheapest successful project is the one that does not rebuild what already works.

A B2B portal on Cin7 is the layer where Cin7’s inventory and order truth meets the buyer, covering account access, order history, reorder, customer-specific pricing, and quote-to-cash flows. Four portal patterns show up in production: the Cin7 B2B portal itself; a storefront platform’s native B2B layer (Shopify B2B Edition, BigCommerce B2B Edition) connected through the standard Cin7 integration; a decoupled portal that runs as a separate front end against Cin7 APIs; and a hybrid pattern. The right one depends on the depth of B2B features the buyer expects and the team capacity available to maintain the experience.