Developer changelog

We introduced two new fields that allow you to accurately nest component products under the parent product in a grouped view.

The minimumRequirement field in discount APIs is now optional, allowing null values. This change simplifies discount setup for merchants in version 2025-01.

GraphQL Admin API 2025-01 deprecates customer_id for customer, allowing direct customer association or upsert, simplifying order creation by removing the need to fetch customer IDs.

As of 2025-01, we've introduced concatenatedOriginContract to subscriptionLine .

You can now query the origin contract of the lines if you have used the Subscription Billing Cycle APIs to...

Starting from 2025-01, unused PriceListErrorCode values will be removed.

As of the 2025-01 Admin GraphQL API, you can now query for delivery promise participants, using...

Starting with the Admin API version 2025-01, we have added the sales_line_item_group_id field to the orders webhook. This field allows you to determine if a specific line_item is part of a...

Starting with the Admin API version 2025-01, we've introduced new error codes for the combinedListingUpdate mutation. These enhancements aim to provide clearer feedback when incorrect data is...

Admin API 2025-01 restricts fulfillment hold access via node queries based on app scopes. Ensure correct scopes to avoid null results when fetching holds.

BXGY discounts now support subscriptions if X is a subscription and Y is a one-time or free item. Use GraphQL mutations to create/update discounts, specifying item types with input fields.

As of 2025-01, the ReverseFulfillmentOrder.order field is nullable if the client lacks read_all_orders scope and the order is over 60 days old or missing, avoiding graphql errors.

As of Admin API 2025-01, we have officially introduced a new fulfillment event status called delayed.

When creating or updating a metafield definition's access the admin field is now optional. When admin is not explicitly set, it will default the same way it is when the entire access field...

Starting in API version 2025-01, RELEVANCE will be removed as a valid value from...

The 2025-01 API allows multiple holds per fulfillment order, requires unique handles, and introduces new webhooks. REST API remains limited to single holds.

As of the 2025-01 version of the GraphQL Admin API, you can now use a limit of up to 2000 variants when running a query on a single product, such as product or productByHandle. This...

In Admin GraphQL API 2025-01, handle in product inputs must be unique, preventing duplicates in product creation/updates. Existing behavior unchanged if handle is omitted.

As of Admin API 2024-10, we have introduced a concept of tax_exempt in a CompanyLocationTaxSettings object for a CompanyLocations. This is a generic tax exemption flag for company locations outs

Admin API 2025-01 adds 'event' and 'origin' fields to store credit transactions, enhancing traceability and auditing for better financial reporting and customer service.

Admin GraphQL API 2025-01 removes deprecated fields; use QueryRoot for collection, customer, draft order, marketing, order, and product queries.

Admin GraphQL API 2025-01 moves productTags, productTypes, productVendors to QueryRoot, now paginated and supporting over 250 results, enhancing data retrieval.

New 'inventoryPolicy' argument lets developers override merchant inventory settings in billing mutations, offering flexibility in managing inventory during billing attempts.

As of version 2025-01 of the Admin GraphQL API, we're adding a new LocalizationExtensionsKey value to support the collection shipping credentials for cross-border shipments into Mexico:...

As of GraphQL Admin API version 2025-01, we've added new values to the CustomerPaymentMethodRevocationReason enum to provide more granular information about payment method revocations. This...

As of API 2025-01, you can use discountsNodes() to search for exact discount codes with the code prefix in the query argument.

Using Script Tags? Start ensuring you're targeting the ONLINE_STORE as the displayScope.

Subscription billing now respects inventory policies, preventing overselling. New processingError feature helps identify product variants causing billing errors, enhancing error diagnostics.

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...

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....

Draft orders now auto-update to current prices at checkout. Set custom prices on line items via GraphQL API, locking them for all calculations like taxes and discounts.

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...

As of Dec 4, 2024, Shopify Plus merchants can customize product thumbnails and quantity badge colors in Checkout via the Checkout Branding API. Aspect ratio setting is in unstable release.

Starting in API version 2025-01, PrivateMetafield will be removed from the GraphQL Admin API. Use <a...

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...

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...

GraphQL requests now support application/graphql-response+json format, affecting status codes. Use /graphql endpoint, application/json content type, and updated Accept headers for 2025-01 API.

The Content-Type: application/graphql request format is deprecated and will no longer be accepted as of 2025-01 schema versions. As of 2025-01 schemas, all requests must specify `Content-Type:...

As of the 2025-01 release of the Admin GraphQL API, the deprecated multiLocation field on ShopFeatures will be...

In API version 2025-01, heldBy is replaced by heldByApp in fulfillmentHold. Update queries to fulfillmentHold.heldByApp.title for full app details.

In Admin GraphQL API 2025-01, CalculateExchangeLineItemInput.variantId and CalculatedExchangeLineItem.variant are nullable, but variantId still requires validation.

As of GraphQL Admin API version 2025-01, the accountOpenerName field will be added to shopifyPaymentsAccount

As of version 2025-01, the userErrors field that is returned by the Admin API bulkOperationRunMutation will include an optional code field.

As of GraphQL Admin API version 2025-01, we're cleaning up the shopifyPaymentsBankAccount endpoint and removing several unused fields.

Specifying grants for specific apps on app-owned metafields is now deprecated. New apps will not be able...

As of 2025-01, the default value for the permitsSkuSharing argument in the fulfillmentServiceCreate mutation has been updated to true.

Please be aware that this argument is deprecated and...