Shopify Admin for AI Agents

The mapping covers the core back office plus store operations. On the read side there are dedicated surfaces for orders, products, customers, discounts, general settings, content metaobjects, and the Analytics and Growth dashboards, reached through actions like list_orders, list_products, view_analytics_dashboard, and view_growth_dashboard. On the write side, orders get their own verbs (create, fulfill, refund, cancel), the catalog gets create, edit, delete, import, and export, and customers and discounts each get create, edit, and delete. Beyond the day-to-day, there are actions for store operations: themes, domains, billing, payments, shipping, installed apps, and purchasing a shipping label. open_admin_home drops the agent on the admin home surface for the current store, and navigate_admin_section jumps to a specific admin section by route.

Reads and writes are strictly separated. The list actions are hard read-only by contract: list_orders opens the Orders list and explicitly must not create, fulfill, refund, or cancel anything, and list_products, list_customers, and list_discounts carry the same rule for their surfaces. Every mutation is its own named action (fulfill_order, refund_order, and so on), so a browsing step can never turn into an accidental write.

Settings follow the same split: view_settings_general opens the General settings page read-only and must not save changes, while update_settings is the separate write path.

navigate_admin_section is allowlisted, not free-form. It takes a section param, and the allowed sections are restricted to surfaces validated in the 2026-06-26 headed route matrix. Your agent cannot wander into unverified corners of the admin by route.

There is no public surface here. Of the 34 actions, 33 require an authenticated merchant session; the one exception is capture_login, which exists to capture that session in the first place. The login URL is admin.shopify.com itself, and the captured session persists through Shopify's admin session cookies, so your agent does not re-authenticate on every run.

The config also knows what logged-out looks like. Pages showing "Log in", "Sign in", or Shopify's "Your connection needs to be verified" interstitial are recognized as login walls, so when a session expires the agent gets a clear signal to re-authenticate instead of misreading the wall as a broken page.

Every dispatch resolves to a named screen, so your agent always knows where it landed: orders, products, customers, discounts, analytics, growth, admin_home, settings_general, or content_metaobjects. That means the agent can branch on the actual state of the session. If list_orders resolves to the orders screen it reads the list; if it hits a login indicator instead, it knows the session needs auth. No screen in this mapping is interpreted from raw HTML, and no selector knowledge lives in your agent.