A digital product model can make it easy to combine colours, sizes and accessories that are not actually offered together. Before commissioning a family of variant images, have the product owner define the allowed combinations and the dependencies between them.
The visual supplier should not infer commercial availability from what the model can display. A technically successful render of an unsupported configuration is still the wrong deliverable for a current-product explanation.
Begin with rules rather than a list of buttons
Identify the choices a customer can make and which choices affect others. A selected size may require a different fitting; a particular enclosure may exclude an accessory; a finish may be available only on certain components. Use the current approved offer as the source.
Epic's variant-manager documentation includes dependencies that activate other variants. The mechanism can express linked visual states, but the supplier still needs authoritative product rules.
Ask the specialist to translate those rules into a manageable scene structure. The buyer's input should remain understandable without software terminology, so the product owner can check it and maintain it when the offer changes.
Separate exclusions from missing references
An unavailable combination should be excluded deliberately. A valid combination whose source model is missing is a preparation gap. Keep those categories distinct; otherwise a production limitation can accidentally become a statement about the product range.
For each dependency, identify the resulting visible changes. Replacing the principal body may also require a different bracket, label or connection position. A colour-only preview can look correct while leaving the wrong accessory attached.
Include a defined starting state for the scene. If each new variant only changes some properties, a previous selection can remain active and create an unintended hybrid. Ask the supplier to demonstrate how the requested configuration is established completely, not just which control is clicked last.
Test one valid dependency and one prohibited combination
A useful proof shows that a dependent part changes when it should, and that a disallowed combination does not enter the output set. This is a visual-production test, not a certification of a sales configurator or an engineering compatibility check.
Consider a hypothetical construction-product family with two enclosure sizes and a service module offered only with the larger unit. The buyer supplies that rule. A test reveals that selecting the smaller enclosure hides the module body but leaves its connector visible. The specialist corrects the complete state before generating the image set.
The example is invented. It demonstrates why valid configuration imagery depends on linked object states rather than a collection of attractive alternatives.
Assign ownership of future rule changes
The product owner should approve the allowed-configuration record and notify production when it changes. A visual scene should not become a parallel, unofficial catalogue of availability. Retain enough traceability to identify which delivered images are affected by an altered rule.
If the current commission needs only a few fixed configurations, it may not justify a comprehensive configurable system. Ask the supplier to compare a bounded image set with a reusable variant structure based on the actual likely reuse, without assuming that more automation is always a better purchase.
Discuss the product explanation with Live Images and confirm whether the specialist variant work fits the film scope. Bring the approved combinations and dependencies before asking production to multiply the outputs.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.