Black Friday Product Photography: 30-Day Prep Workflow for Sellers
The 30-day calendar for refreshing your product photos before Black Friday. Audit, shoot, AI-clean, per-platform export, and A/B test in time to win the seasonal traffic spike.
Growth Marketing
Black Friday revenue scales with photo quality more than with discount depth. The seller with the cleaner main image gets the click; the seller with the cleaner detail shots gets the conversion. But you can't refresh a 200-SKU catalog of product photos in the week before Black Friday. You need a 30-day plan that audits, shoots, AI-cleans, exports per platform, and A/B tests in time to deploy before traffic spikes.
This is the workflow we run with sellers in the September-October window for a November 27 Black Friday. The same calendar works for Cyber Monday (Nov 30), Boxing Day (Dec 26). Any platform-driven flash sale where photo quality has 24-48 hours to deliver the conversion lift.
If you're tight on time, the priority order is: audit first (week 1), then shoot only the top 20% of SKUs by revenue (week 2), then AI cleanup + per-platform export (weeks 3-4). Skip the A/B test step rather than skip the audit. Refreshing the wrong photos is a worse outcome than refreshing fewer of the right ones.
- 30 days is the right window because shooting and exporting are the rate-limiters, not the editing. Compressing the workflow under 14 days forces shortcuts on the platform-specific exports, which is where the conversion lift actually compounds.
- Priority order matters: audit (week 1) -> shoot top 20% by revenue (week 2) -> AI cleanup + boost (week 3) -> per-platform export from one master (week 4). Skipping any earlier step compromises everything downstream.
- Per-platform exports derived from one 4K master is the single highest-ROI step in the plan. 5-15% conversion lift on its own. Letting Amazon, Shopify, or TikTok Shop auto-crop a single upload always loses important product geometry.
- AI cleanup + AI Enhance turns iPhone product photos into delivery-ready images for under $30/year. Track the typical 30-second-per-photo cleanup and the 30-second-per-photo enhance step separately so you can budget the week-3 editing time accurately.
- Build in 2 days at the end for A/B test setup and pre-launch QA. The platforms let you swap photos without resetting the listing. You want the new photos indexed and rendering correctly on mobile before BF traffic arrives.
Why 30 days and not 7
The compressed 7-day-before-BF photo refresh is the most common pattern we see fail. Sellers realize the photos are weak in mid-November, scramble to shoot and edit. Either ship with rushed cleanup or miss the BF window fully. The math doesn't work even when you sprint: shooting a 30-SKU catalog with consistent lighting takes one or two full days minimum, AI cleanup at 90 seconds per photo plus 30 seconds per enhance plus 60 seconds per platform export means roughly 4 minutes per SKU per platform. A 30-SKU catalog across 4 platforms is 8 hours of editing time you don't have in the final week.
The 30-day plan inverts this. Week 1 is the audit — you do the work of figuring out which photos actually need refreshing. Is the highest-leverage step because most catalogs have 70-80% of photos that are fine and 20-30% that are dragging down the listing. Week 2 is the shoot, batched into 1-2 days so the lighting stays consistent. Week 3 is the AI cleanup + boost pass, which is the most time-flexible step because each photo is independent. You can do 30 photos a day or 10 photos a day depending on your other work. Week 4 is the per-platform export and the A/B test setup. Is the step that compounds the prior weeks' work into actual conversion lift on the listing.
What 30 days specifically buys you that 7 days doesn't: the ability to discover and fix problems before BF traffic arrives. If a photo doesn't enhance well (some products with very flat lighting need a re-shoot), week 3 reveals it and you have a week to re-shoot. If a platform's export pipeline rejects an image (Amazon's pure-white-BG enforcement, TikTok Shop's aspect-ratio rules), week 4 catches it. In the 7-day sprint, both of these fail silently and you discover them on BF day.
- 7-day BF photo refresh fails because the math doesn't work: 30 SKUs × 4 platforms × 4 minutes per photo = 8 hours of editing time you don't have in the final week.
- 30 days lets each step happen at the right cadence: audit (1 week), shoot batched (1-2 days), AI cleanup (flexible), per-platform export (1 week with QA buffer).
- The extra time is what catches problems early: photos that need a re-shoot, platform exports that get rejected, mobile-rendering issues that don't show up on desktop.
Days 0-7: audit the catalog
Open a spreadsheet. List every SKU in your catalog. For each, paste in the current main image and score it on five dimensions: lighting quality (1-5, where 1 is yellow indoor light and 5 is clean window light), background cleanliness (1-5, where 1 is prep-table clutter and 5 is pure white or brand-consistent), product clarity (1-5, where 1 is soft focus and 5 is sharp detail), aspect-ratio fit per platform (binary per platform. Does the current photo crop cleanly to each platform's required spec), and mobile readability (1-5, where 1 is hard to read at thumbnail size and 5 is instantly distinct).
Now sort the SKU list by Q4 revenue contribution from last year. Pareto's distribution holds in almost every e-commerce catalog: 20% of SKUs drive 80% of revenue. Cross-reference the photo-score column with the revenue column. Your priority list for the shoot is the SKUs in the top 20% by revenue with photo scores below 4 on any dimension. For a 200-SKU catalog, this is often 8-15 SKUs that need a refresh. Not 40, not 200, just the handful that are actively losing revenue to their photo quality.
If you don't have a top-20%-by-revenue list yet, week 1 is also the week to build it. Pull last year's Q4 sales from Amazon Seller Central, Shopify Reports, Etsy Stats, or your platform of choice. Cumulative-sort by revenue and draw the line at 80%. The SKUs above the line are your refresh priority. Below the line, ignore for the BF refresh. Those listings underperform for reasons photos won't fix in the BF window.
- Score each SKU's photo on lighting, background, clarity, aspect-ratio fit, and mobile readability — 1-5 per dimension.
- Pull Q4 last-year revenue per SKU and cumulative-sort. The top 20% drives 80%; refresh those photos first.
- Cross-reference: top-20%-by-revenue SKUs with any photo dimension below 4 are the BF refresh priority list. Typically 8-15 SKUs for a 200-SKU catalog.
Days 8-14: shoot the priority list
Batch the shoot into one or two full days. Consistency of lighting across the priority list is more valuable than perfect lighting on any single SKU. If your shoot day is Tuesday, all 12 priority SKUs get the same Tuesday-10am window light at the same prep-table setup. The result is a visually-coherent catalog refresh, which buyers register as a designed brand rather than as one-off snapshots.
For each SKU, capture 3-4 angles: the hero shot (45 degrees above for plated products and flat-lay. Straight-on for vertical bottles and packaging), a detail shot (close-up on the texture, label, or feature), a scale shot (with a hand or common object for context). A usage shot (the product in use). The hero shot is what hits the main listing slot on every platform. The others fill the secondary slots that drive conversion once a buyer clicks through. Not every SKU needs a usage shot — judgment call by category.
Equipment minimum: phone with a modern camera (iPhone 12+, Pixel 6+, Galaxy S21+) plus a piece of clean white seamless paper or a clean countertop and a window. Tripod optional but useful for matching angles across the priority list. Don't budget for a DSLR if you don't already have one. The AI cleanup workflow makes a phone shot delivery-ready, and the lighting-and-angle decisions matter more than camera body anyway. The exception is jewelry, watches, and other small reflective products where the macro capability of a DSLR is meaningfully better than a phone's macro mode.
- Batch the shoot into 1-2 full days for consistent lighting across the priority list.
- Capture 3-4 angles per SKU: hero, detail, scale, usage. The hero hits the main listing slot; the others fill secondary slots.
- Phone camera is fine for everything except small reflective products (jewelry, watches) where a DSLR macro mode is meaningfully better.
Days 15-21: AI cleanup + enhancement
Three editing passes per photo, in order. First: Magic Eraser cleanup. Brush over prep-table clutter, stray hands, edge debris, packaging scraps, lighting stands accidentally captured at the frame edge, and any small unwanted elements. The cleanup pass should take about 30 seconds per photo for a well-shot batch and 60-90 seconds per photo for messier captures. Inspect each result and run a touch-up brush pass on any visible seams.
Second: AI Enhance. Phone sensors compress the dynamic range under indoor and mixed-light conditions, leaving photos that read flat. AI Enhance lifts the shadows, recovers highlights, and sharpens product detail. Target 30 seconds per photo at this stage — single submission, no manual tweaks except in edge cases. The boost is what separates 'phone photo' from 'delivery-ready'. Some sellers report 5-10% conversion lift from the enhance pass alone versus the cleanup pass alone.
Third (Amazon only): Background Eraser for pure-white-background main images. Amazon requires the main image to be on a pure-white background (RGB 255/255/255) with no text, watermark, or other graphic. Isolate the product, composite onto a true white surface, and verify the corners are pure white before upload. Amazon will down-rank or suppress listings whose main image fails this rule. Other platforms (Etsy, Shopify, TikTok Shop) don't enforce pure white, but a clean consistent background helps everywhere.
- Three editing passes per photo: Magic Eraser cleanup (30-90s), AI Enhance (30s), Background Eraser for Amazon pure-white BG (60s).
- AI Enhance is the highest-leverage single pass — phones compress dynamic range; enhancement recovers detail that signals 'professional listing.'
- Amazon's pure-white BG rule is strictly enforced. Check the corners of each main image for RGB 255/255/255 before upload.
Days 22-28: per-platform export from one master
Save one 4K master per SKU. Derive every platform-specific crop from that master rather than letting each platform auto-crop a single uploaded version. Per-platform crops from one master is worth 5-15% conversion lift on its own — manual crops respect the product geometry. Platform auto-crops often cut off important detail (the spout of a bottle, the embossed logo on the lid, the texture detail on the rim).
Platform spec quick reference. Amazon main image: 1600×1600 minimum, pure white BG, RGB. Amazon secondary images: 1200×1200 minimum, square or non-square, brand BG allowed. Shopify product images: 2048×2048 square. Shopify variants: same size as main; Shopify enforces aspect ratio across the gallery. Etsy: 2000×2000 minimum, square. Walmart: 2200×2200 minimum, white BG. TikTok Shop product card: 800×800 minimum, 1080×1080 recommended. eBay: 1600×1600 minimum. Google Merchant Center / Shopping ads: 800×800 minimum, transparent or white BG. Reels and Stories for paid social: 1080×1920 portrait.
Export each crop with the same filename pattern: {SKU}_{platform}_{slot}.webp. Example: SKU-1234_amazon_main.webp, SKU-1234_amazon_2.webp, SKU-1234_etsy_main.webp. The naming pattern matters for inventory tracking when you upload, and for the QA pass on day 30. WebP is preferred where the platform supports it (Amazon does. Etsy converts on upload. Shopify and Walmart accept it natively). Fall back to JPEG quality 90 where WebP isn't supported.
- Save one 4K master per SKU; derive every platform crop from it. Worth 5-15% conversion lift versus letting platforms auto-crop.
- Amazon 1600×1600 white BG; Shopify 2048×2048; Etsy 2000×2000; Walmart 2200×2200; TikTok Shop 1080×1080; eBay 1600×1600; Google Shopping 800×800.
- Filename pattern {SKU}_{platform}_{slot}.webp keeps QA tractable. WebP where supported, JPEG quality 90 fallback.
Days 29-30: A/B test setup and launch QA
Pick 2-3 SKUs where you'll run a measurable A/B test. The good candidates: SKUs with consistent baseline traffic (so the test reaches significance quickly), SKUs where the new photo is meaningfully different from the old one (so the test has something to measure). SKUs from your top 20% revenue list (so the lift, if positive, moves a real number). Amazon uses Manage Your Experiments for main-image tests. Shopify uses Shopify Experiments or third-party tools like ABconvert. Etsy doesn't support native A/B testing so the workflow is sequential: swap one variant on day 30, measure 14 days of pre-BF traffic at the new photo, compare to the prior 14 days of pre-BF traffic at the old photo.
Run the pre-launch QA on day 30. Verify all new photos are uploaded, indexed by each platform's search, and rendering at full resolution on a real mobile device. Not just the platform's desktop preview. The mobile preview is what most buyers actually see. A photo that looks crisp at 1600×1600 on desktop can render mushy at 480×480 on a phone. Compression artifacts, banding on gradients, soft edges on transparent BGs — these all show up on mobile preview first. Fix or re-export anything that fails the phone-screen test.
Launch-day-and-after monitoring. On Black Friday morning, set a 2-hour-cadence check on item-level CVR for each refreshed SKU against the 30-day pre-BF baseline. If a refreshed item is converting below baseline (rare but possible. Sometimes a 'better' photo de-emphasizes a buying cue the old photo had), roll back to the old photo within the 2-hour window. All major platforms allow photo swaps without resetting the listing's history or rank. This monitoring window also catches the rare case where a platform's image pipeline has reprocessed the upload in a way that degraded the photo. Re-uploading the original master usually fixes it.
- Pick 2-3 A/B test SKUs from your top-20% revenue list where the new photo is meaningfully different from the old.
- Pre-launch QA on day 30: verify every photo renders sharp at full resolution on a real mobile device, not just desktop preview.
- Launch-day 2-hour-cadence CVR check; roll back any refreshed item that's converting below pre-BF baseline within the 2-hour window.