Executive summary
- What: Shopify CLI 4.8 adds a shopify store command group that creates, lists, inspects and deletes dev stores from the terminal or a coding agent.
- Why: Environment provisioning no longer requires a trip through the Dev Dashboard, so it can live in scripts alongside the rest of your build tooling.
- Who: App and theme developers, agency delivery leads, and any organization running more than a handful of dev stores, which now sit under a 250 store cap.
What changed
Four commands land in Shopify CLI 4.8. The command shopify store create dev provisions a dev store in your Dev Dashboard organization, with flags for name, plan (basic, grow, advanced or plus), country code, demo data and feature previews. Then shopify store list returns the stores in the organization, shopify store info returns detail on a single store, and shopify store delete removes one. Deletion is gated: only a store owner, organization owner or organization administrator can run it.
Shopify has also introduced a limit of 250 dev stores per organization. Client transfer and collaborator stores are excluded from that count, and organizations already above the line have been granted an extended limit. Nothing breaks today, but the ceiling is now real for planning purposes.
These commands sit alongside the Admin API and bulk operation commands already in the CLI, so a single script can create a store, populate it with data, and tear it down again.
Why it matters
Dev store sprawl is a quiet operational tax for any Plus merchant with an internal build team or an agency partner. Stores get created for one QA pass, seeded by hand, then abandoned with stale configuration inside them. Nobody owns the cleanup, so the inventory grows until somebody audits it. Making the lifecycle scriptable moves that work into the pipeline.
The second benefit is test fidelity. Passing plus to the plan flag means checkout extensibility, B2B price lists and Markets behaviour can be exercised on a store that matches production, rather than approximated on a lower plan and discovered as a gap during UAT. For teams shipping checkout or B2B work quarterly, that is the difference between catching a configuration mismatch in development and catching it in a release window.
The cap is worth an inventory pass regardless of how close you are to it. Organizations that have accumulated stores across years of projects and agency relationships rarely have a current picture of what exists.
Role-specific impact
- Marketers: No direct change. Indirectly, faster environment turnaround shortens the wait for a working staging link when reviewing a campaign template or B2B catalogue.
- Developers: Environment provisioning becomes code. Wrap create, seed and delete into a CI job so a feature branch can get a disposable store on the correct plan without a ticket.
- Store admins: Confirm who holds store owner, organization owner or organization administrator rights, since those roles gate deletion, and check your store count against the new ceiling.
Use-case example
Real-world scenario
A Plus merchant runs a quarterly checkout release with three concurrent workstreams. Under the old process, each workstream requested a store through the dashboard, waited on an administrator, then spent roughly 40 minutes seeding products, customers and shipping profiles by hand. That is close to two hours of setup per cycle before testing begins, four times a year. With a provisioning script calling shopify store create dev with the plus plan, demo data and the right country code, the same three environments come up in minutes on production-equivalent plans. A scheduled sweep using store list and store delete retires them at sprint close, keeping the organization under the cap.
Implementation checklist
- Upgrade to Shopify CLI 4.8 or later. Versions from 4.0 auto-upgrade unless that is turned off or the install is project-local.
- Update the AI Toolkit in your coding agent if your team uses one.
- Run shopify store list and export the dev store inventory for each organization you operate.
- Flag stores that are stale, unowned or duplicated, confirm with the last known owner, then delete them.
- Verify role assignments, since deletion requires an owner or organization administrator.
- Add store creation and teardown to your CI or onboarding scripts, pinning the plan flag to match production.
- Set a quarterly reminder to repeat the audit and keep headroom under the cap.
FAQ
Q: Does the 250 store limit affect client stores or collaborator access?
A: No. The cap counts dev stores inside a Dev Dashboard organization. Client transfer and collaborator stores are excluded, so agency access to merchant production stores is unaffected.
Q: Can we still create dev stores through the Dev Dashboard interface?
A: Yes. The CLI commands are an addition rather than a replacement, and both routes create the same store type.
Resources
Shopify documentation: Create and manage development stores
Need guidance? Talk to Makro.