5 signs your configurator is costing you sales

If you sell something configurable — furniture, signage, fixtures, made-to-order goods — your configurator is your most important salesperson. Most of them are quietly broken in ways that compound over time. Here's the diagnostic.

Sign #1 — quotes take more than a few seconds

The single biggest predictor of an underperforming configurator is quote latency. If a buyer changes a dimension or material and the price doesn't update now, you've already lost confidence. The cause is usually one of three things:

• Pricing rules live in a spreadsheet someone emails around. Every change requires republishing the configurator. Updates lag by weeks.
• The price calculation runs on the client with the rules visible in JavaScript. Cheaper to build, but every product change means a code deploy, and competitors can scrape your margins from view-source.
• The configurator calls a slow endpoint that hits your CMS or CRM synchronously on every keystroke. Fast for one user; cripples when traffic shows up.

The right architecture: a server-side pricing engine with rules stored in a database (or a structured config), called from the configurator over a fast API. Anything that has to talk to a CMS, CRM, or supplier system runs as a background sync — not on the hot path of a buyer typing dimensions.

Sign #2 — your B2B partners can't self-serve

If your dealers or installers email PDF quotes back and forth, your configurator is leaving money on the table. B2B buyers in made-to-order categories want the same self-service experience as retail — but with their own pricing, their own bulk discounts, their own quote-to-PO flow.

The fix is a B2B portal that uses the same configurator but with a logged-in role layer: dealer pricing, saved carts, PO numbers, downloadable quote PDFs. Built right, this collapses the sales cycle from weeks to days.

Sign #3 — the option tree branches and you can't explain why

Real-world products have conditional options: certain materials only come in certain finishes; certain dimensions are only available in certain hardware combinations; some configurations require lead-time disclaimers. If your configurator can't model these dependencies cleanly, two things happen:

1. You overpromise — buyers configure invalid SKUs, get them quoted, and you have to renegotiate after the order lands.
2. You underpromise — you hide options that are valid because the rules engine can't handle the conditional, and you lose those orders to a competitor.

Diagnostic: ask your configurator's vendor how they model "this option is only available when those two are selected." If the answer is "we use a flat option list and validate at checkout," that's the problem.

Sign #4 — your sales and production teams disagree on what got configured

When the configurator outputs a quote, that quote should match what your CRM shows the sales team, which should match what production builds. If the three views drift — different SKU codes, different dimension formats, different hardware names — you have a handoff problem, not a configurator problem. Sales promises one thing, production builds another, and nobody catches it until the customer opens the box.

The fix is structured: the configurator emits a canonical configuration object (JSON, version-stamped) on every quote; the CRM stores it as-is; production reads from the same object. Nobody re-keys anything.

Sign #5 — adding a new product takes a developer

The smell test for a configurator's long-term value: who can add a new variant or change a price? If the answer is "a developer pushes code," you bought the wrong thing. Configurators should expose a configuration interface — admin UI, structured spreadsheet, or something CMS-shaped — that the people who actually know the product can edit without breaking the system.

This is where most off-the-shelf configurators fail at scale: they ship with a flexible front-end and a rigid back-end. By month six, every change still requires a developer.

Build vs. buy: the simple decision matrix

By "buy", we mean a SaaS or licensed configurator product — Shopify configurator apps, WooCommerce plugins like WPC Product Bundles, or specialist platforms like Threekit, Doogma, Cylindo. You pay a recurring fee, configure it through a dashboard, and live with what the vendor's roadmap allows.

By "build" we mean a configurator written for your business, in your codebase — code you own, data shapes you control, integrations you can extend.

The honest call:

• Buy a SaaS configurator if your product has fewer than ~50 SKU permutations, your pricing rules fit on a single spreadsheet, and you sell only direct-to-consumer. The annual licence is cheaper than the salary it would take to build custom.
• Customise a plugin if 60–80% of your needs match an existing platform and the gap is plugin-shaped. WooCommerce + a small number of targeted plugins fits a lot of cases — you keep the storefront you have, layer in just the configurator behaviour you're missing.
• Build custom if you have B2B flows, real CRM integration, conditional pricing, or more than ~500 SKU permutations. SaaS will hit a wall around month nine — usually a feature their roadmap doesn't include and you can't change.

Questions to ask any vendor before you sign

Whether you're talking to us, a competitor, or a SaaS configurator, ask these. The answers tell you a lot.

1. "Where does the pricing logic live, and who can edit it?" If it's "our developers," you've signed up for a perpetual retainer. Look for an admin UI or structured config that an operations person can own.
2. "Can you show me the data object that flows from configurator → checkout → CRM → production?" A real implementation has a sample JSON they can email you. A hand-wavy answer means the integration is fragile.
3. "What happens when I add a new conditional option?" Some configurators handle this elegantly. Others require a code deploy.
4. "How do you handle B2B pricing?" Roles, login, bulk overrides — or "we'd have to build that."
5. "What's your performance budget for the price calculation?" Sub-200ms is normal. "It depends" or "we haven't measured" is a flag.
6. "What's the failure mode if your servers are down?" Does the configurator fall back to last-known-good prices, show a maintenance state, or just break?
7. "Who owns the source code on day 365?" The answer should be "you."

Where to start

If you read this and recognised three or more of the signs, you don't need a sales call yet — you need a diagnostic. Get a written audit, scope what's worth fixing in-house vs. rebuilding, and price the work before you commit. We do this as a fixed €1,500 audit and you keep the report regardless of whether we work together. Tell us what you're configuring and we'll send a calendar link.

Or if you'd rather see the kind of architecture we ship before talking, the configurators page walks through the engine, B2B flows, and integrations, and our open-source plugins (Headless Bridge, Simple Post Types) show how we think about ecom plumbing.

---

Etherlabz IT Solutions Pvt. Ltd. — registered in India, working with manufacturers and DTC brands across the EU and globally. We honor strict non-competes; we won't take a client who competes with one of yours in the same geography.