Integration · Magento 2 and Adobe Commerce

Generate on-model photos for your Magento 2 or Adobe Commerce catalog

Use your assistant to generate Product page set views from garment photos. Build an authenticated Commerce adapter to deliver each image to the intended SKU.

Get a demoSet up Uwear MCP
Model wearing a linen-blend band-collar shirt, full-body front on the Pure White studio, generated with nano-banana-pro through the Product page set template
Front hero from the Product page set template: linen band-collar shirt on the Pure White studio, generated with nano-banana-pro through the Uwear MCP.

Use cases

What can you build?

  • Generate catalog views by SKU

    Create front, upper-body and back studio photos. Map each set to the parent or color-specific child SKU before adding gallery entries.[3][17]

  • Build storefront virtual try-on

    Prototype with Uwear MCP, then use a merchant backend and Uwear API. Choose the installed PWA Studio extension or composed product-details block for the shopper interface.[33][34][35]

Model wearing the same linen-blend band-collar shirt, full-body back camera edit on the Pure White studio, generated with nano-banana-pro through the Product page set template
Back view from the same Product page set run: a camera edit of the front hero, so the model, light, and studio carry over. Generated with nano-banana-pro through the Uwear MCP.

Assistant workflow

How do you run this from your assistant?

Proposed integration, not a preinstalled connection. Use Claude Code, Codex or ChatGPT with Uwear MCP and an authenticated Commerce REST adapter; Adobe developer MCP tools supply development context.[6]

  • Commerce Developer MCP Server

    Supplies coding and documentation context. The reviewed developer tools do not document merchant product-media writes.[6]

    Installable developer tooling; aio auth login for documentation retrieval. No explicit GA or beta label established.[6]

  • App Builder MCP Server

    Develops, deploys and invokes runtime actions. Build the Commerce REST adapter as an action with its own Commerce authorization.[6][8][20]

    Documented tooling; the media adapter is custom work, not a preinstalled Uwear connection.[6][8][20]

  • AEM MCP Server

    Uploads and manages AEM assets. If AEM owns the catalog imagery, separate Commerce matching, metadata and approval govern synchronization.[15][37][38]

    OAuth and existing AEM permissions apply. AEM asset writes do not by themselves establish Commerce gallery writes.[15][37][38]

  1. Identify the Commerce deployment

    Confirm Open Source or traditional Commerce, SaaS, and whether AEM owns the images. SaaS uses IMS authentication; core REST media parity is unverified. AEM-managed galleries use the DAM workflow.[20][22][37]

  2. Connect tools and read the SKUs

    Connect Commerce Developer MCP Server and Uwear MCP. Use the REST adapter with an Admin bearer token or OAuth 1.0a integration and catalog permissions. GET /V1/products/{sku} and GET /V1/products/{sku}/media supply product and gallery context.[6][16][20][21]

  3. Approve the Product page set brief

    Load Product page set on its Pure White studio at 2:3 with the AI reviewer on. Review the costed brief in credits before generating. QA is automatic and toggleable: when on, an AI reviewer compares results with source photos and retries flagged results.

  4. Append images through the adapter

    Convert to a supported format, base64-encode the bytes and POST /V1/products/{sku}/media. Set label, filename and roles explicitly; retain the returned media ID with the SKU.[17][27]

  5. Verify each store view

    Read the gallery back and check parent and child products, order, crop and HTML alt text. Wait for results and storefront display before reporting completion.[3][16][23][45]

Run it from your assistant

Run this photoshoot from your AI assistant with a Uwear template.

Connect the Uwear MCP server to ChatGPT, Claude, or Codex and ask for the Product page set template. It is a batch workflow that runs once per garment: front, upper-body, and back product-page shots on a white studio background, plus a 360-degree video, from one garment photo. Any Uwear account can load it by name, and the assistant shows a costed brief in credits before generation starts.

Copy this prompt into your assistant

Connect Commerce Developer MCP Server for documentation context, the Uwear MCP server and an authenticated Commerce REST adapter in this session. Confirm the Commerce edition and image owner, then read my products and galleries and keep their parent and child SKUs. Load "Product page set" on its Pure White studio setup at 2:3, turn the AI reviewer on, and show me the costed brief in credits before generating. After I approve, download and base64-encode supported image files, propose labels and roles, and deliver through POST /V1/products/{sku}/media under /rest/<store_code>; validate SaaS or AEM delivery separately. Wait for readiness and verify the gallery and storefront alt text before reporting.

Set up the MCP server

What one run does, per garment

  1. Generate the front hero

    One full-body front photo of the garment on the template model, in the Basic white photoshoot art direction on the Pure White studio location.

  2. Edit to the upper-body crop

    A camera edit that reframes the front result to an upper-body front frame instead of generating a new image, so the crop comes from the same session as the hero.

  3. Edit to the back view

    A second camera edit of the front result to a full-body back frame, so the product page gets the back of the garment from the same session.

  4. Render the 360 turn

    A 5-second Kling 3 Pro video from the front photo: the model turns a slow, full 360 degrees in place, garment readable throughout.

