Back to Intelligence
Platform UpdatesGlobal

Shopify Functions can now read metafields on delivery options

A global Shopify platform update adds temporary delivery-option data to the 2026-10 Functions input, giving eligible apps more structured information to use during checkout.

Ecomwith EditorialEcommerce intelligence desk

Published
Updated
Risk
low

Reported details

What happened

On API version 2026-10, Shopify Functions can query metafields on options in cart.deliveryGroups.deliveryOptions.

The returned metafield can expose its value, type, and jsonValue, but the data is not persisted after checkout.

Delivery option generator functions and shipping carrier service responses can attach the data; downstream Delivery Customization Functions can then read app-reserved or unprefixed shared namespaces.

The field is available wherever the Functions input includes delivery options, while legacy Order Discounts and Product Discounts APIs have empty cart.deliveryGroups and therefore return no value.

Business relevance

Why it matters

For apps that generate and customize delivery options, structured metadata can pass between functions without relying on delivery-option titles or handles.

The update is relevant globally to apps using the affected Shopify Functions inputs, but it does not change behavior for apps that do not query the new field.

Editorial perspective

Analysis & judgment

  1. This is primarily an integration simplification, not a new persistence layer: the metadata can support decisions during the current checkout but should not be treated as an order record.

  2. Namespace ownership remains a boundary. A function can read its own app-reserved namespace and unprefixed shared namespaces; a namespace reserved by another app resolves to null.

Applicability

Seller impact

Merchants using delivery-generation or delivery-customization apps may see more reliable coordination between those components once the app adopts API version 2026-10.

Merchants should not expect this update to make delivery-option metadata available for later reporting, fulfillment, or order-history workflows.

Action plan

What to do now

  1. 1

    No immediate change is required

    now

    Because the source states that no action is required, keep existing delivery-function configurations unless an app provider identifies a specific use for the new field.

  2. 2

    Ask app owners whether they will adopt the field

    this-week

    If your stack uses delivery option generation and customization, confirm whether the relevant app supports API version 2026-10 and passes metadata through the intended namespace.

  3. 3

    Review metadata handling before relying on it

    monitor

    If an app plans to use the field, verify that checkout-only metadata is consumed during checkout and is not expected to persist after checkout.

What not to do yet

  • Do not redesign delivery workflows solely because the schema now exposes the field, and do not assume it will return values in legacy Order Discounts or Product Discounts APIs.

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.

  1. 01

    Shopify Functions can now read metafields attached to delivery options in the cart. On API version 2026-10, you can call metafield(namespace:, key:) on any option in cart.deliveryGroups.deliveryOptions. This affects apps that build Delivery Customization Functions and any other function whose input includes delivery options. No action is required. What changed In the Functions cart graph, CartDeliveryOption now includes a metafield field: metafield(namespace: String, key: String!): Metafield The returned Metafield exposes value, type, and jsonValue. Metafields on a delivery option are not persisted after checkout. A delivery option generator function or shipping carrier service response attaches them when it generates the option, and they exist only for that checkout. Access follows the existing metafield ownership rules. A function can read metafields in its own app‑reserved namespace and in any unprefixed shared namespace. A namespace reserved by a different app resolves to null. A Delivery Customization input query can now read both app-reserved and shared metafields on delivery options. For example: { cart { deliveryGroups { deliveryOptions { handle ownNamespace: metafield(name

    Shopify Developer Changelog · Workflow status: single-source

    Source link

    Retrieved: September 15, 2026 at 02:07 p.m. UTC

    Claim is bounded to the ingested title or summary; no source body or quotation is retained.

Related tutorials and tools

Ecomwith tutorials
Shopify Functions can now read metafields on delivery options - Ecomwith Intelligence