Acumatica’s Product Configurator on a storefront: what it is and what reaching it costs

It is a rules engine for products that do not exist until somebody orders them, and it sits in Acumatica’s Manufacturing Management suite rather than in Distribution. Acumatica’s own datasheet, version 20231005, describes it as follows: "The rules-based product configurator provides flexibility to define attributes and formulas to create a unique bill of material and routing for finished goods with calculated costs and pricing."

Read that sentence carefully, because it tells you what the configurator is for. It produces a bill of material and a routing. It is a manufacturing artefact, and its job is to make a configured order buildable and costable. It is not a product-selector user interface for a website, and Acumatica does not claim it is.

Acumatica’s product page for the configurator lists what it does, and the list is worth having in front of you when somebody asks whether Acumatica "already has a configurator". As of the page read on 20 August 2026 it names configure-to-order and configure-to-stock, several price calculation methods including fixed prices, roll-up calculations for options and cost-based pricing, dimensional calculations and formulas for material requirements, look-up of previous customer configurations, formula validation against attribute values or quantities, non-stock items included alongside stock items, configured items on CRM opportunities, configured items copying from quotes to sales orders, and printing configuration details on invoices.

That is a serious configurator, and the last two items in that list are the ones a commerce project cares about most: a configured item can start life on a quote and copy into a sales order, which is exactly the path a quote-heavy manufacturer already uses off-line.

There is a named integration point and there is no native storefront experience. Both halves matter.

The named integration point is Configuration Endpoints. Acumatica’s datasheet states: "Extend Acumatica’s Product Configurator via web endpoints to leverage rules-based product options and values logic for configured orders from external apps like website storefronts, custom portals, or other applications". Acumatica names website storefronts explicitly, which is more than most ERP vendors do, and it means the configurator’s rules are reachable from outside Acumatica rather than locked to the Acumatica screen.

What is not there is anything that puts a configurator in front of a buyer. Acumatica’s Shopify and BigCommerce connectors synchronize stock, non-stock and template items, prices, customers, orders and inventory. We found no statement in Acumatica’s commerce material that a configured item can be presented, configured and priced by a buyer on a connected storefront, and we are not going to infer one. If a vendor tells you Acumatica’s configurator "works with Shopify out of the box", ask them to show you the buyer-facing screen and the round trip.

So the shape of the work is clear. The rules live in Acumatica. The buying experience is yours to build. The endpoints are how the two talk.

This is requirement 12 of the twelve, configurable and made-to-order products, and it is filed under breaks for a reason: the decision below is an architecture decision that a platform licence does not make for you.

Each of the three has a real business it suits. The wrong one is the one chosen because it was the demo you saw.

Three things, and naming them is more useful than filling the gaps with plausible sentences.

First, the licensing. Acumatica’s product page places the Product Configurator in Manufacturing Management, and the datasheet we read does not state an edition or module requirement. Whether the configurator and its endpoints are included in your licence is a question for your VAR, and it is worth asking before an architecture depends on it.

Second, the endpoint surface. Acumatica names Configuration Endpoints and describes their purpose, and we did not find public documentation of exactly which operations they expose, in particular whether a storefront can get a validated price for a partial configuration or only for a complete one. That distinction changes the buying experience substantially, because a price that appears only at the end is a very different page from a price that updates as the buyer chooses.

Third, connector behaviour. We found nothing stating how a configured line arrives through the Shopify or BigCommerce connectors, or whether it can. Prove that in a sandbox before you assume the order round trip is free.

If you need those three answered for your own setup rather than in general, that is the kind of thing the Celeste diagnostic is for, and it is also exactly the kind of thing to make a VAR answer in writing.

Frequently, and this is the disqualifier that should come before any configurator conversation. A large share of businesses that describe their products as configurable are selling a finite set of variants that happen to be described in configurator language by the sales team.

The test is arithmetic. Multiply out every combination your customers have actually ordered in the last two years. If that number is in the hundreds and the combinations are all valid, you have variants, not configurations, and Acumatica matrix items plus a variant-capable storefront will serve you at a fraction of the cost. Note the ceiling you meet on Shopify in that case, which is three product options per product, and read our page on matrix items and Shopify variants before choosing.

If the number is unbounded, if a dimension is a number rather than a choice, or if two options can be individually valid and jointly impossible, you have a configuration problem and no variant model will contain it. That is when the Product Configurator, or a dedicated CPQCPQ stands for configure, price, quote. It is software that walks a seller or a buyer through valid product configurations, works out the price, and produces a quote document. tool, starts earning its cost.