The Shopify Dev Dashboard is Shopify's central hub for building and managing apps — creating apps, generating API credentials, watching logs and health metrics, and spinning up development stores to test against any plan including Plus. Since January 1, 2026, it is also the only place to create new custom apps; the legacy Settings path no longer supports new app creation (per Makro Agency). As of September 2026, Shopify CLI 4.8 also lets you create, list, and delete dev stores directly from your terminal. It is a builder's tool, not a place to see your store's sales or profit. If you landed here hoping to understand what your store actually keeps after ad spend and fees, you want the Analytics dashboard or a profit tool instead — this guide covers both, and where the line falls.

What the Shopify Dev Dashboard actually is

The Dev Dashboard is where anyone building on Shopify manages their apps, dev stores, and product catalogs in one place (Shopify — Dev Dashboard). Think of it as the workshop behind the storefront. Nothing your customers see lives here.

It matters to two kinds of people. Developers and agencies building apps live in it daily. And regular merchants land in it the moment they need a "custom app" — usually to connect an outside system to their store or to pull their own data out through the API.

That second group is who this article is for. You do not need to write code to open the Dev Dashboard, but you do need to know what it is and is not before you start clicking.

The main things you can do in it

Shopify introduced the Dev Platform in September 2025 as a single, centralized place for managing apps and dev stores (Shopify Changelog — build apps with the new Dev Platform). The Dev Dashboard inside it handles these jobs:

  • Create and manage apps. See every app tied to your organization, check its status, and configure it.
  • Generate credentials. Produce the Client ID, Client secret, and access tokens an app uses to call Shopify's APIs.
  • Read logs and health metrics. View webhook deliveries, response times, and errors so you can diagnose why an integration broke.
  • Run development stores. Spin up a free test store on any Shopify plan — Basic, Grow, Advanced, or Plus — to build and try changes before they touch your live shop (Shopify — Dev stores).
  • Deploy Hydrogen storefronts to Oxygen from dev stores. As of August 2026, dev stores can now deploy Hydrogen storefronts to Oxygen — previously this required a paid plan, though deployment URLs on dev stores always require a store login (Shopify Changelog — Oxygen on dev stores).
  • Build catalogs. Create filtered product views — for example, scoped by price or taxonomy — for AI agents to read.
  • Manage app versioning. Create new app versions, manage extensions, and release updates to keep your apps current (Shopify Changelog — Dev Dashboard early access).

For most sellers, the first two are the point. You create an app, grab its credentials, and hand them to whatever tool needs to talk to your store.

New in 2026: CLI store management and the 250-store limit

Two meaningful updates landed in September 2026 that affect anyone who manages multiple dev stores.

First, Shopify CLI 4.8 now lets you create and delete dev stores from your terminal or a coding agent — no browser required (Shopify Changelog — Create and delete dev stores in Shopify CLI). The new commands are:

  • shopify store create dev — creates a dev store in your organization for building and testing apps, themes, and Shopify features.
  • shopify store delete — deletes dev stores when run by a store owner, organization owner, or organization administrator.
  • shopify store list — lists the stores in an organization.
  • shopify store info — returns information about an individual store.

Combined with the Admin API and bulk operation support already in the CLI, you can script workflows that create, populate, and reset development environments automatically (Shopify Changelog).

Second, organizations are now capped at 250 dev stores (Shopify — Dev stores). If you or your agency has been spinning stores freely, this limit is now enforced. The CLI delete command and the Dev Dashboard both let you clean up stores you no longer need — note that deleting a dev store is permanent and its data cannot be restored.

Also worth knowing: when you choose a path for new integrations, Shopify describes the Dev Dashboard as the better route for quick integrations, while apps that need interfaces, extensions, or App Store distribution should generally use Shopify CLI (CartCoders — Shopify Custom Apps after 2026).

What changed for custom apps

This is the biggest practical update for merchants who followed older guides. Since January 1, 2026, Shopify no longer supports creating new custom apps through the Shopify admin. All new custom apps must be created through the Dev Dashboard (Makro Agency — transition to Dev Dashboard). Existing custom apps remain unaffected and functional, but any new integration work runs through the new flow.

The change aligns with Shopify's broader push to improve app security, access control, and developer experience (Acumatica Community — creating custom apps via Dev Dashboard). With the new flow, custom apps are created directly within the Shopify developer portal, giving better visibility into permissions, API credentials, and lifecycle management.

