Product Configurator: Plugin, Software or Custom Build
A product configurator is not a dropdown. It is a rule set with pricing logic and a handover to the order. Whether Shopify variants, a WordPress plugin, rented software or a custom build fits depends on your rules and on where the truth about the price lives, not on a vendor's feature list.
Variants or add-ons are enough while every option stands alone and the price is a base price plus a surcharge. A plugin or rented software fits when rules and prices are manageable and come from one source. A custom build pays off only when rules, prices or production data must come from your own systems and no standard product models them. According to the Shopify Help Center, a product can have up to 2,048 variants and three options (as of October 2026).
Quick answer
Variants or add-ons are enough while every option stands alone and the price is a base price plus a surcharge. A plugin or rented software fits when rules and prices are manageable and come from one source. A custom build pays off only when rules, prices or production data must come from your own systems and no standard product models them. According to the Shopify Help Center, a product can have up to 2,048 variants and three options (as of October 2026).
What a configurator actually does
A dropdown lets the customer pick one value from a list: colour red or blue. A configurator connects four things: options, rules, pricing logic and the handover to the order. Rules define which combinations are possible and what follows from a choice, for example that one size excludes certain materials. The pricing logic turns the configuration into a price. The handover makes sure this exact configuration arrives in the cart, the quote or production without anyone retyping it. If one of the four is missing, it is a dropdown with more fields.
When Shopify variants and WooCommerce add-ons are enough
Shopify: variants and options
According to the Shopify Help Center, a product can have up to 2,048 variants and up to three options; anyone who needs more depends on an app from the Shopify App Store (as of October 2026). The variant limit was raised from 100 to 2,048 on 15 October 2025 (Shopify developer changelog). The note there matters: apps that do not use the GraphQL Product API may misbehave with more than 100 variants. The limit of three options stayed; a Shopify representative wrote on 17 October 2025 that only the variant limit is being raised for now. Sources that still talk about 100 variants are out of date.
WooCommerce: Product Add-ons
The WooCommerce extension Product Add-ons adds free or paid options to a product. According to the documentation, field types include multiple choice, checkboxes, short and long text, file upload, date and a customer-defined price. An option's surcharge can be a flat fee, depend on quantity, or be a percentage of the product price. Note: in cart and checkout the extension shows only flat fees by default; the other price types need a filter in code.
Where the limit is (our assessment)
Variants and add-ons are enough while every option stands alone and the price is a base price plus surcharges. Once a choice blocks other options, the price is calculated from dimensions, or the configuration has to reach production as a parts list, you are working against the tool. This is not a measured limit but our assessment of how these tools are built.
What a configurator plugin can do, and where it stops
Plugins depend on their shop system
One example from the documentation of the F12 Configurator plugin by Forge12: it requires WordPress 6.7 or newer, PHP 8.1 or newer and an active WooCommerce; without WooCommerce it does not run. Changing the shop system then affects the configurator too. For every plugin, check the requirements before investing time in setup.
A connector is not a configurator
The Shopify App Store has apps that only connect an existing configurator to the shop. The ASSEMBLIXX listing describes an app that links the ASSEMBLIXX configurator to the shop; without that configurator it does not work. The configuration then lands in Shopify's cart and checkout, but the configurator itself is a separate product. The listing also names data access the app requests, including customer, shop and staff data (retrieved on 21 October 2026). Such access should be agreed with data protection before installation.
Main features and price rules: what the plugin page lists
On the WordPress.org page of a WooCommerce configurator plugin (retrieved on 21 October 2026), templates and real-time price calculation are listed among the main features, conditional price rules among the “premium features” (as of October 2026). For every plugin, read under which features your rules are listed. If your price depends on conditions, that line decides.
What we have not tested
We have not tested any of these plugins or apps. The details come from documentation, listings and plugin pages, as noted above. We therefore do not recommend a specific product.
Renting configurator software: what happens to data and rules
Who owns the rules, and can you get them out?
Before signing, ask whether options, rules and prices can be exported in an open format and whether the export is complete. A product list without the rules between the products helps little when you switch.
Who owns models and media?
For 3D or image material: who holds the rights to models, textures and renderings, and in which format do you get them back?
Where do the prices come from?
Is the price source in the platform or in your ERP or price list? Is there an interface that fetches prices, or do you maintain them twice? Every double maintenance is a source of errors.
What happens when the contract ends?
Does the configurator keep running in the shop, is it switched off, can configurations already captured still be read? Clarify term, notice period and access to existing data. Hosting location and data processing should be agreed with data protection.
Questions, not findings
This list says nothing about how individual vendors behave. It is what we would clarify before a contract.
Custom build: where the effort sits and what the cost depends on
Capturing the rules
The rules are rarely complete in one place. They live in price lists, Excel files and in the heads of individual employees. Writing them down is work that arises in every case, whichever tool you choose later.
Data
Prices, dimensions, parts lists, availability: the configurator is only as correct as this data. Clarify who supplies it, in which format and how often it changes.
Interface and presentation
Selection, preview, messages for invalid combinations, use on a smartphone. Whether the preview is 2D or 3D drives the scope strongly; we have a separate article on the 3D product configurator.
Integrations
Shop, ERP, CRM, production: every interface is a sub-project with its own failure cases, for example when the ERP rejects a price the configurator calculated.
Operation and maintenance
New products, new options, changed prices, updates of shop and browsers. Who takes this over after launch belongs in the plan before the first line of code is written.
On cost: factors instead of sums
We do not name a sum. The price ranges we have seen come from vendors who sell an alternative themselves and state neither source nor method. Only the factors that make up the price are reliable: number of options and rules, 2D or 3D, number and type of integrations, hosting and maintenance, effort for data preparation. With a one-page rule sheet (see below), any quote can be checked against these factors.
Where the pricing logic lives
More important than the tool is the place where the truth about the price lives. There are four usual places; each brings its own maintenance task.
In the shop or plugin
Prices and surcharges are maintained in the shop or plugin configuration. Simple, but the prices then exist next to your price list or your ERP.
In the rented platform
The platform holds rules and prices. You need a reconciliation with your price source, otherwise there are two truths.
In the ERP or price list
The configurator fetches prices from your leading source on every calculation. This requires an interface but keeps the prices in one place.
In your own rules engine
Rules and prices live in your own system; the configurator is only its surface. This is a custom build, and the way to go when rules come from production data.
Every additional price source is an additional maintenance task. Decide first who changes the price, then the tool.
Decision path: variants, plugin, software or custom build
Does a choice change the price or the availability of other options? no → Shopify variants or WooCommerce add-ons yes ↓ Are rules and prices manageable and from one source? yes → Plugin or rented software (clarify data and exit questions) no ↓ Do rules or prices come from ERP, production or dimensions? yes → Custom build, or check software with an interface no → Write the rules down first
Example: price from manufacturing parameters instead of a price list
Starting point
At a window company, surveyors passed measurements back to the office, a salesperson calculated, and the customer was called back afterwards.
Implementation
In the project, the price calculator works with the manufacturing parameters of the plant, not with a price list. The price quoted therefore applies to exactly the version that is produced later.
Limit of the comparison
This is a tool for the surveyor on a tablet, not a public configurator on a website. It shows what a custom build means: the pricing logic depends on production data that a plugin does not know by itself. It does not show that your case needs the same.
Decision aid: seven questions before you choose
1. How many options and combinations are there?
Multiply the values of all options. Few combinations favour variants; many favour maintaining rules instead of individual variants.
2. Who maintains the rules?
A person from the business side or a developer? If only developers can change rules, every price change becomes a ticket.
3. Does the customer need 3D?
First check whether images or image layers are enough. 3D is a separate decision with its own cost; we have a separate article on it.
4. Which systems must be connected?
Shop, ERP, CRM, production: count the interfaces. Each one is its own effort.
5. Where does the data live?
With rented software the configuration runs on someone else's servers. Clarify hosting location and data processing with data protection.
6. By when should it be live?
A tight deadline favours a standard product, as long as the standard covers your rules. Check that against your rule sheet, not the brochure.
7. Who looks after it after launch?
Prices change, products are added, shop and plugin versions move on. Name in advance who takes this over.
When we advise against it
Small catalogue
A few products with few options do not need a configurator. Variants are enough.
Price independent of the options
If the chosen option affects neither the price nor the availability of other options, there is nothing to configure.
Rules that are not written down
Anyone who cannot name their rules is not buying a tool but postponing the problem. Clarify first, then choose.
Next step: write the rules down on one page
Write on one page: all options with their values, the rules of the form “if A, then not B”, the price formula with its source, who may change what, and where the finished configuration should go (cart, quote, production). If that does not work, that is already the result: you need clarity first, not a tool. If it works, quotes from plugin vendors, platforms and developers become comparable at last, and you can see whether variants or add-ons are enough.
Key takeaways
- A configurator connects options, rules, pricing logic and the handover to the order; a dropdown does not.
- Shopify variants (up to 2,048, three options, as of October 2026) and WooCommerce add-ons are the first check before you buy a plugin.
- What matters is where the truth about the price lives and who maintains it, not the name of the tool.
- With rented software, export, rights and exit need to be clarified before the contract.
- A custom build is justified by rules and data a standard product does not model, not by wish lists.
FAQ
Is there a product configurator for Shopify?
Which configurator fits WordPress and WooCommerce?
What does a product configurator cost?
How do I build a product configurator?
Plugin, software or custom build: which is better?
What happens to my rules if I change vendor?
Clarify the rules first, then choose the tool.
We go through with you where your pricing logic lives and whether variants, a plugin or a custom build fits your rules.
Start the process check