Shopify Next Gen Events GA: fewer webhooks, no follow-up calls

Shopify made Next Gen Events generally available in Admin API version 2026-10. Events are a declarative replacement for classic webhooks: you say which change you care about, which data you want, and which records qualify. Shopify runs your GraphQL query and puts the result in the delivery. If your custom app gets a webhook, throws most of them away, and then calls the API for the rest, this is the fix.

What actually happened

Per Shopify's changelog, published October 1:

• Three parts per subscription. A trigger (the change to watch, for example a product joining or leaving a collection), a query (a GraphQL Admin API query for the data you need), and a query filter (for example, only ACTIVE products).
• Trigger and query are independent. A change on one field can fetch completely different data.
• 18 topics. Product, Collection, Customer, Company, Order, FulfillmentOrder, Refund, Return, InventoryItem, InventoryShipment, InventoryTransfer, Location, Article, Blog, Page, MetafieldDefinition, Metaobject, and MetaobjectDefinition.
• Payload. The action and topic, your query result, a fields_changed object, and query_variables with resource IDs. The query runs at delivery time, so data is the current state and fields_changed tells you what moved.
• Configured in shopify.app.toml. Not in the admin UI.
• Classic webhooks still work. Shopify says you can run both in one app and move workflows over one at a time. No deprecation date is announced.

Why it matters for your business

Most Shopify integrations we audit have the same shape: subscribe to products/update, receive thousands of deliveries a day, discard most of them, and call the API for the rest. That burns rate limit, adds a failure point, and slows your sync at exactly the moment a flash sale needs it fast.

Events moves the filtering and the follow-up query to Shopify's side. A sync to your ERP can subscribe only to inventory changes on active products, with the SKU and location already in the payload.

Where to start:

1. Find your noisiest webhook. Count deliveries against actions taken. The worst ratio is the first migration.
2. Find the webhook that always triggers an API call. That follow-up query becomes the Event's query.
3. Keep idempotency. The payload reflects state at query time, not at change time. Your handler still has to tolerate repeats and out-of-order updates.
4. Move to 2026-10 on purpose. Upgrade the app's API version deliberately before you add Event subscriptions.

Sources: Shopify changelog, Shopify developer changelog.