DEPRECATIONADMIN GRAPHQL API

Merchant-owned delivery profile APIs are no longer the live shipping model.

For shops using Market-driven shipping, legacy merchant-owned delivery profile reads can become stale and writes can succeed without changing the merchant’s live shipping configuration. App-owned delivery profiles are not affected by this deprecation.

AUDIT THESE SURFACES

Find the dependency before choosing the replacement.

deliveryProfile / deliveryProfiles / deliveryProfilesCount
Merchant-owned location-group and zone assumptions.
deliveryProfileCreate, deliveryProfileUpdate, and deliveryProfileRemove when they target merchant-owned configuration.
Any cached or synchronized external representation of merchant shipping configuration.

REPLACEMENT LOGIC

The right path depends on what your app is doing.

Read-heavy sales-channel use case: evaluate contextual product/delivery data.
Direct merchant configuration reads: use the Markets API for shops on Market-driven shipping and preserve the legacy branch during transition.
Merchant-owned writes: prefer an app-owned delivery profile when it can represent the app’s rates; otherwise use the Markets API.
App-owned profile: keep the existing delivery profile APIs for your own profile.

FREE READINESS CHECK

Turn the API audit into a migration path.

ShipReady separates merchant-owned reads, writes, app-owned profiles, preview testing, and compatibility confirmation.

Run ShipReady →

OFFICIAL REFERENCE

Shopify developer changelog: merchant-owned delivery profile API deprecation ↗

Independent implementation aid. Re-check current Shopify documentation before release.