CPQ: Configuration, Pricing, and Quoting for Complex B2B Sales

In many B2B companies, quotes are made the same way for years: a salesperson opens an old quote file, changes the customer name, edits a few lines, asks the product team for prices over chat, and sends a PDF. While products are simple, this is enough. When products have many options, prices depend on volume and contracts, and discounts need approval, quoting becomes a source of errors: configurations that cannot be built, prices below margin, discounts beyond authority, and quotes that take days to finish.

CPQ, short for configure, price, quote, is both an approach and a class of software that solves this problem. This article explains when a business needs CPQ, its core functions, how to structure configuration and pricing rules, margin approvals, the relationship with CRM and ERP, and a realistic rollout, including when simpler tools are enough.

Summary

• CPQ ensures a quote is technically valid, correctly priced, and within authority before it reaches the customer
• Configuration rules reject combinations that cannot be built, so errors are caught at quoting rather than in production
• Prices come from one source: price lists, volume tiers, special contracts, and discount rules
• Automatic margin approvals speed up safe quotes and hold risky ones
• Integration with CRM and ERP turns an approved quote into an order without re-entry

When manual quoting starts to fail

Manual quoting is not a problem for every business. Signs that you have passed the limit:

• The quoting cycle takes days because of waiting for technical and pricing answers from several people
• Two salespeople give different prices for the same configuration
• Orders reach production with incompatible or unbuildable configurations
• Discounts are given without approval, or approval happens through unrecorded messages
• Actual project margin differs greatly from what was estimated at quoting
• The price list is updated, but old quote templates are still circulating
• There is no revision history, so it is hard to answer "which version did the customer agree to"

If several of these sound familiar, the cost is real: sales time consumed by administration, leaking margin, and customers waiting longer than with competitors.

The three components of CPQ

Configure: product configuration

Configuration is the process of choosing options so that a valid product or solution results. The system stores rules: option A is only compatible with models B and C; package X requires component Y; maximum number of connections for a given capacity; a certain material cannot be combined with a certain coating. As the salesperson chooses options, the system hides or rejects invalid choices and adds mandatory components automatically.

The result is a consistent component list and, where needed, a bill of materials or specification that can be passed to production. For made-to-order production, the connection is covered in make-to-order ERP and job costing for printing and fabrication.

Price: pricing

A price is not a single number. It combines several sources:

• A base price list per product or component, possibly differing by region or currency
• Volume tiers: the more, the cheaper per unit
• Special contract prices for certain customers agreed in advance
• Promotions and time-limited discounts
• Extra charges: installation, delivery, training, or extended warranty
• Tax, according to applicable rules
• For subscription services, recurring prices and upfront fees are separated

The system calculates price from these rules consistently, so two quotes with the same configuration yield the same price. Broader pricing approaches are in pricing strategy for online stores, whose basic concepts also apply in B2B, and subscription models in subscription business models and recurring billing.

Quote: the quote document

Once configuration and price are valid, the system generates a quote document from a template: branding, solution summary, price breakdown, payment terms, validity period, and standard terms. Some useful features:

• Templates per product type and per language; for international buyers, see [B2B websites for exporters and manufacturers](/blog/website-b2b-untuk-eksportir-dan-manufaktur-menarik-pembeli-internasional)
• A stated validity period with warnings before expiry
• Versions and revisions with change history
• Customer acceptance links, or e-signature, as discussed in [electronic signatures and e-stamp duty for business document flows](/blog/tanda-tangan-elektronik-dan-e-meterai-untuk-alur-dokumen-bisnis)
• Alternative options within one quote, such as standard, advanced, and premium packages

Building configuration rules without being overwhelmed

A common mistake is trying to model every possibility from the start. Too many rules become hard to maintain and no one dares change them. A healthier approach:

• Start with one product line with the highest sales volume
• Document rules in simple tables: component, dependency, exception
• Involve people who understand the product technically, usually engineering or production, and do not rely only on sales
• Define a rule owner; product changes must update rules as part of the product release
• Provide an exception path: special configurations not in the rules are submitted as engineering requests, rather than forced in or avoided

If your product is a service or software project rather than a physical good, the same pattern appears as packages and modules. Cost structure is discussed in calculating the real cost of a software project and software project pricing models.

Pricing and discount rules

Discounts are where margin leaks most often. Design clear rules:

• Discount limits per role: salespeople up to a certain limit, managers up to a higher limit, directors above that
• Discounts depend on volume or contract length, not merely on customer request
• Discounts on certain components may be prohibited, such as services or thin-margin goods
• Stacking of discounts is limited; stacked discounts can produce prices below cost
• A price floor that cannot be breached without special approval

