Shopify Markets Can Now Scope to a Sales Channel
As of API 2026-07, Markets can target a sales channel directly — breaking any sync tool that assumed markets only mean geography.

Shopify's Markets API has always represented buyer segmentation by geography, retail location, or B2B company location. As of API version 2026-07, a Market can also be scoped directly to one or more sales channels through a new channel market type. It's an additive change — Shopify's own changelog is explicit that existing apps don't need to update anything unless their logic creates, queries, or makes assumptions about Markets or market catalog types. For any ERP, PIM, or multi-channel sync tool that does make those assumptions, this is the point where 'a Market means a region' stops being universally true.
Creating and Querying a Channel Market
A channel market is created with MarketCreateInput.conditions.channelsCondition, passing channel IDs through MarketConditionsChannelsInput.channelIds; channels can be added or removed later via MarketUpdateInput.conditions. On the read side, Market.channels and Market.channelsCount return a market's channels, Channel.markets and Channel.marketsCount return a channel's markets, and filtering a markets list by type CHANNEL narrows it to channel markets specifically. Channel.activeRegions reports the regions where a channel currently has active product feeds — useful for checking coverage before assuming a channel market applies everywhere.
Where Channel Markets Sit in the Connection Flow
Channel markets don't replace the product-feed mechanics that already exist. When an app calls the channelCreate mutation, Shopify first reads the channel specification to determine regional coverage, intersects that with the store's existing region markets, and creates a product feed for each covered country — those feeds start emitting events to the app's webhooks immediately. A channel market is layered on afterward: merchants use it to set channel-specific catalog, pricing, and currency, and those settings take effect before contextual product feed payloads reach the app. If the channel specification declares that it expects online store parity — true for traffic-driving channels like Google or Meta — channelCreate itself requires the store to already have a region market with a valid web presence covering the specification's countries, or the mutation fails outright.
New Errors to Map
Three MarketUserErrorCode values are specific to this feature: CHANNEL_MARKET_MUST_HAVE_SINGLE_CHANNEL_DRIVER, CHANNEL_NOT_VALID_FOR_CHANNEL_MARKET, and INVALID_CHANNEL_IDS. A sync tool that bulk-assigns channels to markets, or that treats any channel ID it's handed as automatically valid, will start hitting these errors the first time it touches a channel market — and needs explicit handling for them, not a generic retry.