Shopify Sidekick

Integration is the app ecosystem itself rather than a connector list, which is the structural advantage of being the platform. Sidekick reaches natively across the whole Shopify surface, every screen of the admin, the mobile app and Apple Watch, and since the Winter and Spring 2026 Editions it reaches into third-party apps through Sidekick App Extensions in two forms: data extensions that surface a partner app's data when a merchant asks a relevant question, and action extensions that route the merchant into the right place inside an app and stage the change.

Named launch partners include Klaviyo, Loop, Smile, Judge.me, Matrixify, Avia, Seguno, Checkout Links and Yotpo, spanning email, loyalty, reviews, data operations and conversion. Underneath sits the full Shopify Admin and Storefront API surface, and Sidekick can build Shopify Flow automations from a plain-language description. The tool surface expands as the ecosystem builds toward it rather than as the vendor writes integrations.

Sourceshopify.dev Sidekick documentation and Spring 26 Edition developer announcementread 2026-09-02

Real execution inside the admin, stopping short of unattended completion. Sidekick interprets a natural-language request and carries it out rather than describing how: it creates discount codes, modifies themes, generates product copy and images, creates customers, edits store policies, surfaces underperforming products, builds Shopify Flow automations from a description, and in the Winter 2026 Edition generates whole applications from a prompt, with background multi-tasking added in Spring 2026 and Sidekick Pulse monitoring store data to surface anomalies unprompted.

Sidekick is merchant-initiated and conversational rather than trigger-driven, and its documented third-party action pattern is explicitly stage and confirm, with Shopify's own wording being that it routes merchants to the right spot inside an app and stages changes for confirmation, the merchant acting. The release claim that AI agents now handle entire workflows end to end is announcement framing with no documented unattended path from trigger to completion behind it.

Sourceshopify.dev Sidekick documentation, Winter and Spring 26 Edition announcementsread 2026-09-02

Owning the platform pays off here. Grounding covers the merchant's entire commerce system of record natively, with no integration step and no sync lag: catalog, inventory, orders, customers, policies and historical performance, queried live rather than indexed, with Sidekick able to run ShopifyQL against real orders and analytics.

On top of that sits federated cross-app retrieval: through data extensions a single merchant question causes Sidekick to query multiple installed third-party apps at once, rank the results, fuse them with store context and return one answer with branded cards, so email, loyalty, review and analytics data from separate vendors arrive as a single grounded response. Retrieval respects each staff member's permissions, so the answer is scoped to what that person may see.

Sourceshopify.dev Sidekick documentation and Winter 26 Edition developer announcementread 2026-09-02

Two independent mechanisms, one at run time and one before anything reaches a merchant at all, and both are properties of the platform contract rather than settings a vendor might omit. At run time, changes are surfaced for the merchant to approve before they are applied, and action extensions stage changes for confirmation, so when Sidekick acts inside a third-party app the merchant confirms rather than discovers.

Permissions bound the whole surface: Sidekick respects each staff member's admin permissions, so a person can only act on what they were already authorized to touch. Before publication, Shopify enforces a content and safety policy over every Sidekick extension and scans against it automatically, blocking non-compliant tools from appearing to merchants, with partners selected into the preview. Together this is oversight designed into the extension contract, so it applies uniformly across every third-party agent capability.

Sourceshopify.dev Sidekick documentation and shopify.com/sidekickread 2026-09-02

Attestations and access controls, published by the platform owner. Shopify's security page states "Shopify is certified Level 1 PCI DSS compliant" and "Shopify has been issued SOC 2 Type II and SOC 3 reports for the service we provide to our customers", with a published sub-processor list, a data processing addendum and EEA, UK and Swiss data initially processed by Shopify International Limited in Ireland.

Sidekick respects each staff member's existing admin permissions, so people act only on data they are already authorized to see, and every Sidekick app extension runs inside Shopify's sandbox under Shopify auth with exactly the API scopes of its parent app, so a third-party tool cannot exceed the permissions the merchant granted. Shopify runs an automated security scan on every preview and deploy, records the outcome as a Sidekick event and blocks failing extensions from reaching merchants. The sandbox is a security control rather than a deployment option.

Sourceshopify.com/security, shopify.dev Sidekick app extensions documentation and help.shopify.com privacy pagesread 2026-10-01

Observability exists and it points at developers, not merchants. Extension builders get Sidekick events written to their app's logs in the Dev Dashboard, carrying the security scan outcome, the scan target and the time it ran, so they can confirm whether an extension integrated or was blocked. What the merchant gets is not documented.

There is no audit log of what Sidekick did on their behalf, no record of which extension or data source answered a question, no attribution of an admin change to the agent rather than the user, and no retention policy over conversations. Shopify's own developer education material documents a blind spot.

Builders cannot see Sidekick's UI during development, so comprehensive logging is described as the best debugging tool available, which is an acknowledged gap in the build loop for a surface an ecosystem is being asked to build on.

Sourceshopify.dev Sidekick documentation and Shopify developer education materialread 2026-09-02

A complete commerce record and a chat history, and no agent memory. Sidekick sits on the merchant's permanently held store data, which the vendor describes as extensive knowledge of the merchant and their store, conversation history is retained and accessible, and background multi-tasking keeps task state within a session.

The store data is the business record, and a retrievable chat history is not agent memory. No cross-session recall the merchant can rely on, no learned merchant preferences carried between conversations, no per agent state store and no retention or forgetting control is documented. Commentary anticipating merchant fine-tuning on catalog and customer data is roadmap, not shipped.

