A configurable product can’t be represented by one fixed list of parts. It may support thousands or millions of valid combinations across models, applications, regions, performance requirements, and factories. Every customer order uses only a small portion of those possibilities. Each department, from sales to production, have their own Bill of Materials (BOM) with that information translated in a language most relevant to their functions.  

A 150% Bill of Materials provides a structured way to represent that variability. It contains the complete range of approved components, options, and variants for a product family. When used in conjunction with configuration logic, manufacturers can determine which possibilities belong in a specific customer solution based on their application requirements.  

The concept becomes more useful when it extends across engineering and manufacturing. Across the lifecycle, the 150% eBOM defines engineering possibilities, configuration logic determines which combinations are valid, and the 150% mBOM defines how those possibilities can be built at a specific factory. Connecting these layers preserves customer intent and shows what was selected, why it is valid, and how it should be built.

What is a 150% BOM? 

A 150% BOM is a comprehensive product structure containing all approved components, modules, options, and variants that may be used across a configurable product family. It represents the full range of what could be designed or built, including alternatives that would never appear together in one finished product. 

Consider a configurable industrial pump system. Its 150% product structure may include: 

• Multiple pump sizes and impeller designs 

• Different motor power, voltage, and efficiency options 

• Seal materials for different fluids and operating conditions 

• Stainless steel, cast iron, and specialty-alloy housings 

• Regional electrical and regulatory packages 

• Optional monitoring, control, and safety components 

• Compatible frames, piping, connectors, and mounting assemblies 

 

No customer receives all of these components. The 150% BOM defines the approved universe from which configuration rules derive a valid product. 

Manufacturers may also call it a super BOM, configurable BOM, variant BOM, or maximum BOM, although the exact meaning can vary by organization and system. 

How do 150% eBOMs, configuration logic, and 150% mBOMs work together? 

The 150% concept can apply to both engineering and manufacturing, but the structures serve different purposes. Configuration logic connects them by determining which possibilities are valid for a particular requirement, order, and factory. 

The 150% eBOM defines engineering possibility 

The 150% engineering BOM contains the complete range of approved engineering components and variants for a product family. It captures design intent, including the parts, assemblies, technical relationships, and revisions that engineering has approved. 

For the pump example, the 150% eBOM may include every compatible motor, seal, housing, control system, and certification package. PLM or PDM typically remains the system of record for this product data. 

Configuration logic resolves valid combinations 

The configuration model contains the rules, constraints, and relationships that determine which choices can appear together. It connects customer requirements with engineering features and components. 

This configuration layer is not necessarily another BOM. It provides the logic required to navigate the 150% structure. It can determine which motor meets a requested performance level, which seal works with a specific fluid, and which regional package satisfies the applicable regulations. 

The same governed logic can support sales configuration, engineering validation, and order fulfillment. This keeps each function aligned around a common definition of what is valid without requiring every team to use the same BOM structure. This configuration logic is often defined in Configure, Price, Quote (CPQ) tools.  

The 150% mBOM defines manufacturing possibility 

The 150% manufacturing BOM contains the approved manufacturing content that may be required across product variants, factories, and production scenarios. It can include manufacturing parts, subassemblies, local alternatives, routing options, operations, and documentation. 

Engineering and manufacturing structures do not always organize the product in the same way. The 150% eBOM may group components according to product function and design intent. The 150% mBOM may reorganize those components around how they will be sourced, assembled, tested, packaged, and built. 

Mappings between the eBOM and mBOM preserve the relationship between engineering intent and manufacturing execution. Fulfillment rules then derive the specific mBOM, routing, and instructions needed for an individual order and factory. 

What is the difference between a 150% BOM and a 100% BOM? 

A 150% BOM contains the complete range of approved possibilities for a configurable product family. A 100% BOM contains the specific content required for one valid configuration or order. 

A customer requirement moves through these connected views. A request for a pump that handles a corrosive fluid at a defined flow rate, operates on a specific voltage, and meets an explosion-protection standard resolves to one compatible engineering definition. Manufacturing logic then applies the selected factory, approved local parts, routing, and production instructions. 

The order-specific outputs represent the 100% needed to fulfill that requirement. They remain traceable to the broader 150% structures and the configuration decisions that produced them. 

Why does a 150% BOM need configuration rules? 

The 150% BOM provides the available content. Configuration rules make that content usable. 

Without governed rules, a 150% BOM is a large product structure containing many possible parts. It cannot reliably determine which combinations satisfy the customer’s performance requirements, engineering constraints, regulatory obligations, and manufacturing conditions. 

Configuration logic can define: 

• Which options are required, optional, or mutually exclusive 

• Which components and assemblies are compatible 

• How customer requirements translate into technical selections 

• Which rules vary by region, application, or regulatory standard 

• Which factory or site can fulfill the configured product 

• When an engineering or manufacturing exception requires approval 

• Which engineering and manufacturing content results from each decision 

 

Constraint-based configuration is especially valuable for highly configurable products because it models relationships rather than attempting to predefine every possible configuration path. Teams can introduce a new option, component, or constraint without rebuilding every combination separately. 

The structure, rules, and mappings work together as a governed product model. That model defines the boundaries of what can be sold, engineered, and built. 

Why is the 150% BOM important to the manufacturing digital thread? 

The 150% BOM gives the manufacturing digital thread a structured definition of product variability. Configuration logic connects that definition with customer requirements, while downstream mappings preserve the relationship through engineering and production. When configuration logic is layered on the BOM and product logic, it is a foundation for being able to automate BOM management and create production BOMs from quotes or sales orders.  

It connects customer intent to engineering decisions 

Customers usually describe what the equipment must do, where it will operate, and which performance, safety, or regulatory conditions it must meet. They rarely describe the part-number hierarchy required to deliver it. 

Configuration rules translate those requirements into valid selections from the 150% eBOM. This creates a traceable relationship between the customer’s need and the engineering content included in the product. 

Passing only a final SKU or document downstream loses much of that context. A connected product model preserves both the selected content and the decisions that produced it. 

It creates a governed definition of product variability 

Sales, engineering, and manufacturing often maintain different versions of the same configuration knowledge. Commercial rules may live in CPQ, engineering constraints in PLM or spreadsheets, and production logic in ERP, MES, or local factory systems. 

Only 7% of manufacturers define configuration rules once and reuse them across systems, according to Tacton’s 2026 State of Manufacturing report. The remaining organizations must maintain or reconcile configuration knowledge across multiple functions. 

A governed configuration model gives those systems a common definition of valid product variability across the different BOM structures. Each platform can retain ownership of the information and processes it manages while using consistent rules and relationships. 

It makes product changes traceable 

An engineering or manufacturing change rarely affects every configuration in the same way. A revised motor may apply only to certain voltages, regions, frame sizes, factories, or regulatory packages. 

Connecting the change to the relevant conditions makes it possible to identify affected options, configurations, quotes, orders, and manufacturing outputs. Teams can then determine when the revision becomes effective and whether an active customer order requires review. 

Only 21% of manufacturers automatically propagate engineering changes to downstream systems. For the rest, every product update creates another manual synchronization requirement across product models, sales tools, BOMs, and factory systems. 

It supports factory-specific manufacturing output 

The configured engineering definition still needs to be translated into the way a particular factory will build the product. That translation may account for site capabilities, local sourcing, approved alternates, routing, work instructions, testing, and documentation. 

Only 23% of manufacturers automatically generate BOMs from quotes. Manual handoffs leave production teams to interpret what was sold and reconstruct how it should be built. Errors at this stage can lead to order corrections, rework, expedites, margin erosion, and missed delivery commitments. 

A connected 150% mBOM and fulfillment model allow manufacturers to derive precise factory output without losing the link to the customer configuration or engineering definition. 

Where should the 150% BOM and configuration logic be managed? 

The 150% product definition should work across the manufacturer’s existing system landscape, with clear ownership for each type of data and governed relationships between systems. 

• PLM or PDM owns engineering product data. It remains the system of record for the 150% eBOM, parts, product structures, CAD data, revisions, and engineering change processes. 

• Configuration management governs configurability. It manages the rules, dependencies, constraints, releases, and applicability that determine how the 150% engineering structure becomes a valid customer-specific product. 

• CPQ applies released configuration and commercial logic. It connects customer requirements with valid features, options, pricing, and a structured sales configuration during the buying process. 

• A fulfillment or manufacturing configuration layer manages manufacturing variability. It can maintain the 150% mBOM, map engineering content to manufacturing structures, and derive order-specific output for the selected factory. 

• ERP and MES manage planning and execution. They receive the order-specific mBOM, routing, documentation, and related data required to plan materials, schedule production, and execute the order. 

• Service or asset systems preserve the delivered configuration. They maintain the context required for parts, maintenance, upgrades, and lifecycle support. 

 

This model creates connected sources of truth. Product data does not need to be manually recreated in every application, and configuration logic does not need to diverge across sales, engineering, and manufacturing. 

How does a 150% BOM help manufacturers scale customization? 

A governed 150% product model allows manufacturers to reuse engineering and manufacturing knowledge across more products, orders, regions, and factories. 

Engineering defines approved product possibilities. Configuration rules turn customer requirements into valid product selections. Manufacturing defines how those possibilities can be produced across different sites. Each order receives a precise output derived from the same governed foundation. 

This supports configure-to-order at greater scale while preserving a clear path for genuine engineer-to-order exceptions. Repeatable configurations can move through the lifecycle with less manual intervention, while engineering focuses on requirements that fall outside the approved product model. 

The business impact can include: 

• Greater sales confidence that configured products are technically valid 

• Less engineering effort spent reviewing repeatable combinations 

• Clearer control over new options, revisions, and lifecycle status 

• More complete and factory-specific production information 

• Fewer manual translations between sales, engineering, and manufacturing 

• Better visibility into the impact of customer and internal order changes 

• Fewer order corrections, expedites, and production delays 

• Stronger traceability from customer requirements to delivered equipment 

 

For manufacturers trying to increase customization without adding engineering effort and downstream risk at the same rate, the 150% BOM provides an important foundation. 

What does connected 150% BOM management require? 

Connected 150% BOM management depends on a shared product vocabulary, explicit system ownership, governed configuration logic, cross-functional mappings, and lifecycle controls. 

Manufacturers should be able to answer several questions: 

• Which product options and variants belong in the 150% eBOM? 

• Which manufacturing parts, processes, and factory alternatives belong in the 150% mBOM? 

• Which system owns each part, structure, rule, price, and manufacturing attribute? 

• How do customer requirements resolve to engineering features and components? 

• How does engineering content map to manufacturing structures and routing? 

• Which rules can be defined once and reused across sales, engineering, and fulfillment? 

• How do approved revisions and order changes affect active configurations and downstream outputs? 

• How is the as-sold and as-built context preserved for service? 

 

A practical starting point is one configurable product family and one complete order flow. Teams can prove how a real customer requirement moves through engineering possibility, configuration logic, and factory-specific output. The standards, mappings, and governance established in that flow can then expand to more products, business units, and factories. 

How Tacton supports a connected 150% BOM model 

Tacton helps manufacturers connect customer requirements with governed product configurability and manufacturing-ready output while allowing PLM, ERP, MES, and other systems to retain their intended roles. 

Learn more about Tacton.

 

Frequently asked questions about 150% BOMs 

Is a 150% BOM the same as a super BOM? 

Often. Manufacturers may use the terms 150% BOM, super BOM, configurable BOM, variant BOM, or maximum BOM for a structure containing all available product possibilities. Exact definitions vary by organization and system. 

What is the difference between a 150% eBOM and a 150% mBOM? 

