What changes when you set a different default AI model?

Separate a default from an approved campaign identity

A default offers a convenient reference choice; an approved campaign identity is an editorial decision. In an illustrative bag campaign, the team approved model Rowan for carry scenes and later sets model Ellis as the account default. The new default does not establish that Ellis is approved for the campaign, nor that the previous Rowan images became inaccurate.

Keep the campaign record with the approved reference and intended scenes. If you deliberately change the person, make that a clear creative decision and review the new combined product image. An attractive library portrait cannot establish how the model will hold the bag, whether the garment remains accurate or whether the resulting series looks coherent.

Check which state you are changing

This state map prevents two opposite mistakes: assuming the change affects only untouched future work, or assuming it updates everything already created. Neither is a safe reading of the current workflow. Confirm the state that matters to the next action rather than relying on the word default alone.

Reopen the workbench and inspect the actual selection

The current model interface clears its temporary picker selections when saving a different default. At the same time, relevant workbench drafts can retain a model choice and apply it again when the workbench is rendered. Consequently, a picker you see immediately after the change and one reopened from a saved draft need not tell the same story.

Return to the specific Product images, A+ or Virtual try-on workbench and inspect its visible selected reference. Check whether a person is enabled at all. If the campaign needs Rowan, explicitly select Rowan there; if it needs no person, use the applicable no-model choice. Do not submit merely because the library badge says Ellis. The request should match the intentional current workbench configuration.

Inspect the product-and-model combination before motion

Adobe describes reference images as guidance for newly generated variations, which separates input choice from already completed results.

That source concerns Adobe's style references, not an Itemlume default-model control. In Itemlume, a selected person reference guides an image request; it is not a perfect identity lock. Review the new result for facial appearance, pose, product contact and item accuracy rather than assuming that choosing the intended name settled those questions.

For a video, the approved combined image is the first-frame reference. Changing the model default does not replace the person already pictured in that first frame. Create and approve a new combined image if the video's cast must change. Keep the image decision separate from video generation, and inspect the finished motion against the chosen frame and product evidence.

Record the next selection instead of rewriting history

For the bag campaign, write a concise change note: account default Ellis; approved campaign reference Rowan; next carry image explicitly uses Rowan; previous completed assets retained after their own review. If a new campaign should use Ellis, record that separately and approve its initial scene. Do not rename old tasks as though they had always used the new person.

Recheck the selection after restoring a draft, changing account context or moving between relevant workbenches. If the expected reference is unavailable, resolve that issue before submitting; a substitute should not inherit approval automatically. Use the reference-version handoff to preserve the campaign choice for another creator. A default remains useful only when the actual next request and the approved creative intention agree.