Merchant Center catalog operations workshop / 5 MIN READ
Map the product taxonomy without turning store navigation into a platform category
Create a two-taxonomy crosswalk with category evidence and downstream campaign dependencies.
AI-assisted research and analysis for the SNS Creative Fieldbook
Sources checked 2026-11-07
Google category and merchant product type answer different classification questions. Maintain the mapping explicitly so a merchandising reorganization does not silently change advertising structure or category requirements.
What you will leave with: Create a two-taxonomy crosswalk with category evidence and downstream campaign dependencies.
Use this when
- A store reorganizes its navigation or imports a supplier taxonomy.
- Products receive an inappropriate automatic category or move into unexpected campaign groups.
Not a general information-architecture exercise or permission to choose a false category to avoid applicable requirements.
Decide which classification problem you are solving
Google documents google_product_category as a predefined taxonomy with automatic assignment and overrides in specified circumstances. Separately, product_type represents the merchant's own hierarchy. Check current override conditions before treating the Google field as unrestricted merchandising space.
Write the two purposes into the export specification. One column identifies what the item is under the platform taxonomy; another preserves a useful store classification. A collection such as gifts for commuters may be valuable navigation but does not describe a single product class. Keep that commercial grouping separate from a claim about the nature of every item it contains. Ask what decision the proposed change is supposed to affect before editing either field.
Map from the actual product rather than the supplier breadcrumb
Inspect the offer, its intended function and the exact sold unit. Supplier category names often reflect warehouse organization or sales territories rather than a consumer product taxonomy. Use the current official category list when selecting a supported value and retain the reason for a non-obvious mapping.
Create exception rows for products that fit poorly, multifunction items and bundles. Do not force all records from one supplier into a single category because it makes the lookup simple. A crosswalk should include the source classification, selected destination category, product-type path, owner and review trigger. Where uncertainty affects compliance requirements, escalate the underlying classification question rather than selecting the category with fewer mandatory fields.
Review campaign dependencies before renaming a hierarchy
Ask the media owner which product groups, reporting exports or rules depend on category or product type. Preview the items entering and leaving each affected group. A navigation cleanup can change campaign membership even when the products, prices and availability remain identical.
Keep the hierarchy consistent enough to aggregate. Avoid inconsistent spelling, accidental separators and one branch named after a brand while its siblings describe functions unless that structure is intentional. Test how the chosen source format serializes the path. Maintain one approved primary hierarchy for the campaign use case and inspect how multiple submitted paths are handled under the current documentation. More paths do not necessarily mean every downstream tool uses all of them.
Validate classification outputs and preserve the rationale
Inspect processed product records after release, including ordinary items and every reviewed exception type. Compare the resulting category and product type with the crosswalk, then check affected campaign membership. Keep automatic categorization, submitted overrides and observed processed values distinguishable in the audit record.
Review the mapping when the taxonomy changes, a supplier changes its product family or the business reorganizes categories. Do not rebuild the entire crosswalk merely because one exception needs correction. Save the reasoning for disputed cases so the next catalog operator does not repeat the same guess. The acceptance result is a truthful classification and an intentional campaign structure, not a promised increase in reach or a declaration that all policy requirements are satisfied.
Make the reasoning concrete.
A fictional office retailer puts desks, lamps and laptop sleeves under Work From Anywhere. An export copies this store collection into the Google category field and uses changing campaign slogans as product types.
Copy the navigation everywhere
Opening: Use one store collection value for both fields.
Hypothesis: The spreadsheet appears consistent.
Risk: The platform category is unsupported and campaign groupings lose stable meaning.
Maintain separate mappings
Opening: Classify each sold product appropriately and preserve a deliberate store hierarchy in product_type.
Hypothesis: Each field serves its intended classification job.
Risk: Campaign dependencies need review before replacing old paths.
The catalog and media owners approve the crosswalk and inspect group membership after processing. They retain Work From Anywhere as a commercial collection rather than pretending it is a platform category.
Take the questions into your next brief.
Use these prompts in your own notes. Nothing is submitted from this page.
Purpose
Is the change about product classification or store organization?
Evidence
What product facts justify the chosen platform category?
Crosswalk
Which source value maps to each approved destination value?
Dependencies
Which campaign groups or reports use this hierarchy?
Exception
Who decides ambiguous or multifunction product mappings?
Watch for the wrong conclusion.
- Uploading a marketing collection as a predefined Google category.
- Choosing a false category to evade required attributes.
- Renaming product-type paths without checking campaign membership.
Your next action
Build a crosswalk for one mixed store collection and preview its campaign-group changes.
Sources & scope
Workflows, worksheets and fictional examples are original editorial analysis, not Google instructions or measured business results. Sources support only the specifically attributed platform facts. Platform controls and eligibility can change; verify current account guidance before implementation.
- Google Merchant Center: Google product category →Primary platform documentation · Supports: Supports automatic Google categorization, predefined category values and the limited cases for overrides. Crosswalk governance is original editorial analysis.
- Google Merchant Center: Product type →Primary platform documentation · Supports: Supports product_type as the merchant-defined hierarchy, distinct from Google categories, and the documented handling of repeated paths.