A larger catalog makes small inconsistencies easier to repeat. The wrong variant filename, an overlooked accessory or a crop that cuts off a handle can travel through an entire batch before anyone notices.
Use a workflow with clear handoffs: prepare the products, capture a known set of views, approve the master, export for the destination and inspect the published result. A simple record at each stage is more useful than relying on memory.
At a glance
- Define the views and naming convention before the shoot.
- Approve a representative test set before processing the full batch.
- Track the relationship between SKU, source, export and published listing.
Build the shot list from the catalog
Start with the products and variants that actually need images. Give each row a stable identifier, then list the required views. A front view, rear view, useful detail and contents photo might be a suitable starting set for one range; a different product family can need a different plan.
As an illustration, 40 products with four planned views create 160 planned assets before retakes or destination exports. That is a planning calculation, not a rule about how many photographs a listing needs. Count the work this way so preparation, image selection and review are included in the schedule.
| Record field | Example purpose |
|---|---|
| SKU and variant | Identify the exact item and selected option. |
| View | Front, rear, detail, contents or context. |
| Source file | Connect the image to the camera original. |
| Review status | Show whether capture, edit and export were approved. |
| Destination | Record where the final asset will be published. |
Group similar products and stabilize the setup
Photograph a product family together when the same light and framing work for it. A line of bottles can share a baseline and camera height. A collection of irregular handmade pieces may need adjustments while preserving a coherent visual style. Keep a setup photograph and a reference frame for later comparison.
Prepare the products before they reach the set. Match accessories to the right item, clean surfaces appropriately and set aside damaged packaging that requires a condition view. Mark the completed row immediately after capture. A tray or shelf with a clear “to photograph” and “captured” separation can prevent items from quietly skipping a stage.
Approve the difficult examples first
Choose a small set that exposes the workflow’s limits: a pale object, a dark one, a reflective surface, fine projecting parts and an unusual shape when your catalog contains them. Complete those examples from capture through upload before committing to the full batch.
Check the actual product view, not only whether processing succeeded. Compare edges with the source, confirm the included pieces and inspect label detail. Then open the destination on a phone and desktop. If a crop or background treatment fails here, correct the preset while the number of affected files is still small.
Keep sources, masters and exports separate
Store the camera originals without overwriting them. Keep the approved edit or cutout as a master, and create destination files in clearly named export folders. This gives you a route back when a marketplace changes its image guidance or a new storefront needs a different crop.
Choose filenames that preserve the SKU, variant and view. For example, a structured name can make a blue front view distinguishable from a black rear view before opening either file. If an editor creates automatic numeric suffixes, check the resulting mapping rather than letting the suffix become the only clue to what the file represents.
Maintain a manifest or simple catalog record beside the files. It should be possible to identify which source produced an export and which export was uploaded. This matters when a later product revision replaces a label or changes the contents of a kit.
Save export settings with an approved example
Image editors can save reusable export presets for dimensions, format, color space and naming. Adobe’s Lightroom Classic guidance describes creating separate exported files and reusing presets across a selection. Keep the destination’s current specification beside the preset. Adobe: export workflow and reusable presets.
Write down which settings are actual destination requirements and which are your own catalog choices. A square crop may be your storefront convention, while a background color or file limit can come from a marketplace. Distinguishing the reason makes a later change easier to review.
Inspect a few actual exported files from each batch, including the difficult examples. Confirm that the right preset was selected and that the files open normally. When an error affects only one image, record it against that asset and continue tracking the rest; avoid losing the relationship between completed and unfinished work.
Make publishing a separate quality gate
Upload the approved export, then verify the saved listing. Match the displayed color, included quantity, image order and selected variant to the product record. Check thumbnail crops as well as the larger gallery. For feeds, review the destination’s processing status and the exact image URL.
Record the approved version and resolve failures in a small exception list. A useful review note says what was wrong and what changed: a clipped handle was reframed, an incorrect color was remapped or a file exceeded the destination’s size limit. That makes the next batch easier to improve.
Finish by saving the approved test set, export settings and setup reference together. When a new teammate, supplier or theme enters the process, run that same representative set again. The workflow stays dependable because each stage produces something the next person can inspect.
Sources and further reading
Sources reviewed October 14, 2026. Check the linked documentation and your product category before publishing.