One important caveat: if you delete a legacy custom app, you cannot recreate it through the old process (CartCoders). Before removing any active legacy app, document its scopes, webhooks, credentials, connected systems, and business purpose. A deleted legacy app means rebuilding through the Dev Dashboard from scratch.

In practice, creating a custom app now follows four steps in the Dev Dashboard (Shopify — create apps using the Dev Dashboard): create the app, publish a version with your chosen scopes and webhook API version, install it on your store, then copy the Client ID and secret to request an access token. If a screenshot in an older tutorial does not match what you see, that migration is almost certainly why.

Dev Dashboard vs Partner Dashboard vs your Analytics dashboard

The word "dashboard" gets overloaded inside Shopify, and mixing them up wastes hours. Here is the clean split.

The Dev Dashboard is for building apps and integrations, as covered above. The Partner Dashboard is the business console for agencies and freelancers — it tracks referrals, development stores you build for clients, app listings, and the payouts you earn from them. If your question is about commissions or managing client stores, that is a different tool, and our guide to the Shopify Partners dashboard walks through it.

The Analytics dashboard is the one most store owners actually mean. It lives in your admin under Analytics and shows sales, sessions, conversion rate, and average order value — the numbers about your business, not your code. It is the system of record for what sold. (As of July 2026, Shopify also launched Analytics as a full-stack platform that apps can embed and enrich — but that is a developer feature, not something you configure as a merchant.)

Quick test: if you want to see money, use Analytics. If you want to connect or build something, use the Dev Dashboard. If you get paid to build for other people, use the Partner Dashboard.

The profit question the Dev Dashboard can't answer

Here is where a lot of sellers get stuck. You open the Dev Dashboard expecting insight into your business, and instead you find API scopes and webhook logs. That is by design — building the pipe is not the same as reading the water.

Even your Analytics dashboard, the right place for business numbers, has a known blind spot: it shows revenue but not net profit after ad spend, shipping, transaction fees, and returns (Luca — Shopify Analytics guide). Shopify credits the last click before a sale, so it also undercounts channels like SEO and email that assist earlier. That is not a flaw so much as a scope limit, and it is exactly why the reporting-tool ecosystem exists.

If choosing among those tools is where you are headed, start with our breakdown of how to choose the best ecommerce reporting tools, and the wider map of ecommerce business intelligence for how the pieces fit together. If you sell print-on-demand products and use Printify as your supplier, our Shopify–Printify integration setup guide walks through connecting the two stores end to end.

A worked example: revenue is not profit

The reason this matters is that a healthy-looking sale can be a losing one. Walk a single order.

Say you sell a printed hoodie for sixty dollars. Here is what each cost line does to it — every figure below is an illustration you would replace with your own numbers, not a market statistic.

Line Running total
Selling price $60.00
− Product base cost $60.00 − $22.00 = $38.00
− Shipping to the customer $38.00 − $8.00 = $30.00
− Payment and platform fees $30.00 − $1.80 = $28.20
− Ad spend to win the order $28.20 − $14.00 = $14.20
− Returns reserve $14.20 − $3.00 = $11.20

That hoodie that looked healthy at the product-cost level is really a much thinner order once it sells online with ad spend and fees folded in. Native Shopify shows you the sixty dollars and, on higher plans, the product cost. The rest of that table is what it can't assemble on its own. For a detailed look at how hoodie base costs feed into this math, see our full Printify hoodie base cost breakdown.

Understanding the full picture is especially important for paid-traffic sellers. For a deeper look at how Meta ad spend fits into that math, see our guide on scaling Facebook Ads on Shopify for print-on-demand, and our overview of working with a Facebook Ads agency for ecommerce if you are considering outside help.

Where an AI employee fits

Once you accept that profit lives across several systems — your store, your ad accounts, your print supplier — the job becomes stitching them together and then acting on what they say. That is a different thing from a dashboard.

This is the gap PodVector fills. It reads your Shopify store, Meta Ads, Google Ads, Printify, and Printful data into a live warehouse, then computes your true per-order profit after those costs — the version of the hoodie table above that fills itself in from live data. On top of that sits Victor, an AI employee who analyzes that data and can take Shopify-side actions with your approval: repricing your worst-margin SKUs, bulk-updating prices, setting up discounts, organizing collections, or raising your free-shipping threshold — each as a structured approve/reject card showing old and new values before anything changes.

