Is the Events API stable enough to migrate products/update off classic webhooks while it's still in preview?

Webhooks and Events
1

We run a Shopify app on Gadget, and products/update webhook volume is our biggest platform cost — include_fields doesn’t gate firing on variant churn, so we get far more deliveries than we need. The Events API’s field-level triggers look like the fix. We’ve already validated it on a dev app (audit-only, in parallel with the webhook).

Our question is about production-readiness, since it’s still developer preview:

  1. Is it stable enough to replace a classic webhook for a core path like product sync — comparable delivery/retry guarantees?
  2. How likely are breaking changes to trigger paths, payload shape, or signing before GA? If they change after we remove the webhook, our sync silently breaks — and that’s merchant-facing (stale prices/images in the storefront).
  3. Recommended safe-migration pattern — keep the webhook as fallback / reconcile periodically, or wait for GA before fully cutting over?

@Harshdeep-Shopify

2

I would not recommend using Events as the sole system in production. We’re working towards getting topics on a stable version and would recommend waiting until then^

3

When should we expect to get stable version of Events?

4

We’ll share more when we get closer to releasing Events in a stable API version^

5

Hi @Harshdeep-Shopify I think it would be greatly appreciated if we could the word ahead of time, and not just two weeks before as they’ve done for the collection API overhaul so that we have time to schedule our own app release. Thank you

6

But this isn’t a breaking change or anything. You can still continue to use webhooks.

7

I know that very well, but it might not be a breaking change, webhooks are a huge cost in our infrastructure and It’s been something we’ve requested for a while.

We’d like to migrate asap. So as soon as we are aware of the final stable api we can start migrating to be ready on day one.