Shopify GraphQL Admin API Changes Exclusive Timestamp Filter Behavior

What Changed

Starting with API version 2026-10, exclusive lower bound (>) timestamp filters in the GraphQL Admin API search syntax now exclude the entire second specified, not just the exact millisecond.

Previously, a query like created_at:>'2026-09-15T12:00:02Z' compared against the timestamp 12:00:02.000000. This meant records created within that same second but with fractional seconds greater than zero, such as 12:00:02.500, were still returned since they technically occurred after the .000000 mark.

Under the new behavior, the same filter now excludes the full second. A record created at 12:00:02.500 will no longer match created_at:>'2026-09-15T12:00:02Z', since the filter treats the entire second as the boundary rather than a precise sub-second timestamp.

This change applies to search syntax filtering on timestamp fields such as created_at across resources queried through the GraphQL Admin API.

Why This Matters for Shopify App Developers

Many Shopify apps rely on timestamp-based filtering to implement incremental syncs, webhook replay logic, or polling mechanisms that fetch records created or updated since a specific point in time. Apps that use exclusive timestamp filters to avoid reprocessing the last fetched record may now skip records that fall within the same second as the filter boundary.

This is particularly relevant for apps handling high-volume stores where multiple orders, products, or other resources can be created within the same second.

Practical Implications

Developers should review any GraphQL queries using exclusive (>) timestamp comparisons in search filters. Consider the following:

• Audit sync jobs that use created_at:> or similar exclusive filters for incremental data fetching
• Test pagination and polling logic against API version 2026-10 before upgrading
• Evaluate whether inclusive filters (>=) combined with deduplication logic better suit your use case
• Review Shopify’s API versioning documentation to confirm when this behavior takes effect for your app

Apps pinned to earlier API versions are unaffected until they migrate to 2026-10 or later.

Read the full announcement →