A 150% eBOM contains the full range of approved engineering components and variants. A 150% mBOM contains the full range of approved manufacturing parts, processes, routings, and factory alternatives. Configuration and fulfillment rules connect the two structures and derive the content required for a specific order. 

Is the configuration model another type of BOM? 

No. The configuration model contains the rules, constraints, and relationships used to select valid content from the 150% structures. It provides the logic that connects customer requirements with engineering and manufacturing outputs. 

Can a 150% BOM be used directly for manufacturing? 

A 150% BOM contains alternatives and mutually exclusive content, so it is not a production order by itself. Configuration and fulfillment logic must resolve it into the order-specific mBOM, routing, and instructions required by the selected factory. 

How does a 150% BOM support CPQ? 

The 150% eBOM provides the engineering structure behind available product options. CPQ applies released configuration and commercial logic to customer requirements so sales can create a valid solution and structured sales BOM. 

Why is a 150% BOM important to the digital thread? 

A 150% BOM gives sales, engineering, and manufacturing a connected definition of product variability. Governed configuration logic preserves customer intent, engineering decisions, product changes, and factory-specific manufacturing outputs across the lifecycle. 

Every configurable product a manufacturer builds, from excavators and lifts to medical devices and conveyor systems, depends on an accurate Bill of Materials (BOM). The BOM defines the components, assemblies, and instructions required to turn a product design or customer order into something that can be built.

Creating the BOM itself is not often challenging. Keeping multiple BOMs aligned as a product moves from engineering to sales to production, however, opens the door to many errors. Only 23% of manufacturers automatically generate BOMs from quotes, according to the 2026 State of Manufacturing report. Most still rely on manual interpretation at one or more handoffs between what was sold and what will be built.

BOM management across the manufacturing lifecycle connects product views so teams can trace the customer’s choices through engineering and production without repeatedly translating the same order. That creates a more reliable path from configuration to delivery.

What is a Bill of Materials (BOM) in manufacturing?

A Bill of Materials, or BOM, is a structured list of the materials, components, subassemblies, quantities, and instructions required to define, manufacture, or service a product.

The exact content depends on who is using the BOM and where the product is in its lifecycle. Sales needs a customer-facing view of selected features and options. Engineering needs the technical product structure. Production needs factory-specific parts, assemblies, and routing. Service needs the components and documentation required to maintain the delivered product.

This is why complex manufacturers usually manage several related BOMs rather than one universal list.

What are the main types of BOMs?

The main types of Bills of Materials are the sales BOM, engineering BOM, manufacturing BOM, and service BOM. Each gives a different function the product information it needs.

Gartner research explains that product development, manufacturing, service, procurement, and suppliers depend on different BOM views to work effectively. The goal is a connected family of BOMs with enough shared structure to trace equivalent items across functions, while each team continues to work in the system and format designed for its needs. (Gartner, G00736769)

Consider how those BOM types might represent a configurable excavator.

Sales Bill of Materials

The sales Bill of Materials, or sales BOM, represents the customer-facing product as configured for a specific application. It captures the commercial choices, features, and options included in the quote or order.

For an excavator, the sales BOM may include:

• Base model, such as EX2000
• Engine option, such as Standard Diesel or Tier 4 Compliant
• Boom and arm option, such as Standard Reach, Long Reach, or Heavy Lift
• Track type, such as Steel, Rubber, or Hybrid
• Cab package, such as Standard or Premium
• Add-ons, such as a hydraulic quick coupler, rear-view camera, or telematics system

A sales BOM is often generated through configure, price, quote (CPQ) software. When supported by current product and configuration logic, it gives sales a validated representation of what the customer selected and provides downstream teams with a structured starting point for the order.

Engineering Bill of Materials

The engineering Bill of Materials, or eBOM, represents the product as designed. Created and managed by engineering, often in CAD and product lifecycle management (PLM) systems, it defines the technical structure needed to meet performance, compatibility, and regulatory requirements.

For an excavator, the eBOM may include:

• Hydraulic system assembly, including hoses, valves, cylinders, and pumps
• Chassis frame weldment
• Operator cab, including the frame, glass panels, wiring harness, and seat assembly
• Electrical system, including the main harness, fuses, sensors, and control units
• Engine and cooling subsystem, including the radiator, fan, and alternator
• Fasteners and brackets defined by engineering
• Part numbers, revision levels, and CAD file references

An engineering BOM describes design intent. Production still needs to determine how that design will be sourced, assembled, routed, and built at a specific factory.

Manufacturing Bill of Materials

The manufacturing Bill of Materials, or mBOM, represents how a product will be built. It reorganizes the product definition around manufacturing requirements such as assembly sequence, production routing, factory capabilities, and local sourcing.

For an excavator, the mBOM may include:

• Hydraulic system kit assembled before final installation
• Cab assembly with the seat and wiring pre-installed
• Weldment subassemblies for the undercarriage frame and boom arm
• Alternate parts for localized sourcing, such as regional hydraulic fittings
• Packaging and material-handling items, including crates, labels, and protective materials

The mBOM helps production and supply chain teams plan the order using accurate, factory-specific information. When it reflects the customer’s configuration and current engineering definition, it also reduces the risk of rework, part substitutions, and delivery delays.

Service Bill of Materials

The service Bill of Materials, or sBOM, supports maintenance, repairs, spare parts, and after-sales service for the product that was delivered. It gives service teams a view of the components that can be inspected, replaced, or upgraded throughout the product’s operating life.

For an excavator, the service BOM may include:

• Engine oil filter kit
• Hydraulic seal replacement set
• Electrical harness replacement
• Track tensioner repair kit
• Preventive maintenance items such as filters, belts, and fluids
• Approved replacement versions of revised components

An accurate service BOM helps technicians identify the right parts for the customer’s specific product. It can improve first-time fix rates, support equipment uptime, and reduce the cost of servicing installed equipment.

Manufacturers may also use planning BOMs for forecasting and costed BOMs for pricing or cost analysis. Each BOM serves a defined purpose. The business value comes from keeping those views connected as the product and order move through the lifecycle.

Why do BOM items differ across sales, engineering, production, and service?

BOM items often differ across functions because each team structures and names product information for its own work. Equivalent items may have different descriptions, identifiers, or positions within different BOM hierarchies.

For example, a customer’s selection of a “Tier 4 Compliant Engine” may appear in:

• The sales BOM as a customer-facing engine option
• The eBOM as a specific engine and emissions-control assembly with design revisions
• The mBOM as a factory-specific engine installation kit with local parts and routing
• The sBOM as serviceable engine components, replacement parts, and maintenance procedures

Each view is valid, but the systems holding those views may not know that the items are related. A person then has to interpret the customer’s selection, find the matching engineering definition, determine the correct manufacturing content, and preserve the relationship for service.

Three common conditions allow these connections to drift:

1. Different systems support different workflows. Engineering may author product structures in PLM, production may manage order and material data in ERP or MES, sales may create a sales BOM in CPQ, and service may work in a field service system.
2. Naming and numbering conventions develop independently. Product identifiers often evolve within departments, business units, acquired companies, or factory sites. The same item may be described differently across systems even when it serves the same product function.
3. Cross-functional ownership is unclear. Each team may govern its own BOM accurately without anyone owning the mappings and rules that connect equivalent items across BOM views.

Gartner states, “An inability to associate equivalent items in different views of BOMs will erode the value of digital threads long before the life cycle of a product is complete.” Today’s digital threads are limited to manufacturing and production, according to the analyst, and don’t yet include service or other parts of the lifecycle. As products change, weak associations reduce traceability and create errors that erode margin.

How do 150% BOMs connect engineering, configuration, and manufacturing?

A 150% BOM represents the complete range of approved possibilities rather than the content required for one order. The 150% eBOM defines the engineering options and components, while the 150% mBOM defines the manufacturing parts, processes, routings, and factory-specific possibilities.

Between them, governed configuration logic determines which options are valid and how customer requirements map to engineering and manufacturing content. Each configured order resolves those possibilities into the specific sales BOM, engineering definition, and factory-specific mBOM needed to build and deliver the product.

Connecting these layers preserves the customer’s original requirements while allowing engineering and manufacturing to manage the structures they need. This relationship is an important foundation of the manufacturing digital thread.

How can manufacturers connect equivalent items across BOMs?

Manufacturers can connect equivalent BOM items by establishing a shared product vocabulary, mapping relationships across systems, and governing the configuration logic that determines how customer choices affect engineering and manufacturing content.

This does not require identical names or one system for every BOM. It requires reliable associations that allow each system to recognize the same product decision in its own context.

Define a shared product vocabulary

Start by agreeing on how items, features, options, variants, and assemblies are classified and related. Define the rules for cross-referencing identifiers across BOM types, including how revisions, alternates, and substitutions are handled.

The objective is consistent meaning. A sales option and a production kit can keep different names as long as their relationship is explicit, governed, and machine-readable.

Create cross-functional BOM governance

Bring sales, engineering, manufacturing, supply chain, service, and IT into the governance model. A core team should own the standards, mappings, approvals, and change processes that keep BOM views associated.

This prevents each function from solving the same product relationship independently and gives the organization a clear process for resolving conflicts.

Reuse configuration logic across the lifecycle

Configuration logic provides a valuable shared layer, because it defines how product requirements, features, options, components, and constraints relate to one another.

Today, only 7% of manufacturers define configuration rules once and reuse them across systems. The remaining 93% maintain or reconcile versions of product logic across sales, engineering, and production, according to surveyed manufacturing leaders.

When governed configuration logic is reusable, the selection of a Tier 4 compliant engine can resolve to the correct engineering assembly, manufacturing kit, compatible options, and service content. Each team receives the product view it needs without manually reconstructing the customer’s intent.

Why is the sales BOM important to the manufacturing digital thread?

The sales BOM is the commercial entry point to the manufacturing digital thread because it captures customer requirements as structured product data at the beginning of an order.

For a configurable product, it records what was sold, which options were selected, and which rules shaped the resulting solution. That context should remain connected as the order moves into engineering, production, and service.

When a sales BOM is disconnected from downstream systems, it often becomes a document that another team must interpret. Every interpretation creates a chance to lose a requirement, select the wrong revision, overlook an incompatibility, or make a commitment that production cannot meet.

The business impact appears across the quote-to-delivery process:

• 62% of manufacturers report moderate to severe margin erosion between quote and delivery. Manual changes, rework, and substitutions across disconnected handoffs contribute to that loss.
• 40% are only somewhat or not very confident in delivery commitments at the time of quote. Sales cannot make a reliable promise when engineering, part availability, or production constraints remain invisible.
• 43% cite customization as their top quoting challenge. Added customer choice increases the number of product decisions that must remain accurate through every downstream BOM.

In a connected process, CPQ captures a valid customer configuration and creates a structured sales BOM. Integrations carry that configuration context into PLM and ERP. Engineering can identify the appropriate product definition, while manufacturing can apply factory-specific parts, sourcing, and routing. The digital thread preserves the relationship from the customer’s original choice through execution.

What are the biggest BOM management challenges?

The biggest BOM management challenges are inconsistent product data, manual translation between BOM types, disconnected systems, unclear ownership, and slow change propagation.

When BOMs are not properly connected:

• Engineering changes may not reach sales or manufacturing in time.
• Quotes may include configurations that require downstream correction.
• Production may receive incomplete or outdated order data.
• Service teams may struggle to identify the correct parts for the delivered product.
• Teams may duplicate product rules and maintain conflicting versions across systems.

Only 21% of manufacturers automatically propagate engineering changes to downstream systems, according to survey respondents. For the rest, every product update introduces another manual communication and synchronization requirement.

