...
When using Wizart PIM integration with Zapier, it's important to note that for each supported product type in PIM, we have a specific list of fields that can be used in the Zap action. This ensures that the Zap works correctly and updates only the relevant fields in the PIM system. You can find a comprehensive list of the supported product types and their corresponding fields in our documentation:
...
As a data owner, you have the ability to use the "Update product" action allows you to edit more product fields for legacy of any product typestype. However, less fields can be specified when updating shared products owned by another brand, less fields are available. This is because shared products are owned by another brand and cannot be extensively edited extensively. As a result, and the number of fields available for updating shared products them is limited.
The mandatory fields for any action in our app are:
...
They are required for product update process to find existing sku by brand and collection in PIM, taking into a count that the product can be shared with retailer accounts e.g. with retailer’s account and can be included in multiple collections.
When the action is triggered, it maps the fields from the trigger to the corresponding fields in the PIM system and updates the product information. In other words, the app will use the provided data to compose a request to the Wizart PIM API endpoint. If custom_sku_id does not match any existing product in the PIM system, the update will fail.
How can I obtain all of these fields?
By utilizing the PIM Admin Console, you have the option to export all editable product fields from your PIM Brands as a CSV file. Alternatively, you can use your own data source, but make sure it has the matching columns.
...