Separate enquiries from pricing
An enquiry form collects requirements; it does not automatically calculate a commercial price. CPQ connects configuration, pricing rules and quote documents. Identify whether you sell standard products, made-to-measure goods or service packages. Review real quotations to list the checks the sales team currently performs manually.
Turn compatible options into explicit rules
Dimensions, materials, accessories and installation choices can depend on each other. Explain incompatible selections during configuration rather than at the final step. Assign a business owner to each rule. Track which combinations require retesting when a product or option changes, instead of hiding commercial logic in undocumented code.
Preserve the basis of a price
List prices, customer groups, quantities and additional services may contribute separately. Define the authoritative price source and validity period. Save calculation inputs with each quotation so a later price-list update cannot silently rewrite an old document. Test currency, rounding and tax presentation against approved business rules.
Build discount approval and versioning together
State what a representative can approve and when a manager must review. Distinguish pending approval from ready-to-send documents. Changes to a quotation already shared with a customer should produce a new version. Make the validity of the previous version visible to both operations and sales staff.
Keep CRM and ERP identifiers consistent
Map customers, products, price lists and opportunities explicitly. Turning an accepted quote into an order must not create duplicates on retry. Show pending work when a connection fails. Inspect sample product codes and duplicate customer records before development to identify data-cleaning requirements early.
Accept the system using representative quotes
Define expected results for standard sales, custom dimensions, incompatible choices, approval and price updates. Use anonymised historic examples and ask sales staff to validate calculations. A proposal needs rules, data sources, document format and approval roles. Describing the PDF layout alone leaves most of the workflow unspecified.
Worked example: make the scope concrete
Illustrative scenario. Adapt these checks to your own workflow.
Configurable products need compatibility rules, service charges, discount authority and currency handling beyond quantity times price. Explain invalid combinations in the interface.
A common failure and why it matters
Preserve the rule and price-list version behind a sent quotation. Draft, awaiting approval and sent are different states.
How to verify the delivered work
Test invalid options, excessive discounts and a new price list. Screen and document totals should agree. Highlight changes requiring approval when converting a quote into an order rather than silently rewriting the old quote.
Implementation and maintenance checklist
Business software should make decisions and responsibility visible. Extra fields will not solve an unclear owner, record state or next action. Run one complete process before expanding the feature list, and derive permissions and reporting from it. A management total should be explainable using the records operations staff actually enter. Review the workflow with those staff, not only with the person purchasing the software.
- Roles: Separate creating, reviewing and approving where the process requires it. Search and export must respect the same company and team boundaries as detail screens. Test an account that should not see a record, rather than checking only the administrator experience.
- Data quality: Include duplicate records, missing required information and an incorrect relationship. When correcting a record, preserve appropriate history and attached documents. Define who can merge, archive or reopen an item and what happens to connected reports.
- Handover: Name the process owner and support route, and prepare everyday operating notes. Adding a colleague or removing a departing employee should be an understood administrative task. Document what remains outside the first release so the team does not mistake an unbuilt capability for a broken one.
Further reading
salesforce.com — sales / cpqLet’s bring this idea to your product.
Define your project goals and technical needs with us.
Let’s talk about your project