That model becomes harder to sustain as manufacturers add options, factories, regions, sales channels, and customer-specific requirements.

What are the steps of effective BOM management?

Effective BOM management connects customer requirements, engineering definitions, manufacturing instructions, and service information across the product lifecycle. It gives each team the BOM view it needs while preserving the relationships between what was sold, designed, built, and delivered.

Manufacturers can build that process around several steps.

1. Define each BOM and its purpose

Start by defining the role of the sales BOM, engineering BOM, manufacturing BOM, and service BOM.

The sales BOM captures the product, features, and options selected by the customer. The eBOM defines the product as engineering designed it. The mBOM organizes the parts, assemblies, routing, and instructions required by a specific factory. The service BOM supports maintenance, replacement parts, and upgrades for the delivered product.

These BOMs should remain distinct because they support different decisions. BOM management connects them so a customer requirement can be traced through engineering, manufacturing, and service.

2. Assign a clear owner to every type of BOM data

Determine which system and business function owns each type of information.

PLM or PDM will usually own engineering parts, product structures, and revisions. CPQ will own the configured sales BOM associated with a quote or order. ERP or MES will own manufacturing, material, routing, and execution data. Service or asset systems will manage information about the installed product.

Clear ownership prevents multiple teams from maintaining competing versions of the same information.

3. Establish a shared configuration foundation

Create a governed source for the features, options, rules, and constraints that define which product combinations are valid.

This configuration foundation connects customer-facing choices with engineering and manufacturing content. It allows sales, engineering, and fulfillment to use the same product logic even when their BOM structures and systems are different.

For highly configurable products, the foundation may build on a 150% eBOM containing the full range of approved engineering possibilities. Then, adding a layer of 150% configuration logic helps determine which parts and assemblies apply to a specific customer requirement.

4. Connect the systems that create and consume BOM data

Integrate CPQ, PLM, ERP, MES, and service systems so product information can move through the lifecycle as structured data.

The integration should carry more than a final part number or PDF. It should include the configuration context, product identifiers, revisions, effective dates, and relationships needed by downstream systems.

This approach reduces redundant data entry. Each system can retain ownership of its information while making the relevant data available to the rest of the process.

5. Translate the sales configuration into factory-specific manufacturing output

Define how customer choices resolve to engineering assemblies and how those assemblies map to manufacturing content. A comprehensive manufacturing model can represent the approved parts, processes, and routing possibilities, while fulfillment rules derive the order-specific mBOM for the selected product and factory.

The resulting output should include the parts, local substitutions, routing, and manufacturing documentation required for production. Automated validation should identify missing mappings, incompatible combinations, outdated revisions, or incomplete instructions before the order reaches ERP or MES.

6. Govern BOM changes throughout the product lifecycle

Manage product definitions and configuration logic with version control, effective dates, release states, approvals, and applicability rules.

When engineering introduces a new component or product option, the organization needs to know when it becomes available, which markets or factories can use it, and whether it affects active quotes or open orders.

BOM management should preserve the exact product definition used for every quote, order, manufactured unit, and delivered asset. This creates an audit trail while allowing the product portfolio to evolve.

BOM management should also account for customer and internal changes made after an order has entered fulfillment. Teams need visibility into how a change affects the mBOM, routing, materials, documentation, cost, and delivery plan before approving it.

7. Preserve product context after delivery

Carry the as-sold and as-built configuration into the installed-product record.

Service teams need to know which components, revisions, substitutions, and upgrades apply to each delivered product. Preserving this information supports accurate spare-parts selection, maintenance planning, field modifications, upgrades, and future commercial opportunities.

AI-assisted modeling can make this connected process easier to establish and maintain. It can help teams create product models, identify relationships, and refine configuration constraints. Product experts should continue to review and approve the resulting logic, especially when it affects pricing, compliance, manufacturability, or delivery.

Together, these seven steps create a connected BOM management process. Each function retains the product view and system it needs, while shared configuration logic and governed data relationships preserve the digital thread from the initial customer requirement through manufacturing and service.

What are the benefits of BOM management?

BOM automation helps manufacturers:

• Reduce manual data entry and interpretation between functions
• Prevent invalid or outdated product information from reaching quotes and orders
• Create accurate, order-specific manufacturing outputs
• Propagate approved product changes more consistently
• Reduce engineering review and production rework
• Improve traceability from customer requirements to delivered equipment
• Give sales greater confidence in product and delivery commitments
• Support more configurable orders without adding the same level of manual effort
• More realistic production planning
• More consistent execution across factories
• Stronger margin protection during fulfillment
• Smoother handoffs between sales, engineering, and production

The broader result is a stronger digital thread. Sales, engineering, production, and service can work from connected views of the same product and order while retaining the information each team needs.

Connect what is sold to what is built with Tacton

Tacton helps manufacturers connect buyer engagement, engineering, and order fulfillment through shared configuration logic and structured product data.

Tacton CPQ validates customer requirements and generates a structured sales configuration. Govern product configurability and how it changes, and validate configurations into accurate, manufacturing-ready orders. Tacton helps you preserve engineering intent, reduce manual handoffs, and keep what is sold aligned with what can be delivered across the entire BOM lifecycle.

Tacton integrates with existing CRM, PLM, ERP, and other enterprise systems, allowing manufacturers to strengthen their digital thread without replacing every system that already owns critical product or transactional data.

Tacton was named a Leader in the 2026 Gartner® Magic Quadrant™ for Configure, Price and Quote Applications for the fourth consecutive year.

Explore Tacton’s connected suite

Fragmented product configuration knowledge and poor governance can create hidden costs across the entire manufacturing lifecycle, from higher sales and engineering effort to rework, supply chain inefficiencies, and service issues.  

Errors happen when configuration knowledge is duplicated or reentered across manufacturing systems. Manual handoffs between teams and inconsistencies between systems become increasingly expensive the further they travel from quote to delivery.  

Centralizing configuration around a single source of truth can help manufacturers reduce these costs while improving deal quality, protecting margins, and creating a more connected process across each project. 

What does it mean to have fragmented product configuration logic?  

Product configuration knowledge doesn’t typically live in one place. In complex manufacturing, configuration data and logic can be spread across CPQ, PDM/PLM, ERP, CAD, MES, CRM, service systems, spreadsheets, and homegrown tools. Each system serves a legitimate purpose, but configuration rules can accumulate in several of them, often with different owners and release cycles. That fragmentation makes it harder consistently align sales quotes with manufacturability. 

Fragmentation happens when multiple systems and teams independently maintain pieces or copies of the logic that determines what can be sold and built. 

For example: 

• CAD contains design intent and parametric logic.  

• PDM/PLM contains engineering structures, variant rules, and the engineering Bill of Materials.  

• CPQ contains sales options, constraints, and another implementation of engineering rules.  

• ERP contains manufacturing dependencies and order validation.  

• MES may contain factory-specific work instructions.  

• Spreadsheets/homegrown tools contain sizing calculations, compatibility matrices, or other rules.  

• People may hold exceptions and product knowledge that hasn’t been formally captured.  

 

It’s normal for these systems to coexist and hold the master data needed for their specific functions. The problem arises when the configuration logic that determines what can be sold and built doesn’t carry consistently from one system to the next. The same rules are recreated and synchronized in multiple systems, and each implementation can have a different owner and release cycle, creating opportunities for the logic to drift. 

Why does fragmented product configuration cost manufacturers money?  

Fragmented configuration logic and poorly governed configuration management creates a business risk, both operationally and financially. Manual governance and duplicated configuration logic lead to human error that can result in incorrect quotes, incorrect orders, and incorrect production instructions. Engineering change orders and configuration updates may not automatically populate to all systems, causing some teams to work from outdated configuration logic. The further along that errors are discovered, the more costly they become due to rework, scrap, and penalties.  

How does poor product configuration governance contribute to margin erosion? 

The quoted margin is rarely the same as the final margin once manufacturers eat the costs of downstream errors or delays.    

According to Tacton’s 2026 State of Manufacturing report, 62% of manufacturers experience moderate to severe margin erosion, with errors as early as the initial configuration and quote being a major cause. Protecting margins in high-mix manufacturing is harder without centrally governed product configuration, as sales reps may configure similar requests differently, and multiple ERPs can create inconsistencies across plants. 

What are the hidden costs of fragmented product configuration knowledge across your business?  

The ultimate cost of fragmented product configuration is margin, but this isn’t felt in just one place. Manufacturers deal with hidden costs from the moment the customer is first engaged through aftermarket sales and post-installation maintenance. 

1. Higher cost of sales

Quoting engineer-to-order products will always require heavy engineering involvement, but even configure-to-order products with standardized components still require engineering support for many sales teams.  

Fragmented configuration logic, whether it’s in spreadsheets or homegrown tools, make long sales cycles even longer due to increased engineering back-and-forth, manual validation and approvals, and quote revisions and rework. That additional time increases the cost of the sale. 

2. Higher engineering and overhead costs

Hand-in-hand with a higher cost of sale is higher engineering and overhead costs. Today, 93% of engineering teams spend high effort maintaining configuration data and logic across different systems, like PLM, CPQ, and more.  

Heavy quoting support, manual reconciliation, and configuration rule maintenance consume valuable engineering resources. As product portfolios and configuration complexity grow, especially when critical knowledge is concentrated among experienced engineers, more engineering capacity shifts from innovation to maintenance. 

3. Higher COGS and cost of poor quality

When configuration logic is decentralized, sales, engineering, and manufacturing can work from different versions of what is valid and buildable. A configuration sold by sales may then need to be manually interpreted into an engineering Bill of Materials (BOM) and again into a manufacturing BOM. If rules have drifted or information is lost during those handoffs, production can receive an incorrect or incomplete BOM. Once the problem reaches the shop floor, fixing it requires rework, scrap, overtime, expedited materials, and production delays.

4. Supply chain inefficiency

Product configuration can impact supply chain planning by determining when teams have reliable visibility into the parts and materials needed for an order. When configuration is fragmented, the final BOM may not be clear until later in the process, leading to expedited orders, premium sourcing, and greater reliance on safety stock and work-in-progress. A shared configuration model provides an accurate demand signal earlier, helping teams plan materials with greater confidence and reduce unnecessary inventory buffers. 

Product configuration can impact supply chain planning in both directions. At the same time, connecting relevant operational constraints to the quoting process and configuration logic (what can be manufactured) can help sales make more informed commitments based on what the business can realistically deliver.

5. Higher service and warranty costs

Full configuration management across the lifecycle governs both what can be configured and what was actually configured. Configuration data provides a definitive record of the configured product after delivery that gives service insight into what was installed, and therefore, what services or maintenance will be needed. When that information is segmented across systems and difficult to trace, teams struggle to identify the right spare parts or understand which components and options apply to a specific unit, leading to incorrect parts, repeat service visits, and greater warranty and claims exposure. Maintaining the delivered configuration against the product model gives service teams a more reliable record to support the asset throughout its lifecycle. 

What is centralized product configuration management? 

Centralized product configuration management means maintaining the rules for how your products can be configured in one governed place, rather than recreating them for sales, engineering, and manufacturing. It starts with a complete definition of all the ways a product can be configured. Sometimes called the 150% structure, this includes all possible components, options and variants for a product family, along with the rules that determine which combinations are valid. For each customer order, those possibilities are narrowed down to the specific configuration being sold and built. 

Everyone works from the same logic. That doesn’t mean working from the same screen or systems. Engineering, sales and manufacturing still need different information and different views of the product. PLM/PDM can continue to manage engineering items and structures, while ERP manages materials and production. What changes is that the same configuration logic is applied across those different views, so each system can use its own master data without independently recreating the rules for what makes a valid product. 

