How to Solve PSERR_151

Description

The Zalando error PSERR_151 occurs when an article's EAN matches an article that already exists at Zalando, but it has a different category assigned in TB.One than what is stored in zDirect. Zalando refers to categories as "Silhouettes" or "article types".

Reasons for an category mismatch are usually:

a)Zalando might have changed the category during onboarding on their own behalf to match the category in their shop.

b)You have unintentionally changed your product's category in TB.One after initial onboarding.

Zalando applies a so-called "content-freeze" to existing products. That means even if you make changes to a product in TB.One after the first upload, it keeps the product in its original state. Therefore, category mismatches usually stay unnoticed by Zalando until you onboard new colour/size variants for the product. When you export new articles for an existing product, Zalando checks the categories of these new variants.

Article Status Report Message

Solution: Update the Channel Category in TB.One

Follow these steps to resolve the issue:

1. Determine the Correct Zalando Category

•If you haven't received information from Zalando about the correct category ("silhouette"/"article_type"), contact Zalando support to find out which category to use.

•You can also check Zalando’s category guidelines for reference.

2. Adjust the Zalando Category in TB.One

•Go to "Articles > Product list" and open the affected product.

•Switch to the "Product data" tab and scroll down until you see the primary category assignment for "Zalando (Hauptkanal)".

•Update the field with the correct category as determined in step one.

•Save your settings

Assigning a category

3. Verify Property Assignments

•Changing the category may impact property mappings. Check if category-level properties (e.g., size, material, color) need adjustments. If you map at the global level only, there should be no further adjustments needed.

•Go to "Channels > Zalando (main channel) > Value Mapping" and ensure all mandatory properties are correctly assigned for the new category.

4. Check Your Import and Clusters

•If you import your product data into TB.One, update the category mapping in your import files to prevent the error from recurring.

•If you use clusters, update the Zalando category in the affected cluster as well ("Basic data > Classification > Cluster").

5. Wait for the Next Export to Zalando

•When you have configured all settings, wait for the next daily Zalando export.

•Monitor the status in zDirect to confirm that the error is resolved.