Multi-channel product photography does not mean that one photograph will satisfy every destination.
It means the studio identifies:
- What can share one capture
- What needs another composition or setup
- What can be derived after approval
- What needs a separate final file
- Which current source controls each output
A client's product page, Amazon listing, Shopify theme, Google Merchant Center feed, retailer portal, paid social placement, and print use can require different creative and technical decisions.
Start with the actual committed destinations.
Do not promise a future channel package based only on what the client might use later.
Separate capture decisions from export decisions
Some differences can be created after capture.
Examples can include:
- crop;
- resize;
- compression;
- file format;
- filename;
- alternate color profile under a current requirement;
- metadata;
- destination suffix.
Other differences can require another capture or composition.
Examples can include:
- background;
- prop or model;
- included product quantity;
- product orientation;
- visible packaging;
- required detail;
- lifestyle scene;
- aspect ratio that changes composition;
- product placement;
- channel-specific asset role.
The current destination source and client direction control the decision.
Do not assume that a larger master solves every creative difference.
Use a destination matrix
Create one row for each required destination output.
Suggested columns:
- Product or SKU
- Variant
- Destination
- Region or store context
- Asset role
- Required view
- Creative treatment
- Background or environment
- Crop or composition
- Technical output
- Current official or client source
- Source review date
- Shared capture or separate capture
- Approved source or master
- Delivery filename
- Upload owner
- Accepted exception
The matrix belongs beside the current shot list.
It does not replace the shot list.
Start with the client-owned destination
For a client-owned site, record:
- Current site or theme
- Product template
- Media placement
- Featured or gallery role
- Crop behavior
- Mobile behavior
- Current file requirement
- Alt-text owner
- Upload owner
The exact display can depend on the theme, component, app, and template.
Do not describe Shopify itself as one fixed crop or image package.
Amazon requires role and marketplace context
Amazon distinguishes the main image from additional images and can apply marketplace, category, and product-type rules.
Record:
- Marketplace and region
- Product identifier
- Main or additional role
- Current official source
- Product category
- Expected upload method
- Client upload owner
- Accepted exception
Lenso does not upload to Seller Central or guarantee display.
Use the current Amazon studio guide for detailed source handling.
Shopify display depends on the current store context
Shopify supports product images and other media types.
The exact storefront display depends on the current theme and implementation.
Record:
- Store
- Theme or product template
- Product and variant mapping
- Featured media
- Gallery placement
- Crop and focal behavior
- Output
- Alt-text owner
- Upload owner
Lenso does not edit the theme or upload the media.
Use the current Shopify studio guide.
Google Merchant Center uses feed image roles
Google Merchant Center distinguishes a main image link from additional image links and applies current product-data and image requirements.
Record:
- Merchant or feed context
- Product ID
- Main or additional role
- Variant mapping
- Image URL owner
- Current official source
- Review date
- Feed owner
Google can announce future requirement changes.
Do not copy a future effective date into a long-lived article without a scheduled review.
Decide whether one capture can be shared
A capture can be shared when the destinations agree on the required:
- Product and variant
- Visible quantity
- Included items
- Orientation
- Background or environment
- Composition
- Product detail
- Creative treatment
- Product truth
- Resolution and framing needed for the derivatives
A shared capture still can produce several separate final files.
A separate capture is appropriate when a destination needs a materially different creative or factual representation.
Do not force one setup to serve every channel.
Do not use the strictest channel as the universal direction
A strict main-image rule can define one destination output.
It should not automatically define the client's hero image, lifestyle media, paid social, email, print, another marketplace, or the account style guide.
Use one reusable brand baseline where practical.
Record destination exceptions separately.
Plan current and committed destinations
Ask:
- Which destinations are in the current job?
- Which destination is confirmed next?
- Which outputs are required now?
- Which future destination is only a possibility?
- Who owns current official-source review?
- Who uploads each output?
A possible future destination can influence master capture when the client approves that additional scope.
It is not automatically part of the current deliverable.
Build shared capture groups
A shared capture group records:
- Products covered
- Destinations covered
- Creative treatment
- Source or master
- Required resolution and composition
- Derived outputs
- Separate outputs still required
- Approval owner
Do not call the source `universal master`.
Use:
Approved source for the listed outputs
Each derived output in that group still needs its own row — see the product photography shot list guide for how to expand one capture into the required outputs without losing track of any of them.
Illustrative destination matrix
Product: Serum 30 ml · Destination: Client Shopify store · Asset role: Featured product media · Creative treatment: Current account guide · Shared or separate: Shared capture group A · Final output: Client-approved square image
Product: Serum 30 ml · Destination: Client Shopify store · Asset role: Detail gallery media · Creative treatment: Dropper detail · Shared or separate: Separate detail capture · Final output: Client-approved gallery image
Product: Serum 30 ml · Destination: Amazon US · Asset role: Main image · Creative treatment: Current official main-image rule · Shared or separate: Separate main-image setup · Final output: Amazon handoff file
Product: Serum 30 ml · Destination: Amazon US · Asset role: Additional image · Creative treatment: Approved product detail · Shared or separate: Shared capture group A where the current rule permits · Final output: Amazon additional-image file
Product: Serum 30 ml · Destination: Google Merchant Center · Asset role: Main image link · Creative treatment: Feed owner confirms current rule · Shared or separate: Shared with approved source where the current rule permits · Final output: Feed image URL asset
The values are illustrative.
They are not current technical specifications.
Review every official source before production and delivery
Record:
- Source title
- Official URL
- Region
- Category or context
- Reviewed date
- Reviewer
- Material requirement
- Known future change
Review again when:
- a job begins after the source-review date;
- a client changes category or region;
- a platform announces a future requirement;
- upload behavior changes;
- the output is rejected;
- the article is substantively updated.
Keep upload ownership visible
The studio can deliver channel-ready files without owning the destination upload.
Record:
- Studio delivery owner
- Client upload owner
- Agency or developer upload owner
- Feed owner
- Accepted handoff format
Lenso does not currently upload directly to Amazon, Shopify, Google Merchant Center, a PIM, FTP, or S3 destination.
Use a manifest for the channel handoff
The manifest can identify:
- Product or SKU
- Variant
- Destination
- Asset role
- Delivery filename
- Output
- Current source
- Status
- Secure link
- Upload owner
- Accepted exception
Do not rely on a ZIP filename alone to explain the destination package.
Copyable multi-channel planning record
- JOB
- Client:
- Job:
- Current style guide:
- Current brief:
- Current shot list:
- Decision maker:
- DESTINATIONS
- Destination:
- Region or store:
- Product category or template:
- Committed in this job:
- Possible future use:
- SOURCE
- Official or client source:
- URL:
- Reviewed date:
- Reviewer:
- Known future change:
- OUTPUT
- Product or SKU:
- Variant:
- Asset role:
- Required view:
- Creative treatment:
- Background or environment:
- Crop or composition:
- Technical output:
- Delivery filename:
- Upload owner:
- CAPTURE DECISION
- Shared capture group:
- Separate capture required:
- Reason:
- Approved source or master:
- Derived outputs:
- HANDOFF
- Files:
- Manifest:
- Recipient:
- Upload owner:
- Accepted exception:
- Actual upload or display result:
How this fits in Lenso
Lenso can keep destination requirements attached to product and shot rows, proof decisions, final files, and a delivery manifest.
Lenso does not monitor every channel rule, upload the files, edit a Shopify theme, manage a Merchant Center feed, or guarantee Amazon display.
The studio and client remain responsible for the current destination requirement and upload.
Questions
Can one shoot serve several channels?
Sometimes. It depends on whether the destinations share the required creative and product representation.
Should the studio shoot for every possible future channel?
Only when the client approves the additional planning and capture scope.
Should Amazon define every product image?
No. Its current main-image requirement applies to a specific destination role.
Can one approved source create several files?
Yes, when the creative and technical requirements permit it.
Does Lenso upload to the channels?
No.