Acumatica vs Cin7 for B2B ecommerce: what each does to a storefront

One number, and it is published by Cin7. Cin7’s own help centre states that "Cin7 Core lets you set up to 10 price points for each individual product". Read the same article for quantity breaks, contract prices or prices with a start and end date and you will not find them; it documents static prices, markup-calculated prices and append-calculated prices, and nothing else. Read 20 August 2026.

For a distributor with quantity breaks that is close to disqualifying on its own, because the pricing you sell on does not exist in the system that is supposed to hold it. Acumatica has no equivalent ceiling. It carries price classes, sales price worksheets, quantity breaks and effective dates, and the hard part on Acumatica is not whether the price exists but whether the connector carries it to the storefront, which is a different and more solvable problem.

The second separator is what a storefront costs you in each system, and it runs the opposite way from what most buyers assume. Cin7 publishes a rate card. Acumatica publishes no dollar figures at all, and prices on transaction volume, so the storefront you are about to build is an input to your licence rather than a customer of it. Both of those are facts you can plan around. Neither is a defect. They are just two different bills arriving in two different shapes.

This is the row that ends most shortlists, so it goes first. Every cell below is from a vendor document read on 20 August 2026. Where a cell says the vendor does not document it, that means we could not find a primary source, not that the answer is definitely no.

Read the table with your own price book open. If you can count your distinct price bands per product on one hand and none of them depends on quantity, Cin7 Core holds your pricing and the rest of this page is about other things.

It adds to it, and Acumatica says so in its own Licensing Guide. This is sizing guidance rather than a warning, and it is the single most useful thing an Acumatica buyer can know before a commerce project starts, because almost nobody models it.

Acumatica’s April 2026 Licensing Guide defines the Monthly Commercial Transaction Volume as "the single highest volume of transactions for any of the following eight (8) transaction types: sales orders (of any order type); shipments; AR invoices; customer payments; purchase orders; purchase receipts; AP bills; and AP payments". It then states that "ERP transactions will also result from automated schedules that execute batch processes and/or REST APIs that create, update or delete transactions". Your storefront writes sales orders. Those are countable.

The consequence is stated plainly in the same document: "Exceeding the maximum number for CTVs in any given month in your subscription year creates an out-of-compliance situation, which may require you to increase your Transaction Tier level mid-contract". The tiers in that guide run from S1 at 1,000 monthly transactions to P2 at one million, with P3 above that. So a storefront that doubles your order count is a licensing event, and the honest way to treat it is as a line in the business case rather than as a surprise in month four.

There is a second ceiling and it is the one that bites a real-time storefront. The same guide publishes Web API request maximums per product: 50 requests a minute on Essentials, 100 on Select, 150 on Prime and 300 on Enterprise, with API concurrency maximum queue sizes of five, ten, 20 and 40. Acumatica’s own advice is that "the performance of external integrations requiring an elevated level of activity can be improved by submitting fewer requests when the system is busy, by adding one or more Processing Nodes, or by using SaaS Reserved Resources".

An Acumatica community thread from April 2023 titled "eCommerce and API Limits" shows what that feels like from the inside. The poster describes a 100 calls per minute limit visible on their licence, calls "getting denied or throttled", and difficulty supporting real-time pricing queries that need several calls per item. The reply, from a community MVP rather than from Acumatica staff, was that "L Series tier will give you 6 concurrent web service API requests". The tier names in that thread predate the current guide, so treat it as an illustration of the failure mode and take your actual numbers from the April 2026 guide and your own licence screen.

On cost and on knowing in advance what that cost is. Neither of those is a consolation prize for a company whose pricing genuinely fits in ten bands.

Cin7 publishes a rate card: Standard at 349 US dollars a month with five users and two integrations, Pro at 599 with ten users and four integrations, Advanced at 1,199 with 15 users and six integrations, all with unlimited inventory locations. Acumatica publishes no dollar figures and quotes through a partner, which means a procurement process, a discovery call and a proposal before you know the number. If your board wants a budget line this quarter, one of those two vendors can give you one today.

The implementation gap is larger than the licence gap and it points the same way. Acumatica is a full ERP with a general ledger, and putting one in is a finance project with a cutover, a chart of accounts and a parallel run. Cin7 Core sits on top of Xero or QuickBooks Online and does inventory, purchasing and order management, which is a smaller thing to install and a smaller thing to get wrong.

Cin7 Core is also the right answer for a business that has not yet earned its complexity. Ten price points, one base currency with per-customer currencies, unlimited locations and a documented Shopify integration will run a wholesale operation of real size. The failure mode we see is not companies buying Cin7 Core too early, it is companies staying on it two years after their price book stopped fitting.

Five checks, in this order, each answerable from your own systems rather than from a demo. The first one that fails settles it, so you can stop early.

If you get to the end without a failure, Cin7 Core is very likely the right system and the interesting question moves to the storefront rather than the ERP. If you fail at step one or two, no amount of storefront cleverness rescues it, because the price you need to show does not exist in the system you are asking to show it.

When the thing that hurts is the storefront and not the ERP. We see this misdiagnosis often enough to name it: a wholesale business whose Cin7 Core data is fine decides the fix is a bigger ERP, spends a year on a finance migration, and arrives at the same storefront problem with a larger monthly bill and a tired team.

Acumatica earns its cost when the ERP itself is the constraint, which usually means pricing depth, manufacturing, multi-entity consolidation or a transaction volume Cin7’s plan ceilings will not carry. If none of those is true, the honest recommendation is to keep Cin7 Core, spend the money on the storefront and the integration layer, and revisit the ERP when a real constraint appears rather than an imagined one.

One more honest limit on our own confidence. Cin7’s published documentation is thinner than Acumatica’s in several places that matter here, and a gap in a help centre is not proof of a missing feature. Where this page says Cin7 Core does not document something, that is exactly what it means. Confirm anything decisive with Cin7 in writing before you design around it.