> ## 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.

# Create a Fashion Catalog with Shared Creative Direction

> Create a new catalog, set shared creative direction for every colourway, add SKUs in bulk, and link to campaign events for pre-filled scene direction.

Creating a catalog locks a single creative brief — model, scene, lighting, five-pose grammar — that applies to every colourway in the batch. You configure this brief once in the creation form, paste all your SKU/colour lines, and then upload the individual product references per colourway after creation. The generation engine uses that shared brief to produce a visually consistent set of images across every color variant.

<Note>
  The Planning page shows a **Campaign roadmap** strip at the top, powered by the Events Intelligence feature. This strip shows the next six upcoming fashion events with prep-deadline countdowns. Click **Plan catalog** on any event card to open the creation form pre-filled with that event's campaign season, scene direction, and prep deadline as the scheduled generation time.
</Note>

## Creating a new catalog

<Steps>
  <Step title="Open the creation form">
    In the Planning tab, make sure **Planning V1** is selected. Click **New catalog** in the top-right corner. The catalog creation panel slides open.
  </Step>

  <Step title="Fill in the catalog details">
    Complete the form fields below. Fields marked with `*` are required.

    <ParamField body="Catalog name" type="string" required>
      A short, identifiable name for this batch — for example, `T45-Bubbly`. This name appears in the catalog list, History search, and the Catalog Production board.
    </ParamField>

    <ParamField body="Campaign / season" type="string">
      The marketing campaign or season this catalog belongs to — for example, `Diwali 2026`. If you opened the form from an event card, this is pre-filled from the event's campaign season.
    </ParamField>

    <ParamField body="Priority" type="enum">
      Sets the urgency level for generation and listing assignment. Options: `urgent`, `high`, `normal`, `low`. Defaults to `normal`.
    </ParamField>

    <ParamField body="Listing deadline" type="datetime">
      The hard deadline by which all five poses for every SKU must be listed. Used by the Catalog Production workflow to surface overdue items.
    </ParamField>

    <ParamField body="Generation owner" type="select">
      The team member responsible for managing the generation run. Choose from active workspace members. You can assign this later.
    </ParamField>

    <ParamField body="Listing owner" type="select">
      The team member responsible for completing the listing step after generation. You can assign this later.
    </ParamField>

    <ParamField body="Marketplaces" type="string">
      Comma-separated list of target marketplaces — for example, `Myntra, Amazon, Flipkart`. This is passed to the generation prompts for marketplace-aware composition and cropping rules.
    </ParamField>

    <ParamField body="Look and mood" type="string">
      The overall aesthetic direction — for example, `Premium festive, energetic, youthful`. Gemini uses this when composing the creative direction profile.
    </ParamField>

    <ParamField body="Model direction" type="string">
      Instructions for the model that apply identically across every colourway. The default is `Use the uploaded model face reference exactly; keep that same model across every colourway`. Modify this if you have specific posture, expression, or demographic requirements.
    </ParamField>

    <ParamField body="Styling requirements" type="string">
      Accessories, footwear, drape style, hair, and makeup directions — for example, `Gold jhumkas, block-heeled sandals, loose waves, nude lip`. These seed the catalog-wide Styling Plan that is proposed after the first colourway is preflighted.
    </ParamField>

    <ParamField body="Backdrop / scene direction" type="string">
      The scene and environment for every image. Defaults to `Reproduce the scene, backdrop, props and lighting from the uploaded style reference`. If the catalog is linked to an event, this is pre-filled from the event's brief, mood, color palette, and themes.
    </ParamField>

    <ParamField body="Five-pose direction" type="string">
      Custom pose instructions applied across the batch. The default is `Full product, professional side angle, accurate back view, creative pose, close-up face and product detail` — edit this only if you need to override individual pose framing.
    </ParamField>

    <ParamField body="Lighting" type="string">
      Lighting setup for every image — for example, `Soft directional daylight, clean skin tones`.
    </ParamField>

    <ParamField body="Composition" type="string">
      Framing and crop guidance — for example, `Marketplace-safe crop, product unobstructed`.
    </ParamField>

    <ParamField body="Marketplace / campaign requirements" type="string">
      Background policy, aspect ratio constraints, campaign branding rules, or any other marketplace-specific instructions.
    </ParamField>

    <ParamField body="Special instructions" type="string">
      Any remaining creative or operational notes that don't fit the structured fields above.
    </ParamField>

    <ParamField body="Category" type="enum">
      The garment category. This controls which reference slots appear per colourway (standard slots vs. saree-specific slots). Options: `ethnic/fusion`, `saree`, `western/casual`, `dress`, `formal`, `streetwear`, `activewear`.
    </ParamField>

    <ParamField body="Aspect ratio" type="enum">
      Output image aspect ratio. Options: `3:4` (default), `4:5`, `2:3`, `9:16`, `1:1`, `16:9`. Choose based on your primary marketplace's requirements.
    </ParamField>

    <ParamField body="Preferred generation date and time" type="datetime">
      When the automatic generation run should start — entered in **Asia/Kolkata** timezone. If this time has already passed when the catalog reaches the ready state, the worker starts without another click. You can also click **Tomorrow · 10:00 AM** to fill in the next morning as a quick default.
    </ParamField>

    <ParamField body="Colourway SKUs" type="textarea">
      Paste all your colourway lines here, one per line, in `SKU, Colour Label` format. For example:

      ```
      T45-Bubbly-Pink, Pink
      T45-Bubbly-Green, Green
      T45-Bubbly-Red, Red
      ```

      These are parsed and added as individual colourway rows when you submit the form.
    </ParamField>

    <ParamField body="Run Gemini consistency QA on every pose" type="boolean">
      When checked, Gemini validates every generated pose against the product profile and locks consistency before marking it complete. This adds a QA step per pose but reduces manual review. Off by default.
    </ParamField>
  </Step>

  <Step title="Submit the form">
    Click **Create catalog**. The catalog is created immediately with all pasted colourways added as draft rows. You land directly on the catalog detail view, ready to upload references per colourway.

    A confirmation message shows how many colourways were added, and — if the category is `saree` — reminds you to upload the full front drape, rear drape, pallu spread, and body detail for each one.
  </Step>
</Steps>

## Event integration

If you opened the creation form from an event card in the Campaign roadmap strip, the **Campaign / season**, **Backdrop / scene direction**, and the **Preferred generation date and time** are already filled in. The scene direction is assembled from the event's brief, mood (e.g., `Warm, celebratory`), color palette (e.g., `Gold, Ivory, Crimson`), and themes (e.g., `Heritage craft, festive glow`). You can edit any of these fields before submitting.

When a catalog is linked to an event this way, the scheduling panel inside the catalog also shows a **Use event prep deadline** button that sets the generation time to the event's preparation deadline in one click.

<Tip>
  **Bulk SKU paste:** paste all colourways directly in the creation form's SKU textarea — for example, `T45-Bubbly-Pink, Pink` on one line, `T45-Bubbly-Green, Green` on the next. The parser accepts commas, pipes, or tabs as separators. You can also add more colourways individually after creation using the **Add colourways** textarea on the catalog detail page, or import them from an Excel file.
</Tip>