Your product exists. Your customers know what it is. Your market has used the name for generations.
Google's taxonomy does not have a neat place for it.
This does not mean the product is obscure, illegitimate or badly described. It means a global standard has reached the edge of its vocabulary.
A standard taxonomy is built for exchange
Google's product categories give merchants and Google a shared classification language. Shared languages must be broad enough to work across millions of products and markets.
That scale is useful. It is also why every regional, specialist or emerging product type cannot expect its own branch.
A hand-thrown ikebana vessel may be a precise product in the retailer's world and still map to a broader vase or home-décor category in Google's.
Two things can be true at once.
Choose the closest valid category, not the most flattering one
When no exact branch exists, choose the category that most accurately reflects the product's principal nature.
Do not force it into a more specific but incorrect category simply because specificity feels better. False precision is still error.
Google's guidance is to use the most relevant category available from its published taxonomy. The category can be supplied by text path or numeric ID where required. Google Merchant Center: Google product category
Do not let the external category erase the internal product
The retailer still needs to know whether the item is an ikebana vessel, bud vase, amphora-style vase or sculptural object.
That precision can live in:
- The store's product type
- Product title
- Description
- Structured attributes
- Internal taxonomy
- Relevant landing-page content
The model should be:
Precise store product type
→ Closest valid Google category
Not:
Google's broad category
→ Entire store vocabulary reduced to match it
Attributes carry meaning the category cannot
A broad category can still be supported by clear attributes such as material, colour, dimensions, construction technique, finish and intended use.
The category tells Google the general class of product. The attributes and page content make the item more fully legible.
Record the mapping as a decision
If every ikebana vessel should map to the same Google branch, store that mapping. Do not ask staff, or an AI model, to reinvent it product by product.
If some vessels require a different mapping because the catalogue uses the term in more than one way, define the condition and flag uncertainty.
Taxonomies are translations, not mirrors
The retailer's taxonomy and Google's taxonomy serve different audiences. They do not need to be identical. They need to be connected faithfully.
Semantikal preserves the merchant's precise language, then maps it to the closest appropriate platform structure. Generic systems know the category. Semantikal learns the vocabulary.