Useful Automation/Brief
Shopify Functions can now read metafields on delivery options
Shopify Functions can now read metafields attached to delivery options in the cart on API version 2026-10.
On API version 2026-10, Shopify Functions can read metafields attached to delivery options in the cart. You can call metafield(namespace:, key:) on any option in cart.deliveryGroups.deliveryOptions. The returned Metafield exposes value, type, and jsonValue. Metafields on a delivery option are not persisted after checkout; they are attached when a delivery option generator function or shipping carrier service response generates the option, and exist only for that checkout. Access follows existing metafield ownership rules: a function can read metafields in its own app-reserved namespace and in any unprefixed shared namespace, while a namespace reserved by a different app resolves to null. This affects apps that build Delivery Customization Functions and any other function whose input includes delivery options. No action is required.
What the reporting says
Each line below is stated by the page named above it, and only by that page.
Stated by shopify.dev
- Delivery options in Shopify Functions input now expose their metafields.
- On API version 2026-10, you can call metafield(namespace:, key:) on any option in cart.deliveryGroups.deliveryOptions.
- Metafields on a delivery option are not persisted after checkout.
- 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.
- No action is required.
Our view
This simplifies workflows for Delivery Customization Functions by allowing them to read structured data directly instead of relying on workarounds like packing data into option titles or handles.
What the reporting says: On API version 2026-10, Shopify Functions can now read metafields attached to delivery options in the cart, and that no action is required.
Sources
- Shopify developer changelogText stored 16 September 2026 · checked 16 September 2026
Found through monitored feeds: Shopify developer changelog. A feed address is how the desk finds a story, not the evidence for it — the sources listed above are the pages the facts were taken from.
How this story was checked. Written from the 1 page listed above, stored 16 September 2026; claims checked against that stored text on 16 September 2026.
What that means
- 6 of 6 reported statements were confirmed against the page that carries them; the rest were removed rather than published.
- Figures in the text were required to appear in the stored source text: yes. Identifiers: yes.
- The check reads stored text only: no claim rests on a fresh look that did not happen.
- Where the reporting was silent, the text says so instead of filling the gap.