Back to studio guides

Studio operations

How Studios Build a Product Photography Shot List

How product studios turn intake, style rules, and channel packs into a countable shot list — so extra angles don't show up on set as unpaid work.

By Lenso Editorial

Published August 18, 2026

Diagram of intake, style, and channel inputs flowing into a locked grid of product photography shot-list rows

Tuesday, 9:40 a.m. The merch lead walks onto set with a phone full of Amazon listing screenshots. The sheet the client signed last week has twelve rows: product name, "packshot," white background. The photographer already lit for fronts.

Now they want a 45, a back, a detail, and the Amazon main-image crop. For every colorway. Not just the hero SKU.

Nobody is being difficult. The spreadsheet was never a production order. It was a mood.

A product photography shot list only earns the name if a second shooter, a retoucher, and a QC person can execute it without a meeting. If it still needs translation on set, it is a wish list with a filename.

The signed spreadsheet that still wasn't a production order

The failure usually starts earlier than Tuesday. Someone dumped a SKU list into a sheet, typed "standard packshots" in the angles column, and asked the client to reply "looks good." They did. That reply is not a lock. It is an agreement to stay vague.

On set, vague becomes expensive in a specific way. Lighting is already built for a front-on packshot. Samples for the navy colorway are on the table; the sage ones are still in the courier bag. Then the extra views arrive as a verbal add-on. The photographer can do them. The day cannot do them and still hit the delivery the studio quoted.

That is the whole job of a working list: turn "we need shots" into a countable set of rows before anyone meters a light.

What a working shot list actually is

A working shot list is a countable per-SKU production order: one row per variant, with every required view written in the angles column, specific enough that someone who missed the brief call can still set the shot. It is not a moodboard, not the project brief, and not a blank product photography shot list template sitting unsigned in Drive.

The template is the artifact. This post is the operating method: how the rows get there, who is allowed to change them, and what the list is for after the camera stops.

If a row cannot answer all of these without a Slack thread, it is not ready:

  • Which SKU and which colorway (one row each — never "SKU-001, all colors")
  • Which views are required, written as words a second shooter would not have to interpret
  • Background and styling that match the account's written rules, including what is forbidden
  • Retouching finish in plain language, not "clean it up"
  • Output crop and file name pattern for that row
If two people can read the same row and light two different shots, the list is still a conversation. Conversations do not survive SKU 40.

Assemble it from facts you already collected

Do not start from a blank grid. Start from the facts you already asked for. The list is a compilation step, not a second discovery call.

The client intake form should already have given you approximate SKU and variant counts, channels, sample timing, and a named approver. Per-SKU angles do not belong on that form. They belong here, once those facts exist.

The written style guide should already have locked background, fill ratio, hero angle set, lifestyle rules, and retouching limits for the account. The shot list does not reinvent those rules per SKU. It applies them, and calls out the rare SKU that is allowed to break them.

The project brief template holds project-level decisions: purpose, deliverable package, revision rules, delivery specs. The shot list is the per-SKU execution plan inside that brief. If the brief says Amazon plus Shopify and the list only has "packshot," the brief is lying to the calendar.

Copy those inputs into the sheet in this order: SKU list first, then required views per channel, then styling exceptions, then retouch and output. Do not draft angles from memory of last season unless last season's signed list is sitting next to you.

One product box multiplying into a grid of SKU rows, showing how variants expand a shot list

Count the rows before you book the day

"Forty products Tuesday" is a sales sentence. The day is priced in rows and in setup resets. Count both before you confirm the date.

  1. Rows equal SKUs times colorways. If a hoodie ships in four colors, that is four rows, even when the angles column is identical.
  2. Write every required view in the angles column. "Packshot" is not a view. Front, back, 45, detail, and any marketplace crop that needs a different frame are views.
  3. Treat a lighting or background change as a setup reset, even if it lives on the same row. A lifestyle scene is not free because it shares a SKU with the packshot.
  4. Channel extras are extra work. If Amazon needs a main-image treatment the Shopify PDP does not, that view has to appear as a required view — or you will invent it on set.

This is why multi-channel packages change the shot count. A studio that briefs one channel and derives the rest in export still has to capture the most demanding view on the day. A studio that forgets the second channel until delivery is not doing a crop. It is doing a reshoot.

Once the rows exist, check them against how many SKUs a day the studio can actually finish. Complexity class plus setup resets plus post load will tell you whether Tuesday is a yes, a split, or a no. The sheet is the input to that model. A hopeful calendar is not.

Lock it with the person who will reject the files