What are the benefits of centralized product configuration management? 

Fragmented configuration logic makes customization harder to industrialize. More customer variation brings more manual effort and less certainty around what each order will cost to deliver. At the highest level, centralizing configuration logic makes it easier to take on these projects with greater speed, efficiency, and reliability than competitors.  

The cost-saving benefits of centralized product configuration include: 

1. Better deals and stronger margins

When every salesperson works from the same product rules and has reliable business logic guiding their choices, customers get a consistent answer about what can be configured, regardless of who they talk to. Sales can propose valid, manufacturable solutions faster, see available options in real time, and rely less on engineering support. This can improve the buying experience and help increase win rates, particularly when speed and convenience matter. 

Those same guardrails also keep sales within the boundaries of what can be built, thereby reducing the risk of configuration errors that surface later in engineering or production and erode margin.

2. Fewer configuration errors and lower quality costs

When everyone works from the same truth, orders stay true to the original buyer’s intent and requirements.  

Additionally, a configured product may be the same for the customer but require different manufacturing instructions depending on where it’s built. Centrally governed configuration starts with the 150% structure (i.e., the complete set of components, options, and variants that can make up a product). For each customer order, that structure is resolved into the specific 100% product structure that needs to be built. From there, the appropriate factory-specific manufacturing BOM and routing can be generated based on that plant’s materials, suppliers, and production processes. This helps manufacturers maintain a consistent product definition and production quality across factories, even when plants build differently or operate separate ERPs. 

3. Greater sales and engineering scalability

Centralized configuration helps manufacturers handle more quoting and configuration activity without requiring engineering involvement to grow at the same rate. Sales can independently handle more routine configurations, while engineering focuses on edge cases and defining and maintaining product logic rather than repeatedly validating individual deals or updating the same rules in multiple places. That creates more capacity on both sides: sales can respond faster, and engineering can devote more time to product development. 

4. Better supply chain and working-capital efficiency

A reliable configured order gives operations a clearer picture of what will need to be produced. That visibility can reach supply chain teams earlier, providing a stronger signal for material planning, purchasing, and production. With greater certainty around upcoming requirements, manufacturers can plan inventory and work-in-progress around real configured demand rather than relying as heavily on buffers and last-minute adjustments. 

5. Better lifecycle and service visibility

Configuration data remains valuable long after the initial sale. By maintaining a record of the specific configuration sold and delivered for each asset, manufacturers gain a clearer view of their installed base. Service teams can see which parts, options, and components apply to an individual unit, helping them make more informed maintenance and spare-parts decisions. That same visibility can also help manufacturers identify relevant upgrades, retrofits, and aftermarket opportunities based on what each customer installed, rather than the product family overall.  

How does centralized product configuration governance look in practice? An example 

Imagine a manufacturer selling a configurable industrial compressor. In PLM, engineering maintains the product data and 150% BOM—the full set of possible components, options, and variants. Alongside that product definition, engineering governs the configuration logic that determines which combinations are valid, such as which motor works with a given voltage, which cooling package is required for a certain environment, or which options are incompatible. As components are replaced or new options are introduced, those rules are revised and approved centrally rather than updated separately by each downstream team.  

When a customer needs a compressor with a specific capacity, power supply, operating environment, and performance requirements, sales captures those needs in the quoting process. The commercial configuration applies the same approved engineering logic, along with pricing and business rules, to guide sales toward a valid solution. Sales is not recreating the engineering rules or asking engineering to validate every standard quote. 

Once the customer orders that configuration, the selected options are carried forward rather than manually reinterpreted. The full 150% product definition is narrowed to the specific 100% structure for that order, and the manufacturing information can then reflect the capabilities and requirements of the factory building it. That information flows into the ERP and MES used for production planning and execution.  

If engineering later changes a component or configuration rule, that change is governed at the configuration level and can be traced through the affected quotes and orders instead of relying on separate teams to update their own copies of the logic. 

Configuration fragmentation often shows up in the everyday work required to keep sales, engineering, and production aligned. A few questions can help uncover it: 

• How many systems determine what can be sold and built? Look beyond formal configurators to spreadsheets, ERP rules, engineering tools, and other sources of configuration knowledge.  

• Who owns the configuration rules? If different teams maintain their own versions, changes can become difficult to govern and synchronize.  

• How many quotes require engineering validation? Heavy engineering involvement in routine quotes can signal that configuration knowledge has not been captured well enough for sales to use independently.  

• How often are orders corrected after signing? Frequent corrections can point to gaps between what was quoted and what engineering or production actually requires.  

• How long does an engineering change take to reach sales? Long or inconsistent change propagation can indicate that rules are being maintained separately.  

• Can you trace a delivered product back to its original configuration? If teams cannot easily determine exactly what was sold, built, and installed, fragmentation may extend across the full lifecycle.  

Better configuration governance starts with a digital thread

Product configuration can be easy to treat as a technical concern, but its impact reaches far beyond the systems where configuration rules live. For manufacturers managing high product variety, bringing greater consistency to configuration can help support profitable customization, more predictable execution, and a better experience from the initial customer request through delivery and service. 

Learn how to make the configurable product the center of your manufacturing lifecycle. Read the full article on building a digital thread with configurability at the core. 

If you’re comparing business intelligence tools for manufacturing, the tool you pick determines what questions you can actually answer. General BI platforms give you enterprise-wide visualization, CRM reporting gives you pipeline visibility, and ERP systems give you operational and financial reporting. Alongside these, native analytics, such as Tacton Insights & Analytics in CPQ, understands the configuration context behind your quotes, so you can see not just what your BI tool tells you is winning, but why. 

Explore the main types of analytics tools used in manufacturing, their strengths and limitations for commercial decision-making, and what to look for when evaluating them. 

What is commercial intelligence in manufacturing and why does the analytics tool choice matter? 

Commercial intelligence in manufacturing is the understanding of sales performance, both at a high level (e.g., revenue, pipeline, win rates, etc.) and a deeper level about the drivers behind performance (e.g., why certain deals closed faster, which deals produce the best margin, etc.).  

Commercial intelligence is also the ability for sales, product, and operations teams to independently answer questions about things like win rates, margin drivers, portfolio demand, and forecasting, from data already generated in the sales and quoting process.  

Manufacturing is a distinct use case as product complexity and highly customized solutions creates challenges in understanding performance at the variant level for custom and configurable engineered products. That’s why the type of business intelligence reporting tools matter. While some reporting tools are built for general enterprise use, others are best for answering questions more specifically.  

Types of business intelligence reporting tools used in manufacturing 

Manufacturers typically rely on one or more of these four categories of reporting tools for commercial and operational intelligence. 

General BI platforms (Tableau, Power BI, Looker)

General BI platforms are used for enterprise data visualization. These platforms connect to multiple data sources, taking raw data, often through APIs and re-contextualizing it through dashboards.  

Best for:  

• Cross-functional trend analysis 

• Financial reporting 

• Executive dashboards 

• Data consolidation across systems 

 

Pros:  

• Highly flexible 

• Powerful visualization 

• Connects to almost any data source 

• Strong IT governance 

 

Cons:  

• Requires data modeling and dashboard maintenance by technical teams 

• No native understanding of your product or configuration logic 

• Insights lag behind commercial activity depending on how often data is pulled 

• High dependency on IT for non-technical users 

 

The best fit for general BI platforms in manufacturing is enterprise-wide performance reporting and financial roll-ups.  

CRM reporting (Salesforce and similar)

Customer relationship management (CRM) tools offer reporting on sales pipelines and opportunity tracking with built-in reporting on deals, activities, and revenue.  

Best for:  

• Pipeline visibility 

• Sales activity tracking 

• Revenue forecasting at the deal level 

Pros:  

• Native to the sales workflow 

• Good for rep-level performance and pipeline management 

 

Cons:  

• Tracks opportunities and outcomes, but not the configuration decisions behind what sold and why 

 

The best fit for CRM reporting in manufacturing is sales activity management and pipeline reporting, not product or portfolio performance and how that impacts commercial outcomes.  

ERP reporting (SAP, Oracle and similar)

This type of reporting provides manufacturers with operational reporting built into enterprise resource planning (ERP) systems, covering production, inventory, financials, and order fulfillment.  

Best for:  

• Operational performance 

• Supply chain visibility 

• Financial compliance reporting 

 

Pros:  

• An authoritative source for what was ordered and produced 

• Strong financial controls 

 

Cons:  

• ERP reporting shows outcomes after the fact (i.e., what was sold and shipped), rather than the decisions that got you there  

 

The best fit for ERP reporting in manufacturing is operational and financial reporting post-order over pre-sale commercial intelligence.  

What is CPQ-native analytics? 

CPQ-native analytics is analytics embedded directly inside Configure, Price, Quote (CPQ) systems that contextualize the configuration and quoting data already captured in the sales process. It shows both what was quoted and converted into an order and what is explored but does not convert.  

Best for:  Configuration-level commercial intelligence (e.g., win rate by product and variant, margin analysis, quote velocity, portfolio performance, and demand signals from quote activity) 

Pros:  

• No data prep or IT dependency, because insights are available in the commercial workflow 

• Pre-modeled for manufacturing commercial questions and use cases 

• Captures the full context of the deal from customer requirement through to pricing decision 

• Reveals buying intent, early demand signals, and product combinations customers explored that doesn’t show in historical order reports 

• Understanding the why helps recreate profitable deals or portfolio decisions  

 

Cons:  

• Scope is specific to CPQ data, so it’s not a replacement for enterprise-wide BI tools 

 

The best fit for CPQ-native analytics in manufacturing is commercial intelligence for sales, product, and operations teams who need answers about how the behavior and choices made during sales configuration impact outcomes (e.g., which configurations perform best for a particular application or region, which configurations create margin erosion, which configurations lead to longer sales cycles, and more).  

The commercial reporting gap none of these tools solve alone 

Each business intelligence reporting tool covers a slice. BI has breadth but not product context; CRM has pipeline but not configuration detail; ERP has outcomes but not the decisions that drove them.  

Commercial intelligence in manufacturing the full picture of why products win, where margin erodes, and what quote activity signals about future demand lives in the quoting and configuration process  

Manufacturers already generate this data every time a product is configured and quoted.  

According to the Tacton 2026 State of Manufacturing Report, fewer than half of manufacturers currently report at the configuration level. Commercial teams rely on manual exports, Excel analysis, or wait weeks for BI reports to answer questions that should take minutes  It’s an untapped layer of analytics that gives greater context to configuration decisions. 

General BI reporting tools versus self-service commercial analytics 

The limitations of today’s traditional reporting tools drive a shift toward analytics tools built specifically for manufacturing commercial use cases, embedded in the systems teams already use and pre-modeled for the questions they ask.  

Self-service analytics offers pre-modeled, often customizable dashboards that all stakeholders can access without IT requests, separate logins, or the need to contextualize and model data on their own. Insights are available directly in the quoting and commercial workflow and shareable across the organization.   

The best business intelligence and commercial analytics tools for manufacturers 

 The right tool depends on the commercial question you’re trying to answer. Here are the leading options across categories, and what each does best for manufacturing teams.

1. Tacton Portfolio Performance Intelligence

Category: CPQ-native analytics 

Portfolio Performance Intelligence, part of the Tacton Insights & Analytics suite, is configuration-aware commercial analytics embedded directly in Tacton CPQ.  

Best for: Manufacturers with complex, configurable products who need visibility into win rate, margin performance, portfolio demand, and quote velocity.

Key capabilities:  

• Win rate by configuration and variant 

• Margin analysis at the product and option level 

• Quote velocity and deal friction 

• Portfolio usage (which variants are rarely configured vs. high-performing) 

