Use Shopify market shipping APIs before regional checkout logic fragments

Shopify developer documentation preview image.Shopify
Shopify developer documentation preview image.Shopify

Shopify's 2026-07 Admin GraphQL API adds market-level shipping configuration, giving commerce apps a cleaner way to manage regional rates, carrier-calculated options, and inherited shipping behavior.

Shopify has added market-level shipping configuration to the Admin GraphQL API in version 2026-07. Confidence level: confirmed. The change lets apps read and write shipping rules directly through Markets, which matters for merchants that need different shipping behavior by region, B2B context, POS market, or carrier setup.

Shopify developer documentation preview
Source: Shopify developer documentation preview image.

What changed

The new API surface adds market delivery settings to the Market object. Apps can read Market.delivery.shipping, then use existing marketCreate and marketUpdate mutations to create, update, disable, or remove market-level shipping configuration.

Shopify's changelog says the API supports flat-rate, cart-value-based, weight-based, and carrier-calculated shipping options. The useful detail for app builders is inheritance: when Market.delivery.shipping is null, the market inherits shipping from its parent. When isEnabled is false, checkout stops showing shipping options for that market.

AreaWhat changedWho should check itCaveat
Market objectdelivery.shipping exposes market shipping configurationApps that read market setupRequires read_markets
MutationsmarketCreate and marketUpdate can manage market shippingApps that configure ratesRequires read_markets and write_markets
Rate typesFlat, value-based, weight-based, and carrier-calculated optionsShipping, logistics, and checkout appsRate-group rules differ by option type
InheritanceMarkets can inherit parent shippingMulti-region merchantsnull and isEnabled: false mean different things

Why this is early

This is a fresh Shopify developer changelog entry dated July 1, 2026, tied to the 2026-07 Admin GraphQL API. It is not a rumor or launch-directory item. The supporting Shopify feature-preview docs explain the broader migration from product-driven delivery profiles toward market-centered shipping setup.

The main limitation is source breadth. The implementation details are confirmed by Shopify's own docs, but there is not yet much independent field reporting from app developers. Treat this as an official API availability update, then verify behavior in a development store before changing production checkout logic.

Key takeaways

  • Shopify is moving merchant-owned shipping setup closer to Markets, not only delivery profiles.
  • Apps can now configure market-specific shipping through Admin GraphQL instead of creating separate shipping profile resources for every regional case.
  • read_markets is required for queries, while writes require both read_markets and write_markets.
  • isEnabled: false disables shipping options for that market; null shipping configuration means inheritance.
  • Carrier-calculated, flat, value-based, and weight-based shipping options need separate handling in app data models.

Availability and access

The changelog ties the feature to Admin GraphQL API version 2026-07. Developers should test against the 2026-07 API surface and confirm the required scopes before writing shipping settings. Shopify's feature preview also gives teams a way to inspect the merchant-facing market-driven shipping experience before committing a production migration.

The update does not remove app-owned delivery profiles. Shopify's feature-preview docs say app-provided rates can still appear in the market-driven experience, while merchant-owned shipping configuration moves toward Markets. That distinction is important for apps that provide rates rather than manage the merchant's whole shipping setup.

Practical LinkLoot angle

Commerce teams should use this as a cleanup trigger for regional checkout logic. If your app currently clones profiles, stores custom regional overrides, or infers market shipping from delivery-profile structures, the new API can reduce fragile mapping code.

Start with a read-only audit. Compare a market's current delivery-profile behavior with the new Market.delivery.shipping view, then decide which cases should inherit, which should be explicitly configured, and which should be disabled. For AI-assisted ops playbooks around ecommerce workflows, LinkLoot's automation hub is a useful adjacent checklist: /guides/ai-workflow-automation.

What to verify before you act

  • Confirm your app has read_markets and, for writes, write_markets.
  • Test null shipping configuration separately from isEnabled: false.
  • Check how carrier-calculated options behave with existing carrier services.
  • Verify whether your app owns delivery profiles, reads merchant-owned profiles, or only provides rates.
  • Run checkout tests for each market, B2B context, and POS market you support.

Source check

Confirmed by:

  • Shopify's developer changelog for the market-driven shipping Admin API.
  • Shopify's feature-preview documentation for market-driven shipping.
  • Shopify's Admin GraphQL Market object docs for the broader Markets API context.

Context to watch:

  • Early developer feedback on migration edge cases.
  • Any later Shopify notes for 2026-10 behavior or deprecations around delivery-profile reads and writes.
  • App Store review guidance if shipping apps begin exposing market-level controls to merchants.
FAQ

It is a 2026-07 Admin GraphQL API update that lets apps configure shipping directly on Markets instead of relying only on separate delivery profile resources.