See all services → Shopify Plus Partner
API Developer

Check Timestamp Filters Before Moving to API 2026-10

API version 2026-10 changes how an exclusive greater-than bound on a timestamp filter behaves. Incremental order and inventory syncs that pass a previous response timestamp back as a cursor can silently skip records. Here is what to verify before you upgrade.

Executive summary

What changed

Shopify returns timestamps such as createdAt at second precision, but several resources store them internally with fractional seconds. Before 2026-10, a filter of created_at:>'2026-09-15T12:00:02Z' was compared against 12:00:02.000000, so a record created at 12:00:02.500 matched it. That same record also matched created_at:<='2026-09-15T12:00:02Z', which meant the two ranges overlapped.

From 2026-10, a greater-than value carrying no fractional component starts the window after the end of that second, at 12:00:02.999999. A record matches only when the timestamp the API returns for it is genuinely later than the bound, so the greater-than and less-than-or-equal ranges stop overlapping. Nothing changes, on any version, for the other comparators, for date-only values, or for values that already include fractional seconds.

Why it matters

The old overlap was quietly absorbing a design flaw in a lot of integrations. A connector that stores the latest createdAt it has seen and passes it back as a greater-than bound was relying on second-level truncation to re-fetch the boundary record, then discarding it as a duplicate. Under the new behaviour that same pattern does the opposite: anything created later in the boundary second is skipped, permanently, because the cursor has already moved past it.

The upside is that windows are now deterministic. Adjacent reporting ranges no longer double count the same order, which makes reconciliation against finance systems cleaner. The cost is that incremental sync now needs explicit deduplication. This is the same class of issue we surface in most ERP integration reviews: the sync logic is correct in testing and loses records only under volume.

Role-specific impact

Use-case example

Real-world scenario

A Plus merchant polls orders every five minutes and passes the createdAt of the last order it processed as a greater-than bound. During a promotion running near 90 orders per minute, more than one order frequently lands inside the same second. With 288 polling windows a day, if even a third of boundaries fall on a second holding a second order, roughly 95 orders a day never reach the ERP. Those surface as missing fulfillments and inventory drift. Switching the bound to the inclusive comparator and deduplicating by id removed the gap without changing the polling interval.

Implementation checklist

  1. Inventory every integration that sends a query argument to an Admin API connection, including custom apps, scheduled middleware jobs, and internal reporting scripts.
  2. Search those queries for timestamp comparators and flag each greater-than bound that has no fractional seconds.
  3. For each flagged query, decide whether a missed record is tolerable. For order, payment, and inventory sync it is not.
  4. Replace the exclusive bound with the inclusive one and deduplicate results by id in your own code before writing downstream.
  5. Persist the set of processed ids alongside the last timestamp so that a rerun stays idempotent.
  6. In staging, move the integration from its current version to 2026-10 and replay a high-volume hour, comparing record counts against the old version.
  7. Schedule the production version bump outside peak trading and watch downstream record counts for a full day afterwards.

FAQ

Q: Do we need to change anything if our apps stay on 2026-07 or earlier?

A: No. The behaviour applies only from 2026-10 onward, so this belongs in your version upgrade test plan rather than on your incident list.

Q: Is the inclusive comparator plus deduplication the only safe pattern?

A: It is the simplest and our default recommendation. If your cursor can store and send full fractional precision, passing a microsecond-accurate value to the exclusive comparator also works, provided every component in the chain preserves that precision.

Resources

Shopify API search syntax reference

Need guidance? Talk to Makro.