Zalando image rejection 117 and 123: too few views, a mannequin

Zalando's image guidelines list two common rejection codes: ACS Reject Reason 117, where the minimum image requirement is not met, and ACS Reject Reason 123, where a visible mannequin appears in a mandatory packshot or model view. Fixing 117 means supplying the required number of distinct compliant views; fixing 123 means a view with no mannequin showing. Both come from Zalando's page, updated October 1, 2026 (read 2026-10-02).

What do the two codes mean?

The page states the cause, not a fix. For 117 it says unmet minimum image requirements trigger rejection. For 123 it says visible mannequins are not allowed in mandatory packshots and model views. The "Don'ts" list adds duplicates: do not submit duplicate images. The apparel guide repeats it: duplicating images to meet the count is not allowed and leads to rejection.

Keep a log per article: the reject code, the views you resubmitted, and the Sume job id behind each generated view. Zalando's page says it reserves the right to reject AI-generated assets that do not represent the product accurately, so a resubmission with a generated view should be one you have compared against the real item. If a code repeats after you fixed the cause, re-read the current page, since it is updated from time to time and the codes and wording can change.

How do I fix 123 with an edit?

If your source photo shows a mannequin, an image edit that removes it and keeps the garment shape is the direct route. Send the photo as an input_references item on POST /v1/images and say what must stay: cut, colour, print, seams, labels. Zalando also says not to remove straps or inner back views on apparel packshots, so tell the model to keep them.

A generated result is not automatically compliant. Zalando says it can reject AI-generated assets that fail to represent the product accurately, so compare the output against the real garment before upload. AI ghost mannequin covers the prompt in more detail.

How do I fix 117 without duplicates?

Count first. A set of near-identical crops will not help, because duplicates do not count. Each additional view has to be a different compliant view, such as front, back or a detail. Request one edit per view, each with its own Idempotency-Key, so a retry after a timeout does not create a second paid job. Reuse one winning ad across a catalog shows the one-job-per-SKU pattern.

Per-category counts are in the count table post.

What should I do next?

Here is the short version, in the order to do it.

• Read the reject code in your Zalando account, then match it to the cause above.
• For 123, remove the mannequin and keep straps and inner back views.
• For 117, add distinct views, not copies.
• Check every generated view against the real product.