CPQ Guide

Tag: quoting

  • CPQ vs CRM: Roles, Data, and Boundaries in Manufacturing

    In manufacturing, CRM and CPQ solve different problems. A customer relationship management system records accounts, contacts, leads, opportunities, activities and sales pipeline information. A configure, price, quote system defines which product combinations are valid, applies engineering and commercial rules, calculates prices and costs, and produces a quote for the selected configuration.

    The boundary is important because a CRM is not normally a product rules engine, and a manufacturing CPQ system is not normally the system of record for customer relationships. CRM manages who the customer is, what opportunity exists and where the deal stands. CPQ manages what can be sold, how it must be configured, what it costs and what should be quoted.

    For example, a CRM may contain an opportunity for a food-processing company that needs a pump skid. CPQ can use the required flow rate, pressure, fluid characteristics, materials, motor specification, controls and compliance requirements to validate a pump package, calculate the price and generate a configured bill of materials (BOM). The CRM can then store the opportunity, quote status, customer communications and expected close date while CPQ remains responsible for the product-specific quote.

    These systems are complementary rather than interchangeable. The most effective architecture connects them while preserving clear ownership of product, customer, pricing, engineering and production data. This manufacturing CPQ guide provides the broader context for how CPQ supports complex configurable products.

    What is CRM in manufacturing?

    CRM, or customer relationship management, is software used to manage commercial relationships and sales processes. In manufacturing, CRM commonly stores customer accounts, sites, contacts, sales activities, opportunities, sales stages, territories, forecasts and communications.

    A manufacturing CRM may also contain information about installed equipment, dealer relationships, service opportunities, application requirements and historical transactions. However, it does not automatically understand the engineering validity of every product option or calculate the manufacturing consequences of a configuration.

    Typical CRM responsibilities

    • Managing accounts, contacts, prospects, dealers and customer locations.
    • Recording leads, opportunities, activities, meetings, calls and emails.
    • Tracking sales stages, probability, expected revenue and forecast dates.
    • Assigning opportunities to sales representatives, sales engineers or channels.
    • Managing customer communications and commercial approvals.
    • Providing context for renewals, service agreements, installed equipment and account history.
    • Launching or displaying quotes that were created in CPQ.

    CRM is therefore primarily relationship- and opportunity-oriented. It may display product and quote information, but those records are often sourced from product, pricing or CPQ systems rather than being mastered entirely in the CRM.

    What is CPQ in manufacturing?

    CPQ means configure, price, quote. Manufacturing CPQ is software that models configurable products and applies rules to produce technically valid and commercially accurate quotes. Depending on the platform and implementation, it may also calculate engineering values, generate a configurable BOM, automate CAD outputs, create drawings or pass manufacturing data to enterprise systems.

    Manufacturing CPQ is broader than generic sales quoting because the selected options can affect engineering, purchasing, production, installation and compliance. A configuration is not simply a collection of selectable features. It may contain dimensions, capacities, materials, ratings, interfaces, tolerances, components, labor assumptions and constraints.

    For example, a valve configuration may depend on pressure class, body material, trim material, connection type, temperature range, actuator size and certification. A rule may prevent a particular elastomer from being selected when the process temperature exceeds its rating. Another rule may require a specific actuator or mounting arrangement for a defined torque range.

    The product configuration guide explains product models, options, dependencies, constraints and validation in more detail.

    Typical manufacturing CPQ responsibilities

    • Presenting guided selling questions or engineering inputs.
    • Applying rules that prevent invalid or unsafe combinations.
    • Performing calculations for sizing, capacity, load, flow, power or dimensions where supported.
    • Selecting components and applying configurable BOM logic.
    • Calculating material, labor, overhead, cost, margin, discounts and selling price.
    • Supporting standard configure-to-order (CTO) products and, in some systems, engineer-to-order (ETO) workflows.
    • Generating quote documents, configuration summaries and approval packages.
    • Passing product, pricing and order data to CRM, enterprise resource planning (ERP), product lifecycle management (PLM), computer-aided design (CAD) or manufacturing systems.

    Not every CPQ product supports CAD automation, engineering calculations, BOM generation or PLM integration. Buyers must verify these capabilities against the vendor’s documented functionality and the requirements of the product model.

    CPQ vs CRM: the core difference

    Area CRM Manufacturing CPQ
    Primary purpose Manage customers, relationships and opportunities Configure products, calculate prices and create accurate quotes
    Main business question Who is buying, what is the opportunity and what is the sales status? What can be sold, how should it be configured and what should it cost?
    Core data Accounts, contacts, activities, opportunities and forecasts Product models, options, rules, calculations, prices, costs and quote lines
    Primary users Sales, account managers, business development and sales leadership Sales engineers, application engineers, product managers, estimators and technical sales
    Manufacturing relevance Customer and opportunity context Technical validity, engineering definition and commercial accuracy
    Output Opportunity record, forecast, activity history and relationship record Validated configuration, price, quote, and potentially BOM or engineering outputs
    Typical downstream systems ERP, marketing, service, CPQ and analytics CRM, ERP, PLM, PDM, CAD, MES and order-management systems

    There can be overlap. CRM platforms may offer basic product catalogs, price books and quote objects. CPQ platforms may store customer references and opportunity identifiers. Overlap does not remove the need for data ownership decisions.

    How CRM and CPQ work together

    A common manufacturing workflow begins in CRM and moves into CPQ when the opportunity requires product definition or pricing complexity beyond a simple catalog sale.

    1. Opportunity creation: A salesperson records the customer, application, expected quantity, target date and commercial context in CRM.
    2. Configuration launch: The salesperson or sales engineer opens CPQ from the opportunity, often passing the account, site, currency, channel and opportunity identifier.
    3. Technical discovery: CPQ collects configuration inputs such as dimensions, capacity, material, environmental conditions, motor selection or control requirements.
    4. Validation: Configuration rules identify incompatible options, missing requirements or values outside supported ranges.
    5. Engineering and costing: Where supported, CPQ performs calculations, selects components, generates a configurable BOM and applies cost logic.
    6. Pricing: CPQ applies price lists, customer-specific terms, quantity breaks, discounts, freight assumptions, currency and approval rules.
    7. Quote generation: CPQ creates a quote containing the product description, selected options, commercial terms, exclusions, lead-time assumptions and price.
    8. CRM update: Quote status, total value, version and approval state are returned to CRM for pipeline management.
    9. Order handoff: An accepted quote may be transferred to ERP, PLM, PDM, manufacturing or order-management systems, depending on the architecture.

    This workflow keeps CRM focused on the relationship and opportunity while CPQ manages the detailed product and pricing transaction. The exact sequence varies by organization and integration design.

    Data boundaries between CPQ and CRM

    The most important implementation question is not whether CRM or CPQ can technically store a field. It is which system should own, validate and publish that field.

    Data usually owned by CRM

    • Account name, customer classification and relationship hierarchy.
    • Contacts, communication preferences and sales team assignments.
    • Opportunity stage, forecast category, close date and probability.
    • Sales activities, meetings, tasks and account history.
    • Territory, channel and relationship ownership.
    • Commercial context that does not define the product configuration.

    Data usually owned by CPQ

    • Product options, features, attributes and valid values.
    • Configuration dependencies, exclusions and constraint rules.
    • Engineering calculations and configuration-specific requirements.
    • Configured product descriptions and quote-line details.
    • Pricing logic, discount rules and approval thresholds where CPQ is the pricing authority.
    • Configurable BOM logic and configuration identifiers where supported.
    • Quote versions, configuration state and technical assumptions.

    Data that may be mastered elsewhere

    • ERP: Item masters, inventory, standard costs, customer credit, orders and financial transactions.
    • PLM: Product structures, revisions, engineering change processes and released product definitions.
    • PDM: CAD files, document metadata and design data management.
    • CAD: Parametric geometry, assemblies, drawings and model-specific design outputs.
    • PIM: Product descriptions, marketing attributes and channel content.
    • MES: Manufacturing execution, work instructions, production status and shop-floor reporting.

    These systems are distinct. An ERP item number is not necessarily a CPQ configuration rule. A PLM engineering BOM (EBOM) is not the same as a manufacturing BOM (MBOM), which is structured for production operations. A CAD model is not a CRM product record. The CPQ integration guide covers these system relationships in more detail.

    Product configuration is not the same as quoting

    Configuration, pricing and quoting are related but separate functions.

    • Configuration determines whether a product selection is technically valid and defines its attributes, components or requirements.
    • Pricing calculates what the configured product should cost or sell for.
    • Quoting presents the commercial offer, terms, assumptions and validity period to the customer.

    A CRM product catalog may show a list of products and prices without validating dependencies between options. A basic quoting tool may apply discounts without knowing whether a selected motor can drive a specified pump. Manufacturing CPQ connects these functions when the product model and data are sufficiently mature.

    Manufacturing organizations should also distinguish three approaches to configuration. Guided selling asks business-oriented questions and recommends suitable products. Rules-based configuration uses explicit if-then logic, exclusions and required selections. Constraint-based configuration evaluates relationships and limits across multiple variables, such as dimensions, capacity, loads and available components. A platform may support one, two or all three approaches.

    Manufacturing example: configurable industrial pump

    Consider a company selling centrifugal pump packages. CRM stores the customer, project site, opportunity value, expected delivery date and communication history. A CPQ session collects flow, head, fluid, temperature, material, seal type, motor voltage, enclosure rating, baseplate requirements and control-panel options.

    CPQ may then:

    • reject a pump size that cannot meet the required duty point;
    • require corrosion-resistant materials for a specified fluid;
    • select a seal family based on temperature and chemical compatibility;
    • choose a motor frame and power rating;
    • calculate a price from components, labor and commercial rules;
    • produce a configured BOM or manufacturing selection, if supported;
    • send the technical summary and quote value back to CRM.

    If the pump is a standard CTO product, the validated configuration may proceed to order entry with limited engineering review. If the application requires a new skid layout, unusual materials or a modified baseplate, the transaction may become ETO. CPQ can support the intake and handoff, but it does not automatically replace engineering or PLM unless the implementation explicitly provides those capabilities.

    CRM, CPQ and BOM ownership

    A bill of materials lists the components or assemblies required for a product. CPQ may generate a configurable BOM, but this capability is not universal and should not be assumed.

    An EBOM, or engineering bill of materials, represents the product from an engineering design perspective. An MBOM, or manufacturing bill of materials, represents how the product is assembled or produced. A CPQ system may generate a sales or configured BOM that must be transformed or reconciled before production.

    CRM is generally not the right place to maintain detailed BOM structures. It can display a product summary or quote lines, but complex component relationships, revisions and production effectivity usually belong in CPQ, PLM or ERP according to the company’s architecture.

    The BOM, pricing and quoting guide explains how configured products can connect commercial quoting with downstream product data.

    CRM, CPQ and engineering automation

    Engineering automation can include calculations, component selection, CAD generation, drawing creation and technical document production. These functions are usually closer to CPQ, CAD, PLM or engineering applications than to CRM.

    For example, CPQ might calculate a conveyor length from facility dimensions, select a drive package and pass parameters to a CAD automation service. The service could generate a product-specific layout or drawing. CRM would normally retain the opportunity and may provide a link or summary, but it would not be the authoritative CAD model.

    The CAD and engineering automation guide covers the relationship between CPQ inputs, engineering calculations, CAD models and drawings. Organizations should verify whether a selected CPQ platform performs these functions natively, invokes external tools or only stores the resulting references.

    Where the boundary becomes difficult

    Shared product and price data

    Both systems may display product names, item numbers and prices. Without ownership rules, sales teams may see different values in CRM and CPQ. A common approach is to keep customer-specific opportunity context in CRM, while CPQ retrieves product and pricing data from an approved source and returns the calculated result to CRM.

    Quote records

    CRM may need a quote record for pipeline reporting, while CPQ needs detailed versions, configuration state and rule outputs. The systems should not create competing quote versions. One system should own the detailed quote, with the other storing a synchronized summary and identifier.

    Customer-specific pricing

    Customer agreements may originate in ERP or CRM, while CPQ applies them to a configuration. The implementation should define whether the price list, contract discount, rebate or credit status comes from ERP, CRM or a dedicated pricing service.

    ETO work

    In ETO processes, CPQ may capture requirements and create a preliminary commercial estimate, but engineering may need to approve the design before a final quote. CRM should show the opportunity status, while engineering and product systems retain technical approvals, revisions and released data.

    Benefits of integrating CPQ and CRM

    • Faster technical response: Sales teams can launch a configuration from the opportunity instead of manually recreating customer information.
    • Fewer configuration errors: Rules can prevent invalid combinations before a quote reaches engineering or production.
    • Better opportunity visibility: CRM can show quote value, status, version and approval state.
    • Less duplicate entry: Account, contact, currency and opportunity data can be reused in CPQ.
    • More accurate forecasting: CRM pipeline values can reflect validated quote totals rather than rough estimates.
    • Improved engineering handoff: Technical inputs, assumptions and configuration identifiers can travel with the opportunity.
    • Clearer accountability: CRM owns the relationship while CPQ owns configuration and quote logic.

    Limitations and implementation risks

    Integration does not correct weak product data or unclear business ownership. If product options, rules, costs and revisions are inconsistent, connecting CPQ to CRM may simply move errors faster.

    • Unclear system ownership: The same price, product description or quote status is maintained in multiple systems.
    • Incomplete product models: Rules cover common combinations but not unusual engineering cases.
    • Overloaded CRM: Detailed engineering structures are forced into generic product or quote objects.
    • Weak version control: A quote is revised in CPQ but CRM continues to display an obsolete version.
    • Integration latency: Customer, inventory, cost or price updates are not available when the configuration is performed.
    • ETO ambiguity: The organization treats a preliminary estimate as a production-ready definition.
    • Governance gaps: No product owner is responsible for maintaining rules, option compatibility or release dates.
    • Excessive customization: The integration becomes dependent on one CRM implementation and difficult to maintain.

    CPQ implementation should therefore include data mapping, rule ownership, integration error handling, version management, testing and release governance. The CPQ implementation guide provides a framework for these activities.

    How to decide whether you need CPQ or CRM capabilities

    Business situation Likely requirement
    Standard products with simple prices and no technical dependencies CRM product and quote features may be sufficient
    Many options but limited technical interaction Basic CPQ or guided selling may be appropriate
    Options have dependencies, exclusions or capacity constraints A rules-based or constraint-based CPQ model is likely required
    Configuration affects BOM, engineering calculations or drawings Manufacturing CPQ with engineering and downstream integration should be evaluated
    Every order is substantially designed for a project CPQ may support requirements capture and estimating, but engineering and PLM remain central
    Customer and opportunity management is the main problem CRM should be the primary investment

    Recommended architecture and governance

    A practical architecture normally assigns responsibilities explicitly:

    1. CRM owns accounts, contacts, opportunities, activities and sales-process status.
    2. CPQ owns configuration sessions, technical selections, configuration rules and quote calculations where implemented as the pricing authority.
    3. ERP owns released item masters, orders, financial transactions and often standard costs or inventory.
    4. PLM owns released product structures, engineering revisions and change control where PLM is used.
    5. PDM owns CAD documents and design file management where PDM is used.
    6. CAD and engineering services generate geometry, drawings or calculations where those functions are integrated.
    7. MES manages production execution rather than commercial opportunity data.

    Governance should define who can change a rule, who approves pricing changes, how product revisions are released, how obsolete configurations are handled and what happens when an external system is unavailable. Testing should include valid configurations, invalid combinations, boundary values, price changes, revisions, discounts, approvals and integration failures.

    CPQ vs CRM in CTO, MTO and ETO workflows

    Configure-to-order (CTO) uses a predefined product model and approved options. CPQ can often validate the configuration, calculate the price and create a repeatable order definition.

    Make-to-order (MTO) produces a product after an order is received, usually from a defined specification. CPQ may capture the specification and pass it to ERP or production systems.

    Assemble-to-order (ATO) combines stocked or predefined modules after an order is placed. CPQ can select compatible modules, while ERP manages availability and fulfillment.

    Engineer-to-order (ETO) requires engineering work for the specific customer requirement. CPQ may collect requirements, estimate cost and initiate engineering review, but it should not be described as replacing engineering unless the system and process demonstrably support that outcome.

    The manufacturing workflows guide explains these operating models and their sales-to-production handoffs.

    Semantic map

    The following relationships summarize the entities and boundaries discussed in this guide:

    • CRM manages customer relationships and opportunities.
    • CPQ configures technically valid products.
    • Configuration rules prevent invalid combinations.
    • CPQ calculates configured product prices.
    • Configured products may generate configurable BOMs.
    • ERP manages orders and financial transactions.
    • PLM manages engineering product definitions and revisions.
    • PDM manages CAD documents and design files.
    • CAD automation generates product-specific drawings where integrated.
    • CRM displays quote status and opportunity value.
    • ETO requirements initiate engineering review.
    • CTO configurations use predefined product rules.

    Frequently asked questions

    1. Is CPQ part of CRM?

    CPQ may be embedded in, integrated with or separate from CRM. Conceptually, CPQ is a distinct capability focused on product configuration, pricing and quoting, while CRM manages customer and opportunity relationships.

    2. Can CRM replace manufacturing CPQ?

    CRM may handle simple products, catalogs and basic quotes. It usually cannot replace a manufacturing CPQ system when rules, engineering calculations, configurable BOMs or complex pricing are required.

    3. Does CPQ store customer information?

    CPQ can store customer references needed for a quote, but CRM is commonly the system of record for accounts, contacts, activities and opportunities.

    4. Does CPQ generate a BOM?

    Some manufacturing CPQ platforms generate configurable or sales BOMs, while others only produce quote lines. This capability must be verified for the specific platform and product model.

    5. Should product data be mastered in CRM or CPQ?

    CRM may store commercial catalog information, but detailed options, dependencies and configuration rules are usually better managed in CPQ or a connected product lifecycle system.

    6. Can CPQ calculate manufacturing cost?

    Some CPQ systems calculate material, labor, overhead or estimated cost. Others use external ERP or costing services. The source, refresh frequency and approval process for cost data should be defined.

    7. What does CRM send to CPQ?

    Common inputs include account, contact, opportunity, currency, channel, customer segment, location and commercial terms. The exact fields depend on the integration design.

    8. What does CPQ send back to CRM?

    CPQ commonly returns quote identifiers, configured product summaries, totals, versions, approval status, validity dates and quote status.

    9. Is a CRM quote the same as a CPQ quote?

    Not necessarily. CRM may contain a summary quote record for pipeline management, while CPQ contains the detailed configuration, calculations, versions and technical assumptions.

    10. Can CPQ automate CAD?

    Some platforms integrate with CAD or engineering automation tools, but this is not a universal CPQ capability. Verify supported CAD systems, parameter coverage, drawing outputs and revision handling.

    11. Does CPQ replace PLM?

    CPQ generally does not replace product lifecycle management. PLM typically manages engineering definitions, revisions and change control, while CPQ uses approved product knowledge to configure and quote.

    12. How does CPQ support engineer-to-order sales?

    CPQ can capture requirements, estimate cost, identify standard content and initiate engineering review. The final design, approval and release may remain in engineering and PLM systems.

    13. Should CRM own pricing?

    CRM can display prices and support sales processes, but complex configuration-dependent pricing is often better calculated in CPQ or a dedicated pricing service. Ownership should be explicit.

    14. How are discounts handled between CRM and CPQ?

    Many architectures let CRM provide customer or opportunity context while CPQ validates discount limits against configured product value, margin and approval rules. The authoritative calculation must be defined.

    15. Can CPQ work without CRM?

    Yes. CPQ can operate with other front ends or as a standalone application, although CRM is useful for account context, opportunity tracking and sales activity management.

    16. Can CRM work without CPQ?

    Yes. CRM is sufficient for relationship management and simple quoting. A separate CPQ capability becomes more valuable as product, pricing and engineering complexity increases.

    17. What is the difference between a CRM product catalog and a CPQ product model?

    A CRM catalog usually supports product display and basic selection. A CPQ product model can include options, dependencies, constraints, calculations, component logic and configuration-specific outputs.

    18. What should manufacturers test in a CRM-CPQ integration?

    Test account synchronization, currencies, price lists, configuration validity, quote versions, discount approvals, revisions, error handling, duplicate records and accepted-quote handoff to ERP or engineering systems.

    Related manufacturing CPQ guides