Reported details
What happened
In API version 2027-01, Shopify is removing the metafieldInteger collection source condition inputs and types from the GraphQL Admin API.
The replacement is metafieldInt, including updated condition types and input fields for creating, updating, and reading collection source conditions.
The integer condition value changes from an Int to a String, while the EQUALS, GREATER_THAN, and LESS_THAN relation members remain unchanged.
The supplied evidence comes from the official Shopify Developer Changelog and is marked single-source; no additional source body or quotation is retained.
Business relevance
Why it matters
A version upgrade can break collection-condition integrations if they still send the removed field names or expect the old value type.
The change affects both write and read paths, so updating mutation payloads alone may leave queries or type fragments incompatible.
Because the relation names remain stable, the migration is focused on schema names and value serialization rather than a stated change to the available comparison operators.
Editorial perspective
Analysis & judgment
The mechanism is a GraphQL schema migration paired with a serialization change: metafieldInt replaces the older condition names, and its value is represented as a String. That changes the integration contract at both the field and literal levels, so a merchant should inspect generated types, mutation builders, and query fragments before selecting API version 2027-01. The evidence confirms the named replacements and type change, but does not describe runtime error behavior or every affected client library.
The merchant consequence is concentrated in workflows that use integer metafields to create, update, or read collection source conditions. If those workflows are present, an upgrade can turn a previously valid automation into an incompatible request or response handling path; if they are absent, this migration may not require seller-facing changes. The evidence does not establish how many merchants or apps use these conditions, so impact should be assessed from the merchant’s own code and configuration inventory.
The decision rule is to postpone the API-version upgrade until every discovered metafieldInteger reference has a corresponding metafieldInt update and the value is handled as a String; otherwise, keep the current version while remediation continues. Watch for the version target used by each app and for both read and write references, because the supplied evidence does not provide a separate deadline, testing guidance, or compatibility guarantee for partially migrated integrations.
Applicability
Seller impact
Merchants with custom apps, middleware, or scripts that manage collection conditions should treat this as an integration-readiness issue rather than a storefront configuration change.
Merchants that do not use integer metafield collection conditions may have no direct action, subject to confirming that neither their apps nor operational tooling reference the removed schema.
App developers serving merchants globally should make the migration conditional on detecting the affected fields, since the supplied market applicability is global but usage is not established.
Action plan
What to do now
- 1
Inventory affected references
nowSearch app code, generated GraphQL types, queries, mutations, and configuration for metafieldInteger and CollectionSourceInclusionConditionMetafieldInteger references. Include both collection-condition reads and writes.
- 2
Prepare the schema and value migration
this-weekReplace affected references with metafieldInt equivalents and serialize the integer condition value as a String, while preserving the existing relation members where applicable.
- 3
Validate before changing the version target
this-weekReview generated types and integration checks for both mutation payloads and query fragments before moving an affected app or workflow to API version 2027-01.
- 4
Track version assignments
monitorMonitor which apps and environments are scheduled to use API version 2027-01, and reassess any integration that still contains the removed field names.
What not to do yet
- Do not assume that changing metafieldInteger to metafieldInt is sufficient without also changing the condition value representation from Int to String.
- Do not upgrade affected integrations based only on unchanged relation names; the supplied evidence requires checking both read and write paths.
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.
- 01Source link
As of API version 2027-01, the metafieldInteger collection source condition inputs and types is removed from GraphQL Admin API. If you use metafieldInteger to create or read collection source conditions, you need to migrate to metafieldInt before you upgrade to API version 2027-01. What changed With metafieldInt, the value field on integer metafield conditions changes type from Int to String, to align with the metafield value field on the Storefront API. For details, see the Storefront Metafield.value field reference. The following types and fields are replaced: CollectionSourceInclusionConditionMetafieldInteger is replaced by CollectionSourceInclusionConditionMetafieldInt CollectionSourceInclusionConditionMetafieldIntegerRelation is replaced by CollectionSourceInclusionConditionMetafieldIntRelation CollectionSourceInclusionConditionInput.metafieldInteger is replaced by CollectionSourceInclusionConditionInput.metafieldInt CollectionSourceInclusionConditionUpdateInput.metafieldInteger is replaced by CollectionSourceInclusionConditionUpdateInput.metafieldInt The relation enum members are unchanged (EQUALS, GREATER_THAN, LESS_THAN). The behavioral difference is that value is now a Str
Shopify Developer Changelog · Workflow status: single-source
Retrieved: October 1, 2026 at 08:07 p.m. UTC
Claim is bounded to the ingested title or summary; no source body or quotation is retained.