Revenue, alerts, store management, collaborator permissions, and logs are consolidated into a single view across all your apps and stores. The redesign helps you catch app issues before merchants report them.
Stores were split across 3 tabs, and managing permissions or checking app status meant navigating multiple pages.
Check revenue and action items on Home, then drill into Apps, Stores, or Logs in one click.
Shows combined revenue across all your apps. Visibility follows your existing permission settings, so no extra setup is needed.
Errors and warnings from every app and store in a single table, sorted by urgency.
See API updates and breaking changes right in Home, where you already work.
Counts every store that has the app installed as of today.This includes your own development stores and stores without an active plan. Select the number to see the list of stores with the app installed.
You shipped on Tuesday and Installs dropped by Friday. The installs/uninstalls chart shows whether merchants are leaving or new installs have just slowed.
The post states that if you build for clients, this is where your daily work begins.
When a merchant who installed your app reaches out, you can request access straight from your list of installed stores — no need to look up their domain. You can also request access the same way from the Stores index.
Recorded across every store where your app is installed.
No more reading an entire afternoon of logs to find a single failed webhook.
Errors are flagged, and search and filters let you narrow down to the calls you're investigating.
| Area | Announced feature | Details |
|---|---|---|
| Apps | Everything in one place | Manage distribution, move through app review, and create listings and pricing — all within the Dev Dashboard |
| Apps | App history | A complete log of install, uninstall, and billing events |
| Apps | Access requests | Request access to protected scopes from the Dev Dashboard without switching to the Partner Dashboard |
| Stores | Referred stores | Show referred stores in your store list, with direct access to revenue from each referral |
| Organization | Payouts and billing | Check revenue and payout dates, and manage billing, from the Dev Dashboard |
Charts overlay rate and volume. 50% of 4 requests is noise; 50% of 40,000 is an incident. As the post suggests, alert thresholds should factor in volume, not rate alone.
Investigations beyond 30 days aren't possible. For long-term tracking, you'll need to store logs in your own infrastructure (no export option from the Dev Dashboard is mentioned).
Your own development stores and stores without an active plan are counted too. Before reporting it as an "active merchant count," check the breakdown in the list.
Beyond API calls and webhooks, you can filter Function runs by shop and open individual failed runs. This directly helps isolate "the discount doesn't work for one specific store" issues with discount Functions.
In Business status, deprecated API calls appear as warnings, and Home also shows the developer Changelog. During API version migrations, you can spot which apps are still making outdated calls right from Home. Note that Revenue visibility follows existing permissions, so your team's permission setup directly determines what each person can see.