October 2, 2026 · Muhammad Rehan · More by Muhammad Rehan
Shopify Removes marketCurrencySettingsUpdate in 2027-01
marketCurrencySettingsUpdate is removed in Admin GraphQL API 2027-01 — here's the exact marketCreate/marketUpdate migration path.
What's actually being removed
As of Admin GraphQL API version 2027-01, Shopify removes the marketCurrencySettingsUpdate mutation, along with its MarketCurrencySettingsUpdatePayload, MarketCurrencySettingsUserError, and MarketCurrencySettingsUserErrorCode types. Versions 2026-10 and earlier are unaffected and keep the mutation for the remainder of their supported lifetime — this is a version-pinned removal, not an immediate global cutoff.
Why this has been a silent no-op for over a year
The mutation was deprecated when Markets Home launched in version 2025-04. Since then, every call to marketCurrencySettingsUpdate has returned the UNIFIED_MARKETS_ENABLED user error instead of updating anything. The mutation technically still existed and still compiled, so unmigrated integration code could run without raising an exception while quietly doing nothing to the market's currency settings.
That's the trap worth flagging to any team that hasn't touched this code path recently: the absence of a hard error doesn't mean the integration is working. If currency settings for a market look stale, this mutation — not a network or auth issue — is a reasonable place to check first.
The migration, and why the failure mode gets worse
The fix is direct: use marketCreate when creating a market and its currency settings, and marketUpdate when changing the currency settings of an existing market. Both mutations accept currency settings directly in their input, so no separate currency-settings call is needed at all — one mutation now does what used to take two.
What changes in 2027-01 isn't the behavior of unmigrated code, but how it fails. Today, a call to marketCurrencySettingsUpdate returns a scoped user error — the request still executes, you just get UNIFIED_MARKETS_ENABLED back for that one mutation. Once the field is removed, a request that still references it fails GraphQL validation entirely: the whole request is rejected, not just the one mutation. For a batched or multi-mutation request, that's a meaningfully worse failure mode, and it's worth testing for ahead of the deadline rather than finding out when 2027-01 becomes mandatory for your app.