Commercial Photoshoot File Management Workflow

A reliable commercial photoshoot workflow in the UK depends on consistent SKU names, controlled selects, documented retouching stages and a delivery structure your team can search months later. Treat every image as a managed asset rather than an isolated file, and you will reduce duplicated work, approval errors and missing ecommerce images.

What should happen immediately after a commercial photoshoot?

Immediately after the shoot, secure the original camera files, record the shoot details and create at least two verified backups before anyone starts editing. Do not rely on a memory card, a photographer’s desktop or a single cloud upload as the master copy.

1. Record the job information. Note the client or brand, shoot date, location, photographer, camera cards, product range, agreed deliverables and any usage restrictions.
2. Copy, do not move, the camera files. Transfer the card contents into a dated project folder while preserving the original folder structure where practical. Keep the cards untouched until the transfer has been checked.
3. Use a clear master folder. A useful structure might be Brand_Campaign_2026-04-18, with subfolders for 01_RAW, 02_SELECTS, 03_RETOUCHING, 04_APPROVALS, 05_FINAL and 06_DOCUMENTS.
4. Back up to separate destinations. Keep one working copy and at least one additional copy on a separate drive or managed storage system. A second location is preferable for important commercial work.
5. Log the handover. Record when files were copied, who checked them and where the backups are stored.

This approach reflects the basic capture-to-delivery principle of transferring files, importing them into a catalogue, producing review or retouching outputs and copying the project to multiple drives. A capture-to-delivery photography workflow provides a useful reference for that sequence.

How should you name product photography files?

Product photography files should use a predictable naming convention based on the SKU, view and processing stage, with no spaces or vague labels such as “final-final”.

Agree the convention before the shoot and apply it consistently across capture, selects, retouching and delivery. A practical format is:

BRAND_SKU_VIEW_VARIANT_STATUS.ext

• BRAND: a short, consistent brand or project code.
• SKU: the exact product identifier from the product information system.
• VIEW: a controlled label such as FRONT, BACK, SIDE, DETAIL or TOP.
• VARIANT: colour, size or pack version where relevant.
• STATUS: a clear stage such as RAW, SEL, R1, APP or FIN.

For example, ACME_SKU1842_FRONT_BLACK_SEL.jpg identifies a selected front view of a black SKU. After approval, the corresponding file might become ACME_SKU1842_FRONT_BLACK_FIN.jpg. If the same product has a detail crop, use ACME_SKU1842_DETAIL_ZIP_BLACK_FIN.jpg rather than adding an unexplained number.

Keep the name stable wherever possible. If a file changes from a first retouch to a second retouch, use a version field such as R1 and R2 rather than overwriting the earlier file. Never use the filename alone to store essential information: retain a shot list or asset register with SKU, view, orientation, crop, background, retouching notes, approval status and delivery destination.

How should selects and approvals be managed?

Selects and approvals should happen through one numbered review set and one written decision record, not through scattered email attachments and chat messages.

After ingest, create lightweight review files with enough resolution for composition, focus, product visibility and styling checks. Keep the original RAW files separate from these proofs. A contact sheet or review gallery can show the frame number, SKU and view beside each image, making feedback more precise.

Ask reviewers to comment against a defined checklist:

• Is the correct SKU shown?
• Is the product clean, complete and correctly positioned?
• Is the required angle or detail present?
• Are labels, packaging and colour accurate?
• Does the image meet the agreed crop, background and aspect ratio?
• Is any styling, reflection or compositional issue likely to require retouching?

Nominate one person to consolidate feedback. “Please fix the middle one” is not an actionable instruction when a gallery contains multiple products and views. “SKU1842, FRONT, frame 038: remove the visible fibre beside the collar” is specific enough for a retoucher to follow.

Once the selection is approved, lock it. Move rejected frames into a separate reference folder rather than deleting them immediately, particularly where the client may later request an alternate angle. Mark the approved list in the asset register so production and ecommerce teams are working from the same source.

What is a dependable retouching workflow for ecommerce?