Sourceshopify.com/sidekick and shopify.dev documentationread 2026-10-01

Shopify documents moving data between regions as an operating requirement. Shopify's help center states that it dynamically rebalances storage between multiple Google Cloud Platform regions to offer reliable and scalable infrastructure across its merchant database, and that it needs to be able to move data geographically in order to operate its services, with mechanisms in place to do so lawfully.

It adds that even where merchant customer personal data is stored in Europe, it relies on international transfers to process that data. That is the vendor documenting the opposite of residency: geographic mobility is an operating requirement, not a customer setting.

Jurisdiction facts exist and are not control: personal data from EEA, UK and Swiss customers is initially processed by Shopify International Limited in Ireland, and group and sub-processor DPAs carry protections for Canada, the United States and Singapore. No region selection, no on-premises, no private VPC, no single-tenant option and no residency commitment attaches to Sidekick or to the platform beneath it.

The extension sandbox is runtime isolation, a security property rather than a deployment choice. No Plus-tier residency option is documented, and the platform's own architecture statement argues against one.

Sourcehelp.shopify.com international data transfers and subprocessors pagesread 2026-09-02

Sidekick is one agent, not a catalog. There is no library of named purpose-built agents a merchant browses, no agent template marketplace, and no way to compose, clone or instantiate an agent.

What it does have is a growing capability catalog arriving through the ecosystem: Sidekick App Extensions launched with more than fifteen named partners, each contributing data and action tools, so the set of things Sidekick can do expands without Shopify shipping new agents, and scaffolding templates exist on the builder side through the Shopify CLI. These are tools added to a single agent rather than prebuilt agents added to a library.

Sourceshopify.dev Sidekick documentation and Spring 26 Edition announcementread 2026-09-02

Background monitoring wakes the agent before the merchant asks. Sidekick Pulse monitors store data in the background and surfaces opportunities and anomalies such as a conversion drop or an underperforming product unprompted, alongside inventory alerts and discount optimization prompts.

Around it Sidekick is reachable on every screen of the Shopify admin, throughout the mobile app with voice chat added in the Winter 2026 Edition, and from Apple Watch, with background multi-tasking added in Spring 2026. It faces the merchant rather than the shopper; the buyer-facing surfaces in Shopify's 2026 stack (Agentic Storefronts, Store AI, the Universal Commerce Protocol) are adjacent products separate from Sidekick. Shopify describes what Pulse watches and how often without documenting either.

Sourceshopify.com/sidekick and Shopify Spring 26 Editionread 2026-10-01

No model provider named and no customer-facing model control of any kind. Shopify does not disclose which models power Sidekick in its developer documentation, product page or Winter and Spring 2026 Edition announcements, offers merchants no selection or routing, and provides no bring-your-own-model or bring-your-own-key path; extension developers register tools and do not choose the model that calls them.

For a buyer, this is a platform owner's deliberate abstraction rather than undisclosed dependency on a single supplier, with Shopify treating the model as swappable infrastructure it manages on the merchant's behalf. That is coherent for a product bundled into a commerce platform and sold to non-technical merchants, and it still leaves the merchant with no lever and no disclosure.

Sourceshopify.dev documentation and Shopify 2026 Edition announcementsread 2026-09-02

A full third-party build surface documented first-party at shopify.dev. Sidekick App Extensions are scaffolded through the Shopify CLI, declare capabilities in tools.json and instructions.md, target modules, run a local round trip against the Sidekick preview and deploy atomically, with two extension types shipping, data and action; the program launched with more than fifteen named partners and is open to any developer through Shopify Partners.

Around it sits an MCP estate: a Dev MCP server distributed as an npm package connecting Claude Code, Cursor, Gemini CLI, Codex and VS Code to Shopify's documentation and API schemas, plus Storefront, Catalog and Checkout MCP servers, and the Universal Commerce Protocol co-developed with Google, with the Spring 2026 Edition letting developers self-register an agent profile and call the public endpoint.

Sidekick extensions are MCP-like but not MCP, and Shopify states an existing MCP server cannot be reused, because tools run in its sandbox under its auth against a Shopify-specific schema that is statically indexed.

Sourceshopify.dev/docs/apps/build/sidekick and Shopify developer announcementsread 2026-10-01

Testing splits the same way between developers and merchants. Extension builders get a genuine test loop: a local round trip running the app against the Sidekick preview, hot reload that automatically reruns the security scan on save, pass or fail surfaced as Sidekick events, and an atomic deploy that rejects an unsupported intent type outright rather than shipping it broken.

That is real pre-production testing of agent tools. The merchant, who is Sidekick's customer, gets no sandbox to rehearse Sidekick against their own store, no evaluation of answer quality, no regression check when the catalog or an installed app changes, no scoring and no way to compare configurations.

Sourceshopify.dev Sidekick documentation and Shopify developer education materialread 2026-09-02

Sidekick operates Shopify's own interface through Shopify's own APIs, which is product functionality rather than computer use.

It navigates the Shopify admin, modifies themes, fills forms and generates applications, but that interface is Shopify's own product, reached through Shopify's own programmatic surface, rather than third-party software with no sanctioned interface to call.

Nothing across the developer documentation, the product pages or the 2026 Edition announcements describes browser control, screen operation, robotic process automation or any capability to act in software outside the Shopify surface.

Sourceshopify.dev Sidekick documentation and Shopify 2026 Edition announcementsread 2026-09-02