What it is
Oracle CPQ is the configure-price-quote product Oracle bought as BigMachines in 2013 and now sells as part of Oracle Fusion Cloud Customer Experience. A rep configures a product against rules, the pricing engine applies price lists, discounts and approval policy, and the quote produces a proposal document and, downstream, an order. Admins extend all of it with BML, Oracle’s own scripting language, and the help site still lives at help.bigmachines.com.
Gartner named Oracle a Leader in the 2026 Magic Quadrant for CPQ Applications, published in January 2026 with 16 vendors evaluated; Oracle’s March 17, 2026 release calls it the ninth consecutive year. Releases ship quarterly under A-D labels (26A, 26B, 26C), and the product is moving closer to Fusion: Oracle’s documentation now refers to “Oracle CPQ running in Fusion” as a deployment, with community threads reporting it available inside the Fusion instance from 26C.
The AI surface arrived in 2025-2026. 25C added an AI quote assistance agent. 26B added a Quote Generation Supervisor Agent that, per Oracle’s readiness notes, assembles a quote by orchestrating configuration, pricing and policy checks from CPQ templates and master data, plus AI-assisted product entry that extracts line items from a customer’s PDF into the Redwood quote screen. Oracle’s own 26B page calls the agent by two different names, a sign of how new it is.
Why it shows up in RevOps stacks
- It is on every Salesforce CPQ exit shortlist. Salesforce stopped selling Salesforce CPQ to new customers in March 2025; existing customers still renew and get support, and no end-of-life date is announced. Buyers re-platforming list Agentforce Revenue Management, Conga CPQ, DealHub, Nue and Oracle. Oracle’s CX blog is courting these teams directly.
- It does not require leaving Salesforce. The Oracle CPQ Connector for Salesforce is a managed package that puts CPQ quoting inside the Salesforce opportunity. Versions 7.x and older 8.x have been out of support since 22D, so a new deployment runs on the latest version 8 release.
- It is the native option for Oracle ERP shops. If orders, pricing and fulfilment already run on Oracle Fusion, CPQ keeps quote-to-order inside one vendor’s data model and support contract.
Pricing reality
Oracle does not publish a CPQ figure on its sales pages; it sells per user per month, negotiated by users, modules and integration scope. Listing sites quote a starting price of $240 per user per month (TrustRadius, ITQlick), with a Standard edition reported from $130. At $240, 100 quoting users is $288,000 a year in licences before implementation.
Implementation is a separate, large line. ITQlick estimates $25,000 to $75,000 for a small deployment and more than $100,000 for an enterprise one, and reviewers on G2, TrustRadius and Gartner Peer Insights consistently describe long, BML-heavy projects run by partners. Budget for a dedicated CPQ admin after go-live too; several reviewers name that as a requirement, not an option.
Best for
Deal desk and RevOps leaders at enterprises selling configurable products or services with layered pricing, especially companies already on Oracle Fusion ERP, or Salesforce shops that want an enterprise-grade engine without moving to Agentforce Revenue Management. It suits teams with an admin who will learn BML.
It is the wrong buy for a SaaS team selling seats and usage tiers. That team gets live faster on DealHub or Nue, and if the catalog is a few SKUs at list price, it may not need a CPQ at all; the CPQ definition shows where that line is.
Versus the alternatives
Agentforce Revenue Management (formerly Salesforce Revenue Cloud) is the market-share incumbent. Pick it when Salesforce is your system of record and one platform matters more than pricing depth. Pick Oracle when your ERP is Oracle, or when you want the quote engine outside Salesforce’s licence stack.
Conga CPQ is the other heavy engine, now with PROS price optimization. Pick Conga when the hard problem is computing price (rebates, channel programs, margin guidance) or when part of the org runs Dynamics 365. Pick Oracle when the hard problem is quote-to-order into Oracle back-office systems.
DealHub wins on deployment speed and a buyer-facing DealRoom for subscription businesses. Nue is the fastest-growing entrant, with CPQ, billing and revenue recognition on one data model for Salesforce-native SaaS companies. Tacton wins when the complexity is engineer-to-order configuration with CAD output rather than price.
If none fit, the gap is usually an unowned price book. Settle discount policy first; the deal desk pricing skill shows that layer.
Watch-outs
- BML is a skill you have to staff. Reviewers describe a steep learning curve and scripts that become hard to maintain and slow on large configurations; Oracle ships a Performance Reviewer that flags BML patterns like nested loops. Guard: require the partner to document every BML script and hand over admin, run Performance Reviewer before go-live, and load-test with your largest real quote.
- Quarterly updates remove things. Direct Login and SOAP v1 web services were removed in 26A (which can break SSO built on the SOAP login API), near-real-time sync from Oracle Sales was removed in 26B, and Proxy Login goes in 27A. Guard: assign an owner to read each release’s deprecation notices and regression-test integrations in a test environment before every update.
- The Salesforce connector has a version floor. Out-of-support managed package versions will eventually stop connecting. Guard: confirm the package version in your org during evaluation, put connector upgrades on the release calendar, and test search and reporting, which Salesforce users find narrower inside CPQ.
- The agents are brand new and Fusion-shaped. The 26B supervisor agent shipped this year, and community posts describe CPQ agents being configured in Fusion while CPQ runs as a separate instance. Guard: before the agent counts toward the business case, have Oracle show it producing a quote from your catalog in your tenant topology, and get the licence and setup requirements in writing.
- The Fusion transition is underdocumented. Customers on community threads are asking for a supported migration path from standalone CPQ to CPQ running in Fusion, without published answers. Guard: if you sign a multi-year term now, write into the contract which deployment you are on and who pays for any move.
For where CPQ sits next to billing, CLM and the general ledger, see the quote-to-cash stack.