CPQ reference: definitions, data models, timelines and vendor explainers
Short, dense, heavily anchored pages: what a term means, which objects a package uses, when something happened, who owns a product. Every definition is stated in the first sentence so it can be quoted whole. Three data models are documented object by object from vendor documentation.
The terms people swap, and the dates that matter.
Object by object, from the vendor’s own documentation.
Who owns it, what it is, what it publishes.
How these pages are written
Each reference page leads with the definition or fact in its first sentence, so it can be lifted as a citation and still be true and attributed. Object names are set in monospace and taken from the vendor’s documentation, never from memory. Dates come with a source. Where something has not happened — an end-of-life date, a published price — the page says so explicitly rather than leaving a gap.
End of sale means Salesforce no longer sells CPQ to new customers (since March 2025); existing customers keep their licences, can renew, add users and get support. End of life would mean no support or maintenance — Salesforce says that has not happened and no date has been announced (Salesforce). Full page: end of sale vs end of life.
Ready to run the numbers?
Published licence prices, a fixed implementation fee, and typical timelines by source platform.