Use cases

Product photography studio use cases

See how a product photo job changes when the client's destination is Amazon or Shopify, and how to keep requirements, product details, review decisions, and final files connected.

These guides are for studios. They do not replace Amazon Seller Central, Shopify, the client's current channel requirements, or the studio-client agreement.

Choose a use case

Channel guides

Start with where the client will use the files.

The studio still runs a product photo job. The destination changes the identifiers, image roles, source documents, output constraints, and final handoff that need to be recorded.

Amazon

Amazon product photography jobs

For studios serving sellers, brands, or agencies that need main and additional listing images tied to current Amazon requirements, product identifiers, image roles, client decisions, and an upload-ready handoff.

  • Current Seller Central source required
  • ASIN, SKU, or other product identifier mapping
  • Main and additional image roles
  • Upload method and delivery naming
  • Client approval does not guarantee Amazon display

The guide uses current Amazon US Seller Central references. Recheck the applicable marketplace, category, account, and upload method.

Read the Amazon studio guide

Shopify

Shopify product photography jobs

For studios serving merchants, DTC brands, or agencies that need product and variant images organized for a theme-dependent storefront, collection context, product media gallery, launch, or recurring content update.

  • Theme and placement context
  • Product handle, SKU, and variant mapping
  • Featured media and gallery roles
  • Aspect ratio and output by placement
  • Merchant or agency owns the Shopify upload

The guide uses current Shopify Help Center references. Recheck the merchant's theme, product setup, plan, apps, and upload path.

Read the Shopify studio guide

A client can use both channels. Build separate output rows when Amazon and Shopify need different crops, formats, names, or review decisions.

The studio record

The destination changes. The handoffs remain.

Whether the files are headed to Amazon, Shopify, or both, the studio still needs a current record of what was requested, what was produced, what the client decided, and what was released.

  • A current brief and source reference
  • One row for each product, relevant variant, and required output
  • The person authorized to confirm scope
  • The person authorized to approve final files
  • Proof versions and comments tied to the right asset
  • Requested changes separated from new scope
  • An explicit approval record
  • A final-file set and manifest the client can map to the destination
  • A studio-side record for a future repeat job

A repeat job begins with prior context, not with an assumption that the old requirement is still correct.

What these guides do not cover

They do not provide listing strategy, theme development, advertising advice, merchant account management, category approval, legal advice, or a guarantee of third-party acceptance.

They also do not make Lenso an Amazon or Shopify integration. The client or the client's agency remains responsible for the destination account and upload.

Amazon and Shopify are third-party services. Lenso is not affiliated with or endorsed by either company.

Build the source record first.

One connected client job

Lenso keeps the channel requirement attached to the work.

Lenso does not upload to Amazon or Shopify. It keeps a website request or studio-entered referral, product and shot details, proof versions, comments, requested changes, approval, optional invoice, and final files connected in one studio-controlled job.

Watch the 90-second workflowSee Lenso for studios