E-commerce Video Production: A Pipeline That Survives Volume

E-commerce video is not a smaller version of commercial production. It is throughput work, closer in character to a manufacturing process than to a film shoot, and it is judged on whether the two-hundredth product looks like the first.

That reframing changes what a good brief contains. The creative question — what should a product video look like — is answered once, at the start, and then defended. The operational questions, which are about batching, handling, naming and delivery, are the ones that determine whether the project actually works.

The Template Is the Deliverable

Before any product is filmed, one thing has to exist: a specification that any future product can be shot to.

That specification covers framing and how the product sits in the frame, the background and how it is lit, what motion is used and how long it lasts, the runtime, the aspect ratios, whether there is text or voice, and — critically — what happens when a product has different proportions from the ones used to design it. A template built around a rectangular box fails at the first tall bottle unless somebody has decided in advance how tall items are handled.

The cost of getting this wrong is not a bad video. It is a hundred videos that have to be remade, because consistency is the whole point and a catalogue with two templates in it looks like a mistake.

Designing for Later Products

The corollary is that the template should be designed for the catalogue that will exist, not the one that does. Categories that will be added, a possible second brand, a seasonal range: each of these either fits the system or forces a second one.

Where the template must be rebuildable months later by different people, the setup is documented at the time — light positions, distances, camera settings, lens, background material — in the same way a portrait library is documented. Rebuilding a look from a thumbnail does not work here either.

Batching Is the Throughput

The single largest gain available on a volume shoot is ordering the day by setup rather than by product.

Everything that shares a lighting and camera configuration is shot as one block, with products moving through it. The order will look arbitrary against the catalogue and that does not matter, because the files are reassembled by name afterwards.

Within that, three roles keep a batch moving. Somebody prepares and presents products so the next item is ready before the current one is finished. Somebody confirms each item has actually been captured against the list, since a missing product discovered a week later is a return visit. And somebody manages the files at ingest.

A shoot where the camera operator does all three runs at a fraction of the rate.

Product Handling Is a Real Job

Products arrive from stock, in varying condition, and frequently have to return in saleable condition.

The recurring practical points: items need cleaning and preparing before they are in front of a camera, because dust and fingerprints are visible and are fixed per-image in post if they are not fixed on set. Fragile, perishable or high-value items need a handling plan. And a checklist tracking what arrived, what was shot and what left prevents the two failure modes of a batch shoot, which are a product filmed twice and a product never filmed at all.

Naming Is Where Volume Projects Fail

Large batches rarely fail at the camera. They fail afterwards, when a folder of finished files cannot be matched to catalogue listings.

The fix is boring and effective: a naming convention agreed before the shoot, tied to the identifiers the catalogue actually uses, applied at ingest rather than at delivery, and carried through every export. If the product management system uses a particular code, the video files use that code.

Delivery follows the same principle. A folder of files named for their listings, in the formats the platform requires, can be published by someone who was not at the shoot. A folder named by the camera’s own numbering cannot.

Platform Specifications Are Published

Each destination — a retailer’s own product page, a marketplace listing, a paid social placement, a shopping feed — has its own requirements, and the platforms publish them.

The variables are consistent: aspect ratio, maximum and minimum duration, file size and encoding, whether sound plays by default, and whether the first frame is the still thumbnail. That last one is worth naming, because a video whose first frame is a blank background produces a listing with a blank thumbnail.

The practical consequence for the shoot is that the framing must accommodate the crops the destinations require. A product framed tightly for a square listing has nothing left when the same file is cropped vertically, so the safe area for every intended crop is decided before shooting rather than in the export.

What Sets the Cost

Product count first, then how many setups those products require, because setups consume the day and products do not. Then the complexity of the template — a static presentation, a turntable rotation, a demonstration of use and a fully art-directed treatment are four different rates of throughput. Then post- production per item, which is where a large catalogue’s cost really sits. Then the number of platform versions per product. Then handling, if items are fragile, perishable or valuable.

This page states no prices. The checkable references are the published media specifications of the destination platforms. What is comparable across quotes is products per day, setup count, template complexity, per-product post-production, version count per product and the delivery and naming arrangement. A quote naming those can be read against another; a single figure cannot.