The person who emailed the SKU dump is often not the person who will bounce the delivery. Get the named approver — the same name you collected at intake — to confirm the completed list in writing before you book crew. The product photography workflow puts this in Step 2 for a reason: shot planning is a production gate, not a courtesy PDF.

What "confirmed" means in practice:

  • The approver has seen the actual rows, not a summary like "standard ecommerce coverage"
  • Colorways are listed, not implied
  • Views they will later call "obvious" are written down
  • Anything they still want to "figure out on the day" is either a paid discovery block or it is out

After that confirmation, the photographer's job is to execute the list, not to invent a better one. Taste improvisation is how you get beautiful frames the client did not buy and missing frames they did.

Run it on set as the only list in the room

Print it, pin it, or keep it on one shared screen. The merch lead's camera roll is not a second list. If a new view appears, it has to become a written row before anyone rebuilds the set.

Sequence by setup, not by whoever is holding a sample. Shoot every SKU that shares the packshot lighting before you break for lifestyle. Then do the views that need a reset. That is slower to explain in a kickoff and faster by lunch.

Keep a running mark on each row: captured, skipped, blocked (sample missing, damage, wrong colorway). A skipped row that nobody records becomes a QC surprise two days later, when the set is already struck.

If a sample is the wrong colorway, stop that row. Do not "get close" and hope retouching invents sage from navy.

When someone adds a shot after lock

They will. Treat it as a change to the production order, not as helpful energy.

Write the new row. Name the setup reset it causes. Decide, out loud, whether it fits the remaining day or it waits for a second block. If it is a new composition, a new SKU, or a new channel view, it is not a revision of an existing frame. It is new work.

A short clip of the same SKU is that kind of add. It is not another still angle. It needs its own scene, length, and aspect ratio. How a stills day holds that clip is in adding a product video to a stills shoot.

The polite version is simple: "We can do that. It is not on the signed list, so it is either a paid add or we schedule it." Then put it on the sheet so QC does not later treat the missing original rows as the studio's miss.

QC and next season start from the same list

After wrap, the first quality control pass is completeness against the rows. Did every SKU × colorway × required view actually come back? Mapping errors — the right photo on the wrong variant — are the expensive misses. The list is the map. Do not QC from memory of what you think you shot.

Keep the signed list with the project files the same way you keep finals. How studios organize product photography files is what makes a reorder take minutes: last season's rows are findable, so next season starts by copying the list and marking what changed (new colorway, dropped SKU, extra channel) instead of hosting another "what do you usually shoot?" call.

If you still need a blank grid to fill, use the product photography shot list template. If you need the list to stay attached to the brief, the approver, and the files after the shoot, look at a shared system your team can see — not as a magic shot-list product, as the place the signed rows do not get lost in someone's Downloads folder.

FAQ

How to create a photoshoot shot list?

For a product studio, you create it by compiling — not by brainstorming angles on a blank page. Pull the SKU and colorway list from intake, apply the account's style rules, add every view each sales channel actually requires, and write one row per variant. Then send that completed sheet to the named approver and do not book the day until they confirm the rows, not a vibe.

Is there a shot list template I can use?

Yes. Lenso publishes a free product photography shot list template with per-SKU columns for angles, styling, retouch, output specs, and naming, plus filled examples for apparel, beauty, and home goods. Copy the table, fill one row per colorway, and get the person who will approve finals to sign it before shoot day. A wedding or film shot-list template will not have those columns.

What are some good shots for product photography?

There is no universal "good shots" set that survives contact with a real catalog. The right views are the ones each channel and SKU actually need: a Shopify PDP package is not an Amazon main-image package, and a bottle is not a garment. Write those views as rows (or as an explicit angles column) instead of keeping a mental list of hero / detail / lifestyle. If a view is not on the signed list, it is either a paid add or it waits.

Who should fill out the product photography shot list — the studio or the client?

The studio should draft it. Clients know the products and the channels; they rarely know how to specify a view tightly enough for a second shooter. You take their SKU list and channel requirements, turn that into rows, and send it back for the named approver to confirm. If you hand a blank template to a merch intern and call that "client-filled," you will shoot their ambiguity.

When should a studio lock the shot list before shoot day?

Lock it after samples are expected to match the SKU list and before you confirm crew and the calendar. If samples are still in transit, you can draft rows, but you cannot honestly mark colorways complete. If the client is still "seeing how they feel on the day," you do not have a lock — you have a discovery shoot priced as a catalog day. Put a confirmation date on the proposal so the lock is a scheduled step, not a hope.

See the current product

See accepted scope become a working product content project.

After the studio's commercial and contract process, watch a request or studio-entered lead become a working brief and product rows the studio reviews before client access.

How Studios Build a Product Photography Shot List | Lenso