Remapping Variants to Another Product Cluster

Overview

You may need to reassign existing product variants to another product cluster (e.g. when a variant was added to the wrong product).

Solution

1. Submit a request to Symphony Support, including the:
   1. ID of the source product cluster from where the variants have to be moved,
   2. ID of the target product cluster to which the variants have to be moved,
   3. and IDs of the variants. Mention if you want to move all the variants of a product in which case you don't need to mention any variant IDs.
      Once the variants are remapped, they will be accessible under the URL of the new product.
2. Mention in the support ticket if you want to have a redirect from the old product URL to the new one. 

<supportagent>

The ticket will mention the IDs of the source and target product clusters. If the brand has requested to move all variants of a product or the ticket doesn't mention variant IDs then remap all the variants of the source product cluster or remap only the mentioned variants.

The ticket might also mention if a redirect has to be performed from the source product to the target product.

1. If the variant IDs are not supplied, or the brand wants to map all the variants of the source product cluster to the target product cluster, then collect the list of all the affected variant IDs in the source product cluster from the database:

   SELECT Product_id
   FROM ProductCluster_Product
   WHERE ProductCluster_id = <Old/incorrect Product Cluster id>

2. Create a Change Request Jira ticket under the SPC project including the queries to map variants to the correct product cluster and roll back the change.
   
   1. Query to remap variants from one product to another

      UPDATE ProductCluster_Product
      SET ProductCluster_id = <New Product Cluster id>
      WHERE ProductCluster_id = <Old/incorrect Product Cluster id>
      AND Product_id = <Variant ids separated by comma>;

   2. The rollback query can be created by switching the new and old product cluster IDs in the above query, like so

      UPDATE ProductCluster_Product
      SET ProductCluster_id = <Old/incorrect Product Cluster id>
      WHERE ProductCluster_id = <New Product Cluster id>
      AND Product_id = <Variant ids separated by comma>;

   Note: If remapping needs to be done urgently (e.g. due to promotion), you can elevate the case along with the queries to the PS team who also have write access to the database.
3. Additionally, you may need to set up a URL redirect from the initial product cluster to the product to which the variants were remapped (if explicitly requested by the customer).

After remapping from the database, check under Catalog > Products and find the product to which you mapped the variants and open it, expand the Variants/SKUs section and check if newly mapped variants are in place and displayed properly.

Images and the ability to manage variants are missing.

Variants are displayed properly

If the images are not displayed or the ability to modify variants is missing, you will need to perform the following steps:

1. Recreate the product cluster by exporting the corrupted product and uploading (with a new identifier and URL that will be changed), and then remap all of the linked variants to the newly created product cluster.
2. After remapping is complete:
   1. Find the corrupted product (under Catalog > Products) and open it.
   2. Expand the Search Engine Visibility section.
   3. Copy the URL for this product.
   4. Add duplicate or invalid in the product URL field.
      
   5. Unpublish the product and click Save in the top right corner of the page.
      
3. Find the new product to which you mapped the variants (under Catalog > Products) and open it.
   1. Expand the Search Engine Visibility section.
   2. Paste the URL of the corrupted product (copied in step 2.c above).
   3. Publish the product and click Save in the top right corner of the page.
      

</supportagent>

Testing

After the variants are moved, they should be visible under the target product. In case a redirect was also configured and depending on the nature of the redirect configured, visits to the previous product will either redirect or show the new product without changing the page address.