CPQ Audit Logs
Finance asked who changed the discount on quote Q-4421. Nobody could answer without searching email for two days.
The challenge
Finance asked who changed the discount on quote Q-4421. Nobody could answer without searching email for two days.
A modular cleanroom partition OEM sells configurable wall systems, airlock modules, and filtration upgrades through dealer configurators. When a customer disputes a unit price on an invoice, sales ops needs to show exactly what CPQ quoted, which discount applied, and which user account generated the document. Without a central log, the investigation starts in inboxes, CRM notes, and whoever remembers the Tuesday call.
Configuration rule edits, price list updates, and rep overrides leave no shared record. A manager discovers margin variance on a closed deal and spends days interviewing admins about who touched pricing last week. External auditors ask for evidence that a review happened on a specific date; the team assembles screenshots because the system never kept an immutable trail.
Approval-workflows pages route changes through reviewers before publish. Configuration-governance pages separate authors from publishers. Access-control pages define who may log in. Audit logs are different: they record what already happened, who performed each action, when, and what changed, so investigations and disputes resolve from evidence instead of memory.
Inquiry to config to price to approval to order needs a timestamped record sales, finance, and compliance can query after the fact, not a folder of forwarded emails rebuilt under deadline.
How it works
How Mercura audit logs capture CPQ activity
Mercura writes a log entry for CPQ actions: catalog and rule changes, pricing updates, quote creation and revision, approval decisions, user sessions, and API calls. Each entry stores actor identity, timestamp, action type, object reference, and before-and-after values where applicable. Records append to a store users cannot edit or delete, including administrators. Sales ops and compliance search by user, object, date range, or action type and export results for external review or SIEM forwarding. Approval and governance pages prevent bad changes; audit logs prove what occurred when questions arrive later.
What's included
What CPQ audit logs cover
- Activity logging across configuration, pricing, quotes, and approvals
- Append-only store with tamper-evident records
- Actor, timestamp, action, object, and before/after values per entry
- Filtered and full-text search across log history
- Date-range exports for external audit workflows
- Stream to SIEM or log management platforms
- Per-user activity reports for access review
- Configurable retention for long-term compliance needs
The difference
CPQ investigations before and after audit logs
- Discount and pricing changes untraceable without inbox search
- Customer disputes stall while sales rebuild quote history manually
- Compliance reviews rely on screenshots and verbal confirmation
- Margin investigations interview admins instead of querying records
- No proof of system state on a specific past date
- Any CPQ action searchable in seconds with actor and timestamp
- Quote disputes answered with exact record and calculation context
- Compliance evidence exported from immutable log entries
- Margin reviews start from filtered activity history
- Historical system state documented for contract disputes
Real-world application
Example workflow: cleanroom quote rate dispute
An OEM of modular cleanroom walls and pass-through airlocks sold through regional dealers. A hospital customer claimed invoice pricing exceeded the rate on their signed quote for an ISO Class 7 suite with optional HEPA upgrade. Sales ops opened Mercura audit logs, filtered by quote number and date range, and retrieved the generated document, applied contract tier, discount line, and rep account within minutes. Evidence went to the customer the same afternoon; accounts receivable cleared payment without legal escalation. The dealer later used the same log view to trace an unauthorised price override on a different quote.
Business impact
Why audit logs are the forensic layer CPQ governance depends on
Audit logs turn CPQ activity from guesswork into queryable evidence. They complement approval routing, publish permissions, access control, and version history views. Mercura does not replace your legal hold process or enterprise SIEM policy. Someone must define retention and who may export logs. If the pain is "we know something changed but cannot prove who or when", immutable audit logs in CPQ align inquiry, configuration, price, approval, and order with records finance and compliance can defend months later.
Search who changed a quote, price, or rule in seconds
Book a demo and filter audit logs by quote, user, and date until the before-and-after trail is visible.
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.