Most CPQ software was designed for a sales team selling software subscriptions or a fixed product catalogue. You click a few options, a price appears, a PDF goes out. Simple.
That is not how equipment manufacturing works. An excavator has 4,000 configurable variants. A compressor has attachment combinations that invalidate each other. A medical imaging system is engineered differently for every hospital. None of this fits the standard CPQ model — and the gap between what generic CPQ tools offer and what equipment OEMs actually need is the reason implementations fail.
This is what CPQ for manufacturing genuinely requires.
What makes equipment manufacturing different from every other CPQ use case
Equipment manufacturers deal with three types of complexity that generic CPQ tools cannot handle without months of custom build:
Configure-to-order (CTO) — the customer selects from a defined set of variants, attachments, and options. The configuration must validate in real time: certain attachments are incompatible, certain engine variants require specific hydraulic packages, certain markets require different emissions compliance. Every invalid combination must be caught before the quote goes out.
Engineer-to-order (ETO) — the configuration does not exist yet. A sales engineer builds it from scratch, often with non-standard components, custom dimensions, or novel attachment combinations. The quoting system must support engineering notes, provisional pricing, and revision tracking alongside standard CPQ logic.
Make-to-order (MTO) — somewhere between the two. A defined product structure that gets adapted per customer. Common in industrial machinery and HVAC where the base platform is fixed but the specification varies significantly.
Generic CPQ tools handle none of these natively. Salesforce CPQ, for example, was built for subscription and product-bundle sales. Making it handle BOM-level ETO quoting requires 12–18 months of custom development, an army of consultants, and a configuration layer that sits on top of the platform rather than being part of it.
The six things CPQ for manufacturing must do
1. BOM-level product configuration
The configure-to-order process in equipment manufacturing happens at the bill of materials level, not the product-catalogue level. A quote is not "1× Excavator + 2× Attachments." It is a structured list of components — engine assembly, hydraulic system, cab configuration, undercarriage type, bucket variant — where every selection has downstream implications for price, lead time, and compatibility.
CPQ must model this structure natively. That means variant configuration at every BOM level, real-time compatibility validation, and automatic pricing based on the assembled configuration — not a manual price lookup after the fact.
2. Integration with SAP without middleware
For equipment manufacturers running SAP S/4HANA or SAP ECC, the CPQ system must write back to SAP automatically. Every quote that converts to an order needs a sales order in SAP, a BOM explosion, and a pricing record — without a sales coordinator re-keying data from a PDF.
This is where most CPQ implementations fall apart. Salesforce CPQ requires MuleSoft to connect to SAP. Oracle CPQ requires Oracle Integration Cloud. Both add six to twelve months of integration work and six-figure middleware costs. CPQ for manufacturing should have native SAP connectors that sync material masters, pricing conditions, customer master data, and sales orders without middleware.
3. Multi-tier dealer and distributor pricing
Equipment does not typically sell direct. It goes through a network of distributors and dealers, each with different pricing tiers, territory assignments, and discount authorisation levels. The CPQ system must manage this entire pricing hierarchy — OEM list price, distributor cost, dealer cost, end-customer price — in a single platform.
Dealers need to be able to configure and quote equipment within their authorised parameters without calling the OEM's inside sales team. That means a dealer self-service portal that enforces pricing rules automatically, flags configurations that require OEM approval, and generates a quote PDF the dealer can send to their customer directly.
4. Aftermarket quoting in the same platform
The initial machine sale is typically the lowest-margin transaction in the equipment lifecycle. The margin is in what comes after: spare parts, service contracts, planned maintenance packages, warranty extensions, and upgrade kits.
A CPQ system for equipment manufacturers must handle aftermarket quoting in the same platform as the initial machine configuration. When a dealer raises a parts order or a service contract renewal, the pricing rules, the customer history, and the product knowledge should already be there. Running a separate system for aftermarket creates the gaps where revenue leaks.
5. Configure-to-quote in minutes, not days
The typical quote cycle for configured equipment without a proper CPQ system is three to five days. A salesperson takes a specification, manually checks compatibility, looks up component prices in a spreadsheet, builds a price manually, gets margin approval, and produces a PDF. By the time the quote goes out, the customer has already received one from a competitor.
CPQ for manufacturing should reduce this to under two hours for standard configurations — with the system handling compatibility, pricing, and proposal generation automatically. For standard ETO work, the target is same-day rather than same-week.
6. Guided selling for complex equipment
Not every salesperson knows every product configuration by heart. A CPQ system with guided selling asks the right questions in the right order — application type, duty cycle, operating environment, performance requirements — and narrows the configuration to a valid set of options. This is especially important for dealer networks where the sales representative may sell many product lines and cannot be expert in all of them.
What a CPQ implementation for equipment manufacturing actually looks like
A realistic implementation has four phases:
Phase 1 — Product model build (weeks 1–4): Map your product hierarchy, variants, compatibility rules, and pricing logic into the CPQ system. This is the configuration knowledge that currently lives in your engineering team's heads and your pricing spreadsheets.
Phase 2 — SAP integration (weeks 3–8): Connect the CPQ system to your SAP instance. Map material masters, pricing conditions (condition types, condition tables), and customer master data. Build the order write-back so a converted quote automatically creates an SAP sales order.
Phase 3 — Channel setup (weeks 6–10): Configure the dealer portal with territory assignments, pricing tiers, and approval workflows. Train the first wave of dealers.
Phase 4 — Rollout (weeks 10–12): Phased rollout to internal sales first, then dealer network, with support during the first live quote cycle.
A properly scoped ServiceCPQ implementation with SAP integration completes in 8–12 weeks. Equivalent Salesforce CPQ implementations for the same complexity take 12–24 months.
The difference between CPQ for manufacturing and standard CPQ
| Capability | Standard CPQ | CPQ for Manufacturing |
|---|---|---|
| Product model | Catalogue-based | BOM-level, multi-level hierarchy |
| Configuration | Rule-based bundles | CTO + ETO + MTO |
| Pricing | List price + discount | Waterfall: OEM → distributor → dealer → customer |
| SAP integration | Via middleware | Native connectors |
| Aftermarket | Separate system | Same platform |
| Dealer portal | Not included | Built-in |
| Implementation | 12–24 months | 8–12 weeks |
Frequently asked questions
What is CPQ for manufacturing? CPQ for manufacturing is configure, price, quote software built specifically for equipment OEMs and distributors. Unlike generic CPQ tools, it handles configure-to-order and engineer-to-order complexity, BOM-level product structures, multi-tier dealer pricing, and native SAP integration — the four capabilities standard CPQ platforms cannot provide without heavy customisation.
How is CPQ for manufacturing different from Salesforce CPQ? Salesforce CPQ was designed for SaaS subscriptions and product-catalogue sales. CPQ for manufacturing handles BOM-level configuration, ETO quoting, SAP S/4HANA integration, dealer pricing hierarchies, and aftermarket service contracts — none of which Salesforce CPQ supports natively. Equivalent Salesforce CPQ implementations for equipment OEMs take 12–24 months and require MuleSoft for SAP integration.
How long does a CPQ implementation take for an equipment manufacturer? A properly scoped implementation with SAP integration typically completes in 8–12 weeks for ServiceCPQ. The shorter timeline comes from pre-built product model templates for equipment manufacturing, native SAP connectors that eliminate middleware build time, and a deployment approach focused on the 80% of configurations that are standard, before tackling edge cases.
Can CPQ handle engineer-to-order (ETO) quoting? Yes. ServiceCPQ supports ETO quoting by allowing sales engineers to build non-standard configurations, add custom line items, apply BOM substitutions, and capture engineering notes within the quote workflow. Pricing rules apply automatically based on the configuration, and the finalised quote writes back to SAP as a sales order.
Does CPQ for manufacturing integrate with SAP Variant Configurator? ServiceCPQ can work alongside SAP Variant Configurator (VC) or replace it. When working alongside SAP VC, ServiceCPQ provides the front-end guided selling and proposal generation while SAP VC handles the configuration logic. Alternatively, ServiceCPQ's native configuration engine can replace SAP VC for OEMs who want a more flexible, faster-to-maintain configuration model outside of SAP.