Why you need a PIM before building a configurator

Why you need a PIM before building a configurator

PIM and CPQ, running on the same data

Wabric PIM and CPQ share 1 data model, so update a product once and every new quote, BOM, drawing and BIM file uses it.

See the PIM platform →

A product configurator looks simple. Pick a size, pick a finish, get a price.

But it can only be as accurate as the data behind it. When that data lives in spreadsheets and an engineer's memory, the configurator goes wrong exactly where customers notice: the price, the fit and the drawing.

That's why a configurator needs a PIM (product information management) system behind it: a single, structured source for every product, rule and price.

Key Takeaways

  • A product configurator is only as accurate as its data. A PIM system is where that data and its rules live.
  • Spreadsheets can run a first version. They break once you have hundreds of variants, several price lists and more than 1 person editing.
  • Set up the PIM first, then build the configurator on top of it.
  • For engineered products, the PIM has to hold rules, not just attributes: what fits with what, which sizes are allowed and how the price is calculated.
  • With the data in place, every configuration can produce a quote, a bill of materials, drawings and a BIM object from the same source.

How Does a Product Configurator Work?

A configurator is the front end: the screen where a customer, a dealer or your own sales team builds a product. It often runs on your own website as a white label product configurator. ETS Nord's configurator selects ventilation silencers, Solarstone's plans solar roofs and R-Fix's builds glass railings.

Behind every configurator sit 3 kinds of data:

  • Product data: components, dimensions, materials, finishes, images and certificates.
  • Rules: what fits with what, which sizes are allowed and which options exclude each other.
  • Pricing logic: base prices, surcharges, discounts and price lists per market or partner.

If any of the 3 is wrong or out of date, the configurator either blocks valid orders or lets impossible ones through.

Where Does Configurator Data Come From?

It should come from a PIM system. In practice, at most manufacturers we meet, it comes from Excel files, ERP fields, PDFs, email threads and a few people's heads.

A PIM replaces that patchwork with a single structured database. Each product, rule and price exists once, with version history and user roles. The configurator reads from the PIM through an API, so a change made once shows up everywhere the data is used: the configurator, the website, product sheets and the ERP.

New to PIM? Our guide explains what PIM is and how manufacturers use it.

What Breaks When a Configurator Runs on Spreadsheets?

A first version can run on spreadsheets. It holds until something changes:

  • A price changes. The master file gets updated while someone keeps quoting from last month's copy.
  • The range grows. Every new option multiplies the combinations, and the rules live in formulas only 1 person understands.
  • More people edit. Sales, engineering and product management overwrite each other, with no record of who changed what.
  • You add channels. The webshop, the dealer portal and the ERP all need the same data, so it gets copied by hand.

Every copy is another chance for a wrong price or an impossible combination to reach a customer, or the factory. It's the same reason manual quoting breaks down for engineered products.

Krah Pipes lived this. Every sales manager priced from their own spreadsheet, and a project could bounce up to 16 times over email before the production details were final. Since moving to a Wabric configurator, Krah has 100% pricing consistency, and sales and partners handle up to 80% of technical drawings and revisions themselves.

PIM or Configurator: Which Comes First?

PIM first, for 3 reasons:

  • The configurator sits on the data model. Options, rules and price logic are defined in the PIM. Build the configurator on messy data and you'll rebuild it once the data is fixed.
  • The PIM pays off before the configurator goes live. Clean, structured data already feeds your website, product sheets, price lists and ERP.
  • It's the groundwork for the Digital Product Passport. Under the EU's Ecodesign for Sustainable Products Regulation, in force since July 2024, product groups are being phased into mandatory digital product records. That's a data project first, and structured PIM data is where it starts.

You can build a configurator without a PIM. It just won't stay accurate for long.

What Can a PIM-Driven Configurator Produce?

When the rules live in the PIM, a confirmed configuration is more than a price. This is where a configurator becomes CPQ (configure, price, quote). From the same data, it can produce:

  • a quote with an itemised bill of materials
  • production-ready drawings for the factory
  • a BIM object (IFC file) that architects and engineers place straight into their Revit or Archicad model
  • an order that flows into your ERP

