Key details

  1. Shopify announced the new store commands on September 9, 2026.
  2. The commands require Shopify CLI 4.8 or later.
  3. `shopify store create dev` creates development stores in the organization.
  4. `shopify store list`, `shopify store info` and `shopify store delete` expose the rest of the supported dev-store lifecycle.
  5. Shopify explicitly says the commands can be used from a terminal or coding agent.
  6. Existing Admin API and bulk-operation support can populate scripted test environments.
  7. A new limit of 250 dev stores applies per Dev Dashboard organization.
  8. Client transfer stores and collaborator stores do not count toward the 250-store limit.

What builders should take away

  1. Treat dev stores as disposable infrastructure: give automated workflows naming, ownership and cleanup conventions from the start.
  2. Use the new CLI commands with seeded test data to create repeatable app and theme integration environments instead of maintaining long-lived manually prepared stores.
  3. Scope agent credentials and organization permissions carefully because store deletion is now available through the same machine-operable surface.
  4. Build cleanup around `shopify store list` before an automated workflow can approach the 250-store cap.
  5. Keep client-transfer and merchant-collaboration workflows separate; the CLI lifecycle commands currently target dev stores rather than every Shopify store type.

What changed

Shopify added first-class development-store management to Shopify CLI 4.8 on September 9, 2026. New `shopify store create dev`, `shopify store list`, `shopify store info` and `shopify store delete` commands let developers manage dev stores in a Dev Dashboard organization from the terminal. Shopify explicitly frames the commands as usable from coding agents, and notes that they can be combined with the Admin API and CLI bulk operations to script workflows that create, populate and reset development or testing environments. Shopify is also adding a 250-dev-store limit per Dev Dashboard organization; client transfer stores and collaborator stores do not count toward that cap.

Why it matters

Coding agents become much more useful when they can provision the environment they need rather than asking a human to prepare it. Shopify's new CLI surface moves dev-store lifecycle management into the same machine-operable path as code and API work, enabling more reproducible integration tests, ephemeral stores and automated cleanup. The trade-off is lifecycle control: an agent that can create environments can also accumulate them, and organizations approaching the new 250-store cap need explicit cleanup rules and sufficiently narrow permissions.

Four commands cover the basic dev-store lifecycle

CLI 4.8 can create a development store, enumerate stores in an organization, inspect an individual store and delete a dev store when the caller has the required ownership or administrative role. Shopify's current store documentation confirms that CLI management applies to dev stores, while client transfer and collaborator stores remain Dev Dashboard workflows.

The new commands compose with existing data tooling

Shopify says developers can combine store lifecycle commands with the Admin API and bulk-operation support already available through the CLI. That makes it possible to script a fuller test loop: create a store, seed data, run app or theme tests, then remove the environment when it is no longer needed.

Shopify explicitly expects coding agents to use the surface

The changelog tells developers to install or update Shopify's AI Toolkit in their coding agent and use the new store commands from that environment. This matters because the capability is being designed as a supported agent workflow rather than an accidental shell interface.

Automation now has a hard cleanup boundary

Dev Dashboard organizations are limited to 250 dev stores. Existing organizations above the cap have an extended limit for now, while new automation is expected to use `store list` and `store delete` to clean up stale stores at scale. Client transfer and collaborator stores are excluded from the count.

What to watch next

  • Whether Shopify adds dev-store lifecycle APIs or richer JSON output specifically for CI and agents.
  • Agent-oriented templates for creating, seeding, testing and destroying stores in one workflow.
  • How Shopify enforces the 250-store cap for older organizations that currently exceed it.
  • Whether feature-preview selection and store configuration become fully scriptable during creation.

Still unclear

  • Shopify does not describe these dev stores as truly ephemeral; cleanup still needs to be implemented by the developer or agent workflow.
  • Permissions still constrain who can delete stores, so agent automation depends on the identity and role used to run the CLI.
  • The 250-store policy may evolve as Shopify observes automated use.

Sources

Direct reading behind this dossier.

2 sources
Stores
Shopify Developers primary_documentation

Current documentation for store types, roles and the boundary that CLI management applies to dev stores.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment