Skip to content
Ecomwith
Back to Intelligence
Platform UpdatesGlobal

Shopify lowers Events subscription query limit from 250 to 100 points

The change applies to Events subscriptions, not Classic Webhooks. Apps using Events should review each subscription query and reduce or split queries that exceed the new per-query limit.

Ecomwith EditorialEcommerce intelligence desk

Published
Updated
Risk
low

Reported details

What happened

Shopify says the Events subscription query complexity limit is changing from 250 points to 100 points; the limit applies to each subscription query.

Complexity depends on selected fields, the types of data they return, and the number of items requested in connections using first or last.

The change does not affect Classic Webhooks, and queries run by Events subscriptions do not count toward an app’s API rate limits.

Business relevance

Why it matters

Apps with Events queries above 100 points may need query changes to stay within the new limit; the supplied announcement does not specify an effective date.

The limit concerns each subscription query, so separating different work into multiple subscriptions may help keep each query within bounds.

Editorial perspective

Analysis & judgment

  1. The limit is about the shape and scope of each Events query, not the app’s API rate allowance. A large connection request or broad selection of fields can raise complexity even when the query serves a single workflow.

  2. Shopify’s variant-price example shows why fetching the changed resource directly can be more targeted than requesting a product’s first 250 variants. This is a change to Events subscriptions, not Classic Webhooks.

Applicability

Seller impact

If your storefront or operations app uses Events subscriptions, ask its developer or vendor whether any subscription query exceeds 100 points and whether the integration needs an update.

If your app relies on Classic Webhooks rather than Events subscriptions, this announcement says the limit change does not affect that workflow.

Action plan

What to do now

  1. 1

    Check Events subscription query complexity

    this-week

    If you maintain an app using Events subscriptions, identify queries above 100 points and review the fields and connection sizes contributing to their scores.

  2. 2

    Consider targeted or split queries

    this-week

    If a query exceeds the limit, evaluate separate subscriptions for distinct work or querying the changed resource directly, while preserving the fields and related data the handler needs.

  3. 3

    Confirm timing and implementation guidance

    monitor

    The supplied announcement does not give an effective date. Check Shopify’s changelog and subscription optimization guidance for timing and any further details before scheduling a migration.

What not to do yet

  • Do not rewrite Classic Webhooks solely because of this announcement; Shopify says they are unaffected.
  • Do not assume splitting a query is safe if the resulting subscriptions omit fields or related data required by the handler.

Sources & context

Evidence and sources

A source may provide only a headline or summary. Read the evidence scope below. Links and workflow checks are not independent fact verification. Internal confidence values are workflow signals, not probabilities of factual correctness.

  1. 01

    We’re reducing the query complexity limit for Events subscriptions from 250 to 100 points. This change does not affect Classic Webhooks. Shopify assigns each Events query a complexity score based on the fields it selects, the types of data those fields return, and the number of items requested in connections using first or last, following the GraphQL query cost calculation. The limit applies to each subscription query, and queries executed by Events subscriptions don’t count toward your app’s API rate limits. What to do Review subscription queries that exceed 100 points and shape each subscription around the changes your app handles: Split subscriptions by the work they do: You can configure multiple subscriptions for the same topic, each with its own triggers and query. Query the changed resource directly: For example, for a variant price change, query the affected variant’s price, SKU, and parent Product ID instead of fetching the Product’s first 250 variants. This avoids repeatedly fetching unchanged variants and covers changed variants beyond the first page. Match queries to available variables: A variant price trigger provides $variantsId, but a product title trigger doesn’t.

    Shopify Developer Changelog · Workflow status: single-source

    Source link

    Retrieved: September 22, 2026 at 06:07 p.m. UTC

    Claim is bounded to the ingested title or summary; no source body or quotation is retained.