Acumatica’s customer self-service portal vs a B2B storefront: when is the portal enough?

More than it used to, and the update is recent enough that a lot of advice about it is out of date. Acumatica’s community FAQ for the Modern Customer Portal states that it "is officially GA in 26R1", after a managed availability period during 2025 R2 when it was explicitly "not supported in production environments". The same FAQ lists the five modules it ships with: account history, B2B ordering, pay invoices, case management, and a corporate FAQ or wiki page.

Acumatica’s own product page describes the ordering side in storefront language. Customers can "browse your product catalog with real-time inventory levels", "add items to their cart, adjust quantities, and complete checkout", with payment by card or by "placing orders on account", and they can "view order details, repeat previous purchases, or cancel open orders". The 2026 R1 release page puts it plainly: business customers "place B2B orders safely and securely from the reimagined customer self-service portal with access to inventory levels".

The account servicing side is the part the portal has always been strongest at, and it is the part a bought storefront makes you build. Customers can "view account balances, unapplied payments, overdue amounts, open invoices", "pay single or multiple invoices, downloading statements", access historical documents, and store cards for future transactions. There is case management with severity, status tracking, file uploads and reopening, plus a place to publish instructions and reference material.

The FAQ also lists what is not yet supported in the new portal, which is a useful signal about how new it is: customizable dashboards, pivot tables, ARM reports, the report launcher and viewer, business scenarios, the wiki editor and viewer, user interface customization for new screens, and mobile application support.

The differences are not a feature count. They are two answers to one question: is this software for the customers you have, or for the customers you want? Every row below follows from that.

One row deserves reading twice. The portal reads Acumatica directly, so there is no connector, no sync schedule and no second copy of your catalogue. That removes the entire category of problem the rest of this Library exists to document, and it is worth more than most people credit.

We build commerce for a living and we would still tell a good number of Acumatica distributors to turn the portal on and spend the project money elsewhere. Taking phone and email order entry away from your inside sales team is most of the value a first B2B channel delivers, and the portal does that without a connector, without a sync schedule, and without a second version of your catalogue drifting away from the first.

There is a second argument that gets underrated. Because the portal reads Acumatica directly, it cannot show a price your order desk disagrees with. Every storefront project in this Library spends real money defending that property. The portal has it for free, and it is the property your sales team cares about more than anything on a design mockup.

If you recognize your business in the list below, buy the portal, run it for a year, and let the data from that year write your storefront business case. It is a better brief than any consultant will write for you.

The triggers below are the ones we see, and they share a shape. Almost every one of them is about somebody other than the buyer you already know: a new customer, a second person at an existing customer, a procurement system that will never visit your site, or a marketing team that needs a page the portal has nowhere to put.

One trigger on its own is usually survivable. Two together is where the workarounds start costing more than a platform would have, and where the portal quietly turns into the thing everyone blames.

A note on maturity rather than capability. The Modern Customer Portal reached general availability in 2026 R1, and Acumatica’s own FAQ lists a set of features not yet supported in it, including user interface customization for new screens and mobile application support. That is normal for a first general release. It is also a reason to test the portal against your own requirements rather than against a datasheet, and to ask your VAR what the upgrade path looks like from the classic portal.

Yes, and for a lot of distributors it is the best answer rather than a compromise. The portal serves the accounts you already have: invoices, statements, cases, reordering and account-level ordering, all reading Acumatica directly. The storefront does the selling: discovery, content, new accounts, and the parts of the catalogue you are happy to publish.

Two rules make that shape work, and skipping either one is how it goes wrong. First, decide which channel owns the order for a given customer, and say it out loud to your sales team, because a customer with two ways to buy will use whichever one gave them a better price last time. Second, decide what a customer sees in each place. If the storefront shows list price and the portal shows their contract price, a buyer will eventually notice, and the conversation that follows is about trust rather than about software.

The failure mode to avoid is running both without deciding either. That produces a portal nobody was told about, a storefront the sales team works around, and an adoption problem that gets diagnosed as a user experience issue for two years.

Four things, stated plainly, because on a page that tells some readers to buy less software the edges matter more than usual.

If any of these decide your project, prove them in your own tenant before you commit either way. That is exactly the kind of question the Celeste diagnostic is built to surface before you have signed something.