Make sure the system shows margin to those authorized to see it, but hides cost and margin from documents customers see, and where needed from junior salespeople.

Approval flow

Good approval is fast for safe cases and thorough for risky ones. The system checks rules automatically:

• Quotes within the salesperson's authority are released without approval
• Quotes beyond the limit are forwarded to the right approver, together with a summary of margin, discount, comparison with similar quotes, and the salesperson's reasoning
• Approvals have time limits and escalate if unanswered
• All decisions are recorded with who, when, and why

General approval-flow principles are covered in purchase approval flows, and the design is similar though used on the sales side. Avoid flows with too many levels; each additional level adds days to the sales cycle.

Integration with CRM and ERP

A CPQ separate from other systems only moves the problem. Valuable integrations:

• CRM: quotes are created from sales opportunities and their value returns to the pipeline, so forecasts use real numbers. See [CRM needs for B2B businesses](/blog/kebutuhan-crm-untuk-bisnis-b2b) and [defining sales pipeline stages](/blog/mendefinisikan-tahapan-pipeline-penjualan)
• ERP: the product catalog, stock, lead times, and standard costs flow into CPQ, while accepted quotes become sales orders without re-entry. Master data quality determines success, as discussed in [ERP master data](/blog/master-data-erp-kode-barang-pelanggan-pemasok)
• Billing: payment terms and stages from the quote flow into invoices; see [invoice automation and B2B receivables collection](/blog/otomatisasi-faktur-dan-penagihan-piutang-b2b)
• Customer portal: customers can view, approve, and reorder from quotes previously issued; see [B2B customer and supplier portals](/blog/portal-pelanggan-dan-pemasok-b2b)

Integration patterns can use APIs or webhooks as in webhooks and real-time integration for business. In a modular architecture such as composable ERP, CPQ can be its own module connected through APIs.

Metrics to monitor

Once CPQ is running, monitor to prove its benefits:

• Time from request to quote sent
• Percentage of quotes that become orders
• Average discount and actual margin compared with planned margin
• Number of quotes requiring approval, and approval time
• Number of orders sent back to sales because of invalid configuration
• Number of revisions per quote

This data also enriches team performance analysis, in line with sales team performance metrics. Compare before and after rollout, and be careful about concluding cause and effect because seasons and market conditions also play a part.

When full CPQ is not needed

Not every business needs a dedicated CPQ platform. Some lighter alternatives:

• Simple products with fixed price lists: a quoting module in the CRM or ERP is enough
• Limited configuration: a quote template with controlled formulas and dropdown lists may suffice, as long as versions and access are controlled
• Low quote volume: the rollout cost may not be proportionate; just improve template and approval discipline
• Services with a unique scope each project: quotes resemble proposals and professional judgment more than configuration, so focus on templates, cost calculation, and approval

Also consider building a lightweight custom solution if your flow is unique. The decision framework is the same as custom software vs off-the-shelf software. As a rule of thumb: if your configuration and pricing rules change often, are complex, and affect margin, a CPQ investment tends to be worthwhile.

A phased rollout plan

• Weeks 1 to 3: collect the last 20 quotes, record where time and errors occur, and choose a pilot product line
• Weeks 4 to 6: document the configuration rules, price structure, and discount limits for that line
• Weeks 7 to 10: build or configure the tool, quote templates, and approval flow; test with old quotes as a comparison
• Weeks 11 to 12: train salespeople and pilot with a few people
• Afterwards: integrate with CRM and ERP, then expand to other product lines

Involve salespeople from the start. A tool that feels like it slows them down will be avoided, and quotes will go back to being made outside the system.

Common mistakes

• Modeling all products and exceptions at once so the project never finishes
• Not assigning a rule owner, so rules go stale
• Approvals with so many levels that quotes are slower than before
• Leaving a quoting path outside the system open
• Not connecting to the ERP, so orders are still retyped
• Showing internal cost and margin on customer documents

Frequently asked questions

Is CPQ only for large companies?

Not necessarily. Mid-sized companies with configurable products or complex pricing also benefit. What matters is the complexity of quotes and the impact of mistakes, not company size.

How long does implementation take?

For one product line with documented rules, a pilot can run within a few months. Most time usually goes into tidying rules and data, not the technology.

Does CPQ replace CRM?

No. CRM manages relationships and the pipeline, while CPQ manages configuration, pricing, and quote documents. They complement each other.

Conclusion

CPQ turns quoting from error-prone administrative work into a consistent process: valid configuration, prices from one source, approvals according to authority, and data that flows into orders and billing. Its value shows in shorter sales cycles, better-protected margins, and customers getting faster answers. Start with one product line and well-documented rules. If you want to design a quoting flow connected to your CRM and ERP, the Agsora team can help map the rules and build the solution.