Acumatica Commerce Edition: the name is gone, and no connector is included

If you’re searching for it, you’re reading something old. Acumatica’s current industry editions are Distribution, Retail, Manufacturing, Construction, Professional Services and General Business. The ecommerce-oriented one is Retail Edition, described in the April 2026 licensing guide as suiting online retailers who need integrated ecommerce capabilities.

The rename happened in stages and it’s older than most of what ranks for the term. Acumatica’s own datasheet said Commerce Edition in January 2019. The April 2021 and April 2022 licensing guides say Retail-Commerce Edition. The guide preceding April 2024 already says Retail Edition. We couldn’t pin the exact release in which the middle name was dropped, because Acumatica keeps only two licensing guides on its agreements page.

The stale name persists partly because Acumatica hasn’t finished retiring it. The training course covering the Shopify connector is now titled V210 Retail Edition, its embedded recordings are still labelled V210 Commerce Edition, and the course URL still contains commerce-edition. If a VAR proposal in front of you says Commerce Edition, that’s a document that hasn’t been updated, not a product you can buy.

This is the part worth reading twice, because it’s the assumption that breaks budgets. The datasheets in the April 2026 licensing guide use a three-symbol legend: a tick means included, a plus means available, and a cross means not available. In the Retail Edition datasheet, every line in the Commerce block carries a plus at every tier. BigCommerce Integration, Shopify Integration, Amazon Integration, all of them.

A plus means it is on the price list, not in the box. So Retail Edition on its own gives you Financials, Inventory Control, Order Management and monitoring, and the connector that makes it a commerce system is a separate purchase.

Three further things sit behind their own line items and are unavailable at the entry tier. Shopify B2B Integration and BigCommerce B2B Integration are both crossed out at Essentials. So is Additional Site for Commerce Integration, which means an Essentials customer is hard-capped at one storefront: the guide states plainly that a commerce integration licence covers a single shopping site and additional licences are required for additional sites, and both the Shopify and Amazon store forms enforce it in software.

The customer portal is not included, and it’s not standalone. In Retail Edition the Customer Portal is a plus rather than a tick, it’s priced per portal, it covers one company and one portal URL, and the guide requires a valid CRM licence before you can buy one. CRM is itself a plus. So a buyer who plans to give customers a login through Acumatica is looking at two purchases they had not counted.

The other one is stranger, and worth knowing before an edition conversation. We compared the Retail and Distribution datasheets line by line. They differ in exactly three rows, all in the manufacturing block, and the Commerce block is identical between them. On the published entitlement grid, choosing Retail over Distribution doesn’t change your commerce entitlements at all. Whether it changes the price is not public, and that’s a fair question to put to your VAR.

One edition genuinely blocks commerce. General Business Edition shows a cross against every commerce line at every tier, so a buyer who lands there can’t add a connector later without changing edition.

Acumatica prices on Commercial Transaction Volume, and the definition is specific enough to matter. CTV is the single highest volume among eight document types in a month: sales orders, shipments, AR invoices, customer payments, purchase orders, purchase receipts, AP bills and AP payments. It’s the highest one, not the sum. For a business selling online, that’s almost always sales orders or shipments, so your ERP tier is set by your busiest storefront month.

The ladder runs 22 tiers, from 1,000 transactions a month to over a million. Exceeding your tier in any single month is described as an out-of-compliance situation that may require a mid-contract increase, which means a Black Friday peak is priced as a peak rather than averaged away. Features can be added at any time and removed only at renewal, so over-provisioning is sticky for a full term.

Separately from licensing there are hard system ceilings that a busy connector is the thing most likely to hit: web API connections, API requests per minute, import records per day, concurrency, parallelism and lines per transaction, all scaled by tier. Raising them means buying SaaS Reserved Resources, which is another paid add-on, is unavailable at Essentials, and is SaaS only. Acumatica also notes that any non-browser client consumes a web API connection, and that an external application which fails to log out keeps holding one.

So the escalators, in the order they usually bite: transaction tier, number of storefronts, connector add-ons for B2B and marketplace tax and POS, named users, and then reserved resources for throughput.

Acumatica publishes no guidance on this, and the absence is the finding. There’s no decision framework, no capability-limits matrix, and nothing saying consider a custom integration if. What Acumatica publishes instead is the Commerce Framework, a documented path for building your own connector against any system with a REST API, with classes for entities, mapping, buckets, configuration and an API client. The worked example in those docs uses a WooCommerce binding, which tells you how Acumatica sees anything outside its three native platforms.

There’s a middle path short of that. The Entities form supports custom field mapping and filtering per entity and per direction, including user-defined fields and attributes, so a field the standard mapping ignores can often be carried without writing a connector. It doesn’t apply to every entity, and the availability table is not something we could extract, so treat it as worth checking rather than assumed.

The practical read for a B2B seller is the one this Library keeps arriving at. The native connectors are good at catalogue, stock and orders, and the thing they consistently don’t carry is the effective price your ERP would calculate for a specific customer. That’s a question about pricing architecture rather than about editions, and it’s worth settling before the licence conversation, not after.