A new price list and an existing customer quotation are different records. Give the revised list a clear effective date, keep the old quotation intact and identify which version applies to a new enquiry. If an existing quote needs changing, communicate the revised amount and obtain agreement through the actual order process. Do not silently replace the figure in a historical record.
Version the public facts together
A price can appear in a card image, HTML text, an order selector, structured data and a support template. Update those places together so a customer does not see one amount on the page and another in the prepared message. Record the old and new values in a maintenance note. Clearing the relevant cache may also be necessary when the live site continues to serve an older asset.
Keep the quotation identifiable
A useful quote includes the plan, currency, total, date and any actual validity condition. Do not invent a universal expiry period. Keep a reference that connects the accepted details with the later activation. An editable support message is not a substitute for preserving the terms that were actually agreed. A price change should add information rather than erase the earlier conversation.
Distinguish new sales from renewals
A renewal can be a new purchase decision, but its handling depends on the real service terms. Explain the amount applicable to the requested renewal before payment. Do not assume an earlier price is permanent, and do not assume a revised public card automatically changes an already accepted order. The practical task is to make the current agreement explicit for that customer.
A practical sequence
0 of 4 steps completed on this page.
An example to work through
A customer saved a quote for a three-month term on Monday. The public list changes on Friday. Keep Monday’s quote as a record and discuss any change explicitly; editing its stored number would hide what the customer originally received.
