A sales rep may call the problem “quoting,” while engineering sees invalid combinations, finance sees unmanaged discounts and operations sees an order it must rebuild. CPQ can solve all four problems only when the product model, price logic, quote and manufacturing handoff agree.
This guide is for industrial OEMs selling configured equipment, engineered systems and mixed product-service packages. It explains what to test, where the leading manufacturing CPQ products differ and when Bourne is the stronger fit.
Start with the work that breaks
Do not begin with a feature list. Pull twenty recent quotes: common wins, difficult wins, losses, withdrawn bids and orders that caused trouble after award. Mark each manual step, delay, error and handoff. The pattern will tell you whether you need a configurator, an engineering automation product, a pricing system, proposal software or a workflow across all of them.
A dedicated manufacturing CPQ earns its cost when repeatable product logic sits at the center of the delay. If most work comes from reading customer documents, finding prior decisions, collecting supplier input and routing exceptions between systems, a configurator will cover only one part of the quote.
| What goes wrong | Capability to test | Likely center of the purchase |
|---|---|---|
| Sales selects combinations that engineering rejects | Constraint engine, guided selling and a controlled exception path | Product configuration |
| Engineers redraw similar products for every quote | CAD, drawing, BOM and routing automation | Engineering automation |
| The same product gets a different price by rep or region | Price books, cost inputs, discounts, margin rules and approvals | Pricing |
| Quotes take days to assemble after the answer is known | Document generation, scope control, revisions and customer collaboration | Proposal output |
| Operations rekeys the won quote into ERP | Structured order, BOM, routing and revision handoff | ERP and manufacturing handoff |
| Every RFQ starts in email, drawings and spreadsheets | Document review, requirement capture and cross-system coordination | Bourne or another workflow product |
Separate the five jobs inside CPQ
The category name joins five jobs that require different data and different owners. A product can excel at visual configuration and still leave pricing or order release to another system. Make each vendor show where its responsibility starts and stops.
| Job | Input | Accepted output | Owner who must trust it |
|---|---|---|---|
| Discover | Customer use, duty, capacity, interfaces, site and commercial requirements | A complete requirement set tied to source evidence | Sales and application engineering |
| Configure | Requirements plus the current product model | One valid product or system configuration with exceptions isolated | Product management and engineering |
| Price | Configuration, cost, account, channel, quantity and terms | Net price, margin and approval state with a dated basis | Finance and sales management |
| Quote | Approved scope, configuration, price, exclusions and terms | A customer document that matches the internal decision | Sales, legal and the customer |
| Release | Accepted quote, customer PO and final configuration | Order, BOM, routing, drawings and commitments for execution | Engineering, operations and service |
Write an acceptance test for each row. “Integrates with ERP” says little. “Creates a sales order in the test ERP with the exact configured lines, quantities, effectivity, promised date and approved price” gives the project a finish line.
Follow one pump package through the whole process
Consider an OEM quoting a packaged cooling-water pump system. The customer needs 420 cubic metres per hour at 58 metres of head, 50 hertz power, a corrosive coastal environment, a tight equipment footprint, a 75-decibel noise limit and delivery in twenty-four weeks. The RFQ includes a datasheet, site layout, piping specification and customer terms.
The configurator can select a standard pump family, motor, seal, baseplate, materials and controls. It can reject combinations that miss the duty point or exceed the motor rating. It can size a standard acoustic enclosure. The customer footprint, however, conflicts with the standard maintenance clearance, and the requested coating system differs from the current regional product rule. Those two items need engineering decisions.
A useful CPQ proof carries the approved answers all the way through the quote. It does not stop after showing a green “valid” state on the screen.
| Stage | What the software should do | Result for this quote |
|---|---|---|
| Requirement | Capture each customer value with its source and revision | Duty point from datasheet Rev C; footprint from layout Rev B; coating from specification section 9.4 |
| Configuration | Resolve standard choices and show the rules behind them | Pump, motor, seal, material, controls and standard enclosure selected |
| Exception | Send the exact conflict and current configuration to engineering | Approve revised maintenance access; qualify the requested coating system |
| Cost and price | Recalculate standard and custom scope from current inputs | Base package, enclosure, engineering hours, special coating, freight and margin approval |
| Proposal | State the offered duty, scope, deviations, drawings, delivery and terms | Customer sees the approved access deviation and coating basis instead of a generic option code |
| Order | Create the configuration, BOM, routing, drawings and commercial baseline in the owning systems | Engineering and operations receive the same package the customer accepted |
This example also sets the boundary between products. A manufacturing CPQ should own the repeatable pump rules. Engineering owns the two new decisions. Bourne can read the RFQ, call the configurator, route those exceptions, collect their cost and delivery effects, and carry the approved package through proposal and order review.
Decide how much of the product can be modeled
CPQ works from a maintained model. List the options, attributes, calculations, constraints, assemblies and outputs that define each product family. Then measure the share of recent quotes that stayed inside that model. A stable product family with many valid combinations can justify a substantial CPQ program. A business that engineers most customer requirements from first principles needs a smaller configured core and a strong path for order-specific work.
Oracle’s NetSuite CPQ documentation describes configurable items through questions, answers, rules, pricing and generated records. That is the basic contract: each answer must affect validity, price or a downstream record in a predictable way.
Read the engineer-to-order versus configure-to-order guide before you scope the model. It shows how to draw the line between approved choices and engineering work. If the team cannot agree on that line, software will encode the disagreement instead of fixing it.
| Question | Evidence to collect | Why it matters |
|---|---|---|
| Which families repeat? | Quote and order volume by family, option and region | Sets the first release scope |
| Which rules already exist? | Manuals, spreadsheets, CAD logic, ERP configurators and expert interviews | Shows the migration and validation work |
| Which requests leave the model? | Engineering exceptions from recent bids and orders | Sizes the exception workflow |
| What does each choice produce? | Sales BOM, manufacturing BOM, routing, drawing, document and service outputs | Prevents a configurator that ends at a part number |
| Who owns each rule? | Named product, engineering, pricing and compliance owners | Creates a maintainable product after launch |
Test the configuration engine with difficult products
Give each vendor a product that has nested assemblies, calculated attributes, incompatible options, regional rules and at least one system-level constraint. Ask the seller to configure a valid case, force an invalid case, change a requirement late and explain why the engine accepted or rejected each result.
Tacton’s configurator models assemblies, subassemblies, modules, parts, domains and attributes. It also describes conflict resolution for explicit selections and configuration of interconnected systems such as HVAC, production lines and pump systems. That makes Tacton a serious candidate when constraint-heavy product or system configuration drives the purchase.
Ask how the engine expresses constraints. A long procedural rule chain can become hard to change because order matters. A constraint model can solve combinations from declared relationships, but the model still needs clear structure, test cases and owners. The demo must use your product logic; a polished sample product proves only that the screen works.
| Configuration test | Pass condition |
|---|---|
| Nested assembly | A choice at one level updates every dependent assembly, calculation and output |
| Conflict | The user sees the conflicting selections and valid ways to resolve them |
| Calculated value | The system derives a size or performance value and shows the inputs behind it |
| System configuration | Several products work together under shared capacity, interface and site constraints |
| External check | A simulation or engineering service can return a governed result to the configuration |
| Version replay | The team can reopen an old quote under its original model and explain the result |
Test how product experts maintain it
The administration product matters as much as the seller experience. Your product changes after launch. New motors replace old motors. Regional certificates change. Suppliers retire components. Pricing teams update rates. Product managers add options. The business must make those changes without breaking open quotes or every related family.
Tacton CPQ Administration lets product and pricing experts define product architecture, attribute constraints, BOM structure, data, documents, permissions and workflows. Epicor CPQ uses a visual rules language and includes tools for configurators, products, integrations, channels and users. Those claims give you concrete administration work to test during selection.
Have one of your product experts make a real change in the proof environment. Add an option, change a dependency, retire a component, update a price input, run regression cases, promote the model and roll it back. Count the work and the people required. If only the vendor can do it, include that dependency in the business case.
| Administration control | What the buyer should see |
|---|---|
| Ownership | Named owners for product rules, prices, documents and integrations |
| Test | Automated regression cases for common, boundary and invalid configurations |
| Promotion | Review and approval before a change reaches sellers |
| Effectivity | A clear rule for open quotes, new quotes and dated product changes |
| Rollback | A fast return to the last approved model after a bad release |
| Dependency map | The options, calculations, documents and outputs affected by a change |
Make engineering automation prove its output
A visual product image helps the buyer understand the offer. It does not prove that engineering or production can use the result. If CAD and manufacturing automation drive the project, inspect the generated model, drawing, BOM, routing, work instruction and item data. Check dimensions, tolerances, materials, metadata, revision and downstream editability.
Epicor CPQ combines 2D, 3D and augmented-reality configuration with CAD generation, BOMs, assembly instructions and production documents. Experlogix focuses its manufacturing handoff on BOM, work-breakdown structure and routing data generated from the same rules used during configuration. These are stronger fits than a generic sales CPQ when the expected output must prepare production.
Use the hardest representative assembly in the proof. Open the result in the native CAD, PLM and ERP tools. Then change one configuration input and confirm that every affected output changes while unrelated work stays untouched. A PDF screenshot is not an engineering handoff.
| Output | What to inspect |
|---|---|
| CAD model | Native format, parameters, assembly structure, mates and naming |
| Drawing | Views, dimensions, notes, title block, revision and released template |
| Sales BOM | Customer-facing scope and option grouping |
| Manufacturing BOM | Parts, quantities, effectivity, phantom assemblies and make/buy state |
| Routing | Operations, resources, setup, run time and outside processing |
| Production documents | Work instructions, cut sheets, labels and inspection requirements |
Price the configuration the customer will receive
Manufacturing price rarely comes from one price book. The result may combine base equipment, options, quantity breaks, customer agreements, region, currency, commodity surcharges, freight, installation, warranty, service, discount and a margin floor. Ask which values CPQ owns, which it reads from ERP or another service and which require approval.
Tacton’s pricing product describes geography, customer segment, channel, currency, material cost, shipping, one-time fees, subscriptions, discounts, rebates and margin approvals. The breadth matters less than the exact rule chain your business needs. Rebuild three recent quote prices and reconcile every difference to the approved quote.
Freeze the basis behind a submitted price. The quote record should show the configuration version, price inputs, exchange rate, cost basis, discount, approval and expiry that produced the number. When the customer changes quantity two weeks later, the team must know which values to recalculate and which commercial commitments still stand.
| Pricing test | Question to answer |
|---|---|
| Configuration delta | Does each option change price and margin as expected? |
| Customer agreement | Does the correct contract override the standard book without manual entry? |
| Cost change | Can the team see the margin effect before changing the customer price? |
| Approval | Does a discount or low margin reach the right approver with the full basis? |
| Revision | Can the team explain the difference between quote versions line by line? |
| Expiry | Does the system reopen prices that depend on expired supplier, freight or currency inputs? |
Read the customer document as closely as the configuration
The quote must state what the OEM will supply, what it will exclude, how the product meets the requirement and which commercial conditions apply. A correct configuration inside CPQ can still produce a weak proposal if the document omits interfaces, assumptions, deviations, services or customer-specific clauses.
Tacton quote and document generation uses configuration and pricing data in Word, Excel and PDF templates, supports technical specifications and other documents, and stores proposal revisions for collaboration. Cincom CPQ emphasizes configuration, pricing, quote generation, approvals, sales channels and visual configuration for complex manufacturing. Both can fit an OEM whose proposal follows structured product and price data.
Many RFQs ask for more than a configured product. They include specification clauses, document schedules, compliance matrices, project milestones, liquidated damages and customer terms. Test whether CPQ can represent those requirements and deviations or whether another workflow must assemble them around the configured equipment.
| Proposal element | Control |
|---|---|
| Scope | Every priced line maps to the offered configuration or service |
| Technical response | The answer cites the customer requirement and approved product evidence |
| Assumptions and exclusions | Named owners approve material limits before release |
| Commercial terms | The proposal uses the same terms and approvals as the internal quote |
| Visuals and drawings | The document uses the correct configuration and revision |
| Revision | Each customer issue has a unique status, date and change record |
Follow the won quote into the order
A CPQ project fails when the quote gets faster but engineering and operations still rebuild the order. The accepted configuration, options, custom work, price, delivery promise and documents must reach the systems that plan and build the product. The customer PO also needs a final comparison against the accepted offer before release.
Infor CPQ Enterprise Quoting documents configurable quote lines, configuration details, pricing, attachments, bid documents and conversion privileges. Experlogix describes direct BOM and routing handoff to ERP. Those examples show two distinct levels of completion: a commercial order transaction and a manufacturing package. Decide which one your project must produce.
Run the proof through the target CRM, ERP, PLM and CAD systems. Confirm identifiers, units, configuration keys, BOM levels, routing data, document links, effectivity and revision. Then change the customer PO and prove that the team can see the difference before it becomes an order.
| Handoff record | Acceptance test |
|---|---|
| Customer and opportunity | Correct account, site, contacts, currency and commercial owner |
| Order lines | Exact offered products, services, quantities, options and net prices |
| Configuration | Recoverable configuration ID, rule version and selected values |
| Engineering | Approved custom requirements, calculations, drawings and open release work |
| Manufacturing | Usable BOM, routing, dates, documents and special instructions |
| Commercial baseline | Accepted proposal, PO comparison, deviations and approvals |
Where the products differ
The products below overlap. The distinction is where each vendor puts its deepest current product story and what you should make it prove. Use this shortlist to choose demonstrations, then score the products on your own cases.
| Product | Best fit when | What to make the vendor prove |
|---|---|---|
| Bourne | Customer work crosses RFQ documents, CRM, CPQ, PLM, ERP, suppliers and engineering, sourcing, finance and sales approvals | Requirement capture, source evidence, engineering exceptions, costing inputs, approvals and the final write-back across your systems |
| Tacton CPQ | Complex product or system constraints drive the sale | A difficult multi-level configuration, conflict resolution, model administration, pricing and the order output |
| Epicor CPQ | Visual selling and CAD or manufacturing automation matter | Your free-form or configured geometry, native CAD output, BOM, production documents and ERP handoff |
| Experlogix CPQ | Industrial configuration must produce BOM, WBS and routing data, especially around Dynamics or Salesforce | Your multi-level product, pricing logic, approval path and complete ERP manufacturing records |
| Cincom CPQ | Direct, dealer and customer channels need one complex-product selling process | Role-specific guided selling, price consistency, proposal output, approval and the PLM/ERP connection |
| Infor CPQ | The business wants configuration and enterprise quoting close to an Infor estate | Product rules, quote-to-order flow, bid documents and the exact ERP records created |
| NetSuite CPQ | The configurable item and transaction should stay close to NetSuite | Question-and-answer rules, pricing, generated records, revision behavior and manufacturing depth |
If maintained product rules are the main problem, Bourne should not pretend to replace a mature constraint engine. Use Tacton, Epicor, Experlogix, Cincom, Infor or NetSuite when one of them owns that job better. Bourne can call the configurator and manage the customer work around it.
Run the proof on five real cases
Do not let vendors choose the test data. Give each one the same product definition, customer records, cost inputs and expected outputs. Include the people who must maintain the model and receive the order. A proof that ends at the quote screen misses the expensive part of manufacturing CPQ.
| Case | What it tests | Pass condition |
|---|---|---|
| Common order | Seller speed and guided flow | Sales completes it alone and every output matches the baseline |
| Difficult valid order | Constraint depth and calculations | The engine finds a valid solution and explains the key result |
| True exception | Boundary between CPQ and engineering | The complete case reaches an owner and the approved answer updates the quote |
| Late revision | Version, recalculation and document control | All affected values and documents reopen; unrelated work stays stable |
| Won-order handoff | CRM, PLM, ERP and manufacturing output | The receiving team can release the work without rekeying or reconstructing it |
Score elapsed time, user effort, model changes, source traceability, output quality, manual re-entry and escaped errors. Record every workaround. If the proof requires a spreadsheet or an expert to repair the result, include that step in the future process and cost.
Budget for product-model ownership
The implementation team must collect product knowledge, decide the model boundary, clean source data, write constraints, connect systems, build documents, validate outputs and train internal owners. Licenses can be the easy part. The model becomes a product that needs a backlog, releases, tests and support.
Assign a business owner for configuration, pricing, proposal documents and downstream records. Give each one time to make decisions. A systems integrator can build the first release, but the OEM still owns the product logic and the risk of a wrong configuration.
| Cost area | What to estimate before selection |
|---|---|
| Discovery | Product families, rules, exceptions, outputs and process decisions |
| Model build | Attributes, constraints, calculations, BOMs, routings and test cases |
| Data | Items, costs, prices, customer terms, documents and revision cleanup |
| Integration | CRM, ERP, PLM, CAD, identity, portals and reporting |
| Adoption | Seller, dealer, engineering, pricing and operations training |
| Ownership | Ongoing product changes, regression tests, releases and support |
When Bourne is the best fit
Bourne is best when the quote depends on more than a maintained configuration model. A customer sends an email, specification, drawing set and spreadsheet. Sales needs the right account and prior quote. Engineering must answer an exception. Estimating needs ERP cost and supplier input. Finance must approve margin and terms. The accepted result must update CPQ, CRM, PLM and ERP without another person rebuilding the case.
Bourne gives the team an application for this work, an agent that prepares the case and automations that move approved results. It reads the customer package, assembles the requirements, calls an existing configurator when product rules can answer, routes the remaining engineering decisions, updates cost and price, prepares the proposal and carries the accepted result into order review.
Choose dedicated CPQ when product configuration, pricing and documents make up most of the problem. Choose Bourne when the hard part lives between systems and teams. Many industrial OEMs need both: CPQ to decide what can be sold and Bourne to run the customer work around that decision. See the product configuration workflow for the product view.
Arda Bulut
Arda Bulut is the co-founder and CTO of Bourne and HockeyStack. He leads engineering at Bourne, building the platform people use to create AI products, agents and automations.