Adobe

Adobe Commerce

Curated major addition platform in enterprise commerce with material relevance to the Marcom operating stack and a first-party developer surface.

Commerce & paymentsSystem of recordBYO-UI-ready platform

Representative source ↗Product site ↗

System roleSystem of record

Access maturityBYO-UI-ready platform

Agent postureDeveloper-context only

Reference updatedNot stated by publisher

BYO-UI reviewedJul 10, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Products, categories, prices, inventory, customers, carts and quotes, orders, invoices, shipments, refunds, coupons, stores, and extension configuration.

02 · Data you can retrieve

Query commerce objects through REST and GraphQL, subscribe to Adobe I/O events, and invoke synchronous webhooks for supported checkout and extension flows.

03 · Actions and write paths

Create and update supported catalog, customer, cart, order, fulfillment, and configuration resources; extend checkout, tax, payment, shipping, and totals workflows.

04 · Authentication and permissions

Admin, customer, integration, or OAuth credentials and Adobe Commerce ACL resources determine access; App Builder and App Management add separate controls.

05 · Monitoring, approval, and recovery

Payment, tax, order, inventory, customer-data, and checkout writes require strict idempotency, environment separation, approvals, and financial audit trails.

06 · Gaps and implementation limits

The verified MCP is developer/App Builder context, not a general live-commerce provider. REST/GraphQL, events, and synchronous webhooks have distinct semantics.

First-party access

Documented surfaces

Adobe Commerce GraphQL ↗Adobe Commerce exposes GraphQL endpoints with queries and mutations for its PaaS and SaaS product variants. Schema, deployment model, authentication, store scope, API limits, and mutation consequences define the effective access boundary; this is GraphQL, not database SQL.Source: GraphQL overview MCP / agent surface ↗First-party developer/documentation MCP; not tenant-operational provider API ↗Developer access Developer docs ↗SDKs and platform guidance Events / extensions ↗Webhooks, apps, or extensions Product ↗Native platform experience

Agent access

MCP and adjacent posture

First-party developer/documentation MCP; not tenant-operational providerOfficial Adobe Commerce developer and App Builder MCP toolingCurrent developer tooling; not verified as a general tenant operations server

Role: developer_context

Read scope: Commerce documentation, APIs, code samples, extension migration, App Builder generation and storefront/customization workflows in development environments

Write scope: Write scope was not separately normalized in this pass; inspect the official tool catalog before enabling actions.

Authentication: Authentication model is documented by the vendor; inspect the cited source before implementation.

Approval boundary: Require explicit human confirmation for costly, externally visible, destructive, or hard-to-reverse actions.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4

Action access4

Event access4

Identity4

Governance4

Agent access2

UI extensibility3

Portability4

Observability3

Documentation5

Proposed interfaces

What customers could build on top.

These are design proposals derived from documented access—not claims that Adobe ships these experiences.

Single-platform patterns

Commerce implementation and merchandising workbench
Revenue reconciliation console
Commerce operations cockpit
Customer-resolution workbench

Use in the brief composer →

Multi-platform compositions

Adobe Commerce + CRM or support system: revenue reconciliation console
Adobe Commerce + lifecycle platform + analytics or finance system: cross-system decision workspace

Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

8 recorded sources

Platform core validationRepresentative source

https://developer.adobe.com/commerce/webapi/get-started/ ↗

Products, categories, prices, inventory, customers, carts and quotes, orders, invoices, shipments, refunds, coupons, stores, and extension configuration. Create and update supported catalog, customer, cart, order,…

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 10, 2026

Targeted first-party core-access review

MCPSource inventory

https://developer.adobe.com/commerce/extensibility/mcp/ ↗

First-party MCP documentation or product announcement recorded for this platform.

Publisher updated: Not stated by publisher
BYO-UI reviewed: Jul 10, 2026