Shopify Markets Channel Setup
The store is on Shopify Markets. Five questions decide what that means for your tracking, your GA4 and your product feeds, and how much of the existing stack can stay as it is.
What you are working with.
These two set how much has to change. The market itself runs either way, so this is about cost and rework, not feasibility.
These three set the model.
Currency, reporting and pricing. Between them they decide what stays shared and what genuinely has to be separate.
What that resolves to.
Each line fills as you answer. Anything tagged adds either a subscription or a permanent piece of work, not a one off build.
| Component | What this configuration needs |
|---|
Verified against current Shopify, Google and feed management documentation, September 2026. Vendor plans and feature gates change, so confirm the tier in writing before quoting a cost.
Three things people get wrong.
These are the assumptions that turn a shared setup into a rebuild six months later.
A GA4 property reports in one currency
Every transaction is converted into the property's single reporting currency at the previous day's rate. The original currency survives only in the BigQuery export. So if a market is paid out locally and finance has to reconcile to that payout, a second property is the answer, not a setting.
The feed has to match the storefront
Google Shopping and Meta ads are traffic generating channels, so the click lands on your store. Shopify warns against custom catalog pricing for those channels because the ad price and the landing page price have to agree. Market pricing and feed pricing are one decision, not two.
Separate reporting is not separate accounts
Wanting the market reported on its own is cheap. Wanting it to hold its own budget is not. The separate budget is what forces a pixel per market, a container per market and a plan step up on most server side tools, so keep the two apart in the conversation.
Not sure the answers hold up?
We have run this call for retailers on Shopify Plus, Advanced and Neto. Thirty minutes, your numbers, and a straight answer on architecture before anyone writes code.