Developer changelog

As of Admin GraphQL API version 2025-01, the only valid value for the displayScope field on the ScriptTagInput object is ONLINE_STORE.

The displayScope field remains optional when creating and updating Script tags. When it is omitted from the scriptTagCreate mutation, it will default to ONLINE_STORE from version 2025-01.

This change is related to Script tags being turned off for the Order status page on August 28, 2025, following the launch of UI Extensions on the Thank You and Order status pages.

Hydrogen v2024.10.1 is out today. The December 2024 Hydrogen release contains several quality-of-life improvements, optimizations and bug fixes:

• Support for 2,000 Variants and Combined Listings (#2659)
• Optimized Product Page Performance in Skeleton Template (#2643)
• Multiple <Pagination /> Components Support (#2649)
• Accessibility improvements and DX polish in the Skeleton template.

Check out our full Hydrogen December 2024 release blog post for more details. And please drop your comments, feedback, and suggestions in GitHub Discussions!

As of 2025-01, the admin REST API for the product image resource will return a media image GID instead of a product image GID. This is designed to help make it easier to migrate to GraphQL from REST when interfacing with product images that were created before the introduction of a unified media id.

Previously, the admin_graphql_api_id returned a product image ID: "gid://shopify/ProductImage/43701248884792"

Now, the admin_graphql_api_id will return a media image ID: "gid://shopify/MediaImage/12379812379123"

This change will only affect clients using the latest 2025-01 API version. Older versions will continue to return the ProductImage GID, ensuring backward compatibility. It's strongly recommended to upgrade to using GraphQL as REST is nearing deprecation.

Admin action extensions and admin print action extensions now have access to the resource picker API, allowing merchants select one or more products, collections, or product variants. Additionally they can access the picker API, enabling selection of resources that your app defines.

Get started today by building an admin action extension!

App developers can now configure the "Get Support" button to redirect merchants to your preferred support channel, such as a help desk, ticketing system, forum, or live chat.

Learn more about customizing your preferred app support channel.

All ad types on the Shopify App Store now offer bid suggestions. In addition to search ads, you’ll now see bid suggestions when creating Homepage and Category ads. Bidding within the suggested range can increase the likelihood of your ads being displayed.

Learn more about creating ads in the Shopify App Store.

Changes are coming to how we refer to customer accounts when extensions launch on Dec 11:

New customer accounts will become customer accounts

Classic customer accounts will become legacy customer accounts

This change will take place across all Shopify-owned surfaces, including the Shopify admin, help docs, and dev docs.

Recommended action

As part of this change, we recommend that you make the relevant updates to any references to new and classic customer accounts in your product and documentation.

There will be no breaking changes to APIs or your products as part of this update.

This change reflects the fact that new customer accounts are the future and although we have not yet announced a timeline, classic customer accounts will eventually be retired.

Announcing 150+ updates to Shopify.

See the updates

We just launched the Shopify Subscriptions Reference app, the source code from the Shopify Subscriptions app, which serves as a starting point or example app for merchants and partners looking to build subscription applications.

The reference app can help accelerate app development, provides insight into the Selling Plan APIs and highlights Shopify’s best practices in app development.

Learn more about the Shopify Subscriptions Reference app here.

Developers can now build a single extension using the Purchase Options UI extensions so merchants can more easily create and manage subscriptions, pre-orders, and try-before-you-buy.

To learn more, please visit the developer documentation here.

Effective immediately, apps can manage the storefront and customerAccount access settings for metafield definitions in the merchant namespace. The only acceptable value for admin access remains PUBLIC_READ_WRITE for non app-reserved definitions.

Learn more about access controls for metafields on Shopify.dev.

As of 2025-01 Admin API, you can now make metafield definitions that enforce uniqueness.

The new uniqueValues capability ensures that each metafield has a unique value across all resources. This is available for single_line_text_field, number_integer, url, and id. For now, this capability can only be set on metafield definitions that don’t yet have associated metafields.

As of 2025-01 Admin API, you can use your own identifiers to lookup Products and Customers with the following APIs:

• customerByIdentifier
• productByIdentifier

Custom ids are defined by a new metafield type: id. The unique values capability is required and enabled by default for the id type. The id type unlocks custom ids for Shopify, enabling merchants and partners to specify their own identifiers for objects with metafields.

Following the release of subscription billing attempt respecting merchant’s inventory policy to prevent overselling, we added new features to assist developers in managing billing errors.

As of 2025-01, when accessing billing error details during billing attempts, you can now leverage processingError to identify specific product variants responsible for inventory errors. This update provides better insight into failed billing attempts related to inventory issues by integrating location-specific inventory data directly within the error diagnostics.

Learn more about the Selling Plan API inventory policy.

Shopify Functions input size limit has been increased from 64kB to 128kB. This will enable developers to support a larger number of cart lines.

Learn more about resource limits and how they're calculated for Shopify Functions on Shopify.dev.

Draft orders previously supported most Shopify Functions, but now offer full support of the remaining APIs:

Delivery Customization API: Runs in draft orders admin and checkout.

Payment Customization API: Runs in draft orders checkout.

Cart and Checkout Validation API: Runs in draft orders admin and checkout. Additionally, we have added a new argument named bypassCartValidations that you can pass in the draftOrderComplete and prepareForBuyerCheckout mutations in order to bypass checkout rules when completing or sharing a draft order.

This feature is enabled on all development stores. These enhancements streamline the draft order process, reducing errors and improving the overall experience for both merchants and their customers. Whether creating a draft order in the admin or sending an invoice for customer completion, merchants can rely on the same robust Shopify Function support available in standard checkouts.

Learn more about Shopify Functions in our developer documentation.

Returns are now supported directly through the Customer Accounts API. This includes new fields and a mutation that allow for querying return-related information and self-serve return requests.

This update allows partners to seamlessly build return apps on new customer accounts without needing extra app authorizations. Partners can query returns, create new return requests, and customize the return experience for customers. Additionally, these APIs provide partners with visibility into an order line item's return eligibility, which incorporates Shopify's return rules for merchants with this feature enabled. Partners can determine which items can be returned and the expected refund amount, as well as why items are not returnable.

New APIs:

orderRequestReturn: Mutation that enables the initiation of a return request directly via API. This mutation supports creating a return request on behalf of a customer, allowing the merchant to use the existing return flows within the Admin.

returnCalculate: Query that calculates the potential refund amount based on customer inputs if a return request is approved.

ReturnInformation: Object that provides details about which items in an order are eligible or ineligible for a return.

ReturnConnection: Connection on Order that lists returns associated with an order which includes information such as the return's status or associated reverse deliveries.

For the full set of APIs shipped, please refer to the documentation on Shopify.dev.

With the latest version of App Bridge and Admin UI extensions, you can use the picker API to open a search-based interface to help users find and select one or more resources that you provide, such as product reviews, email templates, or subscription options. Learn more about it in the App Bridge documentation and UI Extensions documentation.

As of 2025-01, item prices on a draft order will automatically reflect the most current product price at checkout. Additionally, you can now set custom prices on draft order line items. When set, the prices will be locked and used as the basis for all further calculations, including taxes, discounts, order totals, etc.

You can set the custom price on a line item using draftOrderCreate, draftOrderUpdate, and draftOrderCalculate by specifying lineItem.priceOverride in the GraphQL Admin API.

All Built for Shopify apps must use the latest version of App Bridge. Update to the latest App Bridge by adding the app-bridge.js script tag to the of every document of your app to meet this requirement.

Starting in July 2025, apps will need to meet this requirement to be eligible for Built for Shopify status.

Built for Shopify now includes new category-specific requirements for Email marketing apps, SMS marketing apps, Ads apps, Analytics apps, Affiliate program apps, and Forms apps. Additionally, the requirements for Subscriptions apps have been updated to require the use of customer account extensions.

Starting in July 2025, apps will need to meet these requirements to be eligible for Built for Shopify status.

Starting July 2025, apps are required to meet the following requirements to achieve or maintain Built for Shopify status.

New category-specific requirements We’re expanding requirements across more categories and updating criteria for Subscription apps: * Ads * Affiliate programs * Analytics * Email marketing * Forms * SMS marketing * Subscriptions (updated criteria)

New design requirements We’re introducing new design requirements including: * Using tabs for secondary navigation * Following UX best practices

Use the latest version of Shopify App Bridge Apps must be embedded in the Shopify admin using the latest version of Shopify App Bridge.

Apps that fail to meet these requirements by the July deadline will be at risk of losing status.

We have introduced new design requirements to our Built for Shopify requirements page. These updates enhance the clarity of our existing design guidelines, making it easier to understand what’s needed to meet the standards for Built for Shopify status.

• Follow UX best practices Your app's UI should demonstrate a good faith effort to leverage common UX best practices and meet a high bar for design quality.

Starting in July 2025, apps will need to meet this requirement to be eligible for Built for Shopify status.

• Use tabs for secondary navigation Use tabs sparingly for secondary navigation purposes when the nav menu isn’t sufficient. Clicking a tab should only change the content below it, not above. Tabs should never wrap onto multiple lines. Navigating between tabs should not cause the tabs to change position or move.

Starting in July 2025, apps will need to meet this requirement to be eligible for Built for Shopify status.

This requirement will replace the following navigation requirement:

Don’t use tabs as primary navigation for your app, since Tabs are used in the Shopify admin as filters on index tables. Use the App Bridge ui-nav-menu web component or NavMenu React component instead.

• For index pages, use full-width layouts For resource index pages, use a full-width page. This is helpful when merchants are dealing with lists of data that have many columns.

This requirement will replace the following layout options requirements:

Use a full-width page when merchants are dealing with lists of data that have many columns.

Don’t use a single-column layout with a full-width page when you’re not dealing with lists of data. This makes the app feel out of place on larger displays. Apps should feel integrated with the Shopify admin.

Keep your app aligned with the Shopify admin by using the Polaris Patterns for common layouts such as index pages and resource detail pages.

• For visual editors, use two-column layouts For visual editors, use a two-column layout. This allows merchants to preview the outcome of their edits in real-time.

This requirement will replace the following layout options requirements:

Complex editors should use the two-column primary/secondary layout in a default-width page. This offers merchants a streamlined editing experience.

Don’t use a two-column primary/secondary layout for your app home page and other pages that don’t require a parent/child relationship between different parts of the interface.

If your app’s page behaves as a dashboard, then use a two-column equal width layout. Use a three-column layout for higher content density.

Don’t use two-column layouts in full-width pages, because it makes your app’s content harder to parse on larger displays.

• For settings pages, use the app settings layouts For settings pages, use the app settings layout to provide merchants with clear context about your app's configuration options.

This requirement will replace the following layout options requirements:

Don’t use annotated layouts for content that isn’t editable. Use a single-column layout instead.

• Place your content in card-like containers Make the majority of your app’s content live in a container, such as a card. This creates visual structure and rhythm that helps merchants find information quickly. Complex components, headings, or images aren’t necessarily required to be in a container.

This requirement will replace the following layout containers requirements:

Make the majority of your app’s content live in a container, such as a card. This creates visual structure and rhythm that helps merchants find information quickly.

Place your app’s content in a card-like container a majority of the time. Complex components or images aren’t necessarily required to be in a container.

• Use black or gray for the majority of text Present the majority of app text in a legible and neutral color, such as black or dark gray.

• *Use green to indicate a successful outcome or status * Green (--p-color-text-success or rgba(1, 75, 64, 1)) should be used to indicate that a status is positive or that an action has been completed successfully. Don't use green to entice merchants or draw unnecessary attention.

• Use yellow to indicate a pending or paused status Yellow (--p-color-bg-fill-caution or rgba(255, 230, 0, 1)) should be used to indicate that a status is on pause or incomplete, or to highlight information that requires merchant attention but isn't urgent. Don’t use yellow for announcements.

• Use orange to indicate an action or item that requires the merchant's attention Orange (--p-color-bg-fill-warning or rgba(255, 184, 0, 1)) should be used to indicate that a status is in-progress, pending, or to tell merchants that something needs their attention. Orange is the strongest, non-blocking color role in the Shopify admin. Don’t use orange for “under construction” or “coming soon” messaging.

• Use red to indicate an unsuccessful outcome or status Red (--p-color-text-critical or rgba(142, 11, 33, 1)) should only be used to convey messaging that implies an action is impossible, blocked, or has resulted in an error. Don't use red to entice merchants or draw unnecessary attention.

The following requirements will be removed:

• Color roles Don't contradict the Color Roles defined by the Polaris design system. In the example above, the dark pink affirming action could be misunderstood as red, which is used in the Shopify admin for destructive actions and critical errors.

• Three-column layouts Set three-column layouts in a full-width page when you’re using them for interfaces like dashboards and analytics. Don’t use three-column layouts to display unrelated content side by side, as it can confuse merchants. Use a single-column layout instead.

Apps can now create and migrate to admin link extensions, which replace both admin links and bulk action links, which were previously created from the Extensions section of your app's Partners Dashboard.

Admin link extensions let you access the same functionality as admin links and bulk action links, but also let you localize links for users, manage links in your app's source control system, and manage their deployment with the Shopify CLI. To upgrade to admin link extensions, follow the tutorial on shopify.dev.

All requirements for achieving Built for Shopify status are now consolidated in one place. The new Built for Shopify requirements page offers a searchable format where you can easily reference all the technical, design, and category-specific requirements.

In the new year we’re simplifying how metafield and metaobject permissions work. This makes the system easier to work with and will further improve API response times.

In summary:

• On Jan 1, 2025, the 2025-01 admin API will remove both private and public permissions for app-reserved metafields and metaobjects from all mutations.
• On Feb 1, 2025, across all API versions, we will fully remove private permissions for app-reserved metafields and metaobjects. We will migrate all existing metafields and metaobjects to be merchant readable automatically. All metafields and metaobjects will also become accessible in liquid.
  
• On Apr 1, 2025, across all API versions, we will fully remove public permissions for app-reserved metafields and metaobjects.We will migrate all existing metafields and metaobjects to be only accessible by your app and the merchant automatically.

Details below:

On Jan 1, 2025:

• The following inputs to app-reserved metafield and metaobject API mutations will be removed in 2025-01: PRIVATE, PUBLIC_READ, PUBLIC_READ_WRITE
• The following outputs from app-reserved metafield and metaobject API queries will be removed in 2025-01: LEGACY_LIQUID_ONLY
• Otherwise, existing queries and data will continue to support these removed input types
  

On Feb 1, 2025:

• The following outputs from app-reserved metafield and metaobject API queries will be removed across all versions:PRIVATE
• Existing app-reserved metafields and metaobjects permissions will be migrated: PRIVATE → MERCHANT_READ
• All metafields and metaobjects will become accessible in liquid
  

On Apr 1, 2025:

• The following outputs from app-reserved metafield and metaobject API queries will be removed across all versions:PUBLIC_READ and PUBLIC_READ_WRITE
• Existing app-reserved metafields and metaobjects permissions will be migrated:PUBLIC_READ → MERCHANT_READ and PUBLIC_READ_WRITE → MERCHANT_READ_WRITE

As of 2025-01, the admin REST API for the product image resource is now deprecated. It is recommended to migrate to GraphQL and use media IDs going forward. The admin_graphql_api_id will return a media image ID to streamline the migration process. More information and a migration guide can be found in the dev docs.

The .dev Assistant now converts REST requests to GraphQL operations. Just copy and paste your REST request, and receive the equivalent GraphQL Admin API query or mutation.

Plus, your conversations with the .dev Assistant just got smarter! You can now ask follow-up questions while maintaining context from your original prompt - no need to start over.

Ready to try it? Head to Shopify.dev and give it a spin.

As of Dec 4th, 2024, you can use the settings under checkoutBrandingInput (see: merchandiseThumbnail) in the Checkout Branding API to modify the appearance of line items in Checkout and Customer Accounts order summary for Shopify Plus merchants.

These line-item customizations include the ability to configure custom aspect ratios for product thumbnails, adjust image fit, and modify the background color of quantity badges. 

Note: The aspect ratio setting is only available on the current unstable release. 

Learn more under checkoutBrandingInput in the Checkout Branding API documentation.

Starting December 5, 2024, app extensions, including admin links, checkout extensibility, and theme app extensions can’t be used to advertise your app, promote related apps, or request reviews.

As of December 4th, 2024, you can now request access to the Chat API to offer real-time customer support on the Checkout and Thank you pages. You will get a new chat component to embed your chat app into Checkout and have complete control over the styling of your interface.

The Chat API allows your chat widget to communicate with your app to query information about the Checkout and Store, like cart details, buyer information, store settings, etc.

Request access to the Chat API through your partner dashboard.

Starting in API version 2025-01, PrivateMetafield will be removed from the GraphQL Admin API. Use app-data metafields instead. If the metafield is needed per resource, consider the migration guide for using app-reserved namespaces.

Apps on Admin API version 2024-10 can use the new optional_scopes app configuration to:

• Separate required scopes from optional
• Request unique sets of access scopes on a store-by-store basis
• Revoke optional scopes granted to the app from a store
• Request and revoke scopes in-context, at app runtime

All while taking advantage of Shopify managed install.

Declaring optional scopes

In your app configuration, specify optional scopes that your app may request, in addition to your app’s required scopes:

[access_scopes]
scopes = "read_products"
optional_scopes = [ "write_products", "read_discounts", "read_themes" ]

Requesting, revoking, and querying optional scopes at runtime

With optional scopes, apps can prompt merchants to grant their app access either from a server-side API, or from a client-side App Bridge API for a more integrated experience. See our documentation on how to request access scopes dynamically for details.

Granted optional scopes can be dynamically revoked from stores by apps. Our APIs supply a revoke method for this, and we also provide a GraphQL appRevokeAccessScopes mutation.

With optional scopes, apps may need to know which scopes are granted on the current store. We supply a query method that lists the granted scopes on the store. Apps can also manually query the accessScopes field on the AppInstallation object.

Learn more

To learn more about optional scopes, see our documentation on how to manage access scopes. See also our client-side App Bridge Scopes API, and our server-side Remix Scopes API.

The JS Buy SDK is deprecated as of January, 2025. It will no longer be updated or maintained by Shopify past that point. A final major version will be released in January 2025 to remove the SDK's dependency on the deprecated Checkout APIs, replacing them with Cart APIs. Updating to this new version will allow the SDK to continue to function for most use cases.

If you are using the JS Buy SDK, you have two options:

1. Recommended Option: switch to the Storefront API Client a. The Storefront API Client manages the API's authentication information and provides various methods that enable devs to interact with the API. This is the preferred and more future-proof solution. See this migration guide to help you transition.

2. Stopgap Option: Upgrade to JS Buy SDK V3 (coming soon) a. This allows you to maintain your current setup with minimal changes for use cases that are supported by the Cart API. A migration guide with details on supported use cases will be available soon. If you choose this option, we still recommend that you switch to the Storefront API Client in the future.

Critical Deadline: July 1st, 2025. You must implement one of these changes by this date, or customers will not be able to complete purchases. Please choose the option that best suits your needs and timelines.

As of 2025-01, you can use the PickupAddress field in both SubscriptionDeliveryMethodPickupOption and SubscriptionPickupOption to query for a customer pickup address.

Learn more about this field at PickupAddress

We've expanded the capability of our discount management system by increasing the limit for automatic app-based discounts from 5 to 25.

This update allows developers to create and manage a larger number of concurrent discount campaigns, offering more flexibility and targeted promotional strategies for merchants. The limit increase enables developers who are currently managing multiple promotions using Shopify Scripts to migrate to Shopify Functions. With the limit increase on Shopify Functions, each discount can be configured with its own start and end dates, giving merchants better precision in promotional timing and controls to govern which discounts can coexist on a cart.

Learn more about discount combinations & limits in the Shopify Dev Docs.

Merchants can now search and browse apps based on a specific category feature in the Shopify App Store. Keep your apps updated with the most relevant category features and follow our best practices.

You can now use more dynamic source attributes in the online store editor. The following new attributes have been added:

• Product: url, featured_image, description
• Collection: url, description
• Article: author, comments_count, content, excerpt
• Blog: content

Learn more about dynamic sources on Shopify.dev.

Apps that are strongly-matched to brand term searches will now be highlighted in search results.

• When a merchant searches for a specific app (e.g. Shopify Inbox), we use organic search results and behavioral data to find the matching app. The high-match app is now prominently featured at the top of search results, above ads.
• This treatment is automatically applied when your app listing is optimized and shows strong branded search match.
• Make sure your app has a specific brand name and follow our best practices around improving organic search.

In addition, we’ve removed the list of restricted keywords previously implemented for search ads.

• More keywords are now available for bidding, including previously restricted brand terms.
• We are ensuring a more equitable advertising environment and to align Shopify's ad products with industry standards and the familiar patterns of other search ad platforms.

As a part of the Customer Account Extensibility Developer Preview, you can now add, remove, or edit menu items in your customer account header menu. This update helps you better understand how merchants will be able to add any type of link to their customer accounts main menu.

Included in this update:

All full-page extensions are now linkable - Before this update, full-page extensions had to be explicitly declared as linkable. Now, all full-page extensions will be linkable by default and merchants will be prompted in the checkout & accounts editor to add a link to your full-page extension in the header menu. To take advantage of this change, deploy a new version of your extension.

To prevent merchants from linking to your page, declare your extension as not linkable.

Add any type of link - Including links to default online store pages (products, collections, pages), customer account pages (order, profile and settings), customer account apps (full-page extensions), as well as any URL. By default, the menu will link to online store (Home), and Orders.

Use the same menu across online store & customer accounts - Merchants will be able to use the same menu in their online store and customer accounts.

Navigation has moved - You can now find the navigation tool in Admin > Content > Menus. It has been moved from its original location of Online Store > Navigation.

You can learn more about full-page extensions here.

As of GraphQL Admin API version 2025-01, the manualPaymentGateway field will be added to orderTransaction object. This field indicates if the transaction is processed by a manual payment gateway.

Category-specific criteria are now available. This feature gives developers more clarity on the category-specific criteria that apply to certain Built for Shopify apps. To view or update your app's category, check its distribution page in your Partner Dashboard.

Your app's pre-selected category is based on its categorization in the Shopify App Store. You can update your category based on your app's functionality. Built for Shopify reviewers have final approval on all categorizations.

Starting in January 2025, all Built for Shopify reviews will require accurate categorization. This applies to existing Built for Shopify apps, as well as new applications.

As of Shopify CLI 3.70, existing Marketing Activity Extensions can be migrated from the Partner Dashboard to CLI. Learn more about how to import and migrate your Marketing Activity Extensions to CLI here

As of Nov 12, 2024, you can use the HideOperation in the Payment Customization Function API to disable native gift card functionality and Shopify-integrated third-party gift card systems. Disabling gift cards hides the gift card field, removes any applied gift cards, and prevents any gift cards from being applied by UI extensions.

The ability to disable the gift card field is available in the unstable API version and will be released to the stable 2025-01 API version.

Learn more about payment customizations.

As part of a move towards open-source fonts, and in an effort to refine our font offerings, we have deprecated some fonts in our library. We’re also expanding the library of open-source fonts, with 32 new high quality typefaces available today.

Action Required: For theme developers with published themes in the Shopify theme store using any of the deprecated fonts, please replace your default font for each preset by January 3, 2025. We have provided recommended replacements in the developer documentation that maintain a similar style to the deprecated font, or you can choose any other available font from our library.

Merchants who are currently using deprecated fonts will be prompted to make updates at a later date.

As of today discount apps can use Admin UI extensions to embed discount configuration UI directly into the discount details page.

Admin UI extensions are hosted by Shopify, which means you no longer need to build and maintain your own web infrastructure to host the UI that configures your discount function's metafields.

Learn more by following this tutorial on building a discount UI with UI extensions and browse the available Admin UI components here.

The Built for Shopify category-specific criteria assessments are now available for Fulfillment service apps. You can review whether these requirements apply to your Built for Shopify app by checking its distribution page through your Partner Dashboard.

These assessments apply to existing Built for Shopify apps, as well as new applications.

On February 28, 2025, POS Links, POS cart app extensions, and POS product recommendations will be deprecated. Developers and merchants will no longer be able to view or access these extensions in Shopify POS.

We recommend you rebuild legacy extensions with POS UI Extensions. Not only do POS UI Extensions have extensive capabilities today, but we’ll continue to grow these capabilities into the future.

POS Links: * Recommendation: Rebuild using POS UI Extensions * Alternative: Embed your app within Shopify POS via the Partner Dashboard, Please note that merchants can manually add and access these from the smart grid.

Cart App Extensions and Product Recommendation Extensions: * Recommendation: Rebuild using POS UI Extensions. POS UI extensions provide necessary components and APIs to develop extensions that run natively on Shopify POS.

If you have any questions, please contact partner support for assistance.

As of 2025-01 the metafieldDelete Admin API method is being removed. The metafieldsDelete method should be used instead. The former relies on the Metafield GID, while the latter takes an array of Metafield Identifiers composed of ownerId, namspace, and key. Note that the Metafield GID is not an option in metafieldsDelete.

As of the latest Shopify’s Standard Product Taxonomy version 2024-10, you can now find additional categories, attributes and values across product areas such as Apparel & Accessories, Home & Garden, Sporting Goods, and more. The taxonomy is an evolving library that’s informed by user feedback and market insights, with each release aiming to help you more accurately classify your products.

More details about this update can be found in the release notes.