All packsWebhook Durability & ReplaySolve
shopify webhook dropped after 4 hours no replay api
Shopify retries for 4 hours, then the event is just gone
Shopify's webhook retry budget is 8 attempts over 4 hours with no replay API afterward -- Shopify's own docs say not to rely on webhook delivery and to build reconciliation instead (D3, D13).
This is one of the things Webhook Durability & Replay already handles. Receive webhooks without losing, duplicating or misordering them when the sender retries.
Is this you?
After 8 retries over 4 hours, a failed Shopify webhook delivery is gone permanently -- there is no dashboard resend, no API replay, nothing. After 8 consecutive failures Shopify additionally deletes an Admin-API-created subscription outright and emails a warning, so a struggling endpoint doesn't just lose events, it loses its own subscription to future ones.
Why this one is easy to get wrong
Every other major webhook provider in this pack's own comparison table offers some recovery path -- Stripe's event history, Apple's notification history, Google Play's Pub/Sub seek -- so "the provider will let me replay it later" is a reasonable assumption right up until Shopify is the one being integrated. Shopify's own docs state the opposite outright: "your app shouldn't rely on receiving data from Shopify webhooks."
What you get instead
Because there is genuinely no replay API, the pack ships a resources-mode backfill source instead: the Shopify reconciler polls the Admin API on updated_at and synthesizes a webhook-shaped delivery from the response, with the same headers Shopify would have sent and a stable delivery_id so a repeated reconcile can't double-count. The honest limit is stated too: a resources-mode source can only recover what's derivable from a current snapshot, never a missed increment, which is why an accumulate handler's effect key must be derivable from the resource itself.
Source: ARCHITECTURE.md D3, D13 — checkable in the pack you receive
How you actually use this
You don’t install a library or wire up an SDK. Your own coding agent builds the code in your project, and you keep it — no runtime dependency on us.
Step 1
Download and unzip
You get a folder: the docs that tell an agent what to build, a starting skeleton, and the test suite that decides when it's done.
Step 2
Open it in Claude Code or Cursor
Point your coding agent at the folder. Nothing to install, no account with us, no API key.
Step 3
Paste one prompt
The pack contains the exact prompt. Paste it as your first message and leave it alone — it works through the build itself, choosing a cheaper or stronger model per task.
Step 4
Run ./verify.sh
One command. It prints a pass or fail for every check. Green means the build is done — the same script we ran to produce the receipt on this page.
Typical build: about 40 minutes of your agent working, mostly unattended. Then you integrate the working module into your app the way you would any code you’d written yourself.
Why you can believe this
3 of 3 runs passedWe ran this pack from an empty folder 3 times and published exactly what happened — every check, the model, the token cost, the wall time. Not a testimonial, and not our opinion: the same verify.sh you run yourself. Read the full receipt →