Shopify custom app logs in the new Developer Dashboard

The integrations we get called in to fix rarely fail loudly. An order doesn't reach the ERP. A price update lands on some products and not others. Stock drifts for a week before someone in the warehouse notices.

Shopify has made that easier to catch. Since the 25th of September, the Developer Dashboard shows health metrics and a filterable log stream for custom apps. You can now see API request volume, error rates, webhook delivery health and admin page speed in one place. If your ERP link or back office sync runs as a custom app, you can finally check it without waiting for a complaint.

What changed in the Developer Dashboard?

Shopify's changelog entry lists three additions for custom apps.

• Performance metrics for API request volume, error rates, webhook delivery health and embedded admin page load speed, with clear thresholds.
• A filterable log stream that captures API requests, webhook deliveries and app events.
• A new homepage that shows every app at a glance, built for agencies and developers who look after several.

The dashboard lives at dev.shopify.com/dashboard. Shopify's documentation says you need app development access to see the app side of it.

What the logs actually capture

According to Shopify's monitoring documentation, the log stream records Admin API requests, webhook deliveries, Function runs, UI extension errors and your own app events. It puts them on one timeline.

You can filter by time range, type, shop and status code. There are eight entry types, including webhook, GraphQL request, REST request and app event. That matters when one app serves more than one store, or when you need to find one failed order in a busy afternoon.

A few limits are worth knowing.

• Logs are kept for 30 days.
• A single search can cover up to seven days.
• Very large request and response bodies are cut off and marked as truncated.

On webhook health, Shopify flags problems on the chart at any volume. The critical alert fires when more than 0.5% of deliveries fail across at least 500 deliveries in 24 hours.

Who this affects

This is for any business with a custom app doing real work in the background. On the stores we look after, that usually means one of these.

• An ERP integration with Business Central, Odoo or NetSuite that syncs orders, customers, stock or prices.
• A wholesale pricing or account tool that sits behind a B2B storefront.
• A fulfilment export to a 3PL or print on demand provider with no native Shopify app.
• A custom admin screen your team uses every day.

B2B teams feel this most. Trade buyers reorder often and expect their price and stock to be right. A silent webhook failure on a wholesale store turns into a phone call to your office.

If your integration runs through a public app or a middleware platform, this update doesn't cover it. Ask that provider what monitoring they give you. The questions below still apply.

What should you check this week?

You don't need to be a developer to get value from this. Set aside 30 minutes with whoever owns your integration and walk through it together.

1. Confirm who has access. Someone on your side, or your partner, needs app development access to see the dashboard.
2. Open the homepage and check every custom app is listed. Apps nobody remembers are worth a conversation.
3. Look at error rates against request volume. A small, steady error rate on a busy sync can still mean dozens of missed updates.
4. Check webhook delivery health. Order and inventory webhooks are usually the ones your ERP depends on most.
5. Filter the logs to your shop and to failed status codes. Look for patterns by time of day, product or order type.
6. Check admin page speed if your team uses an embedded app screen daily. Slow tools get worked around.
7. Agree what happens next. Decide who looks at the dashboard, how often, and what counts as a problem worth fixing.

The last step is the one most teams skip. A dashboard nobody opens doesn't protect anything.

How this fits a wider integration plan

Logs tell you something went wrong. They don't tell you whether Shopify or the ERP should hold the truth. They don't decide what should happen when a sync fails halfway through an order.

That design work comes first. We map which system owns stock, price, customers and orders before we build. We test the edge cases that break syncs in practice, such as partial refunds, split shipments and customer records created in two places. Then monitoring becomes a routine check rather than detective work.

On Fáilte Foods, the Magento to Shopify Plus move included a Business Central integration with real time order and customer sync. On Surrey Cricket Club, we built a custom export that routes orders to print on demand providers without manual work. Both are the kind of background jobs this dashboard now makes visible.

Where parallel helps

We build and look after custom Shopify apps and ERP integrations. That covers Business Central, Odoo, NetSuite, SAP and Sage. The same people who scope the sync build it, and they can stay on after launch. See how we approach apps and integrations.

If you already have a custom app and want someone watching it, our support packages include uptime and security monitoring from £400 a month. Higher tiers add proactive monitoring and releases tested on staging first.

Not sure what's running behind your store, or who owns it? Book a call and we'll walk through your integrations with you.