For studios serving Amazon sellers
Keep Amazon product photography requirements attached to the client job.
Use a current Amazon source, record the product identifier and image role for each required file, confirm who approves the set, and deliver a handoff the client can map to the right listing.
Lenso is not an Amazon app. It does not upload to Seller Central, monitor every category rule, or guarantee that Amazon will display an image.
Official Amazon US sources last reviewed: August 20, 2026. Recheck the marketplace, category, account, and upload method before each job.
Use this guide when the studio owns the image handoff, not the Amazon account.
The studio can record the client's current Amazon requirements, prepare the named image outputs, collect review decisions, and deliver files that are easier to map to the correct products.
The seller, brand, agency, or account operator remains responsible for the Amazon account, listing setup, upload, category rules, and final publication.
- Multi-product or multi-variation jobs
- Main and additional listing images
- Clients using Seller Central image roles or bulk upload
- Brands with several reviewers
- Refreshes caused by new packaging, products, or variants
- Studios that need a product-to-file manifest
Amazon adds a source and identifier layer to the normal studio job.
The creative work is still product photography. The added operational requirement is that every final file must be traceable to the current product identifier, image role, source requirement, client decision, and upload method.
- Current source
- Record the official Seller Central page, region, category, and review date used for the job.
- Product identity
- Record the client SKU and any ASIN, UPC, GTIN, ISBN, EAN, JAN, or other identifier needed for the handoff.
- Image role
- Separate the main image from additional angles, details, lifestyle images, swatches, safety images, or another current Amazon image role.
- Upload method
- Ask whether the client will use legacy bulk file naming, assign images in Seller Central, use an inventory feed, or use another current method.
- Decision owners
- Identify who confirms the current scope, who approves the final files, and who performs the upload. Those roles may belong to different people.
- Display boundary
- A correct studio handoff does not guarantee that Amazon will select or display a submitted image.
Record the Amazon context before production begins.
Do not turn an unanswered listing question into a studio assumption.
- Amazon marketplace and region
- Seller account or brand context relevant to the job
- Product title used by the client
- Client SKU
- ASIN or other product identifier, if assigned
- Parent and child relationship, when it affects the output
- Variant or variation value
- Current category or style-guide source
- Image role for each required file
- Required view or asset
- Product truth and included accessories
- Background and composition requirement
- Technical output requirement
- Expected upload method
- Expected delivery filename or assignment field
- Client scope decision maker
- Final image decision maker
- Seller Central upload owner
- Review deadline
- Launch or handoff deadline
- Accepted exception process
The studio is ready when every required output can be mapped to a product, image role, current source, decision owner, and final handoff.
Use current Amazon US sources, then check the category.
The summary below is a source note, not a substitute for Seller Central. Amazon can change requirements, add category rules, select images from several contributors, and decline to display an uploaded image.
Product Image Guide
Reviewed August 20, 2026
At the last review, Amazon US required at least one compliant main image for each product. The technical guide listed JPEG as recommended, with TIFF, PNG, and non-animated GIF also supported, and a longest-side range from 500 to 10,000 pixels.
The main-image rules included an accurate product representation, pure white background with RGB values 255, 255, 255, about 85 percent product fill, no text, logos, borders, color blocks, or watermarks, and no unrelated props or accessories.
Category and product-type rules can add or change requirements.
Image Variants
Reviewed August 20, 2026
Amazon distinguishes the main image from additional image variants. Current codes include MAIN, PT01 through PT99, angle codes, swatch, safety, ingredient, and other role-specific values. The codes available to a seller can depend on the product and category.
Upload Images
Reviewed August 20, 2026
Amazon currently supports more than one upload path. Legacy bulk naming can use a product identifier, image variant code, and extension, such as a product ID followed by MAIN. Other Seller Central tools can accept a file with another name and assign it to a product during or after upload.
Uploading an image does not guarantee that it will be displayed.
Verify these pages again before using the facts for a current job. If a source is unavailable, do not replace it with a third-party article and present the result as Amazon policy.
Amazon is a third-party service. Lenso is not affiliated with or endorsed by Amazon.
Map each required file to one product and one image role.
This fictional example demonstrates record structure. The output values are not universal Amazon requirements.
| Client SKU | ASIN or product ID | Variant | Image role | View or asset | Official source | Output | Expected handoff name | Decision owner |
|---|---|---|---|---|---|---|---|---|
| SERUM-30-CLR | [ASIN when assigned] | Clear / 30 ml | Main | Front label | Amazon US Product Image Guide, reviewed August 20, 2026 | Client-approved 3000 x 3000 JPEG | [PRODUCT-ID].MAIN.jpg for legacy bulk upload, if that is the chosen method | Client commerce lead |
| SERUM-30-CLR | [ASIN when assigned] | Clear / 30 ml | Additional | 45-degree bottle view | Current category and image-role source | Client-approved 3000 x 3000 JPEG | [PRODUCT-ID].PT01.jpg for legacy bulk upload, if that is the chosen method | Client commerce lead |
| SERUM-30-CLR | [ASIN when assigned] | Clear / 30 ml | Additional | Dropper detail | Current category and image-role source | Client-approved 3000 x 3000 JPEG | [PRODUCT-ID].PT02.jpg for legacy bulk upload, if that is the chosen method | Client commerce lead |
Do not invent an ASIN. Use the client's current identifier and upload method. A Seller SKU or other identifier can be the working key before an ASIN exists.
Separate studio review, client approval, and Amazon acceptance.
These are three different decisions.
- Studio review
- The studio checks the file against the current shot row, approved reference, product truth, technical output, and named Amazon source.
- Client approval
- The authorized client reviewer records a decision for the named proof, version, or set.
- Amazon acceptance
- Amazon determines whether the uploaded image is accepted, selected, or displayed in the destination account.
- The proof identifies the client SKU or product ID.
- The proof identifies the image role.
- The proof or set has a visible version.
- Comments stay attached to the correct file or set.
- A question is not treated as a requested change.
- A requested change names the expected result.
- New scope is separated from a correction.
- The client records Request changes or Approve for the current version.
- Accepted exceptions are named and attached to the affected file.
The client agreement defines the legal effect of approval, silence, delivery, and acceptance. Lenso records the operational decision.
Prepare the handoff for the upload method the client will actually use.
- Record who performs the Seller Central upload.
- Record the selected upload method.
- Use the current naming rule for that method.
- Map every file to the client SKU and Amazon product identifier.
- Map every file to the intended image role or variant code.
- Include a delivery manifest when the set is not self-explanatory.
- Test the actual ZIP, folder, link, and manifest.
- Exclude working files, obsolete proofs, and protected previews.
- Record what was delivered, to whom, and when.
- Tell the client when secure access can expire or be revoked.
A studio can use one internal source name, one review-version name, and another client-facing delivery name when the mapping remains reliable.
Lenso can deliver the final files and manifest. It does not perform the Seller Central upload.
Use the prior job as a starting point, not as current policy.
Packaging, products, variants, category rules, image roles, upload tools, and client decision makers can change.
For a repeat job, review the old brief, shot rows, references, accepted exceptions, delivery names, and final set. Then verify the current official source before reusing them.
- Record what changed.
- Record what remains valid.
- Create new rows for new products or image roles.
- Version any material requirement change.
- Keep the new approval attached to the new job.
Repeat work is studio initiated. The client area is not a self-service Amazon reorder system.
Keep the Amazon source beside the product and client decision.
Lenso can keep a website request or studio-entered referral, structured brief, SKU and shot rows, references, proof versions, comments, requested changes, approval history, optional invoice, manifest, and final files attached to the same job.
- The studio reviews every request before it becomes a job.
- Clients use project-specific Lenso-hosted access.
- Clients do not need a paid studio seat.
- Secure links can expire or be revoked.
- Source storage names can differ from client-facing delivery names.
- Repeat work begins with a studio-created job.
What Lenso does not do for Amazon
- Upload images to Seller Central
- Create or manage listings
- Choose a category
- Manage FBA or FBM operations
- Run Amazon advertising
- Write listing SEO
- Create A+ Content strategy
- Monitor every regional or category rule
- Certify image compliance
- Guarantee upload acceptance
- Guarantee listing display
- Resolve seller-account enforcement
Questions about Amazon jobs in Lenso
Does Lenso upload images directly to Amazon?
No. Lenso manages the studio-to-client job record and final-file handoff. The seller, brand, agency, or account operator uploads the files to Amazon.
Does Lenso guarantee that Amazon will accept or display an image?
No. The studio and client can check a file against the current official source, but Amazon controls acceptance, selection, and display.
Should the studio use an ASIN, seller SKU, UPC, or another identifier?
Use the identifier the client and upload method require. Record the client SKU and any Amazon product identifier needed for the final handoff. Do not invent an ASIN before one exists.
Does every file need the legacy Amazon bulk-upload name?
No. Legacy bulk upload uses a product identifier, variant code, and extension. Other Seller Central tools can assign an image with another file name. Confirm the client's upload method before final naming.
Can the client review the main image before additional images?
The studio controls which proofs or sets are shared and when. The client can record a decision on the current version before the studio prepares or releases another set. Verify the latest grouping and approval behavior in Lenso.
What happens when Amazon changes a rule?
Update the current source record and job requirement, identify the affected files, record whether the change affects scope or timing, and collect a new decision where needed. Do not silently apply an old template.
Can a client return permanently to every Amazon delivery?
No universal permanent-access promise applies. Access is project-specific and can expire or be revoked. The studio can issue fresh access according to its policy and the current account state.
Related resources
See the same record in Lenso
Watch a product request become a proof, decision, and final-file handoff.
Lenso does not replace Seller Central. It keeps the current source, product rows, client comments, approval, and final files connected before the client performs the Amazon upload.