How to Build a Consistent Product Photo Pipeline with Nano Banana 2
E-commerce teams shoot one good product photo and need twenty variations — different backgrounds, seasons, models. Nano Banana 2 can generate that set from a single reference while keeping the product identical. The catch is process: without a fixed reference and a QA step, the product drifts and the set looks inconsistent.
How do you structure the pipeline?
The reliable pattern is reference-first:
- Start with one clean, high-resolution studio shot as the master reference.
- Define a fixed style sentence — lighting, color grade, camera feel.
- For each scene, keep the product description identical and change only the setting.
- Generate 3-5 candidates per scene, then select by eye.
- Run every selected image through a similarity check against the master.
Step five is what most teams skip. Comparing the generated product against the original reference, even with a simple perceptual hash, catches the drifts before they ship.
What prompts keep the product identical?
Separate the immutable part from the variable part. “The ceramic mug with the matte navy finish and visible handle” stays byte-for-byte in every prompt. Only the background and lighting change. Adding style adjectives to the product clause is how identity creep starts — resist it.
What is the cost per set?
Twenty final images, generated five candidates deep and filtered, means roughly 100 generations. At typical per-image API pricing in the cents range, a full set lands in the low single-digit to low double-digit dollars. That compares to a physical reshoot costing hundreds plus studio time, which is why the pipeline is worth building even with some manual selection.
What are the failure modes?
- Logo and text on packaging render inconsistently — add them in post if they must be exact.
- Reflective and transparent products (glass, chrome) drift more than matte ones.
- Aggressive scene changes can alter lighting on the product, breaking the set.
- Low-resolution references produce soft, unshippable outputs.
For packaging with mandatory text, compositing the real label over the generated scene is more reliable than prompting for it.
Where does this fit in a content stack?
The image pipeline is one stage. Teams pairing it with an automated editor — the pattern behind tools like droid for content repos, or a scripted CMS uploader — can go from one shot to a published set without manual file handling. Keep the human in the loop at the selection step; that is where quality is decided.
Quick Summary
- Build sets from one master reference and a fixed style sentence.
- Add a similarity check to catch product drift before shipping.
- A 20-image set costs roughly low single to double-digit dollars.
- Glass, chrome, and in-image text are the weakest cases.
- Composite exact logos in post rather than prompting for them.
Last updated September 2026.
