Merchant-owned delivery profile APIs are deprecated for market-driven shipping

What's changing

We’re moving merchant-owned shipping configuration from legacy delivery profiles to Markets as part of market-driven shipping, a new model where shipping is configured per Market.

When a shop uses market-driven shipping, the legacy delivery profile fields and mutations in the Admin GraphQL API no longer represent the shop’s live merchant-owned shipping configuration. Reads may return a stale snapshot of the legacy configuration, and writes may succeed without errors but will not update the merchant’s live shipping settings.

This affects merchant-owned usage of the following Admin GraphQL delivery profile APIs:

• deliveryProfile
• deliveryProfiles
• deliveryProfilesCount
• deliveryProfileLocationGroup
• deliveryProfileLocationGroups
• deliveryProfileCreate
• deliveryProfileUpdate
• deliveryProfileRemove

App-owned delivery profiles aren’t affected and continue to function as before.

What to do

If your app currently reads or manages merchant-owned shipping configuration, you must follow the upgrade guide for market-driven shipping. The guide explains how to:

• Detect shops that are using market-driven shipping.
• Stop relying on merchant-owned delivery profile APIs for those shops.
• Migrate to Contextual Product Feeds, app-owned delivery profiles, or Markets APIs, depending on your use case.