Quote Versioning for CPQ
The customer accepted version two. Finance opened version one. Keep every revision, line change, and accepted version on the quote record in CPQ.
Each revision
New version without losing prior history
Line history
Changes visible between versions
Accepted version
Clear record of what the customer signed
The challenge
The customer accepted version two. Finance opened version one.
A manufacturer of dust collection and fume extraction systems sends a quote for a cartridge collector, duct run, and controls package. The plant engineer asks for a higher filter efficiency rating. Inside sales creates a revised PDF, saves it as "Quote_final_v2", and emails it. The original file stays in the folder as "Quote_final". When procurement accepts, finance converts the wrong attachment because nobody marked which version is current.
Revision three changes lead time but not price. Revision two changed three line items. A manager asks what changed between versions and receives three PDFs with no diff. Dealers send their own revised files back without updating the record inside sales tracks.
Automated quote generation creates the first document from configuration. PDF generation renders output. Quote management tracks pipeline stage. Quote comparison pages show side-by-side views. Quote versioning is different: Mercura keeps every revision on the same quote record with timestamps, author, and line-level history so accepted version is explicit.
Inquiry to config to price to approval to order needs a revision trail on the quote, not a folder of similarly named PDFs.
How it works
How Mercura versions quotes
When a rep revises a quote in Mercura, the system creates a new version on the same record instead of a disconnected file. Each version stores line items, pricing, options, and configuration state at that point. Users open prior versions, see what changed, and mark which version the customer accepted. Comparison pages support side-by-side review; this capability is the audit trail underneath. Someone must train reps to revise in CPQ rather than emailing standalone PDFs, and align accepted-version labels with how finance and ERP expect orders.
What's included
What quote versioning covers
Revision record
-
New version on the same quote record for every revision
-
Line-level history between versions with author and timestamp
-
Accepted version marked explicitly on the quote
-
Prior versions accessible without rebuilding from email
Accepted truth
-
Same versioning logic for inside sales, dealers, and portals
-
Works with automated generation, PDF output, and comparison views
-
Configuration and pricing changes captured per version
-
Traceability from order entry back to accepted revision
The difference
Quote revisions before and after versioning in CPQ
- Revisions saved as new files with unclear naming
- No record of what changed between versions
- Finance and sales disagree on which file customer accepted
- Dealers send revised PDFs outside the system of record
- Managers rebuild history from email threads
- Every revision stored as a version on one quote record
- Line changes visible between version two and version three
- Accepted version marked before order conversion
- Dealers revise the same quote record from the portal
- Audit trail available without opening archived PDFs
Real-world application
Example workflow: dust collection quote revisions
A builder of cartridge collectors and duct systems for metal fabrication plants sold through regional dealers. Revisions on filter grade and duct length produced files named Quote_v2, Quote_v2_revised, and Quote_final in shared folders. After centralising revisions in Mercura, a filter spec change creates version two with line history visible, the plant marks acceptance on version two in CPQ, finance converts that version to order entry, and revision three on lead time starts from the accepted record instead of a new email attachment.
Business impact
Why quote versioning is revision discipline, not another PDF
Quote versioning keeps revision history honest between first send and order conversion. It complements automated generation, templates, PDF rendering, proposals, pipeline management, and comparison views. Mercura does not replace your document archive or contract storage system. Someone must define when reps create a new version versus edit in place, and train dealers to revise in CPQ. If the pain is "we lose track of which revision the customer accepted", version history on the quote record aligns inquiry, configuration, price, approval, and order with what finance actually books.
See revision history and accepted version on one quote
Book a demo and revise a quote until version history, line changes, and accepted version are visible without searching email attachments.
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.