Executive summary
- What: Shopify consolidated store management, collaborator access, app metrics, and logs into a rebuilt Dev Dashboard at dev.shopify.com/dashboard.
- Why: revenue, error rates, and webhook failures now sit in one triage view, so app problems surface before a merchant reports them.
- Who: agencies and internal teams running custom or private apps across multiple Shopify stores. No merchant facing change.
What changed
The Dev Dashboard Home is now a triage surface rather than a directory. It shows topline revenue across your portfolio, subject to existing permissions, and a business status table collecting errors and warnings from every app and store in urgency order. A suspended app or failing webhook sits above softer warnings such as deprecated API calls or expired collaborator access.
The apps index is one sortable list covering revenue, installs, distribution status, and active alerts. Opening an app gives installs and uninstalls over time, API request volume, error rates, and per API logs. Each error rate chart plots the rate against the underlying request volume, which is the difference between noise and an incident, and deep links into Logs pre-filtered to that API and to failures.
The stores index merges client, development, and collaborator stores into one searchable list, replacing three tabs, and access requests start from that list. Logs now cover every API request, webhook delivery, and app event across all installed stores, with 30 day retention and up to 7 days per filtered view.
Why it matters
This is not a storefront change, but it does change the response time you can expect from whoever maintains your custom apps. Most integration incidents are found by the business, not by engineering: an order sync stops, a warehouse notices missing orders, a ticket follows a day later. Surfacing webhook failures and error spikes on a dashboard someone opens each morning moves detection earlier.
That only pays off if someone watches it. Portfolio alerting is a tool, not a process, and it belongs alongside the rest of your operational monitoring and downtime practices. The 30 day log retention matters too: older incidents are no longer investigable from this data, which argues for exporting anything tied to a financial dispute.
Role-specific impact
- Marketers: no direct change. The indirect benefit is fewer silent failures in apps powering promotions, loyalty, or subscription logic, since a discount function that stops applying for one shop is traceable to a specific failed run.
- Developers: triage is materially faster. Error rate plotted against volume prevents chasing a high percentage on a handful of calls, and one click into filtered logs removes the step of reconstructing which requests failed.
- Store admins: collaborator access state, expiring access, and transfers in progress sit in one table instead of surfacing when someone loses access. With an agency, this is where stale accounts become obvious.
Use-case example
Real-world scenario
A manufacturer on Shopify Plus ran a custom app pushing orders into their ERP. The webhook endpoint started returning 500s after an internal certificate rotation. Orders kept being placed and kept not arriving. Warehouse staff flagged it the next afternoon, roughly twenty six hours later, by which point about ninety orders needed manual entry.
With the failure visible as a webhook error count in the portfolio status table, the same incident becomes a morning triage item rather than a next day escalation. Cutting detection from twenty six hours to under two on that volume is roughly eighty three orders that never need manual re-entry, and no customer facing dispatch delay. The saving is not the dashboard, it is the habit of opening it.
Implementation checklist
- Sign in at dev.shopify.com/dashboard and confirm every app and store you expect is present in the new indexes.
- Audit the stores index for collaborator accounts that should no longer have access, including former staff and past agency partners.
- Clear the existing backlog of warnings in the business status table, particularly deprecated API calls with a version deadline attached.
- Give the portfolio status table a named owner and a daily cadence. An alert nobody reads is not monitoring.
- Set a baseline for normal error rate and request volume per app so a genuine spike stands out against it.
- Define an export step for logs tied to financial or fulfilment disputes, given 30 day retention.
FAQ
Q: Does this affect our storefront or our merchant admin?
A: No. This is tooling for the people who build and maintain apps. Nothing changes for buyers or in the Shopify admin your team uses daily.
Q: Do we still need the Partner Dashboard?
A: For some tasks, yes. Shopify has indicated that app distribution, review, listing, payouts, and protected scope requests are moving into the Dev Dashboard, but that work is still in progress.
Resources
Shopify developer docs: build with the Dev Dashboard
Need guidance? Talk to Makro.