Skip to main content
Quality review is the human checkpoint between AI generation and the Listing Team. Once all five poses for a SKU have been generated, a member of the Review Team (or an Admin) must evaluate the complete set and either approve it for listing or reject it with guidance for re-generation. No SKU reaches the Listing Team without a passing QC decision — this gate is enforced independently of what the UI displays. The QC decision is always a SKU-level decision: you pass or reject the entire five-pose set, not individual poses. This keeps the listing handoff package atomic — the Listing Team always receives all five approved poses together.

​
Who can perform QC

Only workspace members with the Review Team role can submit QC decisions. Admins can always perform QC regardless of role. If you can see the SKU in Catalog Production but the Approve and Reject buttons are absent, your role does not include QC permissions — contact your Admin.

​
Reviewing a SKU

1

Find SKUs awaiting quality review

Open Planning → Catalog Production and use the Stage filter to select Quality review. This narrows the list to only the SKUs waiting for your decision. Use the Assignee filter to see items specifically assigned to you as reviewer.
2

Open the SKU detail panel

Click the workflow icon on any SKU row to open the live workflow panel for that SKU. The panel loads the operational workflow for that SKU — stage history, pose versions, activity trail, and the current five-pose output — updated in real time.
3

View all five poses

In the asset viewer, all five generated poses are displayed side by side. Click any pose image to open a full-size preview. Each pose card shows:
  • The pose title and type (for example: Hero front, Professional side/3-quarter, Authoritative back, Creative Gen-Z editorial, Close-up face+detail)
  • The full prompt used for generation
  • The automatic QA status (such as Automatically verified, Requires human review, or Rejected by QA)
Check each pose against the uploaded front and back references visible in the Reference details section below the pose grid.
4

Approve or reject the set

Once you have evaluated all five poses, make your decision:
  • If all poses meet quality standards — click Approve final set. An optional approval note field lets you add context for the Listing Team (marketplace requirements, deadline reminders, or flagged details). Click Approve final set to confirm. The SKU moves to Approved and a listing handoff package is created automatically.
  • If any pose is unacceptable — click Reject and request changes. The rejection guidance field is required — you must describe what failed before the rejection can be submitted. The SKU moves to Re-generation required and your notes are attached to the next generation job.
When rejecting, be specific in your notes — for example, “Back pose does not match the uploaded back image; the pallu drape direction is reversed” or “Model face changed between poses 2 and 3, creating inconsistency across the set.” Specific, actionable guidance produces better re-generation results than vague feedback like “doesn’t look right.” Your notes are passed directly as additional direction to the next GPT Image 2 generation job.

​
Rejection and re-generation

When you reject a SKU, your written guidance becomes part of the creative brief for the next generation attempt. Here is the full cycle:
  1. You click Reject and request changes and submit your notes (up to 4,000 characters).
  2. The SKU moves to Re-generation required (stage 7). The QC dialog confirms: “QC rejected. Re-generation guidance was recorded.”
  3. A Creative Team member or Planning Manager selects the rejected SKU and triggers a new generation run. The original front and back references are reused; your rejection notes are injected as additional direction alongside the five-pose plan.
  4. The generation job runs, producing a new set of five poses.
  5. When generation completes, the SKU automatically returns to Quality review (stage 6) for another round of evaluation.
  6. You review the new poses and either approve or reject again.
There is no limit on the number of re-generation cycles for a SKU. However, SKUs with repeated rejections may be manually escalated to Blocked or failed by a Planning Manager if the issue cannot be resolved through re-generation alone.

​
Pose versioning

Every generation attempt produces a separate, immutable set of pose versions. The system never overwrites previous generation outputs. From the workflow panel, you can view the full version history of a SKU to compare the current poses against earlier attempts. This is useful when evaluating whether a re-generation actually addressed your previous rejection notes. Only the latest approved pose versions are included in the listing handoff package. If you approve a re-generated set, the handoff is updated to point to the new versions — the earlier rejected versions remain in history but are never sent to the Listing Team.

​
QC status at a glance

The QC status shown on each work item reflects where the SKU sits in the review process: The stage filter and Kanban board use these statuses to group and highlight SKUs that need your attention.