Shopify Standard Product Taxonomy: How to Map Your Categories

AEO answer: The Shopify Standard Product Taxonomy is Shopify’s own fixed category tree. Each product can have one category from it, which unlocks category metafields, feeds tax calculation and helps sales channels classify the product. It is different from product type, which is free text. To map your own categories, match each one to a taxonomy node once, then let products inherit that match through their category.

You push a product to Shopify and the Category field is empty. Product type is filled in, but it is a different field. This guide explains the taxonomy, how it differs from product type and collections, and how MicroPIM maps your categories to it.

Last verified: November 2026, against Shopify’s product category help page and MicroPIM’s Shopify push (taxonomy matching released September 2026).

What is the Shopify Standard Product Taxonomy?

It is a tree of categories, maintained by Shopify and published as an open-source project in the Shopify product-taxonomy repository. There is also a browsable version. Each node has a stable ID, for example hg-3-17-1 for Home & Garden > Decor > Clocks > Alarm Clocks.

According to Shopify’s help page on product category, assigning a category does three things:

• Unlocks category metafields. Size, color or fabric for shirts, for example, with reusable default values.
• Feeds tax calculation. Shopify Tax uses the category to pick the rate.
• Helps other channels. Channels such as Facebook or Google need a standardized category. Shopify maps a Google Product Category to its own when you already have one.

Each product has one category, and Shopify asks for the most specific fit.

Category vs product type vs collection: what is the difference?

The common mistake is sending your category name as product type and assuming the job is done. Shopify’s own productCreate documentation lists category as a separate argument, and the API lets you read the whole tree through the taxonomy query.

How do you map your categories to taxonomy nodes?

You can do it by hand in the Shopify admin or from a CSV. That works for a few hundred products, not for a large category tree that lives elsewhere.

MicroPIM maps categories, not products. The match is stored per category, and each product uses the match of its primary category. Here is what happens:

1. The taxonomy is loaded. The full tree is imported from Shopify’s Admin API into a local table.
2. A local match runs first. The category name and its parent names are compared with taxonomy names. Plurals, accents and filler words are ignored. A score of 0.75 or higher is accepted.
3. An AI fallback handles the rest. Shopify’s taxonomy is in English, so names in other languages usually score low locally. The model can only pick a node that exists in the local table. It cannot invent an ID.
4. The result is stored, including “no match”. A category is matched once, not on every push. The record keeps the source (local, AI or none) and a confidence value.
5. The push sends the category. The product’s category ID goes out on create and update. If a category has no usable match, the closest mapped parent is used.

Product type still carries your MicroPIM category name. If the match fails, the category is left out, so a push never clears a category you set in Shopify.

For setup, see connecting MicroPIM to Shopify. For how category-specific attributes differ across channels, see our cross-channel guide to conflicting category attribute requirements.

How do you check the mapping after a push?

Open a pushed product in the Shopify admin and read the Category field. Then spot-check by category rather than by product, since every product in a category shares the same match.

• Check your largest categories first.
• Look for matches too high in the tree, such as a parent node instead of a leaf.
• Look for products with an empty Category. Their category likely has no match and no mapped parent.

Match quality depends on clean category names, a data hygiene problem like the ones in SKU management at scale.

What we got wrong, and current limits

Our first Shopify push sent only product type. Products arrived with an empty Category field, and we treated that as cosmetic. It is not, because category metafields and tax depend on it.

Current limits:

• No screen to review or change a match yet. The match, source and confidence are stored, but you cannot see or edit them in the app. The code never overwrites a manual mapping, but nothing in the app creates one yet.
• Not self-serve. Loading the taxonomy and matching a whole organization ahead of time are commands our team runs. Otherwise a category is matched the first time one of its products is pushed.
• One category per product. Only the primary category counts.
• Low-confidence matches need review. Local matching suits English names. AI picks can be plausible and wrong.
• Shopify only. This covers Shopify’s taxonomy, not Google or Amazon category trees.

Frequently Asked Questions

Is Shopify product category the same as product type? No. Category is a fixed list from Shopify. Product type is free text you control.

Do I have to set a taxonomy category? Not to save a product, but uncategorized products miss category metafields and accurate tax handling.

Can I change a product’s category later? Yes. If your tool sends a category on every push, change it at the source.

Does the category affect taxes? It can, when you use Shopify Tax. Shopify uses the category to determine the rate.

MicroPIM is our product. This post describes how it handles category mapping today; the taxonomy advice applies with any tool.

Pushing to several stores? Read managing multiple Shopify stores from one catalog. If duplicates are your problem instead, see the “handle already in use” fix. To get your categories mapped, connect your Shopify store or book a demo.