Shopify Channel Mapping: Sending Each Sales Channel Its Own Title and Product Data

A store that sells on its own site, Google and Meta keeps one catalogue and three audiences. The title that reads well on a product page is not always the one a shopping ad needs, and a field one channel requires may not exist in the store at all. Until now the usual answers were a feed app or titles rewritten by hand in each channel. On 28 October 2026 Shopify added a third: channel mapping, a page in the admin that decides, field by field, what each sales channel receives.

This is how it works in Shopify’s own words, the order in which a channel’s field gets its value, what mapping cannot do, and how to use it to fix listings across a catalogue rather than one product at a time. It is listing work, the same work as product listing optimization on any marketplace, done once at the source.

Each eligible channel’s fields, the title, the brand, the product category, the colour and the rest, have a default source in the store. A channel’s brand field might use the product’s vendor, for example. Channel mapping lets you choose a different source for any field, combine several sources into one, or override a field for a single product on a single channel, and the store’s own product details do not change. Shopify’s example is a shorter title kept in a metafield and sent to one channel, while the online store keeps the full title.

Most sales channels are eligible, Shopify says, though not all: Shop and Shopify Collective are named exceptions. The same page also sets the product data used in Shopify Catalog, the version of the catalogue that AI agents and assistants read, which is covered in Shopify’s agentic storefronts.

The page opens from three places: Settings, then Sales channels, then the channel and Edit mappings; from a market that includes the channel; or from a product, through its publishing dialog. A store that already added Google product data such as age group or gender in the Google & YouTube channel need not move it: Shopify says that data is kept in metafields under the mm-google-shopping namespace, and the Google mappings already read them.

Shopify gives the order. First, an override: a value typed for that product or variant in the bulk editor. Then the mapping: the source chosen for the field on the channel mapping page. Then the default: the source the channel uses when nobody chose one. And if the mapped source is empty for a product, the channel falls back to the default for that product, so a title mapped to a metafield that a product lacks still arrives, as the product’s own title.

That fallback is what makes mapping safe to start small. Map the title to a metafield, fill the metafield for the products that need a different title, and every other product goes on sending the title it always sent.

For single-line and multi-line text fields, a mapping can combine product data, metafields and text you type. Shopify’s changelog uses the case most stores will want first, the brand added to the product title so the brand name appears in the channel’s listing title. A title field can be the product title, a hyphen and the vendor, assembled the same way for every product on that channel. For more control, the same fields can be written as Liquid code, with filters to change case or shorten a value.

Some fields cannot be combined. Media fields cannot, an unstructured metafield can be a field’s only source but not part of a combined value, and money fields such as the price can never be a source. On our reading that last rule is a good one: what a channel says a product costs should come from one place, the product.

The most common reason to map a different title for Google is that a product page title and a shopping title do different jobs. The store's title can lean on the page around it; the shopping title stands alone in a grid of competitors.

The facts first. Merchant Center allows titles up to 150 characters, and only the start of a title shows in most placements. Lead with what the shopper filters on: the brand, the product type and the attributes that distinguish it, such as material, size, colour or count. A title that opens with a collection name or a mood word spends its visible space on nothing a shopper is comparing.

No promotion in the title. Sale wording, free shipping and capital letters for emphasis are not allowed in product titles. Promotions belong in the promotion and price fields, where they display properly.

The same product, described the same way. The title has to describe the product the shopper reaches on the landing page. A mapped title can add the brand or an attribute the store title leaves out; it cannot describe a different product or variant.

Build it from data, not by hand. A mapping that combines the vendor, the product type and an attribute such as colour or size gives every product a consistent shopping title at once, and fills itself in for products added later. Hand typed overrides are for the few products the pattern does not suit.

Four limits shape how it is used. A mapping applies to every product published to that channel; there is no mapping per product category, so a rule that suits apparel and not furniture has to be built from data both have, or handled with per-product overrides. A source shared by several channels changes all of them: edit a metafield and every channel that reads it receives the new value. The preview shows what the channel receives, not whether the channel approves or displays the listing. And a saved change updates the channel’s feed, but Shopify says the change can take some time to show on the channel.

