Use case · Dresses and occasion wear

Generate on-model photos of dresses with the drape and the length legible

Supply full-length front and back photos with waist, hem and closure details. Your assistant loads Product page set, shows the credit estimate, and the AI reviewer compares drape and length with your references.

Set up Uwear MCPCheck model credit rates
Model wearing a space-dyed knit maxi dress, full-body front on the Pure White studio, generated with nano-banana-pro through the Product page set template

Front hero from the Product page set template: space-dyed knit maxi dress on the Pure White studio, generated with nano-banana-pro through the Uwear MCP.

Production signals

  • Source photos guide the brief
  • Cost approval before generation
  • Automatic QA, on or off

Mechanism

How does the assistant build the photo set?

Model wearing the same space-dyed knit maxi dress, full-body back camera edit on the Pure White studio, generated with nano-banana-pro through the Product page set template
Back view from the same Product page set run: a camera edit of the front hero, so the model, light, and studio carry over. Generated with nano-banana-pro through the Uwear MCP.

Ask the Uwear MCP to prepare Product page set from full-length dress references. Camera edits reuse the front result; waist, hem and back details stay explicit review requests.

Workflow

The production loop

  1. Prepare the source views

    Supply full-length front and back flats, waist and seam details, hem, slit and zip photos. Show pleats, tiers, each actual colour and the intended styling.[1][2][3][5]

  2. Approve the proposed template

    Start with Product page set and Basic white photoshoot. Ask the assistant to flag missing views and show the credit estimate before generation.[11][7]

  3. Compare the results

    QA is automatic and toggleable: when on, an AI reviewer compares results with source photos and retries flagged results.[11]

Outcomes

What this unlocks

  • Review the full hem and back construction

    Treat pleats, tiers, slits and closures as separate checks. Do not infer unseen lining or turn a generated clip into evidence of fabric behaviour.[1][2][3][5]

  • Check the destination brief

    Zalando’s apparel guide calls for back and front crops to switch when a distinctive selling feature is on the back. This is conditional, not a rule for every dress. Its AI/model eligibility wording remains unresolved; check the destination brief.[8][9]

Run it from your assistant

Run this photoshoot from your AI assistant with a Uwear template.

Connect the Uwear MCP server to ChatGPT, Claude, or Codex and ask for the Product page set template. It is a batch workflow that runs once per garment: front, upper-body, and back product-page shots on a white studio background, plus a 360-degree video, from one garment photo. Any Uwear account can load it by name, and the assistant shows a costed brief in credits before generation starts.

For a separate campaign, propose Instagram drop with High-Street Color Cast Studio: three lifestyle photos and a clip per item. Fabric motion and transparency need separate review.

Copy this prompt into your assistant

Use the Uwear MCP to prepare a Product page set for my uploaded dresses with Basic white photoshoot on Pure White, using nano-banana-pro. Review the full-length front and back photos and the waist, hem and fastening details. Flag missing source evidence. Show the costed brief in credits and wait for approval. Turn the AI reviewer on to compare results with source photos and retry flagged results. Return image and video URLs, with unresolved dress-detail checks noted for review.

Set up the MCP server

What one run does, per garment

  1. Generate the front hero

    One full-body front photo of the garment on the template model, in the Basic white photoshoot art direction on the Pure White studio location.

  2. Edit to the upper-body crop

    A camera edit that reframes the front result to an upper-body front frame instead of generating a new image, so the crop comes from the same session as the hero.

  3. Edit to the back view

    A second camera edit of the front result to a full-body back frame, so the product page gets the back of the garment from the same session.

  4. Render the 360 turn

    A 5-second Kling 3 Pro video from the front photo: the model turns a slow, full 360 degrees in place, garment readable throughout.

Outputs per garment

  • Full-body front photo, 2K, 2:3
  • Upper-body front photo, 2K, 2:3
  • Full-body back photo, 2K, 2:3
  • 5-second 360-degree video

The setup the template pins

Template kind
Batch workflow: runs once per garment row
System key
demo_full_pdp_test_white_studio
Art direction
Basic white photoshoot is the starting system art direction. For the separate Instagram drop proposal, swap to High-Street Color Cast Studio.
Location
Pure White (system studio location)
Model
The Uwear system model by default; the assistant can swap in one of your saved models when it proposes the brief
Image model
nano-banana-pro, 2K, 2:3
Video model
Kling 3 Pro, 5 seconds
QA
Optional. With the AI reviewer on, each result is checked against the source product photo and flagged results are retried
Approval
The assistant shows a costed brief in credits before anything generates

Frequently asked questions

Supply full-length front and back flats, waist and seam details, hem, slit and zip photos. Show pleats, tiers, each actual colour and the intended styling.[1][2][3][5]

Product page set with Basic white photoshoot on the Pure White studio. The default batch workflow makes front, upper-body and back photos at 2K, 2:3 with nano-banana-pro, plus a 5-second 360 video. The assistant shows a costed brief before approval.[11][7]

Compare full-length and detail references. Reformation describes a back slit, Self-Portrait a tiered skirt and Aje a gathered waist. NotShot reports an invented waist seam that splits a dress into two pieces. The template does not establish fabric motion or transparency.[1][2][3][4]

Zalando’s apparel guide calls for back and front crops to switch when a distinctive selling feature is on the back. This is conditional, not a rule for every dress. Its AI/model eligibility wording remains unresolved; check the destination brief.[8][9]

QA is automatic and toggleable: when on, an AI reviewer compares results with source photos and retries flagged results. Use the Uwear MCP first. Credits cost $0.10 per credit; see /models for model rates. The REST API is the fallback for pure automation, with polling or callbacks. Studio is the manual path.[11]

NotShot is a fit for evaluating full-body dress framing and its stated false-waist-seam check. Picjam is a fit for preparing flowing dress sources. Neither offer’s output was tested here.[4][5]

Sources and access dates

  1. [1]
  2. [2]
    Self-Portrait: tiered dress

    Accessed 2026-09-07

  3. [3]
    Aje: gathered dress

    Accessed 2026-09-07

  4. [4]
    NotShot: dress workflow

    Accessed 2026-09-07

  5. [5]
    Picjam: full-length sources

    Accessed 2026-09-07

  6. [7]
  7. [8]
    Zalando: apparel image guide

    Accessed 2026-09-07

  8. [9]
    Zalando: AI and model rules

    Accessed 2026-09-07

  9. [11]

Next step

Map this workflow into your catalog operation.

Start with the use case, then decide whether the right access path is Studio, API, MCP, or a custom enterprise rollout.

Set up Uwear MCPCheck model credit rates