Quick Answer

To refresh an outdated product catalog without reshooting every SKU, audit what you already have, build a Photography Style from the strongest references, choose consistent Framing or Pose, and save the Product Photography direction as a Recipe. Reuse it for new scenes, use Edit separately for colorways, and upscale accurate low-resolution originals. Nightjar keeps that direction available to the Team, so each product does not need a fresh brief, and from an AI assistant it can apply the Recipe to up to 100 Products in one batch after you approve a sample.

Why "Refresh" Looks Like "Reshoot" (and Why It Doesn't Have To)

Catalogs collect visual debt the same way codebases collect technical debt. An early shoot on warm-white seamless. A freelancer's work two seasons later under different lighting. A phone-shot SKU added during a launch crunch. A colorway that was never photographed at all. A dozen legacy listings still living at 800 pixels because that was once enough for the site theme.

A full replacement can be expensive, but budget from the actual gaps, not the size of the catalog alone. As an illustrative calculation, 200 SKUs × six new images × $50 per image is $60,000. A studio quote may already include styling, retouching and delivery: Razor Creative Labs' pricing guide explicitly lists those inclusions. Do not automatically multiply a quote by two or three for them again. Squareshot currently advertises delivery in eight business days or less after payment, with product delivery and proposal approval before that clock starts; it is one provider's offer, not a universal studio timeline.

Catalog data and catalog imagery need different checks. A PIM such as Catsy can help organize product information; an image review must also decide which old photos still represent the product and belong together on the grid. Editing tools can handle several of the refresh steps. The question is whether the operator can reuse approved direction and trace each new image back to an adequate source.

For the visual refresh, the useful shift is to treat direction as reusable: define the look once, save it, and apply it to the next product. Creative judgment establishes the direction; repeatable operations carry it through the catalog. The bottleneck is not just making each image prettier. It is making 200 images belong to one brand without changing what those products are.

What an Outdated Catalog Actually Costs You

The strongest reason to refresh is a specific buying question that the old images no longer answer.

Salsify's 2025 survey of 1,910 shoppers found that 77% rated product images and videos very or extremely important to completing a purchase, while 42% cited missing or low-quality imagery as a reason they had abandoned a purchase. Those are reported attitudes and experiences, not a measured conversion lift from refreshing a catalog.

Use that distinction to prioritize. An outdated label, an absent back view, or a tiny image that conceals a closure is a concrete gap. A photo is not automatically ineffective because it was made three years ago. Keep accurate, useful originals and spend on the gaps a shopper can actually notice.

The Five-Step Catalog Refresh Workflow

The workflow has five steps, in order. Skipping the first two and jumping straight to "generate variants" is the mistake that turns a refresh into more visual drift.

1. Audit the catalog.
2. Build a unified Photography Style and choose Framing or Pose.
3. Save the Recipe.
4. Generate the missing variants.
5. Upscale legacy images.

Step 1. Audit the Catalog

Sort existing Assets into three buckets: anchor (good enough to define the refreshed look), keep-with-upscale (right framing, low resolution), and replace (background, lighting, or framing too far off to salvage).

Review by SKU and gallery role, using filenames or your catalog records to maintain the product match. Nightjar's Library semantic search can also surface Assets by content: a query like "white background bottle" or "outdoor lifestyle bag" helps find visual references. Shortlist the strongest anchor Assets, then choose the relevant references when creating a Photography Style.

Step 2. Build a Unified Photography Style and Choose Framing or Pose

A Photography Style controls camera feel, lighting, color scheme, mood, texture, and atmosphere. Framing sets the view and staging for product-only shots. On-model shots instead use Pose for body arrangement and Camera Distance for the crop. These are separate controls because they fail in different ways: lighting drift is not the same problem as pose drift.

Build a custom Photography Style from the anchor Assets so the refreshed catalog inherits the brand's strongest existing visual language rather than a generic AI default. Pick a consistent Framing for product-only shots and a reusable Pose for on-model shots, so the shot structure stays consistent across SKUs. For a deeper walkthrough of how to extract a brand's visual DNA into a Photography Style, see Photography Styles: build a consistent brand aesthetic with AI.

Step 3. Save the Recipe

A Product Photography Recipe saves reusable direction and settings: Photography Style, Framing or Pose, optional Fashion Model, Background, Custom Directions, image count, aspect ratio, resolution and format. Apply the Recipe, choose the next Product and supporting photos, then confirm the output settings.

A Recipe makes the intended look repeatable. Team-shared Recipes let the founder or art director define direction once and let other Team members apply it without reconstructing the brief. Review a few representative SKUs together before extending that direction to the rest.

Step 4. Generate the Missing Variants

Once the Recipe exists, the per-SKU work is bounded. The variants you need typically fall into five buckets:

• Lifestyle and seasonal scenes: apply the Recipe, then deliberately change Background or Custom Directions for the new scene.
• On-model imagery: reuse a Fashion Model and Pose to carry the intended identity and body arrangement across apparel and accessory SKUs.
• Colorways: use Recolor or /color in Edit separately. See One photo, every color.
• PDP gallery expansion: choose Photoshoot in Product Photography for four coordinated outputs. Supply photos that show the details the new views need.
• Channel variants: change the aspect ratio for the destination, then review the crop. Common briefs include square grids, 4:5 feed images, 9:16 vertical placements and 16:9 banners.

Keep the approved Recipe as the baseline for Product Photography, and compare separate Edit outputs with that baseline before adding them to the same PDP.

Run the Recipe across many Products as an assistant batch

In the web app, you apply the Recipe and generate one Product at a time. When dozens of Products need the same refreshed look, run the Recipe as a batch from an AI assistant instead: the job changes from repeating the form to reviewing one plan. Nightjar connects to Claude (on the web, the desktop app, Cowork and mobile, as a custom connector), Claude Code and Codex through MCP, the open standard AI assistants use to connect to other tools. You sign in to your Nightjar Team; there is no API key, and connecting is free. Then ask in plain language, for example: "Apply our Refresh Recipe to the 60 Products in this list. Show me samples of the glass bottle, the tote and the navy jacket first." Name the Products, or let the assistant match them from your saved list.

• Plan. Planning is free. The plan lists the Products, settings, image counts and total Credit cost, with a spending ceiling for the run.
• Sample. Up to five items run first. This is the representative-SKU review from Step 3: compare those images with the real products while most of the Credits are still unspent, and ask for a revised plan if the direction doesn't hold.
• Rest. After you approve the sample, the remaining Products run, one Generation per Product, and keep running after you close the chat. Any new conversation can find the batch and pause, resume or stop it; pausing releases the Credits held for unstarted items.
• Size. A batch holds 1 to 100 items. It can also list different work per item, such as Upscale for the keep-with-upscale bucket from your audit.

Batch images use your Team's normal Credits at web-app prices and land in the Library under each Product. Making product photos in Claude shows the conversation, and the Nightjar MCP guide has setup steps and current limits. Unlike images generated in a chat on their own, each result starts from the saved Product's photos and facts and follows the approved Recipe, which helps keep a large refresh from becoming a new source of drift.

Step 5. Upscale Legacy Images

Shopify recommends 2,048 × 2,048 pixels for square product images, and its image-size guide says zoom needs images larger than 800 × 800. Amazon's seller guidance specifies 1,000 pixels on the longest side for zoom and 1,600 or more as optimal. An 800-pixel image and a 1,200-pixel image therefore do not have the same problem. Check actual dimensions and storefront display before replacing either.

Run Upscale where the source is accurate but too small. Its targets are 2K (2,048 pixels long edge) and 4K (4,096 pixels long edge), skipping work where the source already meets the target. These long-edge targets are distinct from generation resolution tiers. Inspect labels, edges and fine texture afterward.

How the Refresh Looks Across Different Tool Categories

No single category handles every step well. The honest comparison maps each refresh step against the four credible approaches, so an operator can see at a glance where each one earns its place.

Choose by the gap, not by the label "AI." Nightjar is especially relevant when the existing photos are adequate but the team repeatedly rebuilds product-specific direction: the saved Recipe carries the brief while each selected Product supplies the subject evidence.

What Makes a Catalog Refresh Repeatable Instead of Endless

Nightjar's useful contribution here is separating the subject from the reusable direction. A refresh becomes easier to repeat when the next operator can select both explicitly.

The Product supplies the source photos; Photography Style, Framing or Pose, Background and Custom Directions define the intended image. A Recipe saves that direction for the next SKU. Photoshoot offers four coordinated outputs when the gallery needs expansion; separate Edit and Upscale tools address colorway and resolution gaps. The Library keeps originals and reviewed outputs available for later work.

Photography Styles, Poses, Fashion Models, Backgrounds and Recipes are shared within the Team. That matters when the art director approves the look but someone else handles next month's additions: they can select the same ingredients instead of translating a screenshot into a new prompt. It reduces rebriefing.

A worked example: 80 SKUs with one image and 120 with three have 440 existing images. Reaching five per SKU means 1,000 total, so the gap is 560 if all 440 originals remain useful. At a hypothetical $50 for each new image, filling that gap would cost $28,000 before any separately quoted extras; replacing all 1,000 would be a different $50,000 project. In Nightjar, first classify which gaps are new scenes, recolors or missing factual views. Reuse the approved Recipe for the scenes, edit supported colorways separately, and commission any missing source photography.

For more on the cost side, the real cost of product photography: a breakdown walks through the full math, and can a Shopify brand replace a $10k photography budget entirely with AI covers the budget question directly. For brands tying refreshes to launches, how much does AI product photography reduce the time-to-market for new product drops is the relevant deep dive.

Photograph Changed Products Before Refreshing Them

When the physical product itself has changed, photograph the new version first and add those photos to its Product, so every refreshed image starts from the current item. Keep a real photograph wherever regulated label text must appear exactly as approved. From there, the AI refresh covers routine catalog production, variant coverage, lifestyle context, and resolution upgrades.

Frequently Asked Questions

How can I update old product photos without reshooting them? Audit the catalog, build a Photography Style from strong references, choose Framing or Pose and save the Product Photography direction as a Recipe. Use that setup for new scenes, Edit separately for recolors, and Upscale for accurate but small originals. Reshoot where the source cannot show the current product accurately.

Can AI make my product catalog look consistent if it was shot at different times? It can help. In Nightjar, saved Photography Styles and Recipes let you reapply approved direction to different Product sources. Compare the results together: saved settings reduce drift across the catalog.

What is the cheapest way to refresh an ecommerce product catalog? Start by keeping useful images. Then compare the cost of editing, generating and photographing only the actual gaps, including review and revisions. A full reshoot and a gap-filling refresh are different scopes; ask studios what their quotes already include.

How do I fix mismatched backgrounds across product listings? For Product Photography, choose a Background and Photography Style, save the setup as a Recipe and apply it to each Product.

Can I generate lifestyle and seasonal images from existing packshots? Yes, when the source adequately shows the product. Apply a Recipe and change Background or Custom Directions for the scene; choose Photoshoot for four coordinated outputs. Supply additional real views for any angle the packshot does not show.

How long does a full catalog refresh take with AI vs a traditional reshoot? A physical shoot includes booking, product delivery, photography and approval. Squareshot currently advertises eight business days or less after payment. An AI refresh can avoid the new shoot where sources are adequate, so its time goes to auditing, setup and review.

Will AI-refreshed images still look like the real product? Product photos guide the generation, so each result starts from the saved Product's photos and facts. Check shape, labels, color, materials and scale against the originals.

Do I need to refresh every SKU at once? No. Save the approved direction, then work incrementally, prioritizing top sellers and the most consequential image gaps. Reuse the Recipe on later products and compare new outputs with the approved reference set. From an AI assistant, each priority group can run as its own batch with its own sample.

Will an AI catalog refresh meet Shopify and Amazon image requirements? Check the finished file and the destination's rules. Generation tiers are not an exact pixel-size guarantee; Upscale targets a long edge, not necessarily a square. Background, product fill, accuracy, overlays and category-specific requirements matter as well as resolution.

References

• Nightjar - Product Photography, Recipes, Edit and Upscale.
• Razor Creative Labs: Photography pricing - Provider guidance on quote inclusions.
• Squareshot: Ecommerce photography - Current provider process and advertised turnaround.
• Shopify: Product media types - Product image specifications.
• Shopify: Image sizes - Zoom guidance.
• Amazon: Product photography standards - Seller guidance on dimensions and main-image rules.
• Salsify: 2025 Consumer Research - Shopper-reported importance and abandonment factors.
• Photoroom - Broader editing and brand-workflow alternative.
• Catsy - PIM and catalog management.