Flux

Verified against Flux · 2026-07-30

Mock up new packaging on a realistic retail shelf with Flux.2

A retail-context brief for Flux.2 that places a packaging design into a believable store-shelf scene for stakeholder review, treating the printed design as a fixed detail to preserve rather than something the model is free to reinterpret.

Flux.27 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

PACKAGING DESIGN
a tall cylindrical protein powder tub, matte black with a bold lime-green logo band around the middle. Every printed element — the brand name "SURGE" in bold white sans-serif, "Whey Protein Isolate — Vanilla" beneath it, and a small lime-green checkmark icon — must render exactly as described, since packaging mockups live or die on whether the actual design is legible and accurate, not just plausible-looking.

SHELF ENVIRONMENT
a sports-nutrition aisle in a big-box retail store, mid-shelf height. This should be a specific, recognizable retail category context, not a generic empty shelf — other protein-powder-style tubs of similar height, mostly in black and bright accent colors, typical of that aisle — so stakeholders can judge how the design actually competes for attention next to real category conventions.

SHELF PLACEMENT, FACING, AND CAMERA ANGLE
a row of 4 identical facings side by side at mid-shelf height, camera roughly eye-level and centered on the middle two units, as if standing in the aisle about 4 feet away. State exactly how many units are visible, whether they're shown as a single facing or a multi-unit row, and the camera's height and angle — roughly eye-level or slightly below, the angle an actual shopper walking the aisle would see, not an idealized straight-on product-photography angle.

ADJACENT PRODUCTS
generic tubs in red and blue with abstract logo shapes, clearly a different brand but not resembling any specific real competitor. Neighboring products on the shelf should look like generic, plausible category competitors — not blank placeholders, and not so specific they resemble a real named competitor's actual packaging, which would misrepresent the test.

LIGHTING
flat overhead fluorescent-style lighting, slightly cool white balance, minimal shadow, the flat, slightly cool, evenly diffused overhead lighting of an actual retail aisle — not dramatic studio lighting, since that would make the mockup look like a hero ad shot rather than an honest shelf-presence test.

WHAT SHOULD NOT APPEAR
Because there is no negative-prompt field, state this positively: the shelf contains only the packaging described above and the generic adjacent products described — no shelf-talker signage, no price tag, no promotional sticker unless the packaging description specifically calls for one, and no invented extra text anywhere on the packaging beyond the fixed label details.

COMPARING MULTIPLE DESIGN VARIANTS
If this mockup is one of several packaging design options being tested against each other, keep the shelf_context, category_context_detail, facing_and_position, adjacent_products_note, and lighting_description worded identically across every variant, changing only packaging_description and fixed_label_details between them — a shelf test that varies the environment along with the design makes it impossible to tell whether a stakeholder's reaction is about the design itself or about an incidental difference in the mockup's staging.

CHECK BEFORE FINALIZING
Step back from the image mentally to the distance an actual shopper would glance at a shelf from, not the close-up distance you're likely reviewing it at on a screen, and check whether the the brand name "SURGE" in bold white sans-serif, "Whey Protein Isolate — Vanilla" beneath it, and a small lime-green checkmark icon are still legible at that implied distance — a mockup that only reads clearly when viewed close up hasn't actually tested shelf presence, it's tested close-up label legibility, which is a different and less useful question.

OUTPUT
One image showing the exact packaging design placed convincingly on a real-feeling retail shelf, legible enough at this angle and lighting that a stakeholder could judge its actual shelf presence.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

Treating the printed label as a fixed detail to preserve, rather than a description the model is free to reinterpret, matters because packaging mockups have a much lower tolerance for text drift than almost any other Flux use case. A mockup meant to test whether "SURGE" reads clearly at shelf distance fails its entire purpose if the model renders a slightly different, still-plausible-looking brand name instead — naming fixed_label_details as its own explicit block, distinct from the general packaging description, signals which details cannot be treated as approximate.

The instruction to use a specific, recognizable category context rather than a generic empty shelf matters because shelf-presence testing is inherently comparative. A design only reads as "stands out" or "blends in" relative to what's actually next to it in that category, and a mockup on a blank or unrelated shelf can't answer the actual stakeholder question, which is how this design performs against real category conventions, not how it looks in isolation.

The guidance on adjacent products — plausible but not identifiably a specific real competitor — threads a genuine needle: too generic and the comparison test is meaningless, too specific and the mockup risks depicting an actual competitor's real trademarked packaging inaccurately, which is a problem for an internal review deck meant to represent the category honestly rather than misrepresent a specific rival's actual current design.

Specifying flat, retail-aisle lighting instead of dramatic studio lighting is the single biggest lever for whether the mockup reads as an honest shelf-presence test versus a hero ad shot. Flux's default instinct for "product on a shelf" still leans toward flattering, directional light, because that's the more common framing in its training data for product photography generally, and a stakeholder evaluating actual shelf visibility needs the unglamorous, evenly-lit version, not the best-case version.

Holding every variable except packaging_description and fixed_label_details constant across a set of competing design variants matters for the same reason a controlled experiment holds every condition fixed except the one being tested — a shelf mockup is being used here to answer a comparative design question, and any incidental difference in staging between variants introduces a confound that makes the stakeholder's read of "which design wins" unreliable, even if each individual mockup looks convincing on its own.

Verified against

Flux Flux.2 · 2026-07-30

Changelog

  • 2026-07-30 — Initial publish, verified against Flux.2 for a category-specific retail-shelf packaging mockup with fixed label text.

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
Get a clean, ecommerce-ready product shot from Flux.2 with no negative promptsA structured product-photography brief for Flux.2 that produces a genuinely clean, seamless studio background purely through positive description — because Flux has no negative-prompt field to simply tell it "no clutter, no props, no shadows."Flux.2Flux.1 [pro]2026-07-22Brief Flux.2 for an editorial lifestyle photograph, steered by positive descriptionA camera-and-film-aware natural-language brief for Flux.2 that gets a genuine editorial-magazine look — because Flux has no negative-prompt field, unwanted elements have to be steered out through what you describe, not an exclusion list.Flux.22026-07-24Design a scroll-stopping social graphic on Flux.2 with real reserved caption spaceA platform-aware brief for a social campaign graphic on Flux.2 that reserves genuinely clean space for a text overlay added later in a design tool — achieved by describing the empty area explicitly, since Flux has no exclusion field to keep text or clutter out of it.Flux.22026-08-01Keep a character consistent across multiple scenes with Flux.1 KontextA sequential in-context editing workflow for Flux.1 Kontext that locks a character's face, outfit, and proportions across a series of new scenes by editing forward from one reference image each time, instead of re-describing the character from scratch and getting a visibly different person every generation.Flux.1 Kontext [pro]Flux.1 Kontext [dev]2026-07-26
All Flux prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY