When to leave Cin7, and when to stay

Because the people who know Cin7 best are the ones who cannot publish it. A Cin7 implementation partner writing "here is when to leave Cin7" is writing itself out of a renewal, and a competitor writing it is writing an advertisement. So the question gets answered in private, badly, by whoever is in the room.

Acro Commerce does not sell Cin7 licences and does not sell the ERPs people move to. We get called when a storefront is not working, and a meaningful share of the time the honest finding is that the ERP is fine and the storefront is the problem. That makes this page cheap for us to write truthfully and expensive for almost everyone else.

Cin7 itself has been straightforward about the framing, which is worth saying out loud: it is comfortable being compared on the basis that it is less capable than a full ERP and does the job for many companies at a fraction of the cost. That is an accurate description of the product and an unusually honest position for a vendor. This page takes it at face value in both directions.

One naming rule before the signals, and it matters more here than anywhere. Cin7 is two products. Every signal below is about Cin7 Core, formerly DEAR. Cin7 Omni is a different system with different documentation, and on at least one of the four signals Omni is the answer rather than the problem.

Each signal below is checkable against a vendor document rather than against an opinion, and each has a different escape route. Read the last column first: two of the four are answered by Cin7 Omni without leaving Cin7 at all.

Every cell was read on 20 August 2026. Where the table says a product does not document something, that means we could not find a primary source, not that the capability is definitely absent.

Cin7 documents that "Cin7 Core lets you set up to 10 price points for each individual product". That is a hard published ceiling and it is the most common reason a growing wholesaler outgrows Cin7 Core without noticing.

The reason it goes unnoticed is that Cin7 Core gives you an escape hatch. You can set a custom product price on the customer record, and Cin7 documents that "the sale order price tier takes priority over the customer price tier", so the eleventh, twentieth and hundredth negotiated price all live somewhere. Internally that works. The problem appears at the storefront, because no native storefront integration is documented as carrying a Cin7 Core custom customer price, and the Shopify integration sends one chosen Sale price tier per store.

So the symptom is not an error message. It is a growing pile of accounts whose real price exists only inside Cin7 and inside your sales team’s heads, and a website that quietly shows all of them the wrong number. If your customer service team is correcting web order prices by hand, you have already crossed this line.

How to check it in ten minutes: pull your top-selling product, list every distinct price any customer paid for it in the last quarter, and count the distinct values. Eleven or more, and the ceiling is binding today.

Cin7 Core’s pricing documentation covers static prices, markup-calculated prices and append-calculated prices. It does not document a price that changes at a break quantity, and it does not document a price with a start and end date. Read 20 August 2026.

This is the signal that separates a wholesaler from a distributor, and it is a capability line rather than a size line. A 40-person company selling fasteners on a price that drops at 100, 500 and 2,500 units has a requirement Cin7 Core does not document, while a 300-person company selling finished goods on one negotiated price per account does not. Headcount tells you nothing here; the price book tells you everything.

Cin7 Omni is the answer worth pricing before you leave. Its help centre documents contract prices that can target all customers, a price tier, a customer group or an individual, with an Add Volume Break control taking a Price and a Minimum Quantity, multiple volume breaks per product, and a Start Date and End Date. That is precisely the capability Cin7 Core is missing, from the same vendor, without a data migration to a different company. Most people comparing Cin7 to NetSuite have never been shown this.

Two cautions if you take the Omni route. Cin7 Omni retires Legacy B2B, Products v1 and CRM v1 on 23 November 2026, so plan against the current B2B online store. And Cin7 Omni publishes no maximum number of price tiers, which is not the same as there being none, so get the number in writing if your design depends on it.

Cin7 publishes its ceilings, which is more than most vendors do and makes this the easiest signal to check. Standard at 349 US dollars a month allows five users, two ecommerce and app integrations and 6,000 sales orders a year. Pro at 599 allows ten users, four integrations and 24,000 orders. Advanced at 1,199 allows 15 users, six integrations and 120,000 orders. Read 20 August 2026.

One ceiling binding is a plan change and not a signal. Two binding at once, in the same year, usually means the shape of the business has changed rather than its size, and that is when the arithmetic on staying stops working. The classic pattern is a company adding a storefront and a 3PL while its order count crosses a tier, so it buys up to Advanced and still does not get the pricing depth it actually needed.

Count integrations honestly, because this is where teams undercount. The storefront is one. The 3PL is one. The tax engine, the shipping platform, the marketplace feed and the EDI broker are one each. Four is not many when you list them out.

The order-count ceiling is the one to forecast rather than measure, because a successful B2B storefront changes order shape as well as volume. Self-service tends to produce more, smaller orders than a phone-and-email sales desk does, so a business moving 30 per cent of its volume online can add order count without adding revenue. Model that before launch, not after.

This is the cleanest signal of the four, because it is the one place where Cin7 Core’s documentation is simply silent and the requirement is unambiguous.

Be precise about what is missing, because this claim is routinely overstated. Cin7 Core does document multicurrency: you set a currency on the customer record, and Cin7 Core "automatically obtains the conversion rate from openexchangerates.org", with manual override available. Selling in several currencies is not a reason to leave. What Cin7 Core does not document anywhere is a second legal entity, intercompany elimination or a consolidated statement across entities. Cin7 positions Omni for multi-entity companies, and NetSuite sells OneWorld on exactly this, advertising 27 languages, 190 currencies and "real-time consolidation at local, regional and global levels".

If you have acquired a company, opened a subsidiary or split a trading entity for tax reasons, and your finance team is now producing group numbers in a spreadsheet each month, you have left Cin7 Core’s documented territory. That is an accounting requirement rather than a commerce one, and it justifies a full ERP on its own terms without any reference to your website.

In three situations we see repeatedly, and in all three the ERP is being blamed for something it is not doing.

The first is when the storefront is the problem. A slow, ugly or unhelpful website is a website problem, and replacing the inventory system underneath it changes nothing about the reason buyers are still phoning their orders in. Cin7 Core plus a properly built storefront is a common architecture and it works.

The second is when the data is the problem. Missing product attributes, three spellings of the same customer name and stock counts nobody trusts do not improve during a migration; they arrive intact in a more expensive system, and now they are also blocking a go-live. Fix the data where it is, and if it is still wrong afterwards you have learned something useful and cheaply.

The third is when a process is the problem. A two-day quote turnaround caused by one person approving every price is not solved by NetSuite. It is solved by deciding who can approve what, which is free and takes a fortnight.

It is worth stating what Cin7 Core does well, because a fair disqualifier has to cut both ways. Unlimited inventory locations on every published plan is unusual at that price. Multicurrency selling is documented and included. Cin7 lists advanced manufacturing, production planning and bill of materials traceability under Core. The Shopify integration is first party with a documented settings surface. And it can be run by a small team without a systems integrator on retainer, which is a capability in its own right.

Run these in order. The first three are free and take an afternoon between them, and they routinely change the shortlist.

What you are looking for is a requirement that survives all three checks: a real capability gap, in a system of record, that a storefront cannot work around. Those are the only requirements worth paying an ERP licence for.