Batch product photos. One saved Look, reviewed item by item.
Create AI product photos for a selected catalog without rebuilding the direction for every item. Choose sources, inspect a quoted pilot, confirm the remaining cost and approve individual outputs before downloading the pack.
Apply a Look is available to eligible paid accounts. Listing Readiness is available to signed-in accounts for supported Stage and Library images. Check current plans and allowances.
Choose your productsNew to Stage? Try one product first. A free trial does not include paid catalog runs or start a subscription.
What happens in a catalog run
Select exact products and evidence
Choose two to twenty products, the project and primary source for each, and relevant supporting references. Choose one eligible saved Look. Saving the selection does not start paid processing.
Quote and inspect a pilot
Confirm the pilot quote before starting. Compare its product details with the source, then approve that exact pilot direction if it is suitable. A direction approval is separate from approving an output for export.
Confirm the remainder separately
The already-charged pilot is excluded from the remaining quote. Check selected products, source availability and credits before confirmation. Admitted processing continues if the page closes.
Review each result
Completion is not visual approval. Review current outputs and previous attempts, retain an older approved choice while evaluating a replacement, and read a new quote before any charged retry or replacement.
Prepare the approved-output pack
Check run-level SKU labels and download a ZIP of approved choices with safe unique filenames and JSON/CSV manifests. Review exclusions. A partial pack requires an explicit choice; it is not silently presented as a complete catalog.
Choose the job before the batch
| What you need | Start here | What still needs review |
|---|---|---|
| One scene around one product | Ordinary Stage. Preserve retains the photographed view; Creative redraws it. | Edges, visible details and whether the scene fits the intended use. |
| One Look across 2–20 products | Paid Apply a Look with an eligible saved Look and a quoted pilot. | Each SKU separately. A direction approval is not output approval. |
| Background cleanup, not a new scene | Cutout batch workflow. | Cutout boundaries, format and final export settings. |
Illustrative credit example: five products with one standard output each means a one-credit pilot and a separately confirmed four-credit remainder, if those are the quoted operations. Retries or replacements need their own quote. The app’s actual quote is authoritative; a completed image you dislike is not automatically free.
A saved Look carries a direction, not an identical background or guaranteed lighting match. Catalog outputs are native 1K; enlarging an export does not recover detail.
Take a review worksheet to the upload
Keep the SKU, source, image role, output filename and release decision together. Open the CSV in your spreadsheet, add your own product references, then review the exact downloaded files. No account or email is required.
The example uses fictional SKUs and paths, not customer results or generated-image evidence. This is a manual team checklist, not CatalogCut’s export-manifest schema, an import template or marketplace approval. Keep the app’s actual JSON/CSV export manifest alongside it.
- Map each source to the exact SKU and variant.
- Write a specific review note; hold uncertain or rejected files out of the release.
- Record the approved output version and inspect its actual format, dimensions and product details.
- Download before retention expires, then confirm the uploader received the intended files.
Read how SKU filenames and manifests keep a handoff traceable.
Readiness checks the prepared file, not a promise
Open Listing Readiness from an available Stage or Library image. Choose the destination and slot, prepare the supported PNG or JPEG, and inspect the report alongside the actual downloadable file. Catalog ZIP reports describe the archive members.
- Measured findings
- File facts and observations supported by the available evidence. Subject observations require trusted retained assets; white corners alone are not proof of a clean background.
- Seller review
- Product identity, color, quantity, accessories, category suitability and anything that requires knowledge of the sold item.
- Unknowns
- Questions the evidence cannot settle. Missing, expired or unsuitable subject assets can leave geometry or background checks unknown. Unknown is not a pass.
Current scoped profiles cover Amazon US main and secondary photography guidance, and Shopify global product and collection technical checks. They do not cover every marketplace, region or category. Consult the linked platform requirements before publishing.
Fitting and format changes are deterministic export adjustments, not background removal. Enlarging adds pixels, not restored detail. Prepared files expire within ten minutes or earlier if the original becomes unavailable. Ordinary downloads remain independent of the advisory check.
What this workflow does not promise
- A saved Look reuses direction, not identical geometry or lighting. Preserve uses source-derived imagery; Creative can reconstruct details. Both need review.
- Catalog runs do not support every on-model or specialized garment Look. Use the appropriate ordinary Stage workflow for those tasks.
- Catalog runs produce native-1K Stage outputs. A larger prepared export does not become a native higher-resolution generation.
- Disliking a technically successful result is not an automatic refund. Unknown provider outcomes must be reconciled, not blindly retried or refunded.
- Saved history does not extend image retention. Download approved files before their individual expiry.
- A ZIP is not a marketplace upload template, automatic publication or approval. This guide reports no conversion study, A/B test or marketplace acceptance benchmark.
Find the next decision you need to make
Plan a catalog run
- How to apply a saved Look to multiple products
Choose products and source photos, quote a pilot, approve its direction and review the remainder in CatalogCut. Includes limits and export steps.
- Run a product-photo pilot before editing the full catalog
Choose a useful pilot, define acceptance criteria and separate its cost from the remaining products. A practical sample-first review worksheet.
- Choose a primary product photo and useful reference views
Select a source that shows the sold item, separate useful supporting views and identify missing evidence before starting an AI product-photo run.
- Stage, Campaign or Cutout: choose the right photo workflow
Match the tool to the job: one product scene, a multi-shot campaign, background cleanup or one saved Look across products. Keep their limits separate.
Review products and versions
- How to review AI product photos before export
Inspect identity, color, quantity, edges and small details before approving an AI product photo. Separate visual approval from processing success.
- Review color variants without mixing up product photos
Build a source-to-SKU check for color variants. Compare real references, avoid unsupported color reconstruction and approve each variant separately.
- Replace a product photo without losing the approved version
Keep a known-good export while evaluating a replacement. Track source, direction, output version and approval rather than trusting the newest file.
- What to do when a bulk product-photo run is interrupted
Handle a closed tab, uncertain submission or delayed output without blindly starting another paid job. Review saved state and quote only intended retries.
Check the downloaded file
- What a product photo readiness check can actually verify
Understand measured findings, seller-review checks and unknowns in a listing image report. Check the prepared download, not just a browser preview.
- Prepare Amazon main and secondary images as separate jobs
Separate product-only and supporting image workflows for Amazon. Choose a scoped check, keep original evidence and review category rules before upload.
- Check Shopify product and collection images before upload
Review a Shopify image in its product, collection and mobile placements. Separate file checks from theme crops and product-accuracy decisions.
- Native image resolution vs upscaling in product photography
A larger download is not a more detailed original. Learn how to read native size, exported dimensions and enlargement warnings before publishing.
- White padding is not background removal
Choose between fitting a photo, flattening transparency and removing an existing background. Avoid exporting a white border around the wrong image.
Deliver approved photos
- Product photo filenames: SKUs, ZIPs and export manifests
Keep product photos traceable with SKU labels, safe ZIP filenames and JSON or CSV manifests. Learn what to verify before a catalog handoff.
- A product-photo handoff checklist for ecommerce teams
Deliver approved photos with source references, SKU mapping, destination roles and exceptions. An upload handoff is not automatic publication or approval.
Documentation and evidence
By CatalogCut. Published November 13, 2026. This AI-assisted guide describes the implemented workflow and its limits. The worked examples in the linked articles are illustrative, not customer results. Read our editorial approach.
See saved product-photo examples for individual output examples, not proof of a catalog-wide quality benchmark. For account-specific questions or a correction, contact support.