Service catalogues evolve. A provider may change a session length, replace an included component or adjust the location. Customers who booked earlier should not discover that their receipt now points to a different offer. A token-based payment record is durable only in a limited sense if the commercial promise attached to it can disappear.
Keep the accepted version
The order should retain a dated copy of the relevant description, price basis and conditions. Linking only to a live web page is insufficient when that page is routinely edited. A compact offer snapshot lets support compare the accepted service with the provider's current catalogue without relying on screenshots supplied by the customer after a disagreement.
Classify the change
A corrected spelling and a changed service location do not deserve the same response. The provider needs a practical way to identify changes that affect the customer's decision. Material changes should trigger a clear notice and appropriate options. Minor corrections can be recorded without creating unnecessary alarm or repeatedly interrupting an otherwise straightforward service journey.
Keep the provider accountable
The business delivering the service should approve changes to its offer, even when an ecosystem platform publishes the page. That approval creates a reliable boundary between editorial presentation and commercial responsibility. A platform team should not inadvertently alter an entitlement while improving the wording, simplifying a page or adapting the content for another language.
Preserve trust through revisions
For ALFA, a catalogue that remembers its history can support a growing network of providers without confusing earlier customers. Versioning is not merely a technical archive. It is a way of showing that a customer's accepted agreement still matters after the marketing page changes, and that any replacement offer is explained rather than assumed.