• Early demand signals from quote activity 

• Role-based dashboards for sales, product, and operations 

 

Who it’s for:

• Sales leaders
• Product managers
• Operations and forecasting teams

 

Tacton’s analytics tool is the only tool that understands the configuration context behind commercial outcomes, built for manufacturers where product complexity is the norm. The tool works from your existing configuration logic, pricing logic, and decisions within CPQ.  

Works alongside: existing BI platforms, CRM, ERP, and more.  

 2. Tableau

Category: General BI platform

Best for: Enterprise-wide data visualization and cross-functional reporting

How it works: Tableau connects to multiple data sources via API and native connectors, allowing teams to build custom dashboards and visualizations across any dataset.

Strengths:

• Highly flexible, strong visualization capabilities
• Large ecosystem of integrations
• Good for presenting data to executive and cross-functional audiences
   

Limitations:

• Requires data modeling and dashboard maintenance by technical teams
• Non-technical users depend on IT or analysts to access insights
• No pre-built manufacturing commercial templates
• Insights lag behind commercial activity
   

Ideal customer profile: Large enterprises with dedicated BI or data teams who need flexible, cross-system reporting at scale 

3. Microsoft Power BI

Category: General BI platform

Best for: Organizations already in the Microsoft ecosystem looking for connected reporting across Dynamics, Azure, and Teams

How it works: The platform pulls data from Microsoft and third-party sources via connectors and APIs; business users can build reports within the Microsoft environment they already work in.

Strengths:

• Strong integration with Microsoft products
• Relatively accessible for non-technical users compared to other BI platforms
• Cost-effective for Microsoft-licensed organizations
   

Limitations:

• Best value only for organizations already on Microsoft stack
• Custom manufacturing commercial analysis still requires IT involvement
• No native understanding of product or configuration data
   

Ideal customer profile: Mid-to-large manufacturers running Dynamics CRM or Azure who want reporting consolidated within their Microsoft environment.

4. Looker (Google Cloud)

Category: General BI platform

Best for: Data teams that need a governed, code-first analytics layer across cloud data sources

How it works: Looker uses a proprietary modeling language (LookML) to define data relationships centrally, then surfaces those models to business users through a browser-based interface.

Strengths:

• Strong data governance
• Consistent metrics definitions across the organization
• Good for teams that want a single source of truth across complex cloud data environments
   

Limitations:

• High technical barrier to setup and maintenance
• LookML requires dedicated data engineering resources
• Not designed for operational or workflow-embedded use cases
   

Ideal customer profile: Data-mature organizations with engineering resources who need governed, scalable analytics across large cloud datasets.

5. Salesforce Reports and Dashboards

Category: CRM reporting

Best for: Sales pipeline visibility and rep-level performance tracking within the Salesforce ecosystem

How it works: Salesforce surfaces deal, activity, and revenue data already captured in Salesforce CRM; standard reports are available out of the box with drag-and-drop customization for sales ops teams. 

Strengths:

• Native to the sales workflow
• Accessible to non-technical sales ops users
• Good for pipeline management and forecasting at the opportunity level

Limitations:

• Tracks deal outcomes and sales activity, not what was quoted or configured
• Limited product-level or portfolio intelligence
• Insights are bounded by what Salesforce captures
   

Ideal customer profile: Sales-led organizations that want pipeline and rep performance reporting within their CRM without additional tooling.

6. SAP Analytics Cloud

Category: ERP-integrated BI

Best for: Manufacturers on SAP who need financial, operational, and supply chain reporting in a single environment

How it works: SAP Analytics Cloud connects directly to SAP ERP and S/4HANA data, surfacing operational and financial performance through pre-built and custom dashboards within the SAP ecosystem.

Strengths:

• Deep integration with SAP data
• Strong for financial consolidation and compliance reporting
• Familiar environment for SAP-heavy organizations  

 

Limitations:

• Strong post-order
• Limited visibility into pre-sale commercial activity
• Not designed for quoting, portfolio, or configuration performance analysis
• Value is heavily dependent on existing SAP investment
   

Ideal customer profile: Large manufacturers already running SAP who want analytics consolidated within their existing ERP environment.

Make data-driven commercial decisions with the right tool for complex manufacturing 

Get commercial intelligence to the teams who need it. Tacton Portfolio Performance Intelligence is built specifically for configuration-level commercial analytics that the entire organization, from sales to supply chain, can use to improve win rates, portfolio management, profitability, forecasting, and more.  

Explore Portfolio Performance Intelligence 

Product managers have historically had limited ways to measure how customers interact with configurable products during the sales process. An RFQ can reveal initial customer requirements, but it doesn’t tell the story of how configuration pathways influence the buying process up to the quote. 

If you want to understand customer intent, which configurations contribute to a longer cycle time, or where your initiatives to standardize configurations are working, then you need to access data that has typically been reserved for CPQ owners and sales teams. 

What makes configuration data so valuable for product managers? 

Configuration intelligence is the ability to visualize the full process of the quoting cycle, from initial configuration to the fully evolved solution or quote. CPQ captures customer intent data, rather than just completed transactions, so you can see how a configuration changed over time, or where it stalled or reversed course.  

Product managers gain unique insights from CPQ data, including configurations that were selected but never reached a final quote as well as recurring custom requests or modified product options that require heavy approvals. 

Each of these insights supports the questions you ask on a daily basis, like  

• Which product configurations align most closely with real customer applications? 

• Where is product complexity creating friction for buyers, sales, or engineering?  

• Which recurring “custom” requests should become standardized or modular?  

• Where are sales teams deviating from standard configurations? 

• Which configuration options are consistently linked to longer cycle times? 

• Which product combinations are gaining traction in specific markets or segments? 

 

CPQ data has mostly been used to improve quoting workflows or CPQ models. They’ve been highly underutilized as a strategic tool for product managers. To get to the nuts of bolts of these questions, embedded CPQ analytics is the ideal emerging option for product teams to find direct answers. 

Using embedded, contextualized CPQ analytics solves key pain points for your team. 

Using CPQ data to optimize ETO-to-CTO transitions 

Standardization efforts are usually judged after the fact, by counting custom orders against standard ones or tallying engineering approvals. That tells you the size of the problem, not where it’s coming from. 

Configuration data can tell you which “one-off” requests aren’t actually one-off. For example, you may find that 99% of what looked like unique engineer-to-order requests were the same request recurring, a strong signal that the work belonged in the configurator, rather than an engineer’s desk. Once a recurring pattern is visible, the question changes from “how do we approve this faster” to “what’s the smallest set of guided questions that gets a customer to this outcome without engineering involved at all. 

How to use configuration data to support your modular product strategy 

You need to easily see the configuration process from start to finish and then see that data across all configurations.  

Recurring “custom” requests may indicate opportunities for standardization, missing modules, or evolving market demand. Yet these custom requests may not show original intent in your ERP system. Or, you may not see all of the requests that were not approved during the configuration cycle.  

With configuration data, you can also look at where a standardized component is consistently paired with a nonstandard one that needs approval, a pattern worth investigating even before it shows up across the full portfolio. Is there an opportunity to standardize further, or adjust a standard component to be more useful? 

You can also weigh how often a custom request comes up against how much friction it adds along the way, rather than looking at order counts alone. That’s where modularization or approval steps are causing delays worth fixing. 

Seeing all of the information before the order allows you to identify missing modules and see evolving market needs that doesn’t show up in the final Bill of Materials. In doing so, you can update your portfolio to create more operational scalability and sales efficiency.  

What can configuration approval data reveal about product complexity? 

Today, 55% of manufacturers manage configuration complexity through a mix of guided quoting and downstream engineering adjustments. 

Many teams currently use CPQ data to improve their CPQ configuration models, but this is usually more operational.  

What are the strategic benefits for product and engineering teams in using configuration data to improve these CPQ models and the configuration pathways for buyers and sellers?  

Take, for example, repeated approvals. Frequent engineering approvals for a specific product component or option may reveal opportunities to simplify the configuration model or standardize recurring requests to streamline customers’ buying experience. By analyzing what users select, which options are consistently overridden or approved, and which BOM components are actually included in final products, manufacturers can identify unnecessary complexity in the configuration process.  

For example, if certain guided configuration questions rarely influence the final outcome, they may be creating confusion. If sales requests repeated approvals, this could influence configuration pathways. Certain guided questions may rarely help in conversion. Knowing this creates opportunities to streamline the buying and configuration experience for both sales teams and customers. Product managers can identify what helps convert and what creates operational overhead.   

How can CPQ data help improve product portfolio decisions? 

Configuration data provides a unique way to measure whether your product portfolio is evolving toward a more scalable configure-to-order model. By analyzing recurring custom requests, frequently selected option combinations, and configuration-to-quote conversions, product managers can identify which customer requirements are becoming common enough to standardize. 

That said, configuration data on its own doesn’t tell the whole story. A configuration that stalls or doesn’t convert isn’t automatically a lost cause; it may have supported a different deal, tested a market before it was ready, or served a strategic account for reasons that never show up in a quote. The strongest portfolio decisions come from pairing configuration behavior with the context that only sales, engineering, and account teams have: why a path was taken, and what it was really for. 

Used this way, configuration data is an important place to look to complete the full picture. 

Configuration-aware intelligence is the new commercial imperative for product and engineering teams 

Manufacturers already collect enormous amounts of configuration and quoting data, but most organizations still use it primarily to support quoting operations. Product managers who operationalize CPQ intelligence can reduce portfolio complexity, identify new standardization opportunities, optimize modular product strategies, and align product investments more closely with how customers buy. 

Configuration-aware intelligence also creates a shared view across product management, engineering, sales, and operations. Instead of relying solely on historical orders, engineering feedback, or disconnected reporting systems, teams can make portfolio decisions based on real customer configuration behavior. 

As manufacturers continue to balance engineer-to-order and configure-to-order business models, configuration data is becoming an increasingly important input into product strategy. 

---

 

About the Author

Helena Aurell is a Product Manager at Tacton, where she brings a rare vantage point spanning product, delivery, and the customer side of the business. Having worked with Tacton’s customers across both North America and Sweden, from implementation projects to roadmap and service strategy, her work includes bringing configuration-aware intelligence and analytics to Tacton customers.

According to a 2026 survey of 280 global manufacturers, the top challenge facing sales teams during the quoting process is not technological limitations or internal processes. It’s customization. High-mix products and engineer-to-order solutions make it difficult to quickly create a quote that is accurate and feasible, and leaders report quotation errors as the second most common source of margin erosion by the time of fulfillment.  

Sales and product leaders should take several steps to reduce quoting errors for highly customizable products. First, centralize configuration rules in one system instead of maintaining them in separate systems. Then, ensure that engineering and fulfillment data connects to quoting systems so that quotes reflect real-time product constraints and production capacity. 

Survey respondents show exactly where these errors happen and what they’re doing right to improve quote accuracy.  

What is causing manufacturing quoting errors for sales and engineering teams? 

Manufacturers are largely pointing to customization as a source of its challenges, but customization isn’t the root cause of quoting mistakes. The real causes is in how configuration rules are built, maintained, and passed between systems, and engineer-to-order manufacturers feel this the hardest because nearly every quote requires some degree of custom configuration before it can be priced with confidence. 

Root cause 1: Configuration rules aren’t reused 

Only 33% of manufacturers use consistent configuration logic (the full set of possible product configurations) across sales, engineering, and production. And just 7% define configuration rules (product constraints, attributes, and dependencies) once and reuse that same logic across every system. The other 93% rebuild or re-enter that logic separately in each system. 

