Launching a SKU online means delivering three related but distinct image jobs: a compliant main image that survives marketplace QC, fast-scan selling-point frames for ads and carousels, and a long-form PDP story that answers detail questions. Rhinobird splits the work across AI E-commerce Image Sets, AI E-commerce PDP, and supporting utilities. This planning guide orders those tools, lists preparation steps shared across all of them, and points to Agent Chat skills when ads need models, backgrounds, or bundles.
Define channel requirements before you generate
Write down rules per destination before spending credits:
- Main image — background color, minimum pixel dimensions, product fill percentage, text overlay bans.
- USP / ad frames — aspect ratios for Meta, TikTok, or marketplace sponsored slots; claim language legal approves.
- PDP long scroll — module order your CMS template expects (hero, benefits, specs, usage).
Generators on the English UI expose Image Aspect Ratio or per-tool ratio controls—set them to the strictest destination first to avoid rework.
Prepare one master product asset
Start from the best product photo or approved render. Run Image Enhancement when softness or resolution blocks label review. Run AI Background Removal when background clutter breaks showcase modules or Agent Chat compositing.
Gather merchandising text once: accurate Category, customer-facing product name, and a fact-based description you can reuse in both image set and PDP forms. Feed measurable specs to AI Writing Assistant where available instead of empty superlatives.
Produce main and USP stills with Image Sets
Open AI E-commerce Image Sets. Set required Product Image and Category. Allocate Image Type counts toward:
- Product Showcase — candidates for main-image and clean carousel slides.
- Key Selling Points (USP) — benefit callouts for ads and secondary listing slots.
- Lifestyle & Usage — optional context frames when policy allows non-white backgrounds in carousels.
Review credit totals on Generate, sign in via Login / Sign up, and download from History. Pick the showcase frame that best satisfies main-image rules; reserve USP frames for sponsored tests.
Produce PDP modules with AI E-commerce PDP
When the listing uses a long detail template, open AI E-commerce PDP. Reuse the same master photo and merchandising text. Enable Included modules your template actually displays—common groups include Above-the-Fold Hero Visual, Lifestyle & Usage, Product Detail Close-ups, Ingredient Spotlight, Core Benefits & Selling Points, Detailed Specifications, and Usage Guide & Tips.
Match module counts to CMS slots; generating unused modules wastes credits. Align Country and Language with the live storefront before batching.
Extend into ads with Agent Chat skills
Static sets and PDP modules may not cover social ad concepts. Add:
- Model Handheld for in-hand credibility.
- Background Generation for styled environments without reshooting.
- Bundle Ad Creative for multi-SKU promos.
- Image Editor for last-mile fixes on any exported frame.
Design-stage packaging can start from AI 2D Layout to Rendering, then flow into the same set and PDP steps once a render replaces photography temporarily.
Review batch before upload
- Compare every frame to the master SKU for color and logo placement.
- Read on-image text against legal-approved claims.
- Confirm aspect ratios per channel spec sheet.
- Archive approved downloads from History with run notes for future refreshes.
Failure states across the stack
- Generate blocked on sets or PDP — missing image or Category; complete sign-in.
- Main image rejected by marketplace — regenerate showcase with stricter background brief or manual matting first.
- PDP module mismatch — disable unused Included modules and regenerate instead of uploading irrelevant frames.
- Inconsistent look between USP and PDP — reuse one description block and one master photo across tools in the same session day.
Treating main, USP, and PDP visuals as one planned pipeline—shared master asset, Image Sets for carousel coverage, AI E-commerce PDP for long-form modules, Agent Chat for ad extensions—keeps Rhinobird outputs consistent and reduces duplicate credit spend across launches.