Events Retention Updated, Input Flattened, Deprecate InventorySetScheduledChanges

2/3/2026, 8:00:11 PM

Channel queries and mutations now use flattened argument names; the collectionCreate and collectionUpdate mutations no longer accept an input object, which means callers must now provide individual fields directly. Event filtering across many resource types has been updated to reference a one‑year retention window, with the created_at filter description amended accordingly in all Event connections and the eventsCount query. The channelFullSync mutation's language and country arguments have been clarified to perform a full sync for all languages or countries when omitted. The inventorySetScheduledChanges mutation has been marked deprecated and will be removed in a future release. New metafield capability types (MetafieldCapabilityCartToOrderCopyable and its input) were introduced and the MetafieldCapabilities type now exposes the cartToOrderCopyable field. Additional enum values were added to CheckoutBrandingColorSchemeSelection (COLOR_SCHEME5 and COLOR_SCHEME6) along with new scheme fields in CheckoutBrandingColorSchemes. Several new error code enum values (INVENTORY_STATE_NOT_ACTIVE, ACTIVATION_FAILED, MISSING_COUNTRY_CODE, INVALID_COUNTRY_AND_PROVINCE_CONDITIONS) were added to improve inventory, market, and transfer error handling. Subsequent document updates throughout object types (Article, Blog, Collection, Comment, Company, etc.) updated the details of the events field arguments, specifically the retention period of event data.

Query Changes

πŸ”„ Modified Queries (3)

channelByHandle

Returns a channel by its handle. The channel must have been established by the calling application.

events

A paginated list of events that chronicle activities in the store. Event is an interface implemented by types such as BasicEvent and CommentEvent that track actions such as creating Article objects, fulfilling Order objects, adding Product objects, or staff comments on timelines.

The query supports filtering and sorting to help you find specific events or audit store activity over time.

~ Modified argument: query
eventsCount

Count of events. Limited to a maximum of 10000.

~ Modified argument: query

Mutation Changes

πŸ”„ Modified Mutations (4)

channelFullSync

Initiates a full sync via Product Feed mechanism for the matching Channel.

~ Modified argument: language
~ Modified argument: country
collectionCreate

Creates a collection
to group products together
in the online store and
other sales channels.
For example, an athletics store might create different collections for running attire, shoes, and accessories.

There are two types of collections:

Use the collectionCreate mutation when you need to:

  • Create a new collection for a product launch or campaign
  • Organize products by category, season, or promotion
  • Automate product grouping using rules (for example, by tag, type, or price)

Note:
The created collection is unpublished by default. To make it available to customers,
use the publishablePublish
mutation after creation.

Learn more about using metafields with smart collections.

- Removed argument: input
collectionUpdate

Updates a collection,
modifying its properties, products, or publication settings. Collections help organize
products together
in the online store and
other sales channels.

Use the collectionUpdate mutation to programmatically modify collections in scenarios such as:

  • Updating collection details, like title, description, or image
  • Modifying SEO metadata for better search visibility
  • Changing which products are included (using rule updates for smart collections)
  • Publishing or unpublishing collections across different sales channels
  • Updating custom data using metafields

There are two types of collections with different update capabilities:

  • Custom (manual) collections: You can update collection properties, but rule sets can't be modified since products are manually selected.
  • Smart (automated) collections: You can update both collection properties and the rules that automatically determine which products are included.
    When updating rule sets for smart collections, the operation might be processed asynchronously. In these cases, the mutation returns a job object that you can use to track the progress of the update.

To publish or unpublish collections to specific sales channels, use the dedicated
publishablePublish and
publishableUnpublish mutations.

Learn more about using metafields with smart collections.

- Removed argument: input
inventorySetScheduledChanges

Set up scheduled changes of inventory items.

Caution:
As of 2026-01, this mutation supports an optional idempotency key using the @idempotent directive.
As of 2026-04, the idempotency key is required and must be provided using the @idempotent directive.
For more information, see the idempotency documentation.

⚠️ Deprecated: Scheduled changes will be phased out in a future version.

Type Changes

βž• Added Types (2)

πŸ—οΈMetafieldCapabilityCartToOrderCopyableβž• AddedOBJECT

Information about the cart to order copyable capability on a metafield definition.
Only order metafield definitions are eligible to have this capability enabled.

When enabled, the value from a cart metafield is automatically copied to the corresponding
order metafield when an order is created. The namespace and key must match between the cart and order metafields.

Fields: eligible, enabled
πŸ“₯MetafieldCapabilityCartToOrderCopyableInputβž• AddedINPUT_OBJECT

The input fields for enabling or disabling the "Cart to order copyable" capability.
This capability is only available for order metafield definitions.

When enabled, the value from a cart metafield is automatically copied to the corresponding
order metafield when an order is created. The namespace and key must match between the cart and order metafields.

πŸ”„ Modified Types (25)

πŸ—οΈArticleπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈBlogπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈChannelπŸ”„ Modified
πŸ”„ Field modified: accountName
πŸ”„ Field modified: specificationHandle
πŸ—οΈCheckoutBrandingColorSchemeSelectionπŸ”„ Modified
βž• Enum value added: COLOR_SCHEME5
βž• Enum value added: COLOR_SCHEME6
πŸ—οΈCheckoutBrandingColorSchemesπŸ”„ Modified
βž• Field added: scheme5

An extra scheme available to customize more surfaces, components or specific states of the user interface.

βž• Field added: scheme6

An extra scheme available to customize more surfaces, components or specific states of the user interface.

πŸ—οΈCollectionπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈCommentπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈCompanyπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈCompanyLocationπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈCustomerπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈDiscountAutomaticBxgyπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈDiscountAutomaticNodeπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈDiscountCodeNodeπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈDiscountNodeπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈDraftOrderπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈHasEventsπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈInventoryShipmentAddItemsUserErrorCodeπŸ”„ Modified
βž• Enum value added: INVENTORY_STATE_NOT_ACTIVE
βž• Enum value added: ACTIVATION_FAILED
πŸ—οΈInventoryTransferπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈMarketUserErrorCodeπŸ”„ Modified
βž• Enum value added: MISSING_COUNTRY_CODE
βž• Enum value added: INVALID_COUNTRY_AND_PROVINCE_CONDITIONS
πŸ—οΈMetafieldCapabilitiesπŸ”„ Modified
βž• Field added: cartToOrderCopyable

The capability configuration for automatically copying values from a cart metafield to the corresponding order metafield when an order is created.

πŸ—οΈOrderπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈPageπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈPriceRuleπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈProductπŸ”„ Modified
πŸ”„ Field modified: events
πŸ—οΈProductVariantπŸ”„ Modified
πŸ”„ Field modified: events