Bulk product image generation is limited by review more than by generation. A 200 SKU catalogue at four images each is 800 files. The model you pick changes the cost of the run, and every file still needs an eye on it before it reaches a client. Generation takes minutes. Review takes days. Price the job on review time.
Agencies get this backwards on the first big run. The pitch is that AI collapses a catalogue shoot into an afternoon, so the quote goes out at afternoon rates. Then someone opens folder three of eleven and finds the model has quietly changed a stitch colour on 40 files, and the margin is gone.
This guide covers how to price a catalogue run, the throughput lever most teams never check, how to keep client work separate, and the three specific places bulk generation falls over.
Key Takeaways
- Review is the bottleneck. Plan a bulk run around approval throughput and the rest of the schedule follows.
- Pick the model before you quote. The model changes the cost of every image, and every reject costs as much as a keeper.
- The run cost is on screen before the run starts. Quote from that number rather than from an estimate you reconcile afterwards.
- Parallel runs are 1, 1, 4, 8 and 16 by plan, from Free to Ultra. Free and Basic run one job at a time. Ultra runs sixteen. On a catalogue that is the difference between a day and a week.
- Batch only what is identical. A batch is only safe when every item in it takes the same treatment.
- Sample before you commit. Ten SKUs across the range tells you what 800 will look like.
- Keep one brand profile per client. The workflow reads that profile on every run.
- Team seats start at Ultra, $200 a month billed monthly. Five users are included, and extra seats are $19 each. Every plan below Ultra is one seat.
What bulk product image generation means
Three different jobs get called bulk work, and they have different failure modes.
| Job | What it is | Where it breaks |
|---|---|---|
| Volume | The same treatment across many SKUs | Products that need different treatment get it anyway |
| Variation | Many treatments of one SKU | Output drifts from the source product |
| Rescue | Fixing inconsistent inherited images | The source files are not good enough to fix |
Most agency catalogue work is volume plus rescue. A client hands over 200 supplier images shot by four different people, and the brief is to make them look like one catalogue. That is a standardisation problem with a generation step in it.
Naming which job you are doing decides everything downstream, because the review criteria are different. Volume work is checked for consistency. Variation work is checked for fidelity to the product. Rescue work is checked for whether it improved anything at all.
The cost of a bulk run
In DesignerBox the cost is shown before the run, and the model you pick changes it the most. On one image the difference is small. On 800 it decides which plan you need, so count the images first and budget the rejects with them.
| Catalogue | Total images | Images to run at a 20% reject rate |
|---|---|---|
| 20 SKUs, 4 each | 80 | 100 |
| 50 SKUs, 4 each | 200 | 250 |
| 100 SKUs, 4 each | 400 | 500 |
| 200 SKUs, 4 each | 800 | 1,000 |
| 500 SKUs, 4 each | 2,000 | 2,500 |
Plan allocations, billed monthly: Free 112 credits a month, Basic $15 for 500, Pro $35 for 1,000, Premium $75 for 2,500, Ultra $200 for 8,000. Annual billing lowers the monthly rate and grants the same allocation each month.
Read the table against those allocations and the model choice is the whole story. Run a small sample on two models, read the cost shown before each run, and multiply by the right row. Then quote. A large catalogue on a premium model can need more than one month of credits, and credit packs add more on a paid plan.
Two things that table hides. Credits reset monthly and do not build into an unlimited pool, so a large catalogue is a scheduling problem as well as a budget one. And every failed generation costs the same as a successful one, so a 20% reject rate adds 20% to the cost.
That reject rate is the number worth measuring on your first run. It is the difference between a quotable process and a hopeful one. Against a traditional shoot the comparison still favours this heavily, and what a product photoshoot costs has the day rates to compare against.
Commercial licensing starts at Pro, which is the floor for any client work regardless of volume.
Parallel generation is the throughput lever
This is the setting almost nobody checks before quoting, and on a catalogue it decides your calendar.
Parallel runs are 1, 1, 4, 8 and 16 across Free, Basic, Pro, Premium and Ultra. A Basic plan processes one image at a time. An Ultra plan processes sixteen.
Run the same 800 image job on both and the queue behaves completely differently. Sixteen concurrent jobs turn an overnight run into a lunch break. One concurrent job turns it into something you start on Monday and check on Thursday.
The practical rule for agencies: the tier decision on a catalogue job is a scheduling decision before it is a credit decision. Work out the deadline first, then pick the tier that clears it, then check whether the credits also cover it.
Batch only what is identical
The most expensive mistake in bulk work is batching things that look like they belong together.
A batch is safe when every item in it takes exactly the same treatment. Same background, same light, same crop, same framing logic. The moment one item needs a judgement call, it is not part of that batch.
Sort a catalogue before you run it:
- Group by treatment first. All items that need a plain white packshot go together, whether they are mugs or shoes.
- Pull out the awkward shapes. Anything very tall, very wide, reflective, transparent or fine-detailed goes in a manual pile. Glass and jewellery are the usual offenders.
- Sample ten across the range. Two easy, two awkward, six typical. Run them, review them properly, and only then commit the rest.
- Fix the recipe first. If eight of ten samples are wrong the same way, that is a brief problem. Adjust once and rerun rather than correcting eight files.
- Run the full batch in blocks. 50 to 100 at a time, reviewed before the next block starts, so a systematic error costs one block rather than the catalogue.
Step 3 is the one that pays for itself immediately. Ten samples cost a small share of what 800 images cost, and each run shows its cost before you start it.
In DesignerBox today, a saved workflow runs once per product, with up to 16 runs in parallel on Ultra. Batch, one workflow over a whole sheet of products, is coming. For inherited supplier images, the product imagery templates are a place to start. Teams driving this from an AI chat such as Claude use the DesignerBox MCP server.
Reviewing 800 images without reviewing 800 images
You cannot skip review, but you can make it cheap.
- Contact sheets first. Review 40 thumbnails on one screen. Consistency errors are visible at thumbnail scale, which is the whole point of the grid.
- Check the product first. Colour, texture, logo, proportion, material. Everything else is taste and the client will tell you.
- Spot check at full size. One in ten, plus every awkward item from your manual pile.
- Watch for systematic drift. Errors in bulk work are rarely random. If one is wrong, look for the other 39 that are wrong the same way.
- Keep the source photo beside the result. Fidelity is a side-by-side comparison.
That fourth point is what makes bulk review survivable. Individual errors are expensive to find. Systematic errors are cheap, because finding one finds all of them. Where AI product photo accuracy drifts covers what to look for first, and it is usually fabric and hardware rather than anything obvious.
Keeping clients separate
This is the agency objection, and it is usually phrased as “we already use several AI tools”. The honest answer is that the organisation of the work causes most of the trouble.
A stack of single-purpose tools produces client work that lives in whoever’s account generated it. Six months later a client asks for the same campaign on a new product, and the person who built it has left, the prompts are in a Slack thread, and the brand kit is a PDF someone emailed.
What fixes it is organisational: per-client brand profiles that hold the look, workflows that run the campaign again for the next product, and one Assets library for the files. Brand profiles is the mechanic, and running creative for multiple clients without drift covers the operational side.
Team seats are honest to state plainly: five users are included on Ultra at $200 a month billed monthly, with extra seats at $19. Every plan below that is single seat. For a three person studio that is the real decision, and how agency creative pricing works out puts it against retainer maths.
If you are already paying for several separate tools, the six tool stack runs that arithmetic.
Where batch generation breaks
Three places, consistently.
The source images are not good enough. Rescue work has a floor. If the supplier photo is soft, small or shot under mixed light, a batch run produces 200 consistently mediocre images instead of 200 inconsistently mediocre ones. Check the worst 10% of the source set before quoting.
The product needs judgement. Reflective, transparent, very fine detail, or anything where the material is the product. These do not batch. Price them separately as manual work rather than discovering them mid-run.
The client has an unwritten rule. Every brand has one. The logo always faces left. The lid is always on. Shadows always fall right. It is never in the brief, it surfaces at review, and it invalidates the batch. Get it out of them during the sample stage, which is the real reason the ten sample step exists.
None of those are fixed by a better model, and it is worth being direct about that before a client expects otherwise. What they are fixed by is sequencing: sample, extract the rules, then run.
For the video equivalent of this problem, where file constraints add a second layer, TikTok Shop product videos and the 10 MB cap shows how a platform limit reshapes the whole production plan.
Getting started on a real catalogue
The shortest honest path:
- Pull 10 SKUs across the range and run them on the free plan, which includes 112 credits a month. The cost of each run is shown before you start it.
- Review at full size, extract the client’s unwritten rules.
- Fix the recipe, then save it as a workflow so the next 190 SKUs run the settled version rather than a fresh judgement call.
- Pick the plan by deadline, using the parallel run numbers, and the model by the cost shown before the run.
- Run in blocks of 50 to 100, reviewing between blocks.
Step 3 is the one that compounds. Build the job once against the client’s brand and their own product photos. A saved workflow runs the same way on the next product, so nobody re-decides the background halfway through. You set the brand once, and the workflow reads it on every run. Batch is coming, and it will run that workflow over a whole sheet of products. AI product photography covers the catalogue shots themselves, and scaling creative production without adding headcount is the wider version of this problem.
DesignerBox is AI creative production for agencies and brand teams. Team features, shared brand kits and the API sit on the Ultra plan, and DesignerBox for agencies sets out how an agency runs one workflow per client brand.
FAQ
How many product images can AI generate at once?
Your plan’s parallel run limit sets it more than the model does. DesignerBox runs 1, 1, 4, 8 and 16 runs at once across Free, Basic, Pro, Premium and Ultra. Credits set the total you can produce in a month, and the model you pick changes the cost of each image. The cost is shown before the run.
What does it cost to generate 1,000 product images?
The model you pick sets most of it. DesignerBox shows the cost of a run before you start it, so run ten images on the model you plan to use and multiply. Plans include 112 to 8,000 credits a month, and a paid plan can add credit packs. Pick the model before you quote, and budget for a reject rate on top, because failed generations cost the same as successful ones.
Is bulk AI product photography accurate enough for client work?
For volume and rescue work on straightforward products, yes, provided you start from the client’s own product photography and review the output. It needs review to be reliable, and it is weak on reflective, transparent and fine-detailed products. Sample ten SKUs before committing to a catalogue.
How do agencies keep client brands separate?
With a brand profile per client rather than an account per client. The profile holds the look, and the workflow reads it on every run, so the same campaign runs again for the next product. That is what stops the brand living in one person’s prompt history.
How long does a bulk product image run take?
Generation time is set by your parallel limit. Review time is set by your team, and it is the larger number. A useful planning figure is that reviewing at contact sheet scale with full-size spot checks runs several hundred images per person per day, so an 800 image catalogue is a multi-day approval job whatever the generation speed.
Do I need a commercial licence for client work?
Yes. The commercial licence on DesignerBox starts at the Pro plan, $35 a month billed monthly. Produce any images you deliver to a client on Pro or above, however small the run is.
Can I automate bulk product images without using the interface?
Yes. DesignerBox has 68 tools over MCP, so an AI chat such as Claude, ChatGPT or Cursor can run the same workflows and apps. For your own scripts, the API sits on the Ultra plan. Both routes suit a catalogue process that is already stable. The stages a scripted run has to clear, and the platform limit that caps each one, are set out in what actually automates in a catalog run.
Sources
DesignerBox plan allocations, parallel runs, seat counts and feature gating from the DesignerBox pricing page (designerbox.ai/pricing), September 2026. Plan details change, so confirm on the pricing page before quoting a client. Individual results vary.
