> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aistudio.youthnic.shop/llms.txt
> Use this file to discover all available pages before exploring further.
# Listing Handoff: Deliver Approved Images to Your Team
> Create, send, and track frozen five-pose listing packages for approved SKUs — including automated daily email delivery and manual resend controls.
The listing handoff is a stable, frozen package of the five approved pose images for a single SKU. It is the bridge between the Review Team's approval decision and the Listing Team's marketplace work. Once a handoff package exists, the Listing Team always downloads the same five images regardless of whether re-generation or re-approval happens later — every change produces a new revision, and previously sent packages are preserved for audit.
## How handoff packages are created
A listing handoff package is created **automatically** the moment a Review Team member approves a SKU's five-pose set. The approval action freezes the specific approved pose versions at that exact point in time. You do not need to manually create a package.
If a SKU is later re-approved after additional re-generation (or after a reviewer reopens a previous approval), the system creates a **new revision** of the handoff. The revision points to the newly approved pose versions. Any previously sent handoff package remains untouched and readable in the delivery history.
Once a listing handoff package has been sent, that revision cannot be changed. If you need to re-approve a SKU with different images after a delivery has already gone out, the system creates a new revision — but the previously sent package is preserved exactly as-is for audit purposes. Recipients who acted on the original delivery are not automatically notified of the new revision; send a new delivery manually from the SKU detail panel.
## Automated daily handoff emails
Once per configured business day, an automated process selects all SKUs with unsent final approvals before the local-day cutoff time and sends a consolidated handoff email to the configured Listing Team recipients. The automated send:
* **Skips empty days** — if no SKUs were approved since the previous business day's cutoff, no email is sent
* **Respects business days** — only runs on the weekdays configured in Handoff Settings; holiday dates are excluded
* **Is idempotent** — each SKU handoff item can enter a successful delivery only once; running the process again does not duplicate deliveries
* **Validates approvals immediately before sending** — if a reviewer reopens and rejects an approval between the selection and the send, that SKU is skipped rather than sent in an invalidated state
* **Labels the delivery with the previous configured business day** — so the Listing Team always knows which business day's approvals they are receiving
To review or change the schedule, open **Planning → Catalog Production → Handoffs** (visible to Admins and members with catalog handoff management permissions).
## Handoff settings (Admin)
Admins configure the automated handoff schedule in the **Handoffs** tab:
Navigate to **Planning → Catalog Production** and click the **Handoffs** tab in the toolbar (visible only to users with catalog handoff management permissions).
Under **Schedule and recipients**, set:
* **Automatic daily handoff** toggle — enable or disable the automated send
* **Timezone** — the IANA timezone used for the send time and business-day cutoff (default: `Asia/Kolkata`)
* **Send time** — the local time the job runs each business day (default: `10:00`)
* **Business weekdays** — toggle individual weekdays (Mon–Sun) to mark which days are active
* **Holiday dates** — enter exclusion dates in `YYYY-MM-DD` format, one per line
Choose a **Recipient mode**:
* **Operational team** — send to all active members of a selected workspace team
* **Custom recipients** — send to a comma-separated list of email addresses
* **Operational team + custom** — combine both
When using an operational team, select the team from the **Recipient team** dropdown. Team membership is managed in Admin. Active members can opt out individually using their **catalog handoff email** notification preference in their profile.
Click **Save handoff settings**. Changes take effect on the next scheduled run.
## Listing Team workflow
The Listing Team receives the consolidated handoff email containing all SKUs approved since the previous business day. Each SKU in the email includes its name, batch, campaign, and a direct link to the five-pose package. Alternatively, open **Planning → Catalog Production** and filter by the **Sent to listing team** or **Ready for listing** stage.
Click the SKU to open its detail panel. In the **Generated asset package** view, all five approved poses are displayed with their QA status, full prompt, and individual download buttons. To download all five poses at once, click **Download ZIP** — this packages them as `pose-1.png` through `pose-5.png` inside a ZIP named after the SKU (for example, `summer-saree-red-poses.zip`). To download a single pose, click **Download** on the individual pose card.
Once you have the images and are ready to list, return to Catalog Production and click **Listing in progress** on the SKU row or in the detail panel. This records the listing start timestamp and confirms to the Planning Manager that work has begun.
After the product is live on the marketplace, return to Catalog Production and click **Mark as listed** on the SKU. The SKU moves to **Listed** (stage 12) and leaves the active work queue. The completion timestamp is recorded and the item appears in the **Recently completed** section of the Production Overview.
## Manual send and resend
Admins and Planning Managers with catalog handoff management permissions can trigger a handoff send or resend at any time from the **Handoffs** tab:
* **Send consolidated handoff now** — sends all currently pending approved SKUs to the resolved recipient list immediately, using the current business date as the report date. The preview panel in the Handoffs tab shows exactly which SKUs will be included and how many recipients will receive the email before you confirm.
* **Resend** — available on any past delivery in the delivery history panel. Resending uses the exact same frozen package that was originally sent; it does not re-select from current approvals. The resend is recorded as a separate delivery attempt with its own timestamp and provider result.
Both manual actions require explicit confirmation in the action dialog before any email is sent.
## Delivery history
Every send attempt — automated or manual — is recorded in the delivery history panel with the following details:
| Field | Description |
| ----------------------- | ------------------------------------------------------------------ |
| **Report date** | The business day the delivery is labeled with |
| **Status** | `pending`, `sent`, or `failed` |
| **SKU count** | Number of SKU packages included |
| **Attempt count** | Total number of send attempts for this delivery |
| **Recipients** | The resolved list of email addresses at the time of sending |
| **Provider message ID** | The email provider's message identifier for tracking |
| **Error message** | The failure reason if any attempt returned an error |
| **Next retry** | When the next automatic retry is scheduled (for failed deliveries) |
Expand any delivery row to see the full attempt history, including each attempt's number, trigger type (automated or manual), status, and completion timestamp. Click **Resend** in the expanded row to manually retry a failed delivery without waiting for the automatic retry schedule.
Failed deliveries are retried automatically. The system ensures the same package is never included in two successful deliveries — even if a manual resend and an automatic retry happen to run simultaneously.