For e-commerce and catalog operations

Folder of source photos in, marketplace-ready catalog out

Phone photos, supplier images, 3D renders. The workflow handles white-background isolation, marketplace-spec dimensions, SKU naming, and batch QA. Throughput scales with plan.

Open workflow

When to use this recipe

Built for catalog teams managing hundreds-to-thousands of SKUs and needing throughput, not bespoke work.

30Above about SKUs the batch workflow pays back; below it, manual per-image...
100SKUs typically completes in 10 to 30 minutes
10 to 30 m100 SKUs typically completes in inutes

Many SKUs needing the same treatment

Apparel catalog, supplier-photo cleanup, marketplace migration. Above about 30 SKUs the batch workflow pays back; below it, manual per-image work is faster.

Marketplace-spec output required

Amazon, Walmart, eBay, Shopify, TikTok Shop each have spec requirements (dimensions, background, fill ratio). Workflow bakes specs in; outputs pass marketplace review.

SKU-based naming and organization

Outputs need to land in your DAM or PIM under correct SKU names. Workflow names files to your schema so downstream automation works without manual rename.

Source quality varies wildly

Mix of phone snaps, supplier photos, vintage product imagery, low-res JPEG. Workflow rescues low-quality sources; you do not need to pre-sort by source quality.

The workflow

Six steps from source folder to listing-ready output set.

1
Organize source images into a folder (15 to 30 minutes)
All source images in one location, named (loosely) per SKU. Output naming will come from the workflow; source naming just needs to be searchable.
2
Configure the workflow per marketplace (5 minutes)
Open Bulk Catalog Processor template. Select target marketplace (Amazon, Walmart, eBay, Shopify, TikTok Shop) or define a custom spec. Workflow loads the right spec automatically.
3
Upload the source folder (5 to 30 minutes per 100 SKUs)
Drop the source folder into the workflow. Upload time is bandwidth-bound; the processing has not started yet. Run while you do something else.
4
Run the batch (varies with volume)
Workflow processes each source: background removal, marketplace-spec composition, resolution adjustment, optional supplier-image rescue. 100 SKUs typically completes in 10 to 30 minutes.
5
QA the output set (15 to 30 minutes per 100 SKUs)
Spot-check 10% of outputs across the spec dimensions. Reject any that failed background isolation or have visual artifacts. Re-run rejects through the rescue workflow.
6
Export named per SKU to your DAM (5 minutes)
Workflow names files per your schema (SKU_Marketplace_Spec.jpg or similar). Push to your DAM or download as a zipped folder per marketplace.

Tips and failure modes

Six patterns separating clean catalog runs from frustration.

Background isolation fails on certain products

Hairy, transparent, or reflective products (jewelry, fur, glassware) often need post-process touch-up. Plan QA time. Use the supplier-image rescue recipe for problem cases.

Verify spec compliance before bulk export

Run a 5-SKU pilot batch first. Confirm Amazon-spec or Walmart-spec output passes marketplace review. Then scale to the full catalog.

Naming schema matters more than people expect

Without consistent naming, your DAM/PIM cannot consume the output set. Lock the schema before running the batch, not after.

Multiple angles per SKU

Many marketplaces require multiple angle shots. Workflow can produce front + 3/4 + back from a single source if the source is informative enough. Otherwise, source multiple angles per SKU.

Throughput scales with plan

Free and Basic tiers run small batches sequentially. Pro and above run parallel. For 1000+ SKU catalogs, Premium or Ultra tiers are the right fit.

Push directly to your DAM via API

For teams on Pro tier or higher, API access pushes output directly to your DAM (Akeneo, Salsify, your internal DAM) without manual upload. Round-trip eliminates a manual step.

Frequently asked questions

What catalog ops teams ask before running the bulk workflow.

Processing about 2 to 5 hours on Premium tier (parallel processing). Upload bandwidth-bound (typically 30 to 60 minutes for 1000 source images). QA spot-check on 10% takes about 2 to 3 hours. Plan a half-day for 1000 SKUs.

Yes when generated to spec. The workflow bakes Amazon image rules (1000x1000 minimum, pure white background, 85% product fill, no watermarks). Outputs pass marketplace review the same as photographed images.

Yes. The workflow can emit per-marketplace variants from one source. Output folder structure organized by marketplace, so Amazon goes to Amazon DAM, Walmart goes to Walmart DAM.

The bulk workflow handles light rescue (color cast, exposure). For severely degraded sources (low-res, damaged), run the Supplier Image Rescue recipe first, then push the rescued sources through the bulk workflow.

Yes. Drop subset folders rather than the entire catalog at once. Many teams batch by product category (apparel, footwear, accessories) since each category has slightly different visual treatment needs.

No, this recipe is white-background catalog. For lifestyle (product-in-context), run the Lifestyle Scene Builder workflow. The two recipes complement each other for a full catalog: catalog plus lifestyle.

Process the base product once; AI handles the color/size variant generation. Workflow can produce per-variant outputs from a single hero source if your source captures the product well.

Headline cost is per-credit and varies by source quality. A typical bulk run on Premium tier processes 1000 SKUs for a small fraction of equivalent traditional studio photography. Run the cost calculator with your volume.

Process your full catalog this week

Bulk Catalog Processor turns a folder of source images at any quality into marketplace-spec listings named to your SKU schema. Premium tier supports 1000+ SKUs per day.

Open workflow
DESIGNERBOX
×