Product data mapping per sales channel: how Shopify lets you send different titles to Google and Meta

Since October 28, 2026, Shopify lets you set which product data each sales channel receives separately - without changing what shoppers see in your store. Google Shopping can get a title with the vendor at the front, while in your store the same product stays exactly as the customer saw it.

This resolves an old and tedious conflict: a title that looks good on a product page often performs poorly in a Google feed, and a title that performs in Google looks like a warehouse label in your store. Until now you either chose one, or paid for a separate feed app.

What is Shopify channel mapping?

Shopify channel mapping, live since October 28, 2026, is the ability to choose which data from your store is used for specific product fields on different channels. Changes affect only the selected channel, and your store's product data stays untouched.

Shopify documentation states it directly:

"Choose which data from your store is used for specific product fields on different channels." - Shopify Help Center

The changelog adds the second half, which matters more in practice: channels stay current automatically as your catalog changes. Adding new products does not mean re-mapping anything - the rule applies to all of them.

Where is channel mapping in the admin?

The main path is Settings > Sales channels, then Edit mappings. The same screen can be opened from a market's Channel mapping section, or from a product's Manage publishing dialog.

Shopify notes that most sales channels are supported, but not all: "Most sales channels are eligible, but some aren't, such as Shop and Shopify Collective." You can also set the data used in Shopify Catalog - that is, the data AI agents receive.

That last point matters more than it looks. We wrote about Meta becoming an AI sales channel on September 11 - and the problem surfaced there too: the channel receives the same data that was written for a human browsing your store.

Which fields can be mapped, and which cannot?

Text and category fields can be mapped - title, images, product category, color - using a product field, a variant field or a metafield. Prices cannot: "Money fields, such as price, can't be used as sources for channel mapping."

Text fields have two extra options, and they account for most of the real benefit:

• Combining several sources - for example, the channel's title field built from vendor plus product title, with your own text added. In a Google feed this typically produces "Brand + model + type".
• Liquid code - for more complex logic, a field can be composed with Liquid.

The exceptions are worth knowing in advance. Shopify notes that "Only a field that combines values or uses Liquid code can have an override." In other words, a per-product exception is possible only in a field that combines values or uses Liquid. Product-level fields such as title cannot take a value in the channel column - they must be changed at the source.

One more detail that is easy to miss: a metafield value entered during bulk editing is saved to the metafield itself. That means other channels using the same metafield receive the change too. It is not a bug - but if you expected to change only one channel, the result will be different.

How does field coverage help you find missing data?

Every channel field shows a coverage percentage - how many of your products have that field filled in. Shopify defines it as: "Field coverage is the percentage of products that have a value for a channel field." For variant fields it counts variants, not products.

In practice this is the first screen worth looking at, because it answers a question that previously had no answer: how much of my catalog is actually ready for this channel. The workflow is simple:

1. Open the channel's mapping screen and sort fields by coverage.
2. Start with required fields that show low coverage - those block products, rather than merely reducing quality.
3. From a field's coverage details, use bulk editing to fill in the missing values.
4. If a field shows N/A, the percentage cannot be calculated - check that field manually.
5. Repeat for each active channel separately: coverage in a Google feed and in Shopify Catalog can differ.

Does this replace Google Shopping feed apps?

Some of them, yes; others, no. Channel mapping solves the data preparation problem: what to send to a channel and where to take it from. What it does not solve is pricing rules, campaign management, and channels Shopify does not support.

So if you use an app purely to make the Google feed title different from your store title, there is now a good reason to review it. If the app also manages campaigns, there is nothing to replace it with.

Before Black Friday the practical recommendation is cautious: changing data structure mid-season is a risk, because channels refresh on their own schedule. If the coverage screen shows critically missing required fields, fix those now. Reworking the whole mapping logic is better left to January, alongside an advertising and feed review.

The most interesting consequence of this feature is not the Google feed. It is that product data in Shopify now has a clear split between "what we show a human" and "what we hand to a machine" - and the second list has become manageable.

Frequently asked questions

If you would like us to review what data your store currently hands to Google, Meta and AI agents, get in touch - BBOLD contacts.