Victor reads your ad performance across Meta and Google to surface where money leaks, but ad-platform writes are not yet built — he reads your campaigns and proposes moves, and you act on them manually or he executes the corresponding Shopify-side change once you approve. Victor is not a dashboard; he is an AI employee you can ask questions in plain language about your live data.

For print-on-demand sellers trying to make sense of fulfillment costs, see our step-by-step guide to using the Printful shipping calculator and our breakdown of Printful US shipping times and costs. If you want to understand how AI tools fit more broadly into the POD ecosystem, our guide to AI solutions development for ecommerce covers the landscape.

If you started in the Dev Dashboard trying to wire up your own profit pipeline, that is the manual road. See what a connected profit view looks like if you would rather skip the plumbing.

FAQs

Is the Shopify Dev Dashboard the same as the Analytics dashboard?

No. The Dev Dashboard is for building and managing apps, credentials, and dev stores. The Analytics dashboard, in your Shopify admin, shows your store's sales, sessions, and conversion metrics. They share a word and nothing else. If you want to see how your business is doing, you want Analytics.

Do I need to be a developer to use the Dev Dashboard?

Not to open it or create a basic custom app — the Dev Dashboard walks you through creating an app, publishing a version, and copying credentials. But making that app do something useful, or reading the logs when it breaks, quickly gets technical. Many sellers use the Dev Dashboard only to generate credentials that a no-code tool or a hired developer then plugs in.

How is the Dev Dashboard different from the Partner Dashboard?

The Partner Dashboard is for agencies and freelancers who build stores or apps for other people — it tracks client stores, referrals, and payouts. The Dev Dashboard is purely for building and managing the apps themselves. You might use both if you build for clients, or only the Dev Dashboard if you are wiring up your own single store.

Why did my custom app setup move?

Starting January 1, 2026, Shopify no longer supports creating new custom apps through the admin Settings path. All new custom apps must be created through the Dev Dashboard for a more standardized, secure flow (Makro Agency). Existing apps continue to work, but any new integration starts in the Dev Dashboard. Older tutorials that point to a custom-app page under Settings are out of date.

Can I use dev stores to test Hydrogen storefronts?

Yes, and this expanded in August 2026. Dev stores can now deploy Hydrogen storefronts to Oxygen — previously, Oxygen hosting required a paid plan (Shopify Changelog). Keep in mind that dev stores do not include public environments, so deployment URLs always require a store login.

Can I manage dev stores from the command line?

Yes, as of Shopify CLI 4.8 (released September 9, 2026). The new shopify store create dev, shopify store delete, shopify store list, and shopify store info commands let you manage dev stores from your terminal or a coding agent without opening a browser (Shopify Changelog — Create and delete dev stores in Shopify CLI). This is particularly useful for scripting workflows that create, populate, and reset test environments automatically. Note that organizations are now capped at 250 dev stores, so periodic cleanup with shopify store delete keeps you within limits.

Can the Dev Dashboard show me my profit?

No. It exposes API access and app health, not business results. Even Shopify's Analytics dashboard stops at revenue and gross margin rather than net profit after ad spend, shipping, fees, and returns (Luca). Getting to true profit means combining store, ad, and fulfillment data — either by building that pipeline yourself through the Dev Dashboard, or using a tool that connects those sources for you. If Google Ads is part of your stack, also see our guide to Google Ads data-driven attribution for POD sellers, since attribution gaps can make profit look very different depending on which dashboard you read.

Do I need to set up Google Merchant Center separately from the Dev Dashboard?

Yes — Google Merchant Center is a separate system entirely, not part of the Shopify Dev Dashboard. You connect your Shopify product feed to it through the Google & YouTube sales channel or a direct feed. Our step-by-step walkthrough of Shopify Google Merchant Center setup covers the full process for POD sellers.

If I use Printify with Shopify, do I need the Dev Dashboard?

Not for the standard Printify app connection — that runs through the Shopify App Store and does not require custom credentials. You would only touch the Dev Dashboard if you are building a custom integration outside of Printify's published app, for instance to automate order routing or sync catalog data your own way. For the standard setup, our Shopify–Printify integration setup guide covers everything without any Dev Dashboard steps. If you run a WordPress store alongside Shopify, the Printify WordPress setup guide walks through that path separately.