Category Mapping Examples: how retailers structure products for media planning

A chocolate gift box can be confectionery in the product master, gifts in ecommerce navigation, seasonal in a campaign, and part of a holiday shoppers audience. Each label can be useful. Problems start when teams treat them as interchangeable versions of product truth.

A woman with store displays in the background.

Category mapping connects those structures without changing the SKU's identity. This article stays with applied mapping records, exceptions, and campaign scope. For the canonical taxonomy, identifier, and governance model, see Product Taxonomy & SKU Mapping for Retail Media.

The bridge record used in the examples

Retailers rarely operate one hierarchy. Product information, point of sale, ecommerce navigation, media activation, external advertising platforms, and finance can each organize the same item differently. GS1 guidance allows a primary Global Product Classification plus additional classifications for mapping.[1] Google also separates its predefined product category from a merchant-owned product type hierarchy.[2][3]

For the examples below, the retailer's canonical product hierarchy is the target system. Every source-to-target relationship is recorded explicitly rather than implied by two similar labels.

Stable product ID: SKU, GTIN, or governed trade-item identifier
Source system and code/path: The original hierarchy and its coded path
Target system and code/path: The canonical retailer hierarchy and coded destination
Relationship form: Exact, broader, narrower, partial, conditional, one-to-many, or many-to-one
Inclusion and exclusion rules: The products, attributes, geography, channel, or dates for which the relation applies
Activation labels: Temporary campaign or planning groups kept outside the primary hierarchy
Effective dates and version: The period and bridge-table version used for activation and reporting
Confidence and review state: Approved, provisional, or unresolved, with the basis for confidence
Owner and exception note: The person or team responsible for ambiguity and the required decision
Measurement inclusion rule: Whether the row is in promoted-SKU, disclosed halo, or excluded outcome scope

These fields let one bridge represent exact and non-exact relationships without relying on notes elsewhere. If a source category maps to two targets, use two rows with the same source and a stated inclusion rule. If several source codes roll into one target, retain each source row so the many-to-one relationship remains reproducible.

Example 1: a completed yogurt mapping

Consider an illustrative strawberry yogurt multipack. The product master classifies it as Food > Chilled Dairy > Yogurt > Flavoured Yogurt Multipacks. The ecommerce site exposes it through Fresh Food > Dairy & Eggs > Yogurts > Kids Yogurts. An external platform stops at a broader Yogurt category, while the media team wants a temporary Lunchbox dairy group.

A compact bridge can represent all four views:

Stable product ID: SKU-104582
Source system and code/path: ExternalAds / YOG-100 / Food > Dairy > Yogurt
Target system and code/path: RetailerPIM / D-214-07 / Food > Chilled Dairy > Yogurt > Flavoured Yogurt Multipacks
Relationship form: broader-to-narrower; many external products may map to this source node
Inclusion and exclusion rules: Include chilled flavoured multipacks; exclude drinkable yogurt, ambient yogurt, and single pots
Activation labels: Lunchbox dairy
Effective dates and version: 2026-08-01 to 2026-12-31; bridge v3.2
Confidence and review state: 0.96; approved by category data steward
Owner and exception note: Dairy taxonomy owner; review if pack format changes
Measurement inclusion rule: Promoted-SKU scope only when SKU-104582 is on the campaign selection list

The ecommerce path belongs in a separate discoverability mapping, not in the canonical destination field. Lunchbox dairy is an activation label, not a permanent category. Google documents merchant product type as a merchant-owned hierarchy used for campaign organization, bidding, and reporting.[3]

This row also prevents a common reporting error. The external Yogurt node is broader than the retailer target, so results must not be presented as though the two category totals were exact equivalents.

Example 2: seasonal labels without a second identity

A chocolate gift box can keep the canonical node Food > Confectionery > Chocolate Assortments while appearing in an ecommerce Holiday Gifts collection during November and December. Media planners may also need Christmas, Giftable, Premium, or Limited Availability labels.

Google Ads permits product-group subdivision through category, merchant product type, and custom labels, including seasonal groupings.[4][5] The applied record should keep each job separate:

Primary target: RetailerPIM / CONF-330 / Chocolate Assortments
Navigation mapping: Ecommerce / HOL-GIFT / Holiday Gifts, conditional on the holiday collection
Activation labels: Christmas; Giftable; Premium
Applicability: Selected stores and channels, 2026-11-01 to 2026-12-31
Exclusions: Everyday assortments not included in the approved campaign SKU list
Measurement rule: Count only selected promoted SKUs as direct outcomes; report any wider confectionery result separately

Before mapping, a planner may select every product carrying the word "gift" and accidentally include unrelated items. After mapping, the campaign uses the approved label, date window, channel rule, and exact SKU selection. The seasonal treatment expires; the primary product node does not move.

Example 3: bundles and downstream outcomes

Suppose a retailer sells a coffee machine bundled with starter capsules and a milk frother. The bundle needs its own stable identifier, a main-product rule, and explicit component relationships. Google Merchant Center advises choosing the most appropriate category for a bundle and using the main product's category when one product is primary.[2]

An applied bundle record might contain:

bundle ID: BND-COF-220;
target: Small Appliances > Coffee Machines;
relationship form: bundle-to-main-product, with component rows for the frother and capsule pack;
inclusion rule: the bundle SKU is eligible only while all mandatory components are available;
direct outcome: purchase of BND-COF-220 after eligible campaign exposure;
excluded from direct outcome: a machine-only SKU, a standalone frother, or later capsule purchases.

