Shopify WebMCP checkout: what agents can do and where a Sume clip fits

What Shopify shipped

On September 28, Shopify's WebMCP checkout post said browser agents can navigate, read, update and complete checkout. It needs no new API and no merchant configuration. Only supported fields can be updated, and the buyer must confirm before submit.

Sume does not touch checkout and does not need to. The place a product video helps an agent or a human is earlier: the product page it reads before it decides.

Facts from the post

Read from the Shopify changelog.

Where the clip goes

An agent that browses a store reads the page. A product page with a short vertical clip, a clear title and plain text gives it more to work with than a bare image. Generate the clip with a Sume job when the product is created, then attach the media.sume.com URL to the product.

Trigger it from Shopify's own product event, submit the job with an Idempotency-Key built from the product id so a repeated event does not bill twice, and write the result back on job.completed. The older posts on product video automation and adding video to a product page cover the wiring.

Caveats

Keep claims in the clip accurate, since the buyer confirmation step is the last check, not the first.

• The post describes browser agents, so what an agent sees is the rendered page, not your admin data.
• Do not put prices or promises only in video: the agent will not watch it.
• Sume cannot update checkout fields; treat it as page content only.