Tethered Product Photography: Review Each SKU Before You Clear the Set

Tethered product photography is useful when each new capture reaches a computer for inspection while the product and lighting remain in place. The practical goal is to catch an unreadable label, missed angle, or incorrect SKU assignment before you dismantle the setup.

A successful connection alone is not enough. Rehearse the complete path: capture, transfer, identify, inspect, approve, and back up. Only then move through the product batch.

Verify the exact camera and software combination

Tethering is different from copying existing files off a memory card. Software may read a camera’s RAW files without supporting live capture from that camera. Remote shutter control, live view, and simultaneous card recording also need separate verification.

For Lightroom Classic, check the exact camera model against Adobe’s tethered-camera support list, including the required software version and any operating-system or model-specific notes. Do not substitute the support status of a similar model.

Record the camera model, firmware, computer OS, capture application version, connection method, and intended file format. Follow the camera’s instructions for its connection mode. With USB, use a data-capable cable suited to the connection; a matching plug alone does not establish compatibility. Secure the cable so moving around the table does not pull on the camera port.

Decide where captures will actually be stored. Capture One describes Sessions as a project-oriented, file-based workflow in its Sessions guide. Whether you use a Session or a catalog workflow, verify the original-image destination separately from the application’s database or project file. Write the actual path in the shoot log.

Rehearse one SKU before starting the batch

Use one physical product and its real SKU label for the rehearsal. Keep the next product off the table until the current one passes these checks:

1. Choose the destination. Confirm that the capture folder exists, is writable, and has room for the planned files.
2. Set the identity. Enter the SKU and variant in the naming scheme or capture log before taking the first production frame.
3. Capture a test. Check that a newly created image arrives, rather than mistaking an old preview for a successful transfer.
4. Verify the original. Locate the saved file, confirm its format and name, and open it at useful inspection magnification.
5. Inspect the product. Check label text, critical edges, focus, glare, framing, and the correct variant against the item on the table.
6. Check storage behavior. Confirm whether the camera also recorded a file to its card; do not assume that tethering provides two copies.

Capture One documents card-plus-computer recording with compatibility conditions in its saving-to-memory-card guide. Test the behavior of your actual combination before counting the card as a backup.

Make the SKU transition explicit

The most important naming moment is often the switch between products. Finish reviewing the current SKU, update the destination or naming fields, then photograph the next item. A visible SKU slate can help separate groups, but exclude that identification frame from listing selections.

For example, a hypothetical item MUG-041-BLUE might use the filename stem MUG-041-BLUE_front_001, followed by the camera file’s actual extension. Keep angle labels consistent and use a sequence to distinguish repeat captures. The product-image file-naming guide explains how those identifiers can continue into later edits and exports.

Review each required angle before releasing the product. A sharp front view does not prove that the rear label or base was captured. Build a small product-photo contact sheet for the current SKU when an overview makes omissions easier to spot, while retaining full-size inspection for critical details.

Use a clear hold-and-release decision

This hypothetical rehearsal log illustrates decisions rather than reporting a real shoot:

Assign one person to mark the SKU ready to clear. In a one-person workflow, use the same explicit checkbox rather than relying on having seen a promising thumbnail. Apply the relevant product-photo QA checks while corrections are still possible on set.

Recover from a disconnect without losing the mapping

Stop advancing through products when transfers stop. Note the current SKU, angle, last confirmed computer file, and any captures taken afterward. Check the camera’s storage before assuming those later exposures were saved anywhere.

Follow the application’s connection troubleshooting for the supported setup. After reconnecting, verify the destination and naming fields again, then take a clearly identified recovery test. Reconcile any files retained on the camera with the computer captures. Compare identity and content before importing or renaming; do not overwrite existing files to make the sequence look tidy.

Keep a short handoff card containing:

• Camera, software version, session or catalog name, and original-image path.
• Current SKU and angle, last confirmed filename, and uncertain captures.
• Next filename or sequence and the recovery test result.
• Backup destination, verification status, and release approval.

Copy originals to independent storage and check that the copy completed and files open. Preserve capture logs and relevant project information too; a database backup alone is not proof that the image originals were copied.

If tethering remains unreliable, use card capture with a deliberate import-and-review pause before clearing each SKU. Preserve the same naming and approval steps. Approved source images can then enter a PackScena scene workflow, where any changed product detail still needs human comparison with the source and actual item. Tethering belongs to the capture setup; later scene review does not replace it.