Change a price, a size limit or a compatibility rule once in the PIM, and every one of those outputs follows.

The BIM object matters more than it looks. Architects specify products inside their models, and if your product isn't there as a correct, project-specific object at that moment, a competitor's is.

Here's how automated CAD and BIM drawings work.

Innore's balcony railing configurator generates the BOM, price, drawings and ERP order for every railing automatically. That saves their sales team 80 hours a month.

Which PIM Works Best with a Configurator?

One that stores rules, not just attributes. Most PIM systems were built for catalogues: descriptions, images and attributes for webshops and marketplaces. A configurator for engineered products needs more:

  • Rules and dependencies: compatibility between components, constraints and options that exclude each other.
  • Parametric products: custom dimensions within limits, not only fixed SKUs.
  • Pricing logic: formulas, surcharges and partner price lists that sync with your ERP.
  • Draft, publish and version control: prepare changes, review them, publish to every channel at once and roll back if needed.
  • Roles and permissions: sales, engineering and product management each edit what they own.
  • Multiple languages: the same product in every market language, without a copy per language.
  • APIs: the configurator, webshop, partner portal and ERP all read from the same source.

Catalogue PIMs like Akeneo organise product data well, but they aren't built to turn a configuration into a BOM, a drawing or a BIM file.

Comparing options? Our best PIM software for manufacturing guide puts the main platforms side by side, and Wabric vs Akeneo compares the 2 head to head. For the configurator side, see our best CPQ software for manufacturing guide.

How Wabric Connects PIM and the Configurator

In Wabric, the PIM and the CPQ aren't 2 products joined by an integration. They share 1 data model. The PIM holds products, rules and prices, and the configurator turns each configured product into a quote, BOM, drawings and BIM object from that same model. It also feeds your webshop and the partner portal, where distributors configure products with their own pricing.

Floorin shows the PIM side. Their product data used to sit in Excel, links and email, so every proposal was rebuilt by hand. Now thousands of products live in 1 source, synced with their Odoo ERP twice a day, and proposals come out priced and visual.

Wabric PIM, launched as Wenture PIM, was named Innovation Project of the Year in 2024.

You can set up Wabric PIM yourself, though most teams ask us to help with the data model. Most of our team are engineers, and we've modelled pipes, railings, roofs, doors and modular rooms before.

Summary

A configurator is the part customers see. The PIM is the part that makes it right.

Put products, rules and prices into a PIM first, and the configurator, the quote, the factory drawings and the architect's BIM model all read from the same source. If your product data still lives in spreadsheets, that's your first project, not the configurator.

Frequently Asked Questions

Technically yes, using spreadsheets or other data systems, but it isn't practical at any real scale. A PIM system keeps product data centralized and synced automatically, so configurator updates don't require manual re-entry every time something changes.

A PIM system manages the back-end product data, dimensions, prices, and compatibility rules. The configurator is the front-end interface customers use to select and visualize products, pulling its data from the PIM through an API.

PIM first is generally the better order. It gets the product database into a secure, organized system, and having that structure in place is what makes an accurate configurator possible to build on top of it.

Yes, when the two are connected through an API. A price or spec change made in the PIM syncs automatically to the website, configurator, and any other connected systems, without manual re-entry.

It needs 3 kinds of data: product data (components, dimensions, materials, finishes, images, certificates), rules (compatibility, allowed sizes, options that exclude each other) and pricing logic (base prices, surcharges, discounts, price lists per market or partner).

A catalogue PIM can't: it stores descriptions, images and attributes. A PIM that holds parametric rules can feed a configurator that generates production drawings and BIM objects (IFC files) for every configuration. In Wabric, PIM and CPQ share 1 data model, so the quote, BOM, drawings and BIM object all come from the same source.

Ready to see how Wabric solves this?

30 minutes with someone who understands complex product manufacturing. No pressure, no script.

Talk with Sales →