Preparing an order for a configurable product can involve repeated conversations between sales, engineering and manufacturing. The right CPQ software for manufacturing can help those teams work from consistent product rules and pricing information. Its value depends on how well those rules reflect the products you can actually build.
Consider a small manufacturer of specialist delivery trucks. A customer requests ten vehicles, each with particular equipment and dimensions. Before quoting, the seller needs to check technical compatibility, identify the required components and calculate the commercial terms. CPQ can organise that work, but it cannot replace decisions that have never been defined.
What does CPQ mean?
CPQ stands for Configure, Price, Quote. The software helps a business select a valid product configuration, calculate a price and produce a quotation. For manufacturers, the important question is how those sales choices connect to engineering information and the eventual order.
It is useful to separate repeatable choices from genuinely new design work. A standard range of body sizes and equipment packages can be modelled as options. A request outside the tested range may still need an engineer’s review. A good process makes that exception visible rather than generating a confident-looking quote for an unverified design.
Configure: guide customers through valid choices
Manufacturers producing identical stock items face a different quoting task from those offering many combinations. Configuration tools can create more opportunities to offer controlled variation, without asking each salesperson to remember every dependency.
In the truck example, choosing one body type might limit the available equipment packages. An accessory may require an additional component. The configuration should flag incompatible combinations and explain what the customer can choose instead. The actual engineering constraints must come from the manufacturer’s approved product knowledge.
Do not model every imaginable option on the first day. Start with a product family that has clear rules and enough quotation volume to make the work worthwhile. Record who owns each rule and what happens when a customer requests an exception.
Price: make assumptions and approvals explicit
Pricing can become more complicated as configurations multiply. A quotation may depend on component costs, quantities, regional price lists, currency, delivery terms and customer agreements. Automating the calculation helps only when the underlying data is current and the rules are understood.
Define which discounts a salesperson may offer and which require approval. Keep the approval decision attached to the quotation version. If a component price changes after a quote is issued, the team needs to know whether the original price remains valid or whether the customer must receive a revised offer.
Separate selling price from estimated production cost. They answer different questions. A quote can follow the price list perfectly and still be commercially unattractive if the cost assumptions are stale or a special requirement has been omitted.
Quote: turn the configuration into a clear offer
CPQ for manufacturing can generate a quotation from the selected options and pricing rules. Elfsquad, for example, describes configuration-driven pricing, document generation, approval workflows and connections to other business systems. Those capabilities still require implementation and testing against your own products.
The customer-facing document should explain what is included, the quantity, any exclusions, delivery assumptions and how long the offer remains valid. A professional layout does not compensate for an ambiguous specification. Ask whether someone outside the sales conversation could understand exactly what they would receive.
Keep a version identifier on the quote. If the customer changes one option, make it clear which document supersedes the previous version. This helps purchasing, sales and operations avoid working from different interpretations of the same order.
Connect the quote to the systems used downstream
Before choosing an integration, decide where each type of information is maintained. Product rules, customer records, prices and stock availability may belong to different systems. Agree which system takes precedence when values disagree, and how the team will handle a failed transfer.
A bill of materials generated from a sales configuration may still need validation before manufacturing uses it. Test the handoff with real examples: an ordinary order, an unusual but valid combination, and a request that should be rejected. Check identifiers, quantities and revisions rather than judging only the appearance of the quote.
Measure whether the implementation helps
Record a baseline before introducing CPQ. Useful measures include time from complete requirements to quote, the number of engineering clarification requests, quote revisions caused by errors, and orders returned for missing specifications. Use comparable product families so a change in order complexity does not distort the comparison.
Also review the maintenance burden. Someone must update rules when products change, test price-list revisions and retire unavailable options. Faster quoting is less valuable if outdated configurations create extra work after the sale.
Questions to ask before committing
Ask a supplier to demonstrate your difficult cases, not only a prepared sample. Can your team maintain the rules? How are exceptions approved? What happens when an integration is unavailable? Can you trace an accepted order back to the exact configuration and quote?
A successful pilot should show clearer handoffs and fewer preventable mistakes, with a manageable process for keeping the model current. CPQ can reduce rework, but it does not guarantee the elimination of returns, concessions or engineering changes. Treat it as a maintained business process supported by software.
