How to trace a product creative from source image to published output

Give the authoritative product source a stable identity

Start with the actual edition, color and package size shown by the source, not only the commercial product name. A bottle called Daily Serum may have several labels in circulation. Record which photograph or supplier-approved reference establishes the current appearance and which product facts were supplied for the campaign. Keep that reference distinct from inspiration imagery.

In an illustrative three-scent candle launch, identify the amber jar as scent A, the clear jar as scent B and the printed gift sleeve as a separate packaging edition. A photograph with a useful composition is not automatically authoritative for all three. This initial distinction prevents a later attractive output from silently becoming the factual source for another variant.

Record relationships instead of copying every setting

A compact record can name the source identifier, the selected creative function, the saved result and any edited derivative made from it. Record relevant choices such as copy language, ratio and intended message when they explain the dependency. You do not need to publish private generation instructions or retain unrelated account details to establish this chain.

Connect the product scene used as a video’s first image to its approved clip. Then connect the clip to the captioned social export. This is a sequence of production dependencies, not proof that the generated file matches every source pixel. Product fidelity still requires inspection of the actual result; a well-maintained record can identify a wrong dependency without certifying a correct one.

Use a small lineage table

Frame.io’s version stacks organize revisions and make prior versions available for comparison. That is a useful reference for keeping history visible; it is not a claim that Itemlume currently implements the same stack interface. Frame.io’s versioning guide. Your external record should retain the relationship even if files move.

Ask which descendants a product change invalidates

If candle A receives a new label, inspect every still or clip derived from its old front photograph. Candle B’s separately sourced image may remain valid. A crop created from the old clip does not become current just because its filename lacks a version number. Trace dependencies before deciding which publication assets need replacement.

Separate product invalidation from layout changes. A new headline may invalidate the captioned derivative while leaving the clean product clip useful. A new jar changes the underlying visual evidence and may invalidate more of the chain. This distinction prevents both unnecessary regeneration and the opposite mistake of fixing only text while an outdated product remains visible.

Close the record at publication and retirement

Record which approved derivative was actually published and where, rather than merely noting that a team downloaded something. Retain the source and review decision according to your own production needs. When retiring an obsolete visual, identify its affected placements so a teammate does not reintroduce it from an older export folder during the next campaign.

For the candle launch, the final record might show that edition 2 supplied the approved shelf scene, that the vertical crop is current, and that edition 1 must not be reused. This is an illustrative team method. Itemlume’s asset categories and generation records can support retrieval, but the source-to-publication dependency decisions described here remain a separate human-maintained process.