Back to blog

Replace a product photo without losing the approved version

Keep a known-good export while evaluating a replacement. Track source, direction, output version and approval rather than trusting the newest file.

By CatalogCut4 min read

AI-assisted product documentation based on CatalogCut’s implemented workflow and the linked sources. Examples are illustrative, not customer case studies. How these guides are prepared.

The newest product image is not always the safest one to publish. A replacement can fix the backdrop while damaging a label, or improve framing while introducing the wrong accessory.

Keep the previous approved version identifiable until you have reviewed the replacement. “Latest,” “completed” and “approved for delivery” should be three different facts.

Establish the known-good version

Before requesting a change, note the product identifier, source photo, photography direction and approved output. Keep a downloaded copy if you need to retain it beyond the service's image expiry.

An illustrative record might say: Bottle amber / source front-02 / soft studio direction / approved output A. A replacement is candidate B, not an automatic revision of A's approval. The labels are examples, not CatalogCut's exported filename format.

Also write down the reason for the change. “More room above the cap” creates a clear acceptance test. “Make it better” invites another round of subjective edits without establishing what must remain unchanged.

Know whether you are changing presentation or evidence

A new source photo, a different Look and a different export size are not equivalent changes.

  • A new source can change the evidence for the item's identity and condition.
  • A new Look can change the scene direction used for generation.
  • A replacement generation produces a new candidate that needs review.
  • A resized or reformatted export changes the delivery bytes, even if the chosen composition remains the same.

Treat a changed source or direction as a new configuration decision. Do not carry a pilot approval forward merely because the page still shows the same product name.

Evaluate the replacement beside the source and the approved image

Use three-way comparison: original evidence, known-good output and replacement. First check whether the requested improvement happened. Then check whether the replacement introduced a regression in product identity, quantity, shape, color or small details.

For an item with a printed label, compare the lettering directly rather than inferring that an attractive new frame preserves it. If a source does not show a feature clearly, mark that uncertainty instead of letting either generated version settle it.

This is a version-control problem as well as a visual review problem. A reviewer should be able to say which specific output was inspected and why it was accepted or rejected. Use the per-output product review checklist to keep that decision separate from processing success.

Use catalog history without overwriting the export choice

CatalogCut catalog runs retain attempt history and a separate approved export choice. A newer result can remain unreviewed while an older approved result stays selected. Rejecting a newer candidate does not mean the known-good version must disappear.

Check the current review state and the export choice before preparing the ZIP. Do not assume that the output displayed as the newest job is the file that will be delivered, or that an older approval applies to the latest result.

A technically successful replacement still follows the normal credit rules. If you dislike it, read the new quote before trying again; aesthetic rejection is not an automatic refund policy.

Recheck the final package

Read the manifest to confirm which output was selected, whether it remained available and which rows were excluded. An approved choice whose image has expired is not a usable handoff by itself.

If you resize, optimize or otherwise transform the delivered file, review the new bytes. The previous checksum and readiness report refer to the earlier file, not every future derivative.

Finally, tell the uploader what changed and which file replaces the old storefront image. Clear version identity prevents an approved photo from being displaced by an unreviewed download with a more recent timestamp.

Keep approved output A while reviewing candidate B.

A fictional bottle with an approved export and a newly generated replacement.

  1. Record the known good

    Identify the source, direction and specific approved output before requesting a presentation change.

  2. Compare the candidate

    Compare the replacement with both the source and older approved image to catch regressions.

  3. Choose delivery

    Read the selected export choice and final manifest rather than assuming the newest result will be delivered.

Illustrative workflow. Review checkpoint: A successful replacement still needs review and is not automatically refundable when disliked.

Official sources