Treat the ZIP as a Set Transfer
This workflow is a handoff problem, not just a download action. The Web App requires the Product catalog to be in list view before you select products and start Download images. The resulting ZIP is organized into product folders, so the useful evidence is whether the extracted folder set represents the intended selection.
Record the number of products selected before downloading. After extraction, count the product folders at the top level. Do not use the number of individual image files as the primary comparison: products may contain different numbers of images, while the folder count represents product-level coverage.
- Selection count: how many products were intentionally included.
- Folder count: how many product folders appear after extraction.
- Name key: the product name converted to one consistent case for collision checking.
Resolve Names Before Repeating
Photoroom documents a specific omission condition: two products with the same name are not both included in the download. It also ignores the case of title characters when deciding whether names are identical. Therefore, product_ABC and Product_abc must be treated as one collision even though they look different in ordinary browsing.
The practical decision is simple. If the selected count equals the extracted folder count and no normalized names collide, proceed to handoff review. If the folder count is lower, stop the handoff. Find duplicate names after case normalization, rename the affected products to unique identifiers, and perform a fresh download. Keep the old ZIP marked as incomplete rather than merging it into the replacement.
- Use a stable naming pattern that distinguishes SKU or variant identity, not only consumer-facing product text.
- Check punctuation and spacing consistently as part of your internal naming policy, even though the documented collision rule specifically addresses case-insensitive title matching.
- After renaming, verify the new selection and extracted folder count again.
Separate Completeness From Image Approval
A matching folder count only supports coverage: it does not prove that every image is visually approved or assigned to the right SKU. Once the transfer passes, review the folder-to-product mapping and then inspect the images using your normal product-accuracy process.
This is different from a generation-choice guide. The next action here is determined by transfer evidence: a count or naming mismatch sends you back to catalog naming; a complete transfer sends you forward to image-level review. That separation prevents an apparently tidy ZIP from being treated as a complete catalog handoff.
Worked Example: A Missing Folder
Hypothetical example only; no Photoroom download was executed. A seller selects six products in the Web App Product catalog, switches to list view, and downloads the images. The extracted ZIP contains five product folders. The seller compares the names after converting them to lowercase and finds both Travel_Mug_Blue and travel_mug_blue in the catalog.
The seller does not publish or hand off the ZIP. They rename one product with a unique SKU-bearing name, for example travel_mug_blue-SKU204, then repeat the download. The replacement is accepted for transfer completeness only when six selected products produce six top-level product folders. Image content and SKU accuracy remain separate review steps.
| Evidence | Observed state | Next action |
|---|---|---|
| Selected products | 6 | Retain the selection record |
| Extracted product folders | 5 | Stop handoff; investigate naming |
| Case-normalized collision | travel_mug_blue appears twice | Rename one product uniquely |
| Replacement folder count | 6 required | Proceed to image-level review only after match |
Related questions
Should I compare ZIP file size instead of folder count?
No. File size can vary with image dimensions and image counts. Folder count is the more direct product-level completeness check for this documented ZIP structure.
Where CartVisual fits
Use the browser-local checklist after the ZIP passes the product-count and naming test, to review image-to-product accuracy without implying CartVisual performs Photoroom downloads or catalog publishing.
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Photoroom: Download images for multiple products at once (Web App)
Official source snapshot checked .
The supplied official Photoroom help article covers the Web App Product catalog workflow, list-view prerequisite, ZIP structure, and duplicate-name behavior. It does not document SKU validation, folder-count auditing, naming conventions beyond case handling, or publishing controls; those are original workflow guidance.