A dependable retouching workflow for ecommerce separates technical preparation, creative correction, client review and final export into named stages.

1. Prepare the retouching brief. State the required treatment for dust, creases, reflections, colour, skin or material texture, clipping paths, shadows and background removal. Include references where “natural” or “premium” could be interpreted differently.
2. Send working files with instructions. Use high-resolution files and a retouching list that identifies each requested change by SKU, view and frame.
3. Create a first retouch. Save it as a new version, such as R1, rather than replacing the selected source.
4. Run internal quality control. Check edges, repeated patterns, product geometry, colour consistency, dust removal and any signs of over-processing.
5. Issue a controlled approval set. Keep the review version linked to the source filename and record feedback in one place.
6. Export the approved master. Preserve the agreed colour profile, dimensions, format and metadata requirements.

Commercial post-production commonly includes file management, culling, colour correction, retouching, compositing and delivery as distinct parts of a structured process. This commercial photography post-production guide supports that staged approach.

Do not ask for “final images” without defining final. A product cut-out for a marketplace may need a transparent PNG, while a Shopify product image may require a specific JPEG size and background. Campaign assets may need layered masters, high-resolution TIFFs or alternate crops. Confirm those requirements before retouching begins.

What should the final delivery folder contain?

The final delivery folder should contain only approved assets, a readable manifest and any instructions needed for your team to use the files correctly.

A practical structure is:

• 01_FINAL_JPEG: web-ready files using the agreed dimensions and naming convention.
• 02_FINAL_PNG: transparent cut-outs or files requiring lossless transparency.
• 03_HIGH_RES: print or campaign masters, if included in the brief.
• 04_ALTERNATES: approved crops, angles, detail views or language variants.
• 05_MANIFEST: a spreadsheet listing SKU, filename, view, dimensions, format, colour profile and approval status.
• 06_README: short notes covering delivery date, exclusions, usage information and contact details for queries.

Before handover, check that every approved SKU has the expected number of images, filenames match the manifest, files open correctly, dimensions are correct, colour profiles are consistent and no review versions are mixed with finals. Check the delivery link, permissions and download behaviour as well. A folder that looks complete but contains one zero-byte file or an inaccessible subfolder is not complete.

Agree the delivery timetable in the brief rather than presenting seven to ten business days as a universal rule. Timing depends on the number of SKUs, styling complexity, retouching depth, approval rounds and whether assets need compositing or alternate formats.

How can teams prevent photoshoot asset management problems?

Teams prevent photoshoot asset management problems by agreeing ownership, naming, approvals and retention before the first frame is captured.

Assign responsibility for the master archive, selects, retouching approvals and ecommerce upload. Decide how long RAW files and layered masters will be retained, who can request a change after approval and how revised files will be labelled. If a product is relaunched six months later, your team should be able to identify the original shoot, the approved master and the usage rights without searching through personal inboxes.

For larger ranges, maintain a central asset register rather than depending on folder names alone. Automated tagging, batch renaming and cloud collaboration can reduce repetitive work, but automation should follow an agreed naming system. An automated tool that applies the wrong SKU to hundreds of files creates a larger problem than manual organisation.

If you are preparing a brief, define the shot list, deliverables and usage rights before production; the UK ecommerce photoshoot brief guide covers those decisions in more detail.

For a managed commercial photoshoot workflow covering capture, selects, retouching and delivery, see the WeTrends photoshoot service and share your SKU count, required views, retouching expectations and delivery formats.

Frequently asked questions

What should happen immediately after a commercial photoshoot?

Secure the original camera files, record the shoot details, copy rather than move the files, and create at least two verified backups before editing begins.

How should product photography files be named?

Use a consistent structure such as BRAND_SKU_VIEW_VARIANT_STATUS.ext, with controlled labels for views and stages such as RAW, SEL, R1, APP and FIN.

What should a final delivery folder contain?

Include approved web-ready files, transparent PNGs or high-resolution masters where required, approved alternates, a manifest and a README with usage and delivery notes.