Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.melius.com/llms.txt

Use this file to discover all available pages before exploring further.

Product photography is one of the highest-leverage uses of Melius. Instead of booking a photographer, lighting a set, and waiting three weeks for assets, you can produce production-grade product shots in an afternoon — including lifestyle context, seasonal scenes, and channel-specific variants. The two main workflows: product photography from scratch (generate the whole scene) and product swap (place your real product into an existing scene). Both follow similar mechanics.

​
Workflow A: Product photography from scratch

Goal: generate a hero shot or lifestyle image with your product as the centerpiece.
1

Drop your pack shot on the canvas

A clean product photo on a neutral background. If you have multiple angles, drag in all of them and unified-group them — the agent will use all angles as reference.
2

Paste the PDP URL into the agent chat

Brief: “Pull the product details from [URL] — focus on dimensions, materials, and color. Save it as a text node.” This gives the agent the actual physical specs to anchor on.
3

Add a style reference if you have one

A moodboard, a competitor’s product photography, or an existing campaign whose look you want to mirror. Use the style analysis workflow to turn the references into a usable style description.
4

Create an image-to-image node

Right-click → New image node → Image-to-image. Pick Nano Banana Pro at 2K and the aspect ratio you need.
5

Connect everything in

Pack shot → image input. PDP details → context input. Style description → context input. (Use @ mentions in the prompt as a shortcut.)
6

Write the prompt

Keep it grounded in what’s not changing. Example:
Hero shot of @product in [setting].
Use the exact product from the reference — don't restyle the product, don't change its color, don't modify its shape or proportions.
Use the @pdp-details for accurate dimensions and materials.
Use the @style-description for lighting, composition, and mood.
7

Run 3–4 variations

Inspect the results in full-screen mode (the canvas preview is downscaled). Pick the strongest.

​
Workflow B: Product swap

Goal: drop your product into a scene you already have (or have generated), replacing whatever was there.
1

Drop the target scene onto the canvas

The image where you want your product to appear. Could be one you generated earlier on the canvas, or a stock image you’ve uploaded.
2

Drop your product pack shot in too

Same as before — clean photo, ideally with multiple angles unified-grouped.
3

Create an image-to-image node

Nano Banana Pro, 2K. Aspect ratio matching the original scene.
4

Connect both as inputs

Scene → image input. Product → context input.
5

Write a swap prompt

Example:
Replace the [object/product] in @scene with the @product from the reference image.
Keep everything else identical — same lighting, same composition, same color grade, same camera angle.
Match the placement, scale, and orientation of the original [object].
Make the proportions and placement of the product feel natural and realistic.
6

Run 3–4 variations

Inspect the results. If the product is the wrong scale or placed awkwardly, tweak the prompt with specifics (“the product should be slightly larger, occupying about 30% of the frame width”) and re-run.
There’s a Product Swapper preset in the templates menu that pre-configures this entire flow. If you find yourself doing product swaps frequently, start from the preset instead of building from scratch.

​
Keeping product fidelity high

Product fidelity is the #1 issue marketers raise on onboarding calls. The product almost-but-not-quite matches — the proportions are slightly off, the logo is rendered as a similar-looking-but-not-correct shape, the material drape looks generic. Here’s the fix kit:

​
Always include the PDP URL

The PDP scrape gives the agent your product’s actual dimensions in cm/inches, its material specs, and its color codes. Without this, the model is guessing from a single photo — and it’ll guess wrong on proportions roughly half the time.

​
Always include a pack shot, not just a lifestyle reference

A lifestyle photo of your product in use doesn’t give the model a clean view of the product itself. Drag in a clean studio shot or a transparent PNG as the product reference, separately from any mood references.

​
Add the logo as its own node

If the product has visible branding, drop the logo file (PNG or SVG) onto the canvas as a separate node. Connect it to the image node. In the prompt: “Use the @logo for any branding visible on the product. Do not redraw it — use the reference exactly.”

​
Use Nano Banana Pro for style; GPT Image 2 for visible text

Nano Banana Pro handles material and lighting fidelity better. GPT Image 2 is unmatched for rendering legible typography (product names, labels, packaging copy). If your product has visible text on the packaging, lean GPT Image 2.

​
Force higher resolution

1K previews look softer than the actual output, but going straight to 2K (or 4K) gives the model more detail to work with on small features — fine fabric weaves, embossed logos, label typography. Worth the extra render time.

​
Common pitfalls

  • No pack shot, just a lifestyle reference. The model can’t see the product clearly. Add a clean studio shot.
  • No PDP URL. Proportions and dimensions drift. Paste the URL.
  • Re-prompting the whole thing when the product is slightly off. Edit the existing node’s prompt with a specific correction instead. “Keep everything else, but: the product should be 20% larger / oriented vertically / placed in the foreground.”
  • Logo regenerated from scratch. Add the logo as its own reference node and tell the prompt not to redraw it.
If you’re producing product photography at scale, build the workflow once on one SKU, get it dialed in, then duplicate and swap inputs for each additional product. This is how high-volume DTC teams produce hundreds of product variants per week — see Make a winning ad work harder.
Last modified on May 18, 2026