Zalando designer apparel needs 5 views, shoes 4: a batch grid

Zalando's Premium/Designer guide lists five compliant images for apparel and lingerie, four for shoes, four for bags, accessories and jewellery, and three for underwear (read 2026-10-02). Build one shot grid per article type and track each cell as done, photographed or generated, so a missing view is visible before upload.

The view lists

From the Premium/Designer guide (read 2026-10-02). The standard image guidelines ask for fewer, three for apparel, accessories and shoes (read 2026-10-02).

Which cells Sume can fill

Front crop, full body style view and back view are model views, and the same page asks for real models there (see the model-view post). That leaves packshot-type cells: primary packshot, side, back and top views of shoes, and detail views.

Even those need care. A generated back view invents what you did not photograph, and Zalando's page requires the article to be fully recognizable. Generate from a real photo of that angle, or photograph it.

Track it as data

One row per SKU, one column per view, a status per cell. Submit one job per cell with an Idempotency-Key and the SKU and view in metadata (Jobs and results). If you drive it as a Format, a bulk run holds up to 100 items per queue, and a queue marked completed only means every item is terminal, so read counts.failed before you call the grid done.

Counting a collection

A collection of 40 apparel articles needs 200 compliant images at the designer tier: 40 times five. Knowing that number before the shoot lets you decide how many cells are photographed, how many are processed, and what the budget for each is. Fill the grid in a spreadsheet first; it is the cheapest way to find the gaps.

Before upload

Check size against the 1800 x 2600 minimum for designer brands (request 1808 x 2608), the white packshot background, and that no two images are duplicates, since the guide lists duplicates as a restriction.