How to deal with duplicated shops behaving as one

[matks]

If you duplicate a shop (for example you want to use one for development and one for production, or one for preproduction and one for production) you will probably find out that the changes you do on ps_checkout configuration one one shop are replicated on the 2nd shop.

This is because the shop contains a unique shop identifier in the ps_configuration table and by duplicating the shop, this data was duplicated too. It is used as shop identifier so having both shops use the same UUID create this situation.

To try to avoid this, we wrote article https://help-center.prestashop.com/hc/fr/articles/13394091309074-Associez-une-boutique-%C3%A0-PrestaShop-Account

Dissociate the store before duplicating the database, in order to avoid token conflicts (stored tokens) that may impair the proper functioning of the association.

Now, if you find yourself in this situation, what should you do?

[matks]

The identity of the shop relies on the Cloud Shop Identifier. That information is stored both on the shop and in the cloud. The solution is to create a new Identity for the shop. To do so please reach out to the Support team who will proceed.

What is important is that the 2 shops have 2 different Cloud Shop Identifiers. They can be connected to the same PrestaShop Account, but we need 2 identities, one for each shop. If you have dev, preprod and prod environments, you'll need 3 identities.

[thierry-laval]

Thank you for your reply.
Would it be possible to provide us with the procedure to create a new shop identity directly, or does this need to be handled exclusively by your support team and cannot be done from the PrestaShop side?

[matks]

Hello @thierry-laval

On PS Account v8, if the module detects that there is a duplicate identity, a banner should appear and suggest you create a new identity for the shop you browse. A button is available and clicking on it should create the new identity 😉.