Inventory Count Mutation Update, Subscription Cadence, Metafield Deprecations

8/22/2026, 12:00:19 AM

The inventoryCountCreate mutation’s lineItems argument shows a simpler description but remains functionally identical, ensuring backward compatibility. InventoryCount objects received updated descriptions for createdAt, lineItems, and locationSnapshot to clarify intent. InventoryCountLineItem fields expectedQuantity and totalCountedQuantity now contain more precise descriptions, with no type changes. Two new error codes, INVALID_ITEM for InventoryCountCreateUserErrorCode and REFUND_NO_LONGER_ALLOWED for OrderTransactionErrorCode, are now available for error handling. New subscription types, SubscriptionContractCalculationCadence and SubscriptionContractCalculationMultipleFulfillmentConfig, provide detailed cadence information for billing and multi‑fulfillment scenarios. SubscriptionBillingPolicy now includes a mandatory cadence field, and SubscriptionDeliveryPolicy gains a multiFulfillment object describing multiple deliveries per billing cycle. SubscriptionContractCalculationSuccess adds withMerchandiseCustomizations to indicate if customizations affected the calculation. Legacy CollectionSourceInclusionConditionMetafieldInteger objects and inputs have been deprecated; use the new integer equivalents to avoid 32‑bit Int limits.

Mutation Changes

🔄 Modified Mutations (1)

inventoryCountCreate

Creates an inventory count for auditing and adjusting stock levels at a specific location.

Note:
This mutation is available only in the unstable API version and to development stores
that have enabled the Physical inventory feature preview.

~ Modified argument: lineItems

Type Changes

➕ Added Types (2)

🏗️SubscriptionContractCalculationCadence➕ AddedOBJECT

A subscription cadence: a unit of time and the number of units between occurrences.

Fields: count, unit
🏗️SubscriptionContractCalculationMultipleFulfillmentConfig➕ AddedOBJECT

The multiple fulfillment configuration of a subscription delivery policy: how many fulfillments occur in each billing cycle, and the cadence between them.

Fields: cadence, numberOfFulfillments

➖ Removed Types (4)

🏗️CollectionSourceInclusionConditionMetafieldInteger➖ RemovedOBJECT

A condition based on integer metafield values for including products in a collection. This object is deprecated as of API version 2026-10 in favor of CollectionSourceInclusionConditionMetafieldInt, which supports the full integer metafield value range. On those versions this legacy type is only returned to queries that reference it without also referencing CollectionSourceInclusionConditionMetafieldInt.

Fields: definition, id, relation, value
📥CollectionSourceInclusionConditionMetafieldIntegerInput➖ RemovedINPUT_OBJECT

The input fields for a condition based on integer metafield values.

📋CollectionSourceInclusionConditionMetafieldIntegerRelation➖ RemovedENUM

The relation for comparing integer metafield values.

Values: EQUALS, GREATER_THAN, LESS_THAN
📥CollectionSourceInclusionConditionUpdateMetafieldIntegerInput➖ RemovedINPUT_OBJECT

The input fields for updating a condition based on integer metafield values.

🔄 Modified Types (7)

🏗️InventoryCount🔄 Modified
🔄 Field modified: createdAt
🔄 Field modified: lineItems
🔄 Field modified: locationSnapshot
🏗️InventoryCountCreateUserErrorCode🔄 Modified
Enum value added: INVALID_ITEM
🏗️InventoryCountLineItem🔄 Modified
🔄 Field modified: expectedQuantity
🔄 Field modified: totalCountedQuantity
🏗️OrderTransactionErrorCode🔄 Modified
Enum value added: REFUND_NO_LONGER_ALLOWED
🏗️SubscriptionBillingPolicy🔄 Modified
Field added: cadence

The billing cadence associated with the subscription contract.

🏗️SubscriptionContractCalculationSuccess🔄 Modified
Field added: withMerchandiseCustomizations

Whether merchandise customizations were enabled for the calculation.

🏗️SubscriptionDeliveryPolicy🔄 Modified
Field added: multiFulfillment

The multiple fulfillment configuration when the contract delivers more than once per billing cycle, as derived from the billing and delivery cadences. Null when each billing cycle has a single fulfillment.