Photos and video for 200 SKUs: planning views and deliverables

How to plan photos, videos, views and formats per SKU, including parallel production and review for a 200-product collection.

DELFI ·

200 sku productionai catalog photos and videosbatch visual productionai virtual talent

Article image

Cover image: production by DELFI for Topper.

To plan photos and video for 200 SKUs, calculate deliverables before setting a schedule. One SKU may need several views, video and adaptations. This guide focuses on defining that scope; examples illustrate planning, not measured client results.

Build a deliverable inventory

For every SKU, record category, variant, physical garment availability, required photos, any video, channels and priority. If the color changes, decide whether it needs its own record and references. Keep unavailable products separate from urgent launch items.

To record these decisions in a working document, use AI production tracker for 200 SKUs: batches and status.

When views and adaptations multiply the file count, use How to organize more than 1,000 fashion assets with AI.

Group the collection by difficulty and dependencies

As an example, 200 SKUs could be organized into four batches of 50. The first should represent the whole collection’s complexity, not only basics. Use its lighting, model and styling decisions to inform later batches without assuming every product needs identical treatment.

At DELFI, 50 SKUs is the production minimum. The actual batch structure and schedule depend on the collection and agreed deliverables.

Create the image. Preserve the product.

DELFI combines generative AI with non-generative tools that preserve logos, prints, garment design and fit. By keeping those details instead of generating them again, we avoid the distortion that can come from reinterpreting them.

A single photo also takes 1–2 hours of compute time because non-generative methods take longer to run. That additional work helps preserve product fidelity. Photos are processed in parallel: 100 photos processed at once take approximately 1–2 hours of compute time for the batch, not 200 hours. Time is not added photo by photo. Compute time starts after DELFI approves preproduction. Training, preparation, review, corrections and delivery are scheduled separately for each collection.

See how we preserve your product.

Estimate files rather than promising volume

If each SKU hypothetically required three photos, the scope would be 600 photos before videos or adaptations. This is planning arithmetic, not a standard package or delivery guarantee. Define what counts as a new photo and what counts as a format adaptation.

Review by status

  1. Awaiting references or garment.
  2. In production.
  3. In product and brand review.
  4. Corrections requested.
  5. Approved and delivered.

The approver should identify the SKU and version without opening every file. Consolidate feedback by batch and distinguish product blockers from styling preferences.

Finish with a verifiable handoff

Compare the delivery against the agreed inventory. Check naming, formats and variant matching as well as visual quality. DELFI manages production and human quality control; your brand validates which assets are ready to publish. Do not publish an incorrect variant just to complete a folder.

Real production example: DELFI × Falabella

The following material was produced by DELFI for Falabella. It illustrates visual direction and deliverables, not measured sales results or a comparison against the original garment.

Blue trainers with light laces and a denim miniskirt beside a black stool · Falabella × DELFI

Off-white trainers with burgundy stripes and straight-leg jeans on a brown leather sofa · Falabella × DELFI

Explore the source case and more examples

Group by family, not only quantity

Separate basics, denim, tailoring, knitwear, outerwear, footwear and accessories according to the real collection. Validate a representative reference per family before expanding. Equal SKU counts may require different work.

File and batch inventory

  • SKU, variant and family:
  • Main view, back, detail and video:
  • Derived channel formats:
  • Priority and batch:
  • Status and owner:
  • Agreed and received total:

Two hundred SKUs with three photos would mean 600 photos: a calculation example, not a standard package or guarantee.

Continue reading

Your next collection

DELFI organizes talent and production around collection priorities. File counts do not measure sales: each SKU needs relevant views and correct publication before evaluating performance.

What product do you want to promote, and what does its shopper need to see? Use that answer to agree the talent, usage and production scope.

Discuss your collection with DELFI