Product configuration software: a buyer's guide

Requirements checklist

Area	Questions
Rules	Can it model your dependencies, exclusions and calculations? Rules-based or constraint-based?
Pricing	Options, dimensions, formulas, discounts, regional and dealer price books?
Visualization	2D, 3D, AR, drawings? Updated as choices change?
Users	Reps, dealers, customers, website? Self-service?
Integration	CRM, CPQ, ERP, PLM, CAD? Native or connector?
Data	Who maintains products, attributes, rules and models?
Output	Quotes, BOMs, drawings, routings, order data?
Governance	Versioning, approvals, audit trail, effective dates?

Know which kind you need

• Product customization software usually means consumer personalization on e-commerce: colors, engraving, materials.
• B2B configuration adds engineering rules, pricing logic and quote workflows, often for reps and dealers.
• CPQ adds pricing, discounting, approvals and quote documents on top of configuration.

Many manufacturers need two of these for different channels.

Rules-based vs. constraint-based

	Rules-based	Constraint-based
How it works	Explicit if-then rules run in order	Declared relationships solved together
Good for	Products with a modest number of options	Many interdependent options, dimensions and calculations
Watch for	Rule count grows fast; order of rules matters	Needs clean attribute data; harder to debug without good tools

The distinction matters in Salesforce: the original Salesforce CPQ package is rules-based, and its successor, Revenue Cloud Advanced, uses an attribute-based catalog with constraint-based configuration.

The Salesforce question

If quotes live in Salesforce, note that Salesforce CPQ is now end of sale. Salesforce no longer sells it to new customers, though existing customers keep support and renewals, and new development goes into Revenue Cloud Advanced. Ask every configurator vendor:

• Do you support Salesforce CPQ, Revenue Cloud Advanced, or both?
• Where do rules live: in Salesforce, in your tool, or both?
• If we migrate from CPQ to Revenue Cloud, what changes in the integration?

Scoring template

Criterion	Questions to ask	Weight
Rules engine	Can it express our real compatibility rules without code? How are rules tested and versioned?	High
Pricing	Does it support our price structure, discounts and dealer pricing? Which system prices?	High
Integration	Does it connect to our CRM, CPQ and ERP? Who maintains it?	High
Output	Quotes, drawings, BOMs and order data in our formats?	High
Admin effort	Who updates rules and products, and how long does a change take?	High
Visualization	Does 2D or 3D output help customers decide? Who builds the models?	Medium
Cost	License, implementation, model creation, integration maintenance, admin time	High

Worked scoring example (illustrative)

Weights: High = 3, Medium = 2. Scores 1–5 from the pilot.

Criterion	Weight	Vendor A	Vendor B
Rules engine	3	4 (12)	3 (9)
Pricing	3	3 (9)	4 (12)
Integration	3	4 (12)	2 (6)
Output	3	3 (9)	4 (12)
Admin effort	3	4 (12)	2 (6)
Visualization	2	3 (6)	5 (10)
Cost	3	3 (9)	3 (9)
Total		69	64

Vendor B had the better visuals and lost on integration and admin effort, the two things you live with after launch.

Running a fair pilot

Ask each shortlisted vendor to configure the same two or three real products: one simple, one typical and one of your hardest. Give them the actual rules, pricing and output requirements, including edge cases that cause errors today. Judge correctness first, then speed for the user, then effort for administrators.

Include the people who'll maintain the system. If your product team can't add an option or change a rule without the vendor, every catalog change becomes a services ticket. Ask to see rules maintenance and a real integration, not only a polished 3D model.

What the license leaves out

• Product data cleanup and attribute standardization.
• Rule modeling and testing for each product family.
• 3D model creation or conversion, if you need visualization.
• Integrations and their ongoing maintenance.
• Training for sales, dealers and administrators.

References and IT review

Ask for references with products as complex as yours, and ask them how long rule changes take and who makes them. Bring IT in early to review data handling, authentication, integrations and hosting.

Start small

Start with the product families that cause the most quoting errors or sales effort, then expand. Measure quote errors, rework, time to quote and approval rates before and after, so you know whether it worked.

Where RenderDraw fits

RenderDraw's Product Configurator adds guided, visual configuration to Salesforce-centered quote workflows. Buyers and reps make choices, rules explain conflicts, and a validated selection moves into pricing and the configured quote or proposal workflow, alongside Salesforce CPQ or Revenue Cloud. Bring one configurable product and its rules to scope an evaluation.