Every time a rule has to be recreated instead of pulled from a single source, there’s a new chance for it to be entered wrong, interpreted differently, or left out entirely. It also means most sales reps have no way to validate a configuration in real time at the point of quoting. Without rules centralized in one place, there’s nothing for the quote to check itself against, so a rep can’t know a configuration is invalid until engineering catches it later. Quoting mistakes don’t typically start with the sales rep, but with configuration and pricing rules that were never centralized at the start. 

Root cause 2: Rules for how a product can be built are hard to maintain 

Ninety-three percent of engineering teams report spending moderate to very high effort maintaining configuration rules across systems. That’s not time spent designing new products, but rather time spent keeping systems in sync. Rules can drift at every re-entry point, and outdated logic and maintenance backlogs show up as slow quote turnarounds and last-minute engineering flags on deals already in motion. 

Root cause 3: Complexity is outpacing process 

Today, 67% of manufacturers now report very or extremely complex products. Most quoting processes weren’t built for that kind of complexity, and the ones still relying on manual review, spreadsheet-based configuration, or unscalable rule-based configuration are finding it exceptionally hard to manage those rules as portfolios grow. 

Delivery commitments nobody trusts 

All three root causes converge at the promise made at quote time. Forty percent of manufacturers say they have low confidence in the delivery commitments they make at the time of quoting.  

Where in the quoting process do mistakes happen most? 

Quoting errors concentrate at the handoffs, such as sales to engineering, engineering to production, and quote to BOM. Each transition is a point where configuration logic, part availability, and delivery expectations have to pass between teams working from different systems and sometimes different versions of the truth. 

 

• Quoting invalid configurations: combinations that look valid to a rep but violate an engineering constraint are not always automatically flagged in the quoting system. If that review doesn’t happen, an unbuildable configuration goes out quoted. 

• Quoting prices or dates without a parts-availability check: Since only 30% of supply chain teams find it easy to support sales with parts availability, reps are often pricing and committing to dates without knowing whether the parts exist to hit them. 

• Quoting from outdated configuration logic: Currently, 21% of manufacturers propagate engineering changes automatically. A rule can change on the engineering side and a rep can still be quoting against the old version due to poor configuration management. 

• Manual BOM creation errors at handoff. 23% of manufacturers say they auto-generate manufacturing BOMs from sales quotes. The BOM that production builds from is usually hand-created separately from what was quoted, opening the door for the two to diverge. 

How to reduce manufacturing quoting errors  

Today, 42% of manufacturers expect 11–20% of their sales and engineering workforce to retire within 5–10 years. Dependency on tribal knowledge, as well as growing demand for product customization in the market, makes potential quoting errors an increasingly relevant challenge. These steps for reducing errors go deeper than investing in CPQ, but change the way that you think about how configuration logic and engineering knowledge is captured and managed in your business.

1. Define configuration rules once, reuse everywhere 

Audit where your configuration logic currently lives, likely scattered across CPQ, engineering documents, and ERP, and consolidate it into a single repository that every system pulls from, including CPQ, PLM, and PDM. Assign one owner (typically engineering) to maintain that repository, so no one downstream is ever working from a recreated or re-interpreted version of the rule.  

2. Connect CPQ, engineering, and fulfillment on one source of truth 

Map your current change-propagation process. When engineering updates a rule, trace how long it takes to reach CPQ and fulfillment, and how many of those steps are manual. Replace manual notification so that when your configuration logic repository has changes, those changes are pushed to every connected system the moment they’re made. Even a partial integration, starting with your highest-volume product line, closes a meaningful amount of exposure. 

3. Give sales real-time visibility into parts availability and delivery feasibility 

Connect your fulfillment and sales systems in both directions, not just a one-way data feed. Integrate parts-availability data directly into the quoting tool, so a rep sees manufacturability as they quote, and route quote activity back to supply chain, so fulfillment can see demand forming before it becomes a committed order. Only 30% of supply chain teams currently find it easy to support sales with parts availability, and closing that gap starts with visibility, even before full automation is in place.  

Manufacturers further along this path are beginning to connect quote configurations directly to a manufacturing BOM, removing the manual translation step between what’s quoted and the unique, factory-specific instructions needed for fulfillment. 

4. Use guided quoting to remove manual configuration review as the default path 

Turn technical constraints and configuration logic into business logic. Build guided workflows for sales based on product attributes or common configuration use cases that then present only valid configuration paths to the rep, using a constraint-based configuration engine. Reserve manual engineering review for true exceptions (configurations outside the standard rule set) rather than routing every quote through it by default. More than half of manufacturers have already shifted to this model, pairing guided quoting with exception-based engineering review instead of blanket manual checks. 

5. Track configuration-level performance so error patterns surface early 

Set up reporting that flags which specific configurations generate the most rework, margin loss, or engineering escalations, and review it on a recurring cadence (monthly, not annually). Feed what you find back into your process, so a configuration causing repeat problems or delays can be corrected or factor into future discussions about product and quoting needs. 

Improve quote and order accuracy with key lessons from global manufacturing leaders 

Manufacturers who reduce quoting errors in spite of heavy customization connect configuration rules, engineering, and fulfillment instead of managing them apart. For a deeper look at how manufacturers are addressing configuration complexity, margin erosion, and quoting accuracy at scale, explore the full findings in Tacton’s 2026 State of Manufacturing report. 

Download the State of Manufacturing report 

 

Frequently Asked Questions

1. How fast should a manufacturer respond to an RFQ?
Digitally mature manufacturers respond to RFQs within 48 hours 64% of the time, compared to 47% across manufacturers overall. Only 15% respond in under 24 hours. Response speed matters, but Tacton’s 2026 research found it doesn’t solve the underlying quoting problem on its own. A fast quote built on fragmented configuration rules is still a quote at risk of being wrong. 

2. How does buyer experience affect quoting accuracy?
When buyers struggle to articulate what they actually need or product information is incomplete, sales teams are more likely to quote based on incomplete or misunderstood requirements, which introduces errors before a rep completes the configuration. 

3. Does workforce turnover contribute to quoting mistakes?
It can. 42% of manufacturers expect to lose 11-20% of their sales and engineering workforce to retirement within the next 5-10 years. When configuration knowledge lives in a person’s experience rather than a documented rule set, that knowledge leaves with them. 

4. Is manual quoting still viable for engineer-to-order manufacturers?
Manual quoting can work at low volume, but it doesn’t scale well against rising complexity. 67% of manufacturers now report very or extremely complex products, and manual review struggles to keep pace as the number of configuration variables grows. 

5. What’s the actual cost of an inaccurate manufacturing quote?
Beyond the immediate rework, inaccurate quotes erode margin over time. 62% of manufacturers cite margin erosion as at least a moderate issue between quote and delivery, with 51% pointing to people as the source and 38% pointing to tools and systems. The cost isn’t always visible in a single deal — it shows up cumulatively across a portfolio. 

Customer demand for personalization is the new norm, and the path to growth and scalability increasingly depends on offering configurable products (configure-to-order with engineer-to-order exceptions) without errors. However, that configuration complexity leaves room for quote and order inconsistencies that flow downstream and slow operations, increase costs, and put pressure on margins.

While ERP and PLM systems are valuable for managing orders and inventory or product versions, respectively, these systems alone were never designed with the configurable product as their primary focus.  

When configuration logic is not the focus, it’s harder to scale and sell products that are different every time.  

The configurable product as the center of manufacturing 

You have systems of record for customers, products, and operations, but you may not have a singular governed source for how your configurable products actually work.

The limitations of existing systems 

The configurable product is the common thread connecting every department. In many organizations, the knowledge that defines how products can be configured lives across engineering documents, spreadsheets, ERP records, tribal knowledge, and individual experts. Manufacturers have traditionally organized their systems around functions. ERP manages operations. PLM manages product data. CRM manages customers and their requirements. 

A company may have world-class ERP and PLM systems but still struggle to answer a simple customer question: “Can we build this?” because the configuration knowledge isn’t centralized.  

In practice, this means creating a single place for governing the configuration logic, rules, and dependencies that determine how products can be configured, sold, and manufactured.

Putting the configurable product at the center means treating that product logic as a shared business asset. Instead of each department maintaining its own copy of configuration knowledge, the same rules and relationships are defined once and shared across sales, engineering, manufacturing, and operations.

The cost of de-centering configuration 

Manufacturers are looking for ways to standardize what can be standardized while still meeting unique customer requirements. Without a structured way to manage configuration logic with the potential for hundreds or thousands of configured combinations, complexity grows beyond the capabilities that the business and its systems can manage. For example, an ERP may give the order as a line item but not have the capability to show the full configuration.  

The need for a shared understanding of configurable products is becoming more urgent. In Tacton’s State of Manufacturing 2026 research, manufacturers identified managing increasing product complexity as one of the most significant challenges impacting both operational efficiency, growth, and margin. At the same time, organizations reported ongoing difficulties coordinating information across sales, engineering, and manufacturing teams, highlighting how product knowledge often remains fragmented across the business. 

What is the competitive advantage? 

Consider a manufacturer that receives a request for a highly customized product. On paper, the opportunity is attractive. The customer is willing to pay a premium, and the order could be highly profitable. Without engineering’s configuration knowledge and constraints encoded upfront, sales can’t answer that question alone, and the order stalls waiting on a per-deal engineering review.

When the logic behind configurable products is highly complex and fragmented, answering those questions can take days or weeks. Meanwhile, competitors with a centralized understanding of their product configuration logic respond quickly. They know what is possible, what is manufacturable, and what can be delivered profitably.  

Today, 62% of manufacturers said they experience moderate to severe margin erosion starting at the quote cycle through order fulfillment, highlighting the financial impact on those who are unable to respond efficiently and effectively.  

The role of ERP and PLM in a configuration-centric enterprise 

The argument for a system that centralizes configuration is not an argument against existing systems. 

ERP and PLM remain essential. PLM excels at product data management, documentation, workflows, and governance. ERP excels at operational execution, financial processes, procurement, inventory, and manufacturing operations. Both are foundational systems. 

However, most ERP and PLM systems were originally designed around fixed products and fixed structures. 

As organizations begin managing thousands, or millions, of potential product combinations, the configuration logic itself becomes a separate challenge that neither system was specifically designed to solve. 

A configuration-centric layer adds the configuration logic that governs how configurable products can be assembled, sold, and manufactured while complementing existing ERP and PLM systems. Together, these systems create a complete digital foundation.

How to make the configurable product your central focus

Manufacturers organize their systems around function, not around the product itself: ERP owns operations, PLM owns product data, CRM owns the customer relationship. Centering the configurable product means inverting that logic, building around the one asset every function actually depends on, rather than letting each function define its own version of it.

Many manufacturers already have CRM, ERP, and PLM systems in place. The next step is not replacing them, but connecting them through a shared understanding of the configurable product. 

The ideal starting point is in defining configuration possibilities.  

In practice, that looks like three shifts:

A single definition of “buildable.” Instead of sales, engineering, and manufacturing each maintaining their own version of product configuration knowledge, that knowledge should be managed in one place and shared across every function. Every other system references it rather than recreating it.

Changes that propagate instead of requiring re-entry. When a configuration rule changes, whether from a new option, a supplier substitution, or an engineering fix, that change should reach every dependent system on its own. If a single change still requires someone to manually update it in three or four places, there isn’t actually a single source of truth yet, just multiple copies of an old one.

Customer requirements should remain connected to the configurable product throughout the lifecycle, not stop at the sales order. When the manufacturing BOM is generated automatically from the configured product definition rather than rebuilt by hand, every part and step on the shop floor stays traceable back to the customer requirements that drove it while remaining aligned with approved configuration changes. The same configuration knowledge that defines what is manufacturable can also be used to validate what is sellable. Sales, engineering, and manufacturing all work from the same configuration knowledge rather than maintaining separate copies.

