After a rebrand, old names still make promises

Establish what changed before editing the name

Use the business's actual rebrand records to distinguish a public-name change from an ownership or legal-entity change. Record the effective date, former public name, current public name and the entity responsible for current operations. If responsibility for an earlier order is uncertain, mark that question for the business owner and appropriate adviser instead of letting a text replacement decide it.

An old name can have several meanings. It may be an obsolete instruction in a current refund policy, a still-monitored support address, or the accurate name on an earlier receipt. The action follows its role. Replacing every occurrence would erase useful history while potentially leaving the underlying support route unchanged.

Find the surfaces that still speak for the business

Inventory the active shipping, returns, cancellation and contact pages, then follow the policy links actually presented in checkout. Review downloadable policy files and the messages currently prepared for order confirmations, refunds and support replies. Include saved replies, signatures and images containing the former name when the team still uses them. A corrected homepage does not establish that these other surfaces were corrected.

For each touchpoint, record where it is published or used, the old identifier, the promise surrounding it and who controls the content. Distinguish a current template from an already-sent message. A policy file on a current page remains part of the inventory even if nobody intended to keep promoting the old version. A dated archived record belongs in the historical record list, with an owner who can retrieve it.

Read beyond the name itself. Check which team receives replies, which contact route customers are directed to and whether a promised action can still be performed by the named business. A new label attached to an obsolete destination leaves the practical contradiction unresolved.

Approve truthful continuity for current content

For current content, choose the accurate new reference or an explanation of the relationship between the former and current brand. Use continuity wording only when the business's records support it. If the operator changed, obtain an approved explanation of who handles current orders and earlier inquiries; do not invent a transfer of responsibilities. Keep legal interpretation separate from the editorial decision about which text is still being displayed.

The FTC's U.S. truth-in-advertising guidance requires advertising across media to be truthful, not misleading and supported. It does not approve a particular rebrand phrase or determine obligations for earlier orders. Stripe's website activation guidance separately requires the site's business name and product descriptions to align with the application and calls for contact and policy information. These are reasons to inspect the full current presentation, not evidence that a name edit satisfies every legal or provider requirement.

Where Stripe is the actual provider, compare the approved website wording with what that account has been told. For another provider, use its own request and records. A storefront edit cannot establish that the provider updated its account information or accepted the changed business.

Keep a traceable boundary between current and historical versions

Retain the earlier policy or message version with its actual date and the record owner. Publish approved changes to the current surface and record when they became visible. Do not overwrite an earlier receipt or support conversation to make it appear that the new brand was named at the time. If a public archive could be mistaken for the current policy, make its historical status and the route to current information clear while preserving the original record privately.

Finish the map by reopening each changed public page or file and checking the active message template. Record the observed name and destination, not only an editor's saved value. Keep unresolved earlier-order responsibility separate from completed copy changes. For a Prism website-review consultation, provide the public URLs, the real nature of the rebrand and the conflicting wording you want considered. Scope, responsibilities, fees and terms are agreed before work; a review does not certify continuity or approve processing.

Rebrand continuity map

Use these checks for each affected current touchpoint, maintaining a separate private record for historical versions. The map is complete only when the responsible business and approved wording are established, or the remaining question has a named owner. Do not paste customer messages or private identity records.

Worksheet entries are not submitted by Prism’s worksheet and are not saved by the site. Use record types, availability, anonymized observations, or match/mismatch results. Do not enter government identifiers, customer names or addresses, customer messages, receipt-access links, card or bank details, passwords, or keys. Send sensitive documents only through the provider’s verified secure channel.

These are temporary notes. Leaving or reloading this page may clear them. Worksheet entries are not sent automatically. If you copy notes into the consultation message and submit the form, Prism receives them as part of your request.