SHOPIFY WEBHOOKS
Shopify webhook timeouts — the five-second window
Shopify waits roughly five seconds for a response. Slow handlers time out, get retried — and repeated timeouts are what ultimately get your subscription deleted. Under load, the spiral is fast.
Why Shopify webhooks fail silently
Heavy work inside the request cycle
Order processing, inventory syncs, and third-party calls inline in the handler routinely blow the window.
Cold starts on serverless targets
A cold function plus a slow dependency can exceed 5s before your code even runs.
Retry storms compound it
Shopify retries failed deliveries — the retries hit an already-struggling endpoint and make it slower.
The fix
- 1
Respond 200 before doing the work
Persist the payload, acknowledge, enqueue the processing. Your handler should do nothing else.
- 2
Keep the webhook path warm
Isolate the webhook handler in a small, hot function — don’t let it share a cold-start profile with your full app.
- 3
Watch p95 on the webhook route specifically
Endpoint-level latency is invisible in app-wide APM averages — monitor the webhook path in isolation.
- 4
Get latency telemetry for free
HookShield records per-forward latency and status — timeout patterns surface on the dashboard before they accumulate into a deletion.
DEAD-MAN'S SWITCH
Never find out about a dead webhook from a customer again
Point Shopify at a HookShield ingest URL. Every delivery is logged, signed, and forwarded — and if pings stop arriving, you're alerted before the silence becomes an incident.