Returning a field to its default has a trap. Every source you added must be removed and any text you typed deleted; Shopify warns that text left in the field, even a hyphen or a space, is then sent for every product in place of the default.

Coverage percentages show which fields are missing. Knowing why each matters to a channel decides which gaps to close first.

Identifiers. A product's GTIN, its brand and, where there is no GTIN, its manufacturer part number let a channel match it to the same product elsewhere and show it in comparisons. Google has long advised that correct identifiers help products appear in more places, and custom or handmade products should say they have none rather than leave the field empty.

Category and type. Google assigns a product category itself from the data, and a store can set its own product type, which is where its own taxonomy belongs and what campaigns can be split by. Meta reads its own category field. A missing or vague type makes campaigns harder to organise and reports harder to read.

Apparel attributes. For clothing, channels ask for colour, size, gender and age group in many countries, and products missing them can be limited or not shown at all. A clothing store's coverage on those four is usually the first thing to fix.

Availability and condition. Required everywhere, and wrong more often than they look: a product shown as in stock that is not, or used stock marked new, is a disapproval waiting to happen and a poor experience for the shopper who clicks.

Fix required fields first, identifiers next, then the attributes that help a product appear in filters.

Each field on the mapping page shows a coverage percentage: the share of products, or of variants for a variant field, that have a value, counting active products published to the channel, or every product for Shopify Catalog. The details mark each field as Required, Recommended or Optional for that channel and split the products that have a value into those served by the default, by your mapping and by an override. A Fix button opens the bulk editor with only the products missing that value.

What a value typed there does depends on how the field is mapped, and it is worth knowing before typing a hundred of them. Into a combined or Liquid field, it is an override for that product on that channel alone. Into a field mapped to a metafield, it is saved in the metafield, so every other channel, Shopify Catalog and the theme that read the metafield receive it too. Into a field sourced from a product field or the channel’s default, it cannot be saved there at all, and the change belongs in the product itself.

A mapping is right when the channel shows what was intended. Shopify's mapping page shows what will be sent; the channel's own tools show what arrived and what it did with it.

Give it time to sync. Changes reach a channel when the product data is next sent and processed, which is not instant. Check a day after a change rather than an hour after.

Google. Merchant Center lists products with problems: disapprovals, missing fields, mismatches between the data and the landing page. After a mapping change, the count of affected products should fall. If it rises, the mapping created a problem, often a title that now reads differently from the page.

Meta. The catalogue in Meta's commerce tools reports items with issues in the same way. Look there for missing required fields and for items rejected under its policies.

Spot check by eye. Pick a handful of products from different categories and look at how each appears: the title, the image, the price and the availability. A mapping that combines fields can produce odd results on products whose data is unusual, and a person sees those faster than a report does.

Record each mapping change and its date. When a channel's numbers move a week later, the record shows whether the mapping is the likely cause.

On our reading, start with the required fields at the lowest coverage on the channel that sells most, since a missing required field is the likeliest reason a product is not shown at all. Then the title, because it is what a shopper reads first in a shopping result: decide whether the channel needs the brand in it or a shorter form, and build that once as a mapping. Before saving, preview two or three products of different kinds, including a draft one, since the preview shows any product without publishing it. Keep any channel-specific wording in metafields named for it, so nobody later edits a value without knowing which channels read it. Staff need the View and Create and edit permissions on products to change mappings, and Sidekick can be asked to write a mapping rule, which is worth reviewing before saving, as Shopify itself advises.

The words themselves are still the work: mapping decides where a title goes, not whether it is a good one, which is covered in product descriptions and supplier feeds, and for the store’s own visibility in eCommerce SEO. If your catalogue reaches several channels and you are not sure what each receives, ask us to map it with you.