Outputs per garment

  • Full-body front photo, 2K, 2:3
  • Upper-body front photo, 2K, 2:3
  • Full-body back photo, 2K, 2:3
  • 5-second 360-degree video

The setup the template pins

Template kind
Batch workflow: runs once per garment row
System key
demo_full_pdp_test_white_studio
Art direction
Basic white photoshoot (system art direction)
Location
Pure White (system studio location)
Model
The Uwear system model by default; the assistant can swap in one of your saved models when it proposes the brief
Image model
nano-banana-pro, 2K, 2:3
Video model
Kling 3 Pro, 5 seconds
QA
Optional. With the AI reviewer on, each result is checked against the source product photo and flagged results are retried
Approval
The assistant shows a costed brief in credits before anything generates

Pure automation

How does API delivery work?

For Magento Open Source and traditional Adobe Commerce, POST /V1/products/{sku}/media under /rest/<store_code>. Download the result and send entry with media_type: image, label, position, disabled, types and content: base64_encoded_data, type and name. The response is a media entry ID. Do not send a result URL as content.[17][20]

  1. Build an App Builder runtime action

    Run the authenticated media adapter in an App Builder runtime action. Enqueue eligible SKUs from a scheduled scan or available Adobe I/O Events; do not block a synchronous product save on generation.[8][20][36]

  2. Run generation without an assistant

    Submit Uwear REST API jobs and receive completion webhooks or poll. A published Production Automation can also start when a garment is processed, a tag is added or an outfit is created. These are Uwear workspace triggers; platform delivery still needs an adapter.

  3. Deliver and read back the media

    Download and encode the result bytes, call the Commerce media endpoint and retain SKU/result/media IDs to prevent duplicate additions. Read back the affected gallery.[16][17]

Platform requirements

What image specifications apply?

Magento 2 and Adobe Commerce: What image specifications apply?
SpecificationRequirement or guidance
Upload formatsThe default Magento 2.4.8 validator accepts image/jpg, image/jpeg, image/gif and image/png. Default WebP or AVIF support is not established.[27]
FilenameAdmin guidance limits the filename, including extension, to 90 characters. Validate the deployed REST path separately.[4]
Ratio and backgroundUse consistent proportions and check the theme crop. The reviewed guidance does not require a universal square ratio or white background.[5]
Alt text and image rolesUse label for alt text, position for order and types for roles. Verify the rendered storefront alt text and affected store views.[23]
VideoThe standard UI uses YouTube or Vimeo links. Plan external video hosting or a custom storefront player for the 360 clip.[41]

Existing options

Which AI image tools are already available?

Documented features from the linked sources. These are not independent quality tests.

  • AI Product Studio, Meetanshi Technologies LLP

    A fit for generation and editing inside Product Edit, with gallery save and a Lifestyle Model Try-On preset. Requires a Gemini key and separate usage charges. License price and review counts were not verified; an unselected zero total is not a free license.[30]

  • AI Base Image Generator, Webkul Software Private Limited

    A fit for Admin-to-gallery on-model generation with model controls. The vendor displays US$289 before edition, support and installation options; a paid Gemini plan is required. Marketplace pricing and review totals remain unverified.[32]

Frequently asked questions

Yes, through a built, authenticated Commerce REST adapter alongside Uwear MCP. The reviewed Adobe MCP tools do not establish merchant gallery writes. Confirm edition and image ownership first; core REST support does not prove SaaS parity.[6][17][20][22][37]

Keep parent and child SKUs separate. Select the intended SKU for each media addition, set roles and order, and check its store views. Do not assume a parent update changes every child gallery.[3][17][23]

The standard Commerce video UI uses YouTube or Vimeo. Use external video hosting or a custom storefront player; a raw Uwear video URL is not proven compatible with that UI.[41]

No native Commerce publisher is established here. Build the App Builder runtime action or another authenticated delivery adapter; Uwear workspace triggers start generation, and the adapter owns the media POST and verification.[8][17]

Uwear uses credits at $0.10 per credit; model rates are on /models. The assistant shows a costed brief before generation. QA is automatic and toggleable: when on, an AI reviewer compares results with source photos and retries flagged results.

Generate in Uwear Studio, download the stills and upload them in Commerce Admin with alt text and roles, or use CSV image import. If AEM manages imagery, use its asset workflow.[4][29][37]

Research

Sources and access dates

  1. [3]
  2. [4]
  3. [5]
  4. [6]
  5. [8]
  6. [15]
  7. [16]
  8. [17]
  9. [20]
  10. [21]
  11. [22]
  12. [23]
  13. [27]
  14. [29]
  15. [30]
  16. [32]
  17. [33]
  18. [34]
  19. [35]
  20. [36]
  21. [37]
  22. [38]
  23. [41]
  24. [45]

Next step

Connect your catalog to Uwear.

Start with an assistant-led test, then build the API delivery your catalog needs.

Get a demoSet up Uwear MCP