Why Did My Next Tethered Product Photo Inherit the Previous SKU's Descriptive Metadata?

Separate capture naming from descriptive fields

A tethered workflow can generate sequential filenames while applying metadata through another setting. Capture One's official help documents Next Capture metadata copying from the last capture, the primary variant, or a selected clipboard.

Begin with the first affected image. Record its actual filename, product identity, IPTC description, keywords, and any other SKU-bearing metadata. Compare those fields with the preceding capture and the currently selected primary variant.

If the filename correctly identifies the new product but the description names the old one, the failure is not necessarily a filename-counter problem. It may be a metadata source or clipboard-scope issue.

Do not rely on a visible filename alone to approve the image for distribution. Embedded metadata can remain wrong even when the photograph and folder name are correct.

Trace the metadata source before changing fields

Inspect the configured Next Capture metadata option. If it copies from Last, compare the preceding image's IPTC fields. If it copies from Primary, confirm which variant was primary at the moment of capture. If a selective clipboard is used, inspect exactly which fields it contains.

Determine whether the problem affects every field or only a subset. A correct photographer credit combined with an incorrect product description may indicate that some metadata is intentionally shared while product-specific fields were copied too broadly.

Use a working copy to correct existing metadata and a controlled new capture to evaluate the future-capture configuration. Changing the source option is not proof that old files have been repaired.

Keep metadata provenance separate from the physical product revision. A descriptive field naming the correct SKU still requires a photograph of the correct item.

Hypothetical bottle-session metadata leak

Hypothetical illustration—not an executed Capture One session: a merchant finishes photographing SKU B-10, a blue 500 mL bottle. Its metadata description is 'Blue bottle, 500 mL' and its keywords include 'blue' and 'B-10.'

The next session photographs SKU W-20, a white 350 mL bottle. The file is named W-20-001.RAW, but its metadata still describes B-10.

The proposed investigation compares the last B-10 capture, the first W-20 capture, and the configured metadata-copy source. If the source is Last, the copied description and keywords are consistent with that configuration.

A test capture after selecting the intended metadata policy should be inspected for both correct product-specific fields and any deliberately retained shared fields. The worksheet does not claim that these records were actually generated.

Correct existing records and protect the next batch

For already captured images, identify the affected files and correct the wrong metadata using verified SKU information. Do not globally replace every keyword if some terms accurately describe both products.

For future captures, select an appropriate metadata source or clipboard scope before the first photograph of each SKU. Use a test capture and inspect its embedded fields, not just the Capture One viewer labels.

Before delivery, compare the final photograph, filename, product revision, IPTC description, and keywords. Where exported derivatives are involved, inspect whether the intended metadata is retained or deliberately excluded.

Accept the batch only when each product-specific field describes the actual photographed item. Metadata correction does not alter image pixels, and an accurate filename does not compensate for a wrong description.

Record your own observations

The filled rows are illustrative examples. Use the blank row for your own files and observations.

Download the editable CSV worksheet

What the references establish

• Capture One Online Help — Applying metadata to captures: Official help documenting future-capture metadata copying from Last, Primary, or a selected metadata clipboard, including IPTC fields and keywords.