CPQ Approval Workflows
Product manager published a label-width rule at 4pm Friday. By Monday, dealer quotes included combinations engineering had blocked for two years.
Approval engine · session
Multi-object routing
Input
Configuration rule
Approval engine
One framework · object-type routing
Reviewer
Product Engineering
Quote send approval is a specialised case · this engine covers any governed CPQ object
The challenge
Product manager published a label-width rule at 4pm Friday. By Monday, dealer quotes included combinations engineering had blocked for two years.
A labeling and print-apply equipment OEM maintains hundreds of compatibility rules between print engines, media widths, and applicator heads. Changes are supposed to pass engineering review before they reach the production CPQ environment dealers configure against. In practice, admins with publish rights edit rules directly, and email sign-off happens after the change is already affecting quotes.
When a bad rule ships, inside sales and channel partners quote valid-looking configurations that manufacturing cannot build. Rollback means searching Slack threads to learn who edited what, then manually reverting while open quotes still show the wrong combinations. Pricing rule updates and configuration templates follow the same informal path.
Quote-approval-workflows pages control whether a finished quote can leave sales. Configuration-governance pages define who may author changes. Audit-log pages record what happened after the fact. Approval workflows are different: they route configuration rules, pricing updates, templates, and catalog edits through review before those changes publish to production CPQ.
Inquiry to config to price to approval to order depends on master data your team trusts. That trust requires a publish gate on CPQ changes, not a policy slide deck reps ignore when deadlines press.
How it works
How Mercura routes CPQ changes through approval before publish
Product ops define approval rules per object type in Mercura: configuration constraints, pricing rules, configuration templates, catalog entries, and related CPQ assets. Authors work in staging; when they submit for publish, the workflow evaluates risk triggers such as affected product families, margin impact flags, or change category. Required reviewers receive a task with diff preview showing exactly what will change in production. Approve publishes; reject returns the draft with comments. Multi-level chains cover pricing committee plus engineering lead on high-impact edits. Delegation handles absence. Every decision is recorded on the object. Quote-approval-workflows enforce policy at quote send; this capability enforces it on the rules and prices quotes depend on.
Routing patterns
Sequential and parallel review
Change preview
Approvers see what will change before deciding
Configuration rule change
Requested by Anna Jensen · Affected configurations 148
Illustrative demo data
Before
Max load = 1200 kg
After
Max load = 1500 kg
What's included
What CPQ approval workflows cover
Trigger
- Approval routing for rules, pricing, templates, and catalog changes
- Per-object-type rules: who reviews, under what conditions, in what order
Route
- Multi-level and parallel approval chains
- Delegation and escalation when reviewers are unavailable
Review
- Diff preview so approvers see production impact before release
- Publish blocked until required reviewers complete sign-off
Record
- Decision history searchable by object, date, approver, and outcome
- Works alongside quote send approval and configuration governance roles
The difference
CPQ changes before and after approval workflows
Informal sign-off after publish
- 01 Rule and pricing edits reach production before reviewers respond then
- 02 Dealer quotes use combinations engineering thought were blocked then
- 03 Rollback depends on memory and chat history then
- 04 Compliance audits cannot prove controlled review occurred then
- 05 No single view of pending CPQ changes awaiting approval
With Mercura
- 01 Publish held until configured reviewers approve the change
- 02 Approvers see diff preview before production CPQ updates
- 03 Rejected drafts return to authors with documented comments
- 04 Approval evidence stored on each object for audit review
- 05 Managers see pending CPQ approvals across teams in one place
Real-world example
Example workflow: print-apply compatibility rule change
An OEM of print engines, applicators, and factory labeling lines sold through dealer configurators. A product manager widened allowed media width on a popular engine series to unblock a channel promotion. The edit skipped engineering review and published Friday afternoon. By Monday, three dealer quotes paired the engine with applicator heads the factory had retired. After Mercura approval workflows required engineering sign-off on constraint changes before publish, the same promotion request generated a diff preview showing affected BOM paths. Engineering rejected the draft, authors adjusted the rule set, and only then did dealers see the new combinations in production CPQ.
Business impact
Why approval workflows are the publish gate for CPQ master data
Approval workflows turn governance policy into an enforced step before configuration rules, prices, and templates reach production. They complement quote send approval, configuration authoring permissions, audit logs, and access control. Mercura does not replace your change advisory board or quality system documentation outside CPQ. Someone must define reviewer roles and keep routing rules current when product lines split or merge. If the pain is "we changed a rule and quotes broke before anyone reviewed it", publish-gated approval in CPQ aligns inquiry, configuration, price, approval, and order with master data sales and manufacturing can trust.
Business impact
Controlled changes
Publish held until required reviewers approve.
Consistent review
Per-object-type rules define who reviews and in what order.
Compliance evidence
Approval history searchable by object, date, approver, and outcome.
Compare
Quote approval vs approval workflows
| Quote Approval Workflows | Approval Workflows | |
|---|---|---|
| Scope | Quotes | Any governed CPQ object |
| Typical trigger | Discount, margin, deal value | Change type, risk, object, policy |
| Typical reviewer | Sales / Finance | Sales, Pricing, Engineering, Product, Compliance |
| Outcome | Quote can/cannot proceed | Change can/cannot take effect |
| Primary use | Commercial policy | Enterprise governance |
Quote Approval is a specialised use case of structured approval — not a more advanced product.
Governance map
How identity, permissions, change, review, publish, history, and evidence connect
Workflow complete · change ready
See CPQ rule changes held until reviewers approve publish
Book a demo and walk through a configuration edit blocked in staging until engineering signs off with diff preview.
Let’s build together.
We empower manufacturers to master product modeling, streamline quoting process, reduce errors, and ultimately deliver the tailored solutions that customers demand.