Bring configuration into focus

When manufacturers centralize configuration knowledge, the entire manufacturing lifecycle feels the impact. 

Sales can generate quotes faster with confidence that configurations are buildable. Engineering is less burdened by repetitive work and has better control over product complexity and configuration management across systems. Manufacturing gets cleaner handoffs, with orders that reflect valid configurations and Bills of Material that reflect proper manufacturability.  

But most importantly, companies see improved margins due to those cleaner handoffs. Successful companies can confidently tell customers “yes”, because they understand their products deeply enough to know what is possible, what is manufacturable, and what remains profitable. 

Learn more about building an effective smart factory.

 

---

About the Author

Hanna Kemppainen is SVP Executive Projects at Tacton. She previously led Variantum as CEO, a Finnish software company whose configuration management solutions helped manufacturers manage product configuration truth from engineering through delivery. That work now sits at the center of Tacton’s Buyer-Centric Smart Factory, connecting what’s sold to what’s engineered and built. At Tacton, Hanna leads integration efforts to bring teams, systems, and customers onto one connected platform.

Can you explain why one deal wins while another—nearly identical—loses? 

Right now, you’re likely tracking win rates, revenue, and pipeline. But can you pinpoint which configuration decisions or configuration changes are actually driving those outcomes? 

More than half of manufacturers can’t, because that intent-based insight lives at the configuration level where quoting activity happens each day. 

Your data is spread across ERP, CRM, and BI tools, making it difficult to visualize and contextualize how specific configuration choices across the sales cycle impact commercial performance. 

Tacton Insights & Analytics gives you direct visibility into configuration-level data within Tacton CPQ. Portfolio Performance Intelligence, the first add-on capability within Tacton Insights & Analytics, helps you understand how configuration inputs drive win rates, margin, and sales velocity, and guide your business decisions faster. It’s a comprehensive analytics tool that sales, product managers, operations, and more can use to improve commercial outcomes. 

What is Portfolio Performance Intelligence?

Portfolio Performance Intelligence is a configuration intelligence solution embedded within Tacton CPQ that helps manufacturers understand how product configurations perform in the market. 

 

Rather than reporting only on products sold or revenue generated, it connects configuration choices, customer requirements, and quoting activity directly to business outcomes. 

This allows manufacturers to answer questions such as: 

• Why does one configuration win while another loses?  
• Which product variants drive the highest margins?  
• Which custom requests should become standard offerings?  
• Where is complexity slowing down sales cycles?  
• What products and options do customers typically buy together?

 

By analyzing configuration-level data directly within the quoting process, you can dive deeper into the decisions and behaviors that influence performance long before an order is placed. 

What does configuration data tell you about your business?  

Unlike ERP, CRM, and traditional BI tools, configuration data captures how customers build solutions, which options they select, what they modify, and how requirements evolve throughout the sales process. 

This provides a unique view of customer intent and product performance that is often difficult to uncover through traditional reporting alone. 

Portfolio Performance Intelligence helps manufacturers understand: 

• Which configurations consistently win deals—and which don’t  

• Which product features, options, and requirements contribute most to win rates  

• Which product variants create complexity without driving revenue  

• Which configurations generate the strongest margins  

• Where approvals, revisions, or customization slow the sales process  

• Which products and options are most frequently purchased together  

• How buying behavior differs across industries, applications, regions, and channels  

• Which recurring custom requests may indicate opportunities for standardization or modularization 

 

Why should you analyze your CPQ data with Tacton Portfolio Performance Intelligence?

Improve sales performance and win rates

Understand which configurations, product features, and solution combinations perform best across different industries, applications, regions, and customer segments. 

By connecting configuration choices to win rates, manufacturers can identify what drives successful outcomes and replicate those patterns across the business. 

Optimize product portfolio decisions

Move beyond product-level reporting to understand performance at the configuration level and manage complex portfolios. 

Identify underperforming variants, recurring customer requests, and opportunities to simplify portfolios, reduce complexity, and prioritize innovation based on actual market demand. 

Measure standardization and CTO progress

Track approval frequency, custom request patterns, engineering involvement, and sales cycle length across configurations. 

This helps manufacturers understand whether standardization, modularization, and CTO initiatives are reducing complexity and improving scalability. 

Improve planning and demand visibility

Configuration data reveals how customers build complete solutions, which says much more than just which products they purchase. 

By analyzing common product combinations, option selections, and configuration trends, manufacturers gain deeper insight into demand patterns and customer preferences. 

Accelerate business decisions

Answering questions about product performance often requires data from ERP, CRM, BI, and engineering systems. 

With configuration intelligence embedded directly within the quoting process, teams can access the context behind customer decisions without waiting for custom reports or analyst support. 

How to use Tacton Portfolio Performance Intelligence

Tacton Insights & Analytics is embedded directly within Tacton CPQ. Portfolio Performance Intelligence gives you a head start on analyzing your product and sales performance by doing much of the upfront data work for you.  

Portfolio Performance Intelligence gives you immediate access to configuration-level performance data without the complexity of traditional analytics projects. 

• Embedded directly within Tacton CPQ  

• No external BI tools or data modeling required  

• Customizable, purpose-built dashboards (from easy-to-use templates) designed around manufacturing use cases  

• CPQ-native data model from your CPQ activity that already understands your products, variants, and rules  

 

Once you’ve configured your dashboard to include the information you most want to track, you’re ready to start analyzing and sharing insights across your teams.  

This the first add-on module, available as a paid feature. Additional capabilities, including sales velocity analysis and expanded dashboards, will be rolled out in future iterations. 

Start using your CPQ data to make better decisions  

Your CPQ already captures the data. Now you can finally use it to understand what drives performance and act on it.  

Schedule time with Tacton to see how Insights & Analytics can help you identify what’s working, fix what isn’t, and improve sales, margin, and product strategy.  

Schedule a Demo

Learn More About How to Use Portfolio Performance Intelligence

Manufacturers are good at reporting on what happened. You may already run detailed commercial analytics: win rates by product line, discount rates by rep and region, quote-to-order conversion, sales cycle length by product category, engineering change order volume, number of approvals, NPI adoption after launch.  

These are the reports that mature commercial and finance teams rely on, and they’re genuinely useful. However, they all share similar blind spots. They tell you what happened, but not the context and decisions behind why. If you have a longer sales cycle with complex quoting processes, the why almost always starts with a decision made during configuration and quoting. 

What is configuration awareness? 

Configuration awareness is the ability to capture and retain the full context of every configuration decision made during the quoting process, rather than just the final order.  

That includes: 

• Which options a customer selected, adjusted, or removed 

• Which configurations required engineering approval or override 

• Which combinations were explored but ultimately abandoned 

• How a solution evolved across multiple quote iterations 

 

When selling highly configurable products (e.g., high-mix industrial machinery, engineer-to-order systems, configure-to-order equipment with complex dependencies), this context is generated every time a quote is built. Most businesses generate it. Very few can see it.  

What is configuration intelligence? 

Configuration intelligence is what happens when that configuration data is connected to business outcomes (e.g., win rates, margin, product performance, demand patterns) and made available for analysis. 

Where configuration awareness is about capturing context, configuration intelligence is about using it to answer the questions that drive commercial performance:  

• Why do certain configurations win in some markets but not others? 

• Which product variants are generating margin, and which are eroding it? 

• What demand is building before orders arrive? 

• Where is complexity slowing down your sales cycle? 

 

The difference between the questions you can answer now and the questions you can answer with configuration data give you a deeper understanding of how to change business outcomes for the future.  

How do you get configuration-level data? 

Configuration intelligence requires a CPQ platform that is purpose-built to model complex, configurable products. Manufacturers can use data contextualized by CPQ, such as configuration parameters and pricing logic, to capture not just what was quoted, but the full decision context behind it. 

Generic CPQ platforms built for transaction management flatten or lose that context before it can be analyzed. Manufacturers with high product complexity, deep configuration logic, and engineer-to-order or configure-to-order sales motions need a CPQ foundation that holds that context natively, with an embedded analytics layer built on top of it. 

How each team in the manufacturing lifecycle can use configuration  data 

The questions configuration intelligence can answer look different depending on who’s asking. Here’s what it unlocks across the manufacturing business. 

Sales and commercial teams: understand what actually wins 

Your goal as a sales leader is to achieve consistent commercial performance and win rates across regions, rep teams, and market segments. 

Your teams know that winning often comes down to which configuration was recommended and how it fit the prospect’s business goals, not just how well a rep managed the relationship. Configuration data makes the patterns behind those wins explicit and replicable. 

By cross-referencing product attributes with industry, application, and geography, teams can see that a specific motor configuration, for example, consistently wins in industrial applications but underperforms in commercial ones — or that a feature set that converts in North America struggles in Europe.

 

That analysis translates directly into commercial performance:

• Which configurations drive the strongest win rates by market or segment
• Where long sales cycles or high discount rates are tied to specific product decisions
• Which premium configurations convert quickly versus which ones stall
• How product mix connects to revenue outcomes across the team

 

Product and engineering: build an efficient portfolio that performs 

Your goal is to develop a product portfolio that is profitable, manageable, and aligned to what customers actually want. 

In high-mix manufacturing, individual variants within a product family can quietly drag on margin, create engineering overhead, or contribute to lost deals, while the family looks successful in aggregate. Configuration data provides the granular visibility needed to refine your portfolio based on customer buying behavior. 

Imagine that a product family generating strong revenue overall may contain specific options that are rarely selected, consistently appear in lost deals, or trigger repeated engineering involvement. Configuration data surfaces those patterns and shows where recurring custom requests point toward gaps in the standard portfolio. 

Configuration data also enables direct measurement of CTO and standardization progress, something order data and approval counts can’t do alone. If customers repeatedly request the same customization, that’s a signal to create a standard module.

If certain configurations consistently trigger approvals or extend sales cycles, they’re candidates for redesign or retirement. 

 

Across both decisions, configuration data makes it possible to:

• Identify which variants create value and which add complexity without return
• Surface recurring custom requests that signal roadmap gaps
• Measure where CTO and standardization efforts are succeeding and where they aren’t
• Make portfolio investment decisions based on actual customer behavior, not aggregate sales data

 

C-suite and finance executives: connect configuration decisions to margin 

Profitable growth is created by understanding not just where revenue is coming from, but where margin is being made or eroded.  

Two deals can look identical on the revenue line while having very different profitability profiles. One closed cleanly. The other looped through approvals, pulled in engineering, and was discounted twice. That difference started during quoting — and standard financial reporting can’t see it.  

Imagine that configuration data from your company’s CPQ activity. It shows which specific product attributes and variants are associated with high discount rates, engineering involvement, or extended approval cycles, therefore connecting those behaviors directly to margin outcomes before they accumulate on the P&L. 

 

For commercial, operational, and finance teams, that means:

• Identifying which configurations drive profitable growth vs. erode margin
• Understanding the relationship between product decisions, discount behavior, and deal profitability
• Informing pricing strategy with configuration-level performance data
• Catching margin erosion at the configuration level, not the P&L level

Operations and supply chain: plan around what customers actually  build 

Production and inventory planning should anticipate early demand and emerging buyer behavior rather than simple order history. 

For operations teams in complex manufacturing, order data is a lagging indicator. Configuration data, or how configuration decisions across the sales cycle, moves the signal earlier and at a more useful level of detail. 

Take, for example, which motors, controls, accessories, and service options customers consistently select alongside a given machine. Which combinations are gaining frequency in quotes months before they show up in orders. Where component-level demand is quietly building.

 

