What should you keep before deleting a product source asset?

Identify the exact record you intend to remove

Start with the filename, product edition and reason for deletion. A duplicate upload, an obsolete package photograph and a reference whose permitted use has changed need different decisions. In a hypothetical candle campaign, the merchant has uploaded the same amber-jar photo twice. Removing one duplicate is a storage choice; withdrawing an old label from a live campaign is a publication review.

Check that the selected entry is the source you mean to remove. A generated candidate, an approved download and an uploaded product photo can look similar in a thumbnail grid. Use a full view and the product identifier to distinguish them. Do not use a matching display name as proof that two records have the same content or that either one is the authoritative original.

Preserve the evidence needed for the next real task

Keep an appropriate copy of the authoritative photograph outside the disposable library entry when future product review requires it. Also preserve approved finished assets and a short association between source edition and output. For the candle, the useful record says which jar size and label were checked, which result was approved and where it was published. It need not collect unrelated customer material or private system instructions.

Adobe Stock’s licensing FAQ distinguishes a right to use an asset from ownership and lists use restrictions. Those are Adobe Stock terms, not CartVisual deletion rules. Check the actual permission for your source.

Preserving a source does not create permission to keep using it. If the issue is a withdrawn reference or an obsolete product edition, obtain the appropriate next decision for the dependent campaign. Keep only the records your authorized workflow needs. A duplicate-photo cleanup and a request to remove personal material are separate tasks; this guide does not establish a universal retention period or a complete account-erasure procedure.

Map the copies before making the deletion decision

The current library routine removes the chosen catalog entry and attempts to delete its attached library file. A disappeared entry is not a certificate that every stored copy was erased. Recorded generations and batches are separate mechanisms, and a batch can retain its own source copy. In the candle example, a duplicate library entry may be removed while the approved campaign remains valid. If the package is obsolete, review those remaining publications explicitly rather than assuming that deleting a source updates them.

Fictional cleanup R5 has library entries L1 and L2 with the same display name. First compare their full images and edition evidence; matching names do not establish duplicates. Suppose L2 is confirmed as the redundant upload and L1 is the authorized original. Removing L2 is a narrow library cleanup.

Batch B5 may still hold its own submitted source snapshot, and approved result O5 may already be downloaded and published in placement P5. Neither is recalled by removing L2. If instead the issue is permission withdrawal or an obsolete label, stop treating it as duplicate cleanup: identify B5, O5 and P5 for the relevant owner’s separate review. These identifiers are invented; no file was removed and no retention or erasure claim was tested.

Finish active work before relying on a cleanup

Inspect related tasks and batches before removing a source needed for another decision. A waiting batch item and a completed approved result do not have the same role. Keep the material necessary to understand unresolved work, and avoid using deletion as a substitute for inspecting its state. A saved source removal is not a provider cancellation control or evidence that a generation charge has been reversed.

Use the relevant library deletion control for the intended record only. Verify that the entry is no longer listed, while keeping your external original if it remains authorized and needed. The workflow does not promise recovery after deletion. If the record may be needed for a near-term edit or product dispute, resolve the retention decision before removing it rather than planning to reconstruct evidence from a generated result later.

When an old edition should leave a publication channel, give the channel owner the exact asset and placement to review. A local deletion cannot remove a cached advertisement, an emailed attachment or an editor copy. Mark the publication task separately so the storage cleanup is not recorded as a completed campaign recall.

Close the cleanup with a small, useful record

Record what was removed, which authoritative source remains and which approved outputs are still in use. For the duplicate candle photo, the final note can simply identify the retained original and approved campaign. For an obsolete label, include the open replacement placements and their owners. This preserves the decision without turning routine cleanup into an unnecessary collection of private account information.

Use source-to-output traceability to build the associations. Refer to product revision replacement planning when the sale item changes. Library cleanup, task-state review and external publication removal should each have an observable result. Treat a source deletion as complete only for the particular record it actually removes.