What is the Comparison step?
The new comparison step provides precise control over file data before integration into the PIM. It enables a clear visualization of differences between the values in the file and existing information in the PIM, allowing verification of accuracy and preventing unintended overwrites. This ensures informed decisions on which changes to approve or reject, maintaining data integrity and consistency.
Please check how to use it on the related article.
Configuration
- ⚠️ A PIM connector must be set up for the comparison step to function correctly (Set up a connector article)
- The setup can be more complex if the workflow has more steps required to generate the product identifier or uuid, for instance a match history step.
-
If your connector uses UUID (Universally Unique Identifier) push:
- You will also need to utilize UUID memory keys and configure the UUID reference base.
- Additionally, to ensure existing products are displayed for comparison, you will need to import your existing products into the reference base.
- If your connector uses regular identifiers: No additional configuration is required for the connector
-
If your connector uses UUID (Universally Unique Identifier) push:
When dealing with variants, the product model is derived from the first product.
For example, if we have 2 existing variant products A and B in our raw Excel file that share the same parent, we’ll use product A as the main product to generate a product model that can be compared with the existing product model from the PIM. This means that changes on the product model will only be recognized on attributes on product A, while they are ignored on product B.
Add the step to a workflow
The minimal setup is always the following: Mapping → Normalisation → Comparison → the other steps which will deal with created products.
In the project configuration, add another step and select “Comparison”.
