What to do when changing your store's domain

Request the change from the store connection so that support can validate the new domain and keep the business, public URL, widgets, and integrations synchronized. The previous public URL redirects to the new one when the change is applied.

If you only change the domain and keep the same platform and identifiers, there is usually no need to migrate reviews, products, or orders. If you also change CMS or platform, it is treated as a migration: create the new connection, synchronize the complete catalog, and prepare the product equivalences preferably using the numeric IDs from both platforms. EAN, SKU, or MPN are less reliable alternatives.

Email domain and sender: after changing to the new domain, first validate the email domain and then the first sender from that domain, always. Domain validation requires the configuration indicated by Revi, such as SPF and DKIM; the validation of the first sender requires opening the link sent to that address.

When there is already a verified sender from that same domain, new senders you add under the domain are validated automatically. A validated sender from another domain does not replace the validation of the new domain.

If there is a valid domain and sender, invitations will be sent with one of the available senders. If both conditions are not met, Revi will use its own sender from revi.services to avoid interrupting the sending. You can temporarily stop automatic invitations while you complete the validation.

Open a ticket with the previous and new domains, previous and new CMS, affected connections, change date, and any validation errors. If there is product migration, attach the equivalences file.