--- title: 2022-10 release notes description: Update your app from API version 2022-07 to 2022-10. api_name: release-notes source_url: html: 'https://shopify.dev/docs/api/release-notes/previous-versions/2022-10' md: 'https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md' --- ExpandOn this page * [Breaking changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#breaking-changes) * [Graph​QL Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#graphql-admin-api-changes) * [Graph​QL Storefront API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#graphql-storefront-api-changes) * [REST Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#rest-admin-api-changes) # 2022-10 release notes Note We're no longer publishing API release notes. Instead, you can find the latest updates on Shopify APIs in our [developer changelog](https://shopify.dev/changelog). You can filter updates by area. For example, you can filter API updates by the API name and version, such as GraphQL Admin API changes in version 2025-04. | Release date | Date version is no longer supported | | - | - | | October 1, 2022 | October 1, 2023 | **What's new in 2022-10** The following features were added in version 2022-10 of Shopify's APIs. Highlights from the GraphQL Admin API changes: * Checkout Profiles API * B2B API released * Web Pixel API released * New mutation to bulk activate or deactivate a single inventory item at multiple locations * Support for custom content by market through the Translations API * Location Management API released * Full markets and multi-currency support for `DraftOrders` * `SellingPlan` and `SellingPlanGroup` fields are now supported by the Translations API * New `references` connection on `Metafields` * Metafield support for `Locations` * Duplicate and Create Inventory Reservations in `DraftOrders` * Local Delivery & Pickup for Subscriptions Highlights from the GraphQL Storefront API changes: * You can now use the Storefront API to attach shipping address preferences to the carts of non-logged-in customers and the fetch cart delivery groups through the new `deliveryAddressPreferences` field, which has been added to the Storefront API's `CartBuyerIdentity` and `CartBuyerIdentityInput` objects * New `references` connection on `Metafields` * Querying for `CheckoutProfiles` * New `deliveryAddressPreferences` field added to cart buyer identity objects Highlights from the REST Admin API changes: * New `merchant_of_record_app_id` field on the [`Order`](https://shopify.dev/docs/api/admin-rest/latest/resources/order) object * New `marketing_sms_consent_enabled_at_checkout` field on the [`Shop`](https://shopify.dev/docs/api/admin-rest/latest/resources/shop) object *** ## Breaking changes These changes require special attention. If your app uses these API resources, and you don’t adjust your usage of the resources according to the following instructions, then your app might break when you update to this API version. ### Protected customer data requirements As of version 2022-10, published, public apps that use [GraphQL Admin API](https://shopify.dev/docs/api/admin-graphql) and [REST Admin API](https://shopify.dev/docs/api/admin-rest) resources must meet the [protected customer data requirements](https://shopify.dev/docs/apps/launch/protected-customer-data). The protected customer data requirements focus on data minimization, transparency, and security so that you can better support merchants' path towards compliance with privacy and data protection rules. ### Deleting a reference type metafield definition As of version 2022-10, if you [delete a reference type metafield definition](https://shopify.dev/docs/api/admin-graphql/latest/mutations/metafieldDefinitionDelete) with the `deleteAllAssociatedMetafields` argument set to `false`, then `REFERENCE_TYPE_DELETION_ERROR` is returned with the following error message: Deleting a reference type metafield definition requires deletion of its associated metafields. ### Deprecated Fulfillment cancel endpoint on the REST Order API The `Fulfillment` `cancel` endpoint on the REST Order API is now deprecated: `/orders/{order_id}/fulfillments/{fulfillment_id}/cancel.json`. Use `/fulfillment/{fulfillment_id}/cancel.json` on the `Fulfillment` endpoint instead. ### Deprecated `title` field on `ProductVariant` resource You will no longer be able to register `title` translations on the `ProductVariant` resource. The `title` will be automatically generated using the `option` translations when they are registered. ### Deprecated customer-related `Order` properties The following `Customer` object properties on the REST Admin API's [`Order`](https://shopify.dev/docs/api/admin-rest/latest/resources/order#top) resource have been deprecated: * `last_order_id` * `last_order_name` * `orders_count` * `total_spent` These properties will still be available in the [`Customer`](https://shopify.dev/docs/api/admin-rest/latest/resources/customer#top) resource. ### Deprecated Order and Line​Item properties We've introduced a breaking change to the `LineItem` resource. The `fulfillment_service` field is no longer supported in the REST and GraphQL Admin APIs. Fulfillment services will all be opted into SKU sharing in 2023-04. Consider using one of the following options instead: * [`assigned_location` property on the REST`FulfillmentOrder` resource](https://shopify.dev/docs/api/admin-rest/2022-04/resources/fulfillmentorder) * [`assigned_location` field on the GraphQL`FulfillmentOrder` object](https://shopify.dev/docs/api/admin-graphql/2022-04/objects/FulfillmentOrder#field-fulfillmentorder-assignedlocation) When a fulfillment service app sets `permits_sku_sharing` to `true`, some existing behaviour will break. When a product variant's `fulfillmentService` parameter (REST and GraphQL) is set to `manual`, it no longer means that the variant is stocked only at a merchant-managed location. Therefore, apps that use the `fulfillmentService` parameter in this way should instead use the `location` parameter on the `FulfillmentOrder` resource to determine which location or fulfillment service fulfills for a given line item. The following other line item properties on the REST Admin API's `Order` resource are deprecated: * `origin_location` * `destination_location` The following object property on the REST Admin API's `Order` resource is deprecated: * `total_price_usd` ### Subscription billing cycles We've added subscription billing cycles to the existing Subscriptions Contract APIs so that you can make changes to an upcoming order without affecting the base subscription contract. The following changes are included: * Skipping future orders * Making changes to the line items of an upcoming order, including any additions, quantity changes, or removals * Combining the orders of one or more subscriptions contracts to save on shipping costs Note With the introduction of subscription billing cycles, the `SubscriptionBillingAttemptCreate` mutation will create a billing attempt for the billing cycle at the `origin_time`, if specified. Otherwise, a billing attempt will be created for the current billing cycle by default. ### Changes to Money​V2 related fields The [`Money`](https://shopify.dev/docs/api/admin-graphql/2022-07/scalars/Money) scalar is being removed from the Storefront API. It was previously used for monetary fields that don't have a V2 suffix (`: Money`). As a result, the following changes have been made: * Non-V2 fields now use [`MoneyV2`](https://shopify.dev/docs/api/admin-graphql/2022-07/objects/MoneyV2) objects for their type (`: MoneyV2`). * Monetary fields that do have the `V2` suffix (`V2: MoneyV2`) are deprecated in favor of the `: MoneyV2` equivalent. These fields will be removed in subsequent releases. The Money V2 changes help to improve the consistency of the GraphQL Admin API and make it clearer to use these fields. *** ## Graph​QL Admin API changes The following are all the changes currently introduced in the 2022-10 version of the GraphQL Admin API. ### Deleting a reference type metafield definition #### Breaking As of the API version 2022-10, if you [delete a reference type metafield definition](https://shopify.dev/docs/api/admin-graphql/latest/mutations/metafieldDefinitionDelete) with the `deleteAllAssociatedMetafields` argument set to `false`, then `REFERENCE_TYPE_DELETION_ERROR` is returned with the following error message: Deleting a reference type metafield definition requires deletion of its associated metafields. **New error code** * `REFERENCE_TYPE_DELETION_ERROR` was added to `MetafieldDefinitionDelete` mutation ### Protected customer data requirements #### Breaking As of version 2022-10, published, public apps that use the GraphQL Admin API must meet the [protected customer data requirements](https://shopify.dev/docs/apps/launch/protected-customer-data). The protected customer data requirements focus on data minimization, transparency, and security so that you can better support merchants' path towards compliance with privacy and data protection rules. ### Deprecated title field on Product​Variant #### Breaking You will no longer be able to register `title` translations on the `ProductVariant` resource. The `title` will be automatically generated using the `option` translations when they are registered. Learn more about [`TranslatableResourceTypes`](https://shopify.dev/docs/api/admin-graphql/latest/enums/TranslatableResourceType#value-productvariant). ### Deprecated Order and Line​Item properties #### Breaking We've introduced a breaking change to the `LineItem` resource. The `fulfillment_service` field is no longer supported in the GraphQL Admin API. Fulfillment services will all be opted into SKU sharing in 2023-04. Consider using the [`assigned_location` field on the GraphQL`FulfillmentOrder` object](https://shopify.dev/docs/api/admin-graphql/2022-04/objects/FulfillmentOrder#field-fulfillmentorder-assignedlocation) instead. When a fulfillment service app sets `permits_sku_sharing` to `true`, some existing behaviour will break. When a product variant's `fulfillmentService` parameter (REST and GraphQL) is set to `manual`, it no longer means that the variant is stocked only at a merchant-managed location. Therefore, apps that use the `fulfillmentService` parameter in this way should instead use the `location` parameter on the `FulfillmentOrder` resource to determine which location or fulfillment service fulfills for a given line item. ### Subscription billing cycles #### Breaking We've added subscription billing cycles to the existing Subscriptions Contract APIs so that you can make changes to an upcoming order without affecting the base subscription contract. The following changes are included: * Skipping future orders * Making changes to the line items of an upcoming order, including any additions, quantity changes, or removals * Combining the orders of one or more subscriptions contracts to save on shipping costs Note With the introduction of subscription billing cycles, the `SubscriptionBillingAttemptCreate` mutation will create a billing attempt for the billing cycle at the `origin_time`, if specified. Otherwise, a billing attempt will be created for the current billing cycle by default. ### Disable transactional SMS Due to carrier constraints, Shopify can no longer send customized SMS messages. This change risks a degraded experience for merchants using the feature. You can disable transactional SMS to mitigate a negative impact on the merchant experience. By disabling transactional SMS sent by Shopify, you can enable third parties to take over this job and provide customizable SMS. **New fields**: * `transactionalSmsDisabled` field was added to the [`Shop`](https://shopify.dev/docs/api/admin-graphql/latest/objects/Shop#field-shop-transactionalsmsdisabled) object **New webhook subscription topics**: * `transactionalSmsDisabled` field was added to the [`SHOP_UPDATE`](https://shopify.dev/docs/api/admin-graphql/latest/enums/webhooksubscriptiontopic#value-shopupdate) webhook subscription topic, which is now triggered when the `transactionalSmsDisabled` state of a shop changes ### Bulk activate or deactivate a single inventory item You can now use the new [`inventoryBulkToggleActivation`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/inventoryBulkToggleActivation) mutation to bulk activate or deactivate a single inventory item at many locations, with a maximum of 250 locations at a time. ### Retrieve manually held fulfillment orders You can now use the new [`manualHoldsFulfillmentOrders`](https://shopify.dev/docs/api/admin-graphql/latest/queries/manualHoldsFulfillmentOrders) query to retrieve all of the manually held fulfillment orders for a shop. Fulfillment orders can also be filtered based on `Order` filters: * `order_risk_level` - The fraud risk level of the order. * `order_financial_status` - The financial status of the order * `shipping_address_coordinates_validated` - Whether the shipping address was geolocated and it is a valid address. ### Merchant of Record You can now access information on the application acting as the Merchant of Record on the Order object. This information is only populated for supported applications. **New fields**: * `merchantOfRecordApp` field has been added to the Order object. ### Market​Web​Presence association is accessible through Shop​Locale endpoints As of `2022-10` you can now add, remove, and view the [`MarketWebPresence`](https://shopify.dev/docs/api/admin-graphql/latest/objects/MarketWebPresence) object that's associated with a [`Locale`](https://shopify.dev/docs/api/admin-graphql/latest/objects/Locale) through the [`ShopLocale`](https://shopify.dev/docs/api/admin-graphql/latest/objects/ShopLocale) GraphQL object. **New fields**: * `marketWebPresences` field has been added to `ShopLocale` ### Metafields You can now access a `references` connection on a `metafield`. Use this connection to resolve metafield values of a list reference type to their underlying resource. This new connection is paginated and works similarly to the existing `reference` field, which is used for single references. ### Unpublished locales can now be added to a Market​Web​Presence As of `2022-10` the [`marketWebPresenceUpdate`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/marketWebPresenceUpdate) endpoint now supports adding unpublished locales as `alternateLocales`. ### Support for custom content by market You can now use the Translations API to surface custom content to buyers in a specific market, including custom content for a store's default language. This feature enables merchants to provide localized and custom content, such as: * Support showing regional spelling or preferred terms. For example, a "Sweaters" menu title for a United States market, and a "Jumpers" menu title for a United Kingdom market. * Display promotional content based on the buyer's market. For example, a custom Thanksgiving announcement bar in October for Canadian buyers. **New queries and mutations**: * [`translatableResource`](https://shopify.dev/docs/api/admin-graphql/latest/queries/translatableResource) * [`translationsRegister`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/translationsRegister) * [`translationsRemove`](https://shopify.dev/docs/api/admin-graphql/latest/mutations/translationsRemove) ### Selling​Plan and Selling​Plan​Group fields are now supported by the Translations API The following `SellingPlan` and `SellingPlanGroup` fields are now supported by the Translations API: * `SellingPlanGroup.name` - Public-Facing Name of the Selling Plan Group * `SellingPlan.description` - Optional, more verbose description of the Selling Plan * `SeillingPlan.option1` - Delivery frequency * `SellingPlan.option2` - Delivery frequency (optional) * `SellingPlan.option3` - Delivery frequency (optional) ### New metafield definition types have been added Two new metafield definition types have been added: * `collection_reference`: A reference to a collection on the online store. * `list.collection_reference`: A list of collection references on the online store. ### Duplicate and Create Inventory Reservations in Draft​Orders You now have the ability to do the following on DraftOrders: * Duplicate drafts * Creating drafts from orders * Execute bulk operations such as add/remove tags and deleting drafts * Create drafts with inventory reservations * Access previously hidden fields, such as metafields, on drafts and line items ### Custom and Standardized Product Types have been deprecated in favor of Product Category and Type On the [`Product`](https://shopify.dev/docs/api/admin-graphql/latest/objects/Product) object, the `standardizedProductType` field is deprecated in favor of `productCategory` and the `customProductType` field is deprecated in favor of `productType`. **New fields**: * The `productCategory` field has been added to the `Product` object. ### Full markets and multi-currency support for Draft Orders We have added full support for markets and multi-currency on `DraftOrders`. You will now be able to specify the market region that should apply to a `DraftOrder`, inheriting your configured market settings such as pricing. The selected market region's attributes will be available on their respective objects. Additionally, we have built out full support for multi-currency in draft orders. You will now be able to query a new set of fields that expose all monetary values relevant to a draft order in multi-currency. As part of these changes, you will now be able to use all draft order payment completion flows in multi-currency. Learn more about these fields in the [`DraftOrder`](https://shopify.dev/docs/api/admin-graphql/latest/objects/DraftOrder), [`DraftOrderLineItem`](https://shopify.dev/docs/api/admin-graphql/latest/objects/DraftOrderLineItem), [`DraftOrderAppliedDiscount`](https://shopify.dev/docs/api/admin-graphql/latest/objects/DraftOrderAppliedDiscount), [`DraftOrderInput`](https://shopify.dev/docs/api/admin-graphql/latest/input-objects/DraftOrderInput), [`CalculatedDraftOrder`](https://shopify.dev/docs/api/admin-graphql/latest/objects/CalculatedDraftOrder) and [`CalculatedDraftOrderLineItem`](https://shopify.dev/docs/api/admin-graphql/latest/objects/CalculatedDraftOrderLineItem) API reference. ### Create B2B Draft​Orders via Purchasing​Entity​Input You can use the [`PurchasingEntityInput`](https://shopify.dev/docs/api/admin-graphql/latest/input-objects/PurchasingEntityInput) input object to create and update B2B `DraftOrders`. This input object attaches company, location, and contacts to the `DraftOrder` object. The input object can also be used to create and update a traditional direct-to-consumer (D2C) draft order, requiring only a customer ID. ### Metafield support for locations As of API version 2022-10, the [`Location`](https://shopify.dev/docs/api/admin-graphql/latest/objects/Location) object supports metafields. You can use [metafields](https://shopify.dev/docs/api/admin-graphql/latest/objects/Metafield#fields) to store additional information, such as store hours, and then reference the information in Liquid. ### Local delivery and pickup for subscriptions You can now manage delivery methods of subscriptions contracts with shipping, local delivery, and pickup. A new [`deliveryOptions` field on the `SubscriptionDraft` object](https://shopify.dev/docs/api/admin-graphql/latest/objects/SubscriptionDraft#field-subscriptiondraft-deliveryoptions) provides a `SubscriptionDeliveryOptionResultSuccess` type for all three delivery methods. To edit or create contracts, `localDelivery` and `pickup` fields can be included in the extended [`SubscriptionDeliveryMethodInput`](https://shopify.dev/docs/api/admin-graphql/latest/input-objects/SubscriptionDeliveryMethodInput) input object, which can be used in the `SubscriptionDraftInput`. Note The following considerations apply: * The [`deliveryMethod` field on the `SubscriptionContract` object](https://shopify.dev/docs/api/admin-graphql/2022-04/objects/SubscriptionContract#field-subscriptioncontract-deliverymethod) returns `null` for clients using API versions earlier than 2022-10 when the contract is created with local delivery or pickup. If you've been inferring a subscription has only digital products because the delivery method is `null`, then adopt our new GraphQL changes. * We also recommend taking a look at general delivery terms your app might be using, such as "delivers" or "ships". Consider replacing them with broader terminology like "fulfills" or "recurs" that cover all modes of delivery. ### New mutations for marketing activities You can now use the `marketingActivityCreateExternal` and `marketingActivityUpdateExternal` mutations to create and manage marketing activities, without the need to implement a marketing activity app extension. These endpoints allow app developers to more easily link their marketing efforts, and accompanying tracking information to Shopify, so merchants can have a more complete picture of their marketing performance. **New mutations**: * `marketingActivityCreateExternal` mutation was added * `marketingActivityUpdateExternal` mutation was added ### Subscription billing cycles We have added [subscription billing cycles](https://shopify.dev/docs/apps/build/purchase-options/subscriptions/billing-cycles) to the existing [`SubscriptionsContract`](https://shopify.dev/docs/api/admin-graphql/latest/objects/SubscriptionContract) APIs so that you can make changes to an upcoming order without affecting the base subscription contract. This includes the following changes: * Skipping future orders: * Making changes to the line items of an upcoming order, including any additions, quantity changes, or removals * Combining the orders of one or more subscriptions contracts in order to save on shipping costs ### New mutations to manage locations We have added mutations that allow you to manage your [locations](https://shopify.dev/docs/api/admin-graphql/latest/objects/Location) using GraphQL. The mutations enable you to add, edit, deactivate, re-activate, and delete locations. **New mutations**: * `locationActivate` mutation was added * `locationAdd` mutation was added * `locationDeactivate` mutation was added * `locationEdit` mutation was added * `locationDelete` mutation was added ### B2B APIs are now available We have added queries, objects, and mutations to introspect and manage B2B primitives, including [`companies`](https://shopify.dev/docs/api/admin-graphql/latest/queries/companies), [`company`](https://shopify.dev/docs/api/admin-graphql/latest/queries/company), [`locations`](https://shopify.dev/docs/api/admin-graphql/latest/queries/companyLocations), and [`company contacts`](https://shopify.dev/docs/api/admin-graphql/latest/queries/companyContact) with associated [`roles`](https://shopify.dev/docs/api/admin-graphql/latest/queries/companyContactRole). For a full listing of queries and mutations, refer to the B2B section in the [GraphQL Admin API reference](https://shopify.dev/docs/api/admin-graphql). ### Web Pixel API is now available You can use [web pixel app extensions](https://shopify.dev/docs/apps/build/marketing-analytics/pixels) to connect your marketing and analytics pixels to a merchant's online store for collecting customer events. For more information, refer to the [Web Pixel Extension API reference](https://shopify.dev/docs/api/web-pixels-api). *** ## Graph​QL Storefront API changes The following are all the changes currently introduced in the 2022-10 version of the GraphQL Storefront API. ### Changes to Money​V2 related fields #### Breaking The [`Money`](https://shopify.dev/docs/api/admin-graphql/2022-07/scalars/Money) scalar is being removed from the Storefront API. It was previously used for monetary fields that do not have a V2 suffix (`: Money`). As a result, the following changes are being made: * Non-V2 fields now use [`MoneyV2`](https://shopify.dev/docs/api/admin-graphql/2022-07/objects/MoneyV2) objects for their type (`: MoneyV2`). * Monetary fields that do have the `V2` suffix (`V2: MoneyV2`) are being deprecated in favor of the `: MoneyV2` equivalent. These fields will be removed in subsequent releases. The Money V2 changes help to improve the consistency of the GraphQL Admin API and make it clearer to use these fields. ### New field added to cart buyer identity objects You can now use the Storefront API to attach shipping address preferences to the carts of non-logged-in customers and the fetch cart delivery groups. **New fields**: * `deliveryAddressPreferences` field was added to the `CartBuyerIdentity` and `CartBuyerIdentityInput` objects. ### New references connection on metafields You can now access a `references` connection on a `metafield`. Use this connection to resolve metafield values of a list reference type to their underlying resource. This new connection is paginated and works similarly to the existing `reference` field, which is used for single references. ### New metafield definition types have been added Two new metafield definition types have been added: * `collection_reference`: A reference to a collection on the online store. * `list.collection_reference`: A list of collection references on the online store. ### Access to a shop's brand settings You can now query a shop's brand settings and assets via the new [`Shop.brand`](https://shopify.dev/docs/api/storefront/latest/objects/Brand) field. **New fields**: * The `brand` field has been added to `Shop`. ### Querying for checkout profiles You can now query for a [`CheckoutProfile`](https://shopify.dev/docs/api/admin-graphql/latest/objects/CheckoutProfile) or multiple `CheckoutProfiles`, which provide insights about the profiles on a shop. **New queries**: * `checkoutProfile` query was added * `checkoutProfiles` query was added ### New delivery​Address​Preferences field added to cart buyer identity objects You can now use the Storefront API to attach shipping address preferences to the carts of non-logged-in customers and the fetch cart delivery groups. To attach shipping address preferences, the `deliveryAddressPreferences` field has been added to the Storefront API's [`CartBuyerIdentity`](https://shopify.dev/docs/api/storefront/latest/objects/CartBuyerIdentity) and [`CartBuyerIdentityInput`](https://shopify.dev/docs/api/storefront/latest/input-objects/CartBuyerIdentityInput) objects. **New fields**: * `deliveryAddressPreferences` field was added to `CartBuyerIdentity` object * `deliveryAddressPreferences` field was added to `CartBuyerIdentityInput` input object *** ## REST Admin API changes The following are all the changes currently introduced in the 2022-10 version of the REST Admin API. ### Protected customer data requirements #### Breaking As of version 2022-10, published, public apps that use the REST Admin API must meet the [protected customer data requirements](https://shopify.dev/docs/apps/launch/protected-customer-data). The protected customer data requirements focus on data minimization, transparency, and security so that you can better support merchants' path towards compliance with privacy and data protection rules. ### The Fulfillment cancel endpoint on the Order API has been deprecated #### Breaking The `Fulfillment` `cancel` endpoint on the REST Order API is now deprecated: `/orders/{order_id}/fulfillments/{fulfillment_id}/cancel.json`. Use `/fulfillment/{fulfillment_id}/cancel.json` on the `Fulfillment` endpoint instead. ### Deprecated customer-related Order properties #### Breaking The following `Customer` object properties on the REST Admin API's [`Order`](https://shopify.dev/docs/api/admin-rest/2021-10/resources/order#top) resource have been deprecated: * `last_order_id` * `last_order_name` * `orders_count` * `total_spent` These properties will still be available in the [`Customer`](https://shopify.dev/docs/api/admin-rest/2021-10/resources/customer#top) resource. ### Deprecated Order and Line​Item properties #### Breaking We introduced a breaking change to the `LineItem` resource. The `fulfillment_service` property is no longer supported in the REST Admin API. Fulfillment services will all be opted into SKU sharing in 2023-04. Consider using the [`assigned_location` property on the `FulfillmentOrder`](https://shopify.dev/docs/api/admin-rest/latest/resources/fulfillmentorder) instead. When a fulfillment service app sets `permits_sku_sharing` to `true`, some existing behaviour will break. When a product variant's `fulfillmentService` parameter is set to `manual`, it no longer means that the variant is stocked only at a merchant-managed location. Therefore, apps that use the `fulfillmentService` parameter in this way should instead use the `location` parameter on the `FulfillmentOrder` resource to determine which location or fulfillment service fulfills for a given line item. The following other line item object properties on the `Order` resource are deprecated: * `origin_location` * `destination_location` The following object property on the REST Admin API's `Order` resource is deprecated: * `total_price_usd` ### Cursor-based pagination supported for retrieving locations As of API version 2022-10, [GET requests for a list of locations](https://shopify.dev/docs/api/admin-rest/latest/resources/location#get-locations) are paginated. By default, you can display up to 50 locations on each page. For more information about REST endpoints that support cursor-based pagination, refer to [Make paginated requests to the REST Admin API](https://shopify.dev/docs/api/usage/pagination-rest). ### Disable transactional SMS Due to carrier constraints, Shopify can no longer send customized SMS messages. This change risks a degraded experience for merchants using the feature. You can disable transactional SMS to mitigate a negative impact on the merchant experience. By disabling transactional SMS sent by Shopify, you can enable third parties to take over this job and provide customizable SMS. **New properties**: * `transactional_sms_disabled` property was added to the [`Shop`](https://shopify.dev/docs/api/admin-rest/latest/resources/shop) object **New webhook subscription topics**: * `transactional_sms_disabled` property was added to the [`shop/update`](https://shopify.dev/docs/api/admin-rest/latest/resources/webhook) webhook topic, which is now triggered when the `transactional_sms_disabled` state of a shop changes. ### Order IDs for the Order Risk resource As of API version 2022-10, you can't create or update [order risks](https://shopify.dev/docs/api/admin-rest/latest/resources/order-risk) without specifying an order ID. Previously, you could create order risks by specifying the `order_id` property as `null`. This enabled you to create order risks prior to creating the order and block checkout. However, this functionality isn't used by apps. As a result, the update to specify an order ID isn't a breaking change. ### New Merchant of Record application field on Order object You can now access information on the application acting as the Merchant of Record on the Order object. This information is only populated for supported applications. **New fields**: * `merchant_of_record_app_id` field has been added to the Order object. ### New Marketing SMS Consent property on Shop object A new `marketing_sms_consent_enabled_at_checkout` property has been added to the [`Shop`](https://shopify.dev/docs/api/admin-rest/latest/resources/shop) object. The property is also present on the [`shop/update`](https://shopify.dev/api/admin-rest/latest/resources/webhook) webhook, which now triggers when the `marketing_sms_consent_enabled_at_checkout` state of a shop changes. **New property**: * `marketing_sms_consent_enabled_at_checkout` property was added to the `Shop` resource *** * [Breaking changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#breaking-changes) * [Graph​QL Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#graphql-admin-api-changes) * [Graph​QL Storefront API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#graphql-storefront-api-changes) * [REST Admin API changes](https://shopify.dev/docs/api/release-notes/previous-versions/2022-10.md#rest-admin-api-changes)