Later standalone capsule purchases may be a potential downstream or halo outcome, but only if the campaign contract and measurement design define the capsule set, exposure rule, attribution window, and causal method in advance. Otherwise, report those purchases separately. They do not become promoted-bundle sales simply because the shopper previously bought the bundle.

This before-and-after distinction matters. A loose report might combine bundle revenue with all later capsule sales. A controlled report keeps bundle sales direct, applies the disclosed downstream definition only where contracted, and shows the two results separately.

Example 4: one primary node for a multi-use product

A reusable insulated bottle can appear in drinkware, sports, travel, and back-to-school collections. Four primary categories create duplicate product counts and inconsistent campaign denominators.

A better record uses one target such as Home & Kitchen > Drinkware > Insulated Bottles, then adds conditional relationships to sports and travel collections. Attributes such as capacity, insulation, leak resistance, and material support selection. A Back to school activation label carries its own effective dates.

If a source sports hierarchy includes only bottles above 750 ml, record that inclusion rule. The relationship is partial or conditional, not exact. If no defensible primary node exists, send the item to an exception queue with proposed alternatives, an owner, and a review date. A machine suggestion can remain provisional; it should not turn uncertainty into false precision.

From mapping row to campaign scope

A media buyer needs a reproducible product scope, not the whole taxonomy model. For each campaign, store the canonical nodes, exact SKU list or versioned selection rule, activation-label definitions, exclusions, bridge version, and outcome scope.

Product selection: Before control: "Holiday chocolate" typed into a planner After control: Approved label plus exact SKU snapshot and effective dates
External category bridge: Before control: Similar names treated as equivalent After control: Relationship recorded as exact, broader, narrower, partial, or conditional
Reclassification: Before control: Current category silently replaces the launch view After control: Launch bridge version retained or restatement decision documented
Outcome scope: Before control: Promoted, brand, and category sales mixed After control: Promoted SKUs reported separately from any disclosed halo set
Exceptions: Before control: Unmatched items forced into Other After control: Unresolved queue with owner, reason, and review deadline

IAB/MRC guidance supports SKU-level reporting where relevant and transparent disclosure of halo products.[6] A category report should say whether it includes advertised SKUs, other products from the advertiser, or a wider category. See Retail Media Analytics: the reports buyers actually need for the broader reporting design.

Category mapping is also different from shopper affinity. A product belongs to a category because of what it is; a shopper can have category affinity because of browsing or purchase behavior. Keeping those records apart prevents audiences from becoming a substitute for product truth.

Five checks before activation

Identity: every source record resolves to a stable product ID, with pack variants and bundles handled explicitly.
Relationship: each bridge states its form and cardinality instead of assuming similar labels are exact matches.
Applicability: inclusion, exclusion, geography, channel, and date rules are present where the mapping is conditional.
Activation: planners can build the group through governed labels and selection rules without editing the canonical hierarchy.
Measurement: an analyst can reconstruct the promoted SKU set, bridge version, and outcome scope after the campaign.

Reject the mapping if codes are missing, effective dates are absent, many primary categories create duplicates, unmatched items disappear, or halo sales are counted without a declared set and method.

FAQ

What is category mapping in retail?

Category mapping is the recorded relationship between one product-classification structure and another, including the systems, codes, relationship form, applicability rules, dates, and review state.

Should a product have more than one category?

It can have one primary classification plus additional mappings, navigation collections, attributes, and campaign labels. Each relationship needs a defined purpose.

What is the difference between a category and a custom label?

A category describes what the product is within a hierarchy. A custom label groups products for a temporary or business-specific purpose such as season, launch status, or performance band.[4][5]

How should retailers map bundles?

Preserve the bundle identifier and components, apply a governed main-product or bundle-node rule, and define direct and downstream outcomes before reporting.[2]

How often should mappings be updated?

Update them when assortments, products, or source taxonomies change, while preserving versions and effective dates. Do not overwrite history needed to reproduce a campaign.

What should a media buyer ask for?

Ask for the included nodes, exact SKU scope, activation-label definitions, exclusions, bridge version, effective dates, and outcome scope.

Bottom line

A useful category map is a working bridge, not a second product truth. The record should show both systems, coded paths, relationship form, applicability rules, version, owner, and measurement treatment.

The practical test is whether a planner can build the intended campaign from the record and an analyst can later reproduce which products and outcomes were counted.

Sources

[1] https://ref.gs1.org/guidelines/tiig, GS1 Trade Item Implementation Guideline [2] https://support.google.com/merchants/answer/6324436?hl=en, Google product category [3] https://support.google.com/merchants/answer/6324406?hl=en, Google product type [4] https://support.google.com/google-ads/answer/6275317?hl=en, Google Ads product groups [5] https://support.google.com/google-ads/answer/6275295?hl=en, Google Ads custom labels [6] https://www.iab.com/wp-content/uploads/2024/01/IAB_Retail_Media_Measurement_Guidelines_January2024.pdf, IAB/MRC Retail Media Measurement Guidelines

Ready to see how this works in practice?

Footprints AI helps brands and retailers measure what matters. See our customer success stories or get in touch to discuss your retail media strategy.