Upgrade decision guide

Choose the right market-driven shipping migration path.

The correct replacement depends on whether your app owns the profile, reads merchant configuration, writes it, or can become a sales channel.

NowFeature previewTest in a development store

Oct 1, 2026Merchant rolloutCompatibility warnings begin

Jul 1, 2027Full migrationAll merchants on the new model

01Preferred where applicable

App-owned DeliveryProfile

Choose this whenYour app creates and manages only its own rates.

Upgrade actionKeep the DeliveryProfile APIs. Verify ownership, and use coversAllItems if it matches your app’s model.

Scopes: No additional scope listed

02Preferred where applicable

Choose this whenYou read combined merchant and app rates and can operate as a sales channel.

Upgrade actionShopify’s preferred reader path avoids branching between legacy and market-driven stores.

Scopes: read_product_listings

Choose this whenYou must read merchant shipping configuration directly.

Upgrade actionBranch on ShopFeatures.marketDrivenShipping. Read Market.delivery.shipping for migrated shops.

Scopes: read_markets

Choose this whenApp-owned profiles cannot represent your use case and you must modify merchant configuration.

Upgrade actionBranch during rollout. Use marketCreate and marketUpdate for migrated shops.

Scopes: read_markets + write_markets

Fast decision tree

Does the app only manage its own delivery profile?

YesStay on DeliveryProfileTest app-owned behavior in preview.

NoContinue ↓

Does it read merchant rates?

Sales channelContextual Product Feeds

Direct configMarket.delivery.shipping

Does it write merchant rates?

Can own ratesApp-owned profile

Must edit merchant configmarketCreate / marketUpdate

During rollout: Apps using direct Markets reads or writes must branch between market-driven and legacy stores until all merchants have migrated.

Primary source

Dates are targets and can shift. Use the feature-preview development store and the current upgrade guide before shipping changes.