Ask a merchandising team why a product launched without images and you will get a story about the photographer. Ask the photographer and you will hear that the images were delivered three weeks ago. Both are telling the truth, and the gap between them is where the work actually stalls.
Short answer: map the pipeline as a sequence of handoffs and measure the wait between each pair, not the duration of each step. In almost every catalogue operation the bottleneck is a single queue, usually retouching approval or metadata entry, and it is invisible because everyone is measuring their own step and reporting it as fast.
The seven handoffs
Written out, a typical pipeline for one product looks like this. Yours will differ in the details and not in the shape.
- Sample arrives. Someone books it in, and it either gets a shoot slot or waits for one.
- Shoot. Frames are captured against a known setup, ideally the same setup as last season.
- Ingest. Raw files land somewhere, are backed up, and get a first identifier.
- Selection. Someone picks the frames that will be used. This is fast and is nearly always waiting on someone senior.
- Retouch. Cleanup, colour, background. This is slow and is often outsourced, which adds a round trip.
- Approval. Brand or merchandising signs off. This is the queue.
- Catalogue. Metadata entered, asset associated with a product record, published.
Between each pair there is a wait. The sum of the waits usually exceeds the sum of the work by a factor of three or more, which is why hiring another retoucher rarely helps.
Measure the waits, not the steps
Instrument this crudely before you buy anything. For fifty recent products, record one timestamp per handoff. You do not need a system for this; a shared sheet for two weeks is enough to find the answer.
Two numbers matter. Touch time is the total of the work itself. Lead time is the wall clock from sample arrival to published. The ratio between them tells you where you are. A well-run operation is somewhere around one to four. Most are one to fifteen, and everyone in the chain is genuinely busy.
Then look at the single largest gap. It is nearly always one of three: samples waiting for a shoot slot, retouched files waiting for approval, or finished files waiting for someone to type metadata. Each has a different fix, and buying a platform is only the fix for the third one.
Capture metadata at the point it is known
The metadata queue is self-inflicted and it is the easiest of the three to remove.
Most of what ends up being typed later was known at shoot time. Which product this is. Which angle. Which season and campaign. Who shot it. The set it belongs to. Typing it a week later, from a filename, by someone who was not there, is both slower and less accurate.
The mechanics are unglamorous and they work:
- Shoot into a named structure. A directory per SKU, or a capture template that writes the SKU into the file’s metadata at capture. IPTC photo metadata fields are written by most capture and editing software and survive most exports, and ExifTool will tell you whether yours survived.
- Use the shot list as the data source. The list already contains the SKU, the angle and the required frames. It is a manifest. Ingesting against it means the association is made by matching, not by typing.
- Let automatic extraction do the mechanical fields. Dimensions, format, capture date and camera settings should never be entered by a person. Subject tagging can be proposed automatically as well, which is useful for search recall and should not be trusted for approval state or rights.
- Enter judgement fields once, deliberately. Approval, rights, and the default description are the fields worth a human. Everything else should arrive by itself.
Stop producing crops as a pipeline step
Steps five and seven in most pipelines include producing the six or eight sizes each channel needs. That work is real, it is repeated per asset, and it produces files that go stale independently of the master.
It is also avoidable. If renditions are derived from the master on request, the pipeline ends at the approved master and the channels take what they need. That removes a step, removes a storage problem, and removes the class of bug where a product page updates and the marketplace listing does not.
This is the operational reason to prefer a delivery layer that transforms by URL rather than a folder of exports. The transformation model turns eight export tasks into eight parameter strings, and the mechanics of that are in what a DAM actually does.
The approval queue
This is the hardest one, because it is a people problem wearing a process costume.
Three things reliably shorten it:
Approve sets, not files. A reviewer looking at four hundred individual images will batch them mentally anyway, badly. Present the shoot as a set with a contact sheet and let approval happen at set level, with exceptions flagged individually.
Define what approval means. Half of all approval delay is a reviewer who is not sure whether they are checking brand compliance, retouching quality, or product accuracy. Write down which, and route each to the person who can answer it. Three fast reviews in parallel beat one slow one that covers everything.
Give it a deadline that has a default. Unreviewed after five working days means approved, or means escalated, but it has to mean something. A queue with no timeout is not a queue, it is a place things go.
What should you fix first?
In this order, because the earlier ones make the later ones cheaper.
- The metadata queue, by capturing at the point of knowledge. Cheapest fix, fastest payback, no purchase required.
- The crop step, by deriving renditions instead of producing them. One integration change, and it removes work permanently.
- The approval queue, by changing what approval means and who does it. Free, slow, and political.
- The shoot slot, which is usually a capacity question and the only one that costs money. Product photography without a studio backlog covers the ways to add throughput without adding a studio.
Do not start by buying a workflow tool. A tool imposed on an unmeasured pipeline formalises the queue rather than removing it. Once the shape is known, the wider operating model, including who owns which step and what happens at seasonal peak, is in running product content as an operation. The launch-day version of the same checklist is in the catalogue launch checklist.