Blog

Shopify submarkets and state markets: what a redirect needs

By Beacon Wave Studio · October 1, 2026 · 7 min read

When Shopify Markets launched, a market was a flat thing: a bag of countries with a currency, a domain or folder, maybe a price adjustment. It has stopped being flat. Markets can now be nested, so a Germany market can sit inside a Europe market and inherit most of its settings. Retail locations and B2B company locations can be markets. And, in early access, a market can target a part of a country, a state or a province, so that Texas and Alaska get different shipping options without being different stores. The 2026-10 Admin API even exposes the parent and child relationships so apps can read the tree.

Merchants who use a geolocation popup or redirect reasonably ask what all this means for it. Does a country rule still make sense when the market is a submarket? Should the popup know about states now? The short answers are yes and no, and the reasons are worth five minutes, because they also explain where a geolocation app ends and Shopify begins.

How a shopper ends up in a market

This is the part most explanations skip. A shopper is never placed into a market directly. The storefront has a localization: a country and a language, visible in Liquid as localization.country, and set either by the domain or folder they arrived on, by the theme's country selector, or by a POST to Shopify's /localization endpoint with a country code. Shopify then works out which market that country belongs to and applies that market's currency, prices and content. The country is the handle; the market is what Shopify looks up.

A geolocation app lives entirely on the handle side. GeoBeacon detects the visitor's country using Shopify's own browsing_context_suggestions endpoint, matches it against your rules, and if a rule says “visitors from Germany should shop in Germany”, it submits the same localization form the theme's country selector would. Which market Germany belongs to is not the app's business. That design choice is what makes the rest of this post short.

Submarkets: your rules keep working, your copy might not

Shopify's inheritance documentation describes a market as having a lineage: a parent-child relationship is inferred when a child market's region is a strict subset of the parent's, with the store default as the universal parent. When a country sits in more than one market, Shopify applies the most specific one. A shopper switched to Germany therefore lands in the Germany submarket if there is one, and in the Europe parent if there is not. Create or delete the submarket and the same rule, the same country code, resolves to a different market with no change on the GeoBeacon side.

What can go stale is what the popup promises. GeoBeacon's default text says the target has “local pricing, shipping and payment options”. With inheritance, a submarket may override only one of those. A Germany submarket under a euro-pricing Europe parent will typically keep the parent's currency and price list and differ in language, shipping rates and perhaps a local domain. The popup is still right to offer the switch; it is just not right to lead with pricing. Edit the copy per rule to name the thing that actually changes: “Shop in German with delivery from our Berlin warehouse” converts better than a generic promise, and it does not set up a disappointment at checkout.

The one case where a submarket does change the rule itself is a language split. If you created a Switzerland submarket to serve German, French and Italian shoppers in the same country, the country rule still points at Switzerland; the language is a separate decision, and the bilingual countries post goes through how GeoBeacon handles that without guessing from an IP address.

Sub-region markets: nothing to redirect to, yet

The state-level feature is more interesting and, for a geolocation tool, almost entirely irrelevant for now. Shopify's developer changelog is explicit about scope: sub-region markets “support shipping first”, and discounts, catalogs, theme contextualization and market metafields “are not yet supported”. The admin says the same in plainer words: create markets that target states or provinces “so that you can set up different shipping options for different sub-regions”. The schedule published alongside market-driven shipping has merchant rollout beginning in October 2026 and every shop moved by July 2027.

Put those together and there is no Texas storefront. A shopper in Houston and a shopper in Anchorage see the same prices, the same theme and the same promotions; the difference appears at checkout, when their address determines which shipping options they are offered. There is nothing for a popup to switch them into, and a redirect that tried would have to know their state from their IP address, which is where geolocation stops being reliable. Country-level detection is good enough to act on silently in most cases. State-level detection on mobile networks, VPNs and corporate connections is not, and a wrong guess would show a shopper in Austin an Alaska shipping banner.

GeoBeacon does not try. Shopify's suggestions endpoint returns a country and a language, which is what the app reads and all it reads. If sub-region markets grow storefront features later, the right design is still the same one: detect the country, let the shopper confirm, and let Shopify apply whatever the market tree says.

If you want a state-specific message anyway

There are legitimate reasons to speak to one state: a shipping cut-off that applies to Hawaii, a tax note for a province, a store opening in one city. None of them need a redirect. Shopify's per-market theme customization lets you vary sections per market, which now includes sub-region markets at the shipping level, and a plain announcement bar reading “Free shipping to the lower 48; Alaska and Hawaii see rates at checkout” does the job for everyone without guessing anyone's location. The market-specific promotions post covers the pattern of keeping promotions inside the market they belong to.

Checking your setup after a Markets change

1. Open Markets in the admin and switch to the graph view. It draws the hierarchy and marks which settings each market inherits and which it overrides. Make a note of what each submarket actually changes.
2. In GeoBeacon, open each rule and compare the popup text with that note. Where a submarket inherits currency and pricing, remove the pricing claim from the copy.
3. On the storefront, append ?geobeacon=DE (or any two-letter code) to a page URL to simulate a visitor from that country. Accept the popup and confirm the page lands in the market you expect, with the currency and language you expect. The no-VPN testing guide has the full procedure.
4. If you created sub-region markets for shipping, do nothing in GeoBeacon. Test a checkout with an address in that region instead, because that is where the feature lives.

Why this matters beyond the edge cases

A geolocation tool that stored its own copy of your market structure would need updating every time Shopify added a level to the tree, and it would be wrong in the gap. By working with country codes and letting Shopify resolve the market, GeoBeacon stays correct through submarkets, retail and B2B markets and whatever sub-region markets become, with the merchant's only job being to keep the popup honest. If you are setting up Markets for the first time and want the redirect side handled, GeoBeacon is free to try.