Freezing a quote the moment it's accepted

A quote in Welkent is a living document right up until the moment a customer accepts it: prices can update, catalog items can change, materials costs shift. That's exactly how it should work while a quote is still a draft. The moment a customer clicks accept, though, that flexibility becomes a liability. If the underlying data a quote references can still change after acceptance, what a business can prove the customer actually agreed to becomes murky, and murky is the last thing you want when a quote is the basis for a real contract.

A snapshot, not a live reference

Welkent handles this with a freeze-at-accept step. The instant a quote is accepted, its full content, prices, line items, terms, gets captured into its own standalone record rather than continuing to reference the live catalog and pricing data it was built from. What the customer agreed to is locked in exactly as they saw it, immune to whatever happens to the underlying data afterward.

That snapshot is append-only. Nothing about an accepted quote gets edited in place after the fact; any correction or follow-up is a new record, not a mutation of the old one. Combined with hashing each snapshot, this makes the record tamper-evident: if anyone ever needed to verify that an accepted quote's stored content genuinely matches what was frozen at acceptance time, the hash makes any alteration detectable rather than trusting that nobody touched the row.

Capturing more than just the content

Alongside the frozen content itself, the system records the IP address and user agent of the actual accept click. That's a deliberate choice to capture the circumstances of acceptance, not just its content, useful if a dispute ever comes down to whether a specific action genuinely happened at a specific time from a specific place.

Where a quote is MitID-signed, the signed PDF itself becomes the canonical legal record, superseding the internal snapshot as the authoritative version. The internal freeze-and-hash mechanism still matters for the majority of quotes accepted without a MitID signature, giving them a comparable level of evidentiary integrity even without a cryptographic signature attached.

A retry worker, because acceptance has to actually land

Freezing a quote at the moment of acceptance only works if that freeze reliably happens, even if something goes wrong partway through, a database hiccup, a transient failure writing the snapshot. A retry worker exists specifically to make sure an acceptance event that didn't fully complete gets picked back up and finished, rather than leaving a quote in a state where a customer believes they've accepted something that never actually got properly frozen on Welkent's side.

None of this is complexity for its own sake. A quoting platform whose quotes become the basis for real contracts has to be able to answer, with confidence, exactly what a customer agreed to and when, even years later. Building that guarantee in at the moment of acceptance is a lot more reliable than trying to reconstruct it after the fact from a system that never treated acceptance as a boundary worth protecting.

See how accepted quotes fit into the rest of the platform on Welkent's product page.