Shopify Market: configurable shipping via GraphQL API

A model shift for multi-market shipping

Having different international markets share the same shipping profile was never a real strategy, just a technical compromise. Until now, differentiating shipping rates by market on Shopify required separate shipping profiles, custom workaround logic, and a non-trivial manual maintenance burden.

With API version 2026-07, the GraphQL Admin API takes a radically different approach: shipping is now configured directly on the Market object, with no need for additional resources or parallel structures.

What actually changes in the API

The update introduces a new management model centered on the Market object, with several key features:

• Market.delivery.shipping reads the shipping configuration specific to that market
• marketCreate and marketUpdate handle creation, editing, and removal of the configuration in a unified way
• If a market has no configuration of its own, it automatically inherits the parent market's configuration, or the store default
• The isEnabled: false flag hides all shipping options at checkout for that specific market

This native inheritance logic removes the need to duplicate configurations across similar markets, drastically reducing the maintenance overhead for stores managing dozens of active markets.

The four supported rate types

The new model supports four rate types, each applicable individually per market:

• Flat rate
• Rate based on cart value
• Rate based on package weight
• Rate calculated by the carrier in real time

This granularity makes it possible to define differentiated shipping pricing strategies by geographic area without needing to touch resources external to the Market itself.

The operational risk to watch

The most delicate aspect of this change concerns its silent behavior in the event of misconfiguration. A market with isEnabled: false shows no shipping options at checkout, without generating any visible error. For a customer, this translates into a blocked checkout, with a direct loss of conversions and no clear signal of the underlying cause.

Teams managing multi-market architectures should therefore set up automated checks that periodically verify the isEnabled status across all active markets, catching anomalous configurations before they impact real sales.

Impact for Shopify Plus teams and app developers

For teams managing multi-market architectures on Shopify Plus, this is the API change with the most direct operational impact in recent release cycles. The main benefits can be summarized in three points:

• Fewer workarounds based on duplicated shipping profiles
• Native inheritance logic between parent and child markets
• Granular shipping control by country or geographic area

Anyone developing apps or integrations that interact with Shopify Markets needs to review their existing logic before migrating, since the new model replaces the approach based on separate shipping profiles. For those planning this kind of technical work, it may be useful to check the Barikreativa pricing table for Shopify developers to estimate the cost of an audit or a multi-market shipping configuration migration.

What to do before July 2026

Anyone redesigning international shipping, or developing applications that touch the Market object, should read the full documentation before API version 2026-07 takes effect. Planning ahead makes it possible to:

• Map existing markets and their respective shipping configurations
• Verify which markets will inherit configuration from the parent or the default
• Test checkout behavior on each market before releasing to production

This update represents a concrete step toward simpler, more native management of international shipping on Shopify, but it requires careful attention during the transition phase to avoid silent checkout disruptions.