That earlier visibility changes what’s possible in planning:

• Anticipate component-level demand based on configuration patterns, not just order history
• Plan inventory around complete solution configurations, not individual SKUs
• Reduce the gap between demand signal and production response
• Build forecasting models that reflect how customers actually configure

 

Improve commercial performance with your configuration data  

Each function is asking different questions, but they share the same underlying problem. The most valuable signals about customer intent, product performance, and commercial outcomes are generated during the configuration and quoting process, and most manufacturing businesses have never had a structured way to see them. 

Configuration intelligence allows your teams across the business to connect the context that already exists inside your quoting process to the business outcomes each team is responsible for. When that connection is made, the questions that used to take weeks to answer, or simply went unanswered, become part of how every team operates. 

Portfolio Performance Intelligence is built natively into Tacton CPQ, giving product, sales, commercial, and operations teams direct access to configuration-level insights  without additional tools, data exports, or IT requests.  

Learn More

Visibility is the foundation of effective demand forecasting and production planning. Manufacturers can only plan for the demand they can see, and supply chain and production teams often lack early insight into the specific configurations, features, and option combinations customers are requesting. Without that level of visibility, supply chain teams may miss emerging demand patterns, inventory risks, and component dependencies that directly impact service levels and profitability. 

Currently, 50% of manufacturers report that they’re able to track demand forecasting and inventory planning. However, only 45% track configuration decisions made before the order, and 30% or less track feature and option demand or the most or least quoted configurations. It’s an overlooked layer of data that can increase efficiency much earlier for high-mix, low-volume production.  

The limits of traditional forecasting models 

Traditional demand forecasting and production planning looks to historical orders to understand future demand. While it’s a reliable source of information, it only provides information after the order is made, rather than emerging demand trends that can improve lead times and margin.  

How can supply chains forecast demand for configurable products? 

Highly configurable products make production planning even more challenging. Supply chain and operations leaders must account for thousands or millions of possible combinations, constant changes in customer requirements, and regional and customer-specific preferences against a growing portfolio.  

Supply chains forecast demand for configurable products most effectively when they combine historical order data with configuration, quote, and feature-level demand signals. 

Quote activity helps supply chain teams identify growing feature demand and potential component constraints weeks or months before those changes appear in order history or a manufacturing Bill of Materials. 

Configuration-level insight helps answer: 

• Which options are appearing more frequently in quotes?  

• Which premium configurations are gaining traction but haven’t yet converted to orders?  

• Which feature combinations are being evaluated by customers?  

• Which regional preferences are emerging?  

• Which products are being configured but abandoned?  

• Which new product variants are generating interest? 

• Which product variants are increasingly bought or combined together? 

 

Those insights can significantly improve forecasting, inventory planning, supplier collaboration, and production scheduling. 

Why configuration decisions matter for supply chain leaders 

Imagine you’re selling commercial HVAC systems. 

Your forecast accurately predicts demand for 1,000 units next quarter. Inventory levels are healthy, and procurement has ordered components based on historical demand patterns. Yet production delays begin to increase. 

Looking at order volumes alone, demand appears stable. But configuration-level analysis reveals something important: 

• Customers are increasingly pairing a premium control system with a high-efficiency compressor package.  

• When those options are selected together, they require a specialized circuit board sourced from a supplier with a 16-week lead time.  

• The circuit board isn’t a problem when the options are ordered separately. It becomes a bottleneck when the combination becomes more popular.  

• Quote activity shows this combination appearing in nearly twice as many opportunities as six months ago, but supply chain teams weren’t tracking configuration trends closely enough to spot the shift.  

 

The manufacturer forecasted how many HVAC systems customers would buy. They didn’t understand how customer preferences were changing within those systems. They couldn’t see that six months before orders increased, the premium control system and high-efficiency compressor package began appearing together in a growing percentage of quotes. 

As a result, a single constrained component delayed production. Inventory accumulated for components associated with declining configurations. Procurement reacted after shortages appeared rather than planning ahead. Delivery commitments became harder to meet.  

How to improve demand forecasting accuracy

If you want to improve forecasting accuracy, start by looking beyond completed orders. Earlier demand signals, such as the decisions made during the sales configuration and quoting process, provide insights into customer preferences before they affect inventory, procurement, and production planning, giving teams more time to make better decisions and see potential risks.

1. Connect commercial and operational data

Improving demand forecasting starts with connecting data across the customer journey, not only in orders, but also quotes, configuration decisions, inventory, and production data. Just as the quoting process should have manufacturability embedded in configuration constraints, the quoting process should also provide downstream manufacturing teams with important quote and configuration data. This provides visibility into changing customer preferences before they affect procurement and production schedules.

2. Track demand at the configuration level

Only 27% of manufacturers can track metrics such as most quoted configurations, fastest-growing options, and feature adoption trends to identify shifts earlier. Embedded analytics that contextualize your CPQ data can show you which configurations require longer sales cycles or what is explored but doesn’t often convert. 

3. Measure business impact, not just demand

Not all demand contributes equally to profitability. Analyze which configurations generate the highest revenue, margins, and conversion rates alongside which products create the most operational complexity. This helps align supply chain investments with business outcomes. 

4. Identify emerging supply chain risks 

Look for demand patterns that could create future constraints. Which growing configurations rely on long lead-time components? Which option combinations require specialized resources? Understanding these relationships helps teams anticipate bottlenecks before they impact delivery performance.

5. Continuously refine forecasts with performance data

Demand forecasting should be an ongoing process. Regularly review metrics such as quote-to-order conversion rates, feature and option demand trends, most and least quoted configurations, and forecast accuracy. These insights help you improve planning decisions while balancing inventory, capacity, and profitability. 

Demand Forecasting for Manufacturing 4.0: From Product Forecasts to Configuration Intelligence 

Demand forecasting in manufacturing is evolving from product-level forecasting to configuration intelligence. Manufacturers that incorporate configuration, feature, option, and quote data into forecasting processes gain earlier visibility into demand shifts and can make more informed inventory, procurement, and production decisions. 

Manufacturers need configuration-level demand intelligence, because historical order data doesn’t reveal the full picture of emerging customer preferences, future component demand, or changing configuration trends. 

Learn how manufacturing leaders are forecasting today in our State of Manufacturing Report and discover how Tacton helps manufacturers turn configuration and quote data into actionable forecasting and planning insights.  

Engineering teams are spending too much time and effort maintaining product configuration models. 

According to Tacton’s 2026 State of Manufacturing report, 93% of engineering teams report spending moderate to very high effort maintaining configuration logic across systems. Meanwhile, 81% of manufacturers report moderate to extremely high effort maintaining CPQ models. 

The impact of engineering change orders (ECOs) on quoting accuracy, as well as configuration maintenance across systems like PLM, CPQ, ERP, and MES, is becoming a significant drain on engineering resources. This comes in the form of rule updates, validating product changes, troubleshooting inconsistencies between systems, and ensuring changes are reflected to sales and the supply chain.  

As manufacturers continue to expand configurable product portfolios, finding a more efficient way to manage ECOs and configuration maintenance is becoming increasingly important for responsiveness and continued innovation. 

Why do engineering change orders (ECOs) increase configuration maintenance? 

Every engineering change order creates downstream work. A component replacement may affect product compatibility. A design update may introduce new constraints. A pricing change may require updates to product configurations. A new feature may impact manufacturing processes or sales options. 

Only 33% of manufacturers currently maintain consistent configuration logic across sales, engineering, and production. Even fewer automatically propagate engineering changes across systems. For most manufacturers, configuration knowledge is still being recreated, translated, or manually synchronized across departments. 

Manufacturers don’t have the connectivity to ensure every system, department, and process reflects that change consistently. 

Over time, configuration maintenance can become one of the most resource-intensive aspects of managing product complexity and changes. 

How do you manage engineering change orders in CPQ without breaking open quotes? 

This is one of the most common challenges manufacturers face. 

Sales teams may have active opportunities in progress when an engineering change order is introduced. If product logic is fragmented or configuration models are difficult to maintain, an ECO can create confusion about which configurations remain valid, which pricing rules apply, and whether existing quotes need to be reviewed. 

This leads to manual intervention from engineering teams, delays in the quoting process, and increased risk of errors. 

The most effective approach is ensuring configuration knowledge is managed consistently and changes are governed centrally through a configuration management platform or environment that automatically propagates changes across traditional manufacturing systems, like CPQ, MES, or PLM.  

When engineering changes are reflected through a shared configuration model rather than maintained independently across multiple systems, manufacturers can reduce the risk of inconsistencies that affect active quotes.  

How constraint-based CPQ reduces configuration maintenance 

Many manufacturers assume that increasing product complexity requires increasing the number of configuration rules. 

In reality, the amount of maintenance required often depends on how products are modeled. 

Traditional rule-based approaches typically require organizations to manage growing numbers of dependencies, exceptions, and configuration rules as product portfolios expand. Every engineering change may require additional rules or updates across numerous rules, increasing maintenance effort and introducing risk. 

CPQ with constraint-based configuration takes a different approach. 

Rather than relying on an ever-growing web of rules and exceptions, constraint-based models use product relationships to determine valid configurations. When product knowledge is managed through a centralized 150% BOM (representing all valid product options and components in a single structure), engineering changes can be applied to the underlying product model and reused across sales, engineering, and manufacturing processes, reducing the amount of configuration maintenance required as products evolve. 

This provides several advantages when managing engineering changes: 

• Fewer rules to maintain 

• Reduced model complexity 

• Easier implementation of product updates 

• Less risk of conflicting logic 

• Greater confidence that configurations remain valid after changes 

For manufacturers managing large numbers of ECOs, reducing rule maintenance within CPQ can significantly improve engineering productivity while helping ensure configuration accuracy. 

What Is the Best Way to Manage Configuration Changes Across Systems? 

In addition to maintaining a CPQ model, managing ECOs effectively requires a consistent approach to configuration management across the entire product lifecycle. 

Leading manufacturers increasingly focus on three principles: 

Centralize configuration knowledge 

Many manufacturers maintain product structures, configuration rules, BOM logic, and engineering constraints in multiple systems. Every ECO then requires updates in several places, increasing the risk of inconsistencies and rework. A centralized source of product knowledge helps engineering teams manage changes once and propagate them downstream, reducing maintenance effort while improving alignment across sales, engineering, and production.

Build for reuse

Only 7% of manufacturers currently define configuration rules once and reuse them everywhere. Reusable product structures and shared configuration logic reduce the effort required to maintain product models as products evolve. 

Propagate changes efficiently 

When engineering changes can be automatically propagated to production systems, organizations spend less time maintaining duplicate information and more time improving products and processes. 

Engineering change orders will continue. Engineering maintenance pains don’t have to. 

Manufacturers are unlikely to see fewer engineering change orders in the future. 

Product portfolios continue to expand. Customer requirements continue to evolve. Product complexity continues to increase. 

What will separate leading manufacturers is how effectively they manage configuration maintenance. 

The State of Manufacturing report reveals that most organizations still have significant opportunities for improvement. Nearly every engineering team reports substantial effort maintaining configuration logic, while only a small percentage of manufacturers have established reusable, consistent approaches to configuration management. 

The organizations making the most progress recognize that engineering change orders and configuration maintenance are not the same thing. 

While ECOs are unavoidable, excessive maintenance effort is often the result of fragmented systems and disconnected configuration processes. 

By centralizing configuration knowledge, reducing rule maintenance, and adopting approaches such as constraint-based CPQ, manufacturers can manage engineering changes more efficiently and free engineering teams to focus on innovation instead of maintenance. 

Read the full report