What a Product Taxonomy Is (And Why Every Store Past 50 Products Needs One)
- Crystal Waddell
- Jul 11
- 9 min read
A product taxonomy sounds like something a librarian would want and a store owner would never need.
Here's the plain version: a taxonomy is the fixed set of questions you ask every single product, and the fixed set of answers each question is allowed to have.
That's it.
Not software.
Not a project.
A short list of questions, and the answers you'll accept.
For my store, the questions are things like:
What occasion is this for?
Who is it for?
What's it made of?
And the allowed answers to "occasion" are a closed list:
wedding,
closing,
housewarming,
birthday.
Not whatever I feel like typing that day.
Every product gets asked those questions.
Every product answers from the list.
That's a taxonomy.
Why 50 products is the line
Under about fifty products, you are the taxonomy.
You remember which items are wedding gifts.
You know, without looking, which ones the realtors buy.
When someone asks what you sell for closings, you answer instantly, and you're right.
Your memory is doing the work a database would do, and it's doing it well enough.
Past fifty, it quietly stops working.
Not all at once.
You just start noticing that you're not sure anymore.
You go check. You find one you forgot.
You start keeping a list somewhere. The list goes stale.
The number 50 isn't magic, and it isn't really about products.
It's about the moment your catalog outgrows the one person holding it in their head.
Some people hit that at 40.
I hit it, badly, painfully, somewhere north of 150.
The tell is simple: when you have to go look, you no longer have a taxonomy.
You have a memory, and memories don't scale.
Shopify already gives you half of one
Here's what most store owners don't realize: Shopify has already handed you a taxonomy. It's just not the whole thing, and it's not the half you'd expect.
Shopify's Standard Product Taxonomy is a predefined list of product categories, and Shopify's documentation is direct about it: all of your products should be assigned to a category.
A category looks like a breadcrumb: Home & Garden > Decor > Clocks > Alarm Clocks, and picking one does more than tidy up your admin.
According to Shopify, the category unlocks category metafields (the product attributes that map to that category), lets you use those attributes as smart collection conditions and product-list filters, makes it easier to sell on channels that require a standard category like Google and Facebook, and helps determine the correct tax rate at checkout.
And if you never pick one?
Your product saves as uncategorized.
That's a real value sitting on real products — and "uncategorized" is where products land whenever nobody picks a category.
Most often happens to the products you created in a hurry.
The category metafields part is the genuinely useful bit.
Assign a category and Shopify offers you the attributes that belong to it, with default entries you can use as-is or rename to fit your brand.
Shopify's own example: if black doesn't suit your branding, rename the entry to graphite, and it updates everywhere that colour is used.
That's a taxonomy.
Shopify built it.
It's already in your admin.
The half Shopify does not give you
So why isn't that the end of the post?
Because Shopify's taxonomy describes what a product is.
Your business runs on what a product is for.
Shopify can tell the world that the thing you sell is a cutting board.
It cannot tell anyone that the cutting board is a closing gift for realtors, because "closing gift" is not a category in any standard taxonomy on earth.
It's not a property of the object.
It's a property of why someone buys it, and that lives in your head, in your marketing, and in the way customers actually ask for things.
Shopify is explicit that the taxonomy has limits here: custom attributes aren't supported.
You can't invent a new attribute inside the standard taxonomy and expect it to be there.
So the shape of the work is two halves.
Shopify's half: the standard category, plus the category metafields it unlocks.
Take it.
It's free, it's structured, and it feeds Google.
Your half: the axes your business actually sells on:
Occasion.
Audience.
Material.
Format.
These you define yourself, as your own metafield definitions, with your own closed list of allowed values.
Most stores do neither.
They leave half their products uncategorized, and they keep "closing gifts" in their memory.
Then they wonder why nothing filters, nothing feeds, and nothing scales.
And why it feels like their products are invisible to buyers.
Category, type, and the difference nobody explains
Two fields, similar names, completely different jobs.
Shopify's docs draw the line clearly, and each product gets exactly one of each.
Product category is the standard field from Shopify's taxonomy. You pick from Shopify's list, not your own. It's what channels and tax engines read.
Product type is a custom field, unique to your store. Shopify's guidance is that if your product doesn't fit any existing standard category, that's what product type is for.
The mistake I see constantly is treating one as a substitute for the other.
Product type is not where you put "wedding."
Product type is what the thing is in your own words. The reason a customer buys.
It deserves its own field, defined by you, with a closed list of values.
One field, one question.
The moment a field is answering two questions, your taxonomy is already broken.
The rule that makes a taxonomy real
A list of fields isn't a taxonomy. A list of fields with closed values is.
This is the part people skip, and it's the part that does the work.
Open a field with no allowed list and you'll get wedding, weddings, and Wedding inside a month, because you were busy and you typed what came to mind.
Three values, one idea, and now every rule and filter you build on that field is quietly wrong.
Closed values mean the answer is chosen, never typed.
Shopify's category metafields already work this way, with default entries you select and can customize.
You want your own fields to behave the same.
So the rule is: decide the allowed answers before you fill in a single product.
Write them down somewhere that isn't your head.
Then no product goes live without them.
That single rule is the difference between a taxonomy and a good intention.
Why this is the same job as fixing your Google feed
Here's the part that surprised me, and it's the reason I do this work at all.
The fields that power your storefront, the ones your collections and filters read, are the same fields Google reads to decide whether to show your products at all.
Shopify says as much: assigning a standard category makes it easier to sell on channels that require one.
And if you already use Google's product categories, Shopify maps between them when your Google category matches Google's value or ID.
So when you sit down to build a taxonomy, you are not doing an organizational project that pays off "eventually."
You are simultaneously making your collections buildable as rules instead of hand-picked lists, making your storefront filters actually return your products, filling in the exact fields Google is asking you for, and, incidentally, getting your tax rates right.
One project.
Four payoffs:
Your collections build themselves. They become rules against a field instead of hand-picked lists you maintain forever.
Your storefront filters actually return your products. A filter can only find what's in a field.
Google gets the exact fields it's asking you for. The standard category, plus the attributes it unlocks.
Your tax rates come out right. Shopify uses the product category to determine the rate collected at checkout.
I didn't understand that when I started, and it's the single best argument for doing it properly rather than patching one symptom at a time.
How to build one in an afternoon
Don't start with Shopify.
Start with a customer.
Write down how customers actually ask for things:
"Something for a wedding."
"A closing gift for a client."
"Something for a guy."
Those sentences are your axes. Three or four is plenty; you do not need twelve.
For each axis, write the closed list of allowed values.
Occasion:
wedding,
closing,
housewarming,
birthday.
If you can't list the values, the axis isn't real yet, and that's useful to know.
Now go to Shopify. Assign the standard product category to your products, and take the category metafields it offers you.
That's the free half, and it's the half Google cares most about.
Define your own axes as metafields, with those closed value lists.
This is the half that makes your store yours.
Adopt the one rule: no product goes live without them.
Backfill in pieces. Start with the axis you filter on most. The rest can wait.
That's the whole thing. It isn't a technology project.
It's a decision, written down, and then enforced.
Testing your taxonomy
Here's how you know you have a real taxonomy.
Could someone who doesn't work for you file a new product correctly, without asking you a single question?
If the answer is yes, congratulations: the knowledge is in the store, not in you.
Your collections can be rules.
Your filters will work.
Your feed will be complete.
And you can hire, or take a holiday, or forget things, and nothing quietly breaks.
If the answer is no, then whatever else you've built, you're still the database.
That's the thing worth fixing, and it's fixable in an afternoon and a few quiet evenings of backfill.
Frequently asked questions
What is a product taxonomy in Shopify?
It's the fixed set of fields you use to describe every product, and the fixed set of allowed values each field can take.
Shopify provides part of one: its Standard Product Taxonomy is a predefined list of product categories, and each category unlocks matching category metafields (product attributes).
The rest, the axes your business actually sells on, you define yourself.
What's the difference between product category and product type?
Product category is the standard field from Shopify's taxonomy, chosen from Shopify's predefined list. Product type is a custom field unique to your store. Each product gets one of each.
Shopify recommends using product type when your product doesn't fit an existing standard category.
What happens if I don't set a product category?
Your product saves as uncategorized. This happens most often on products created by CSV import or by an app.
Uncategorized products miss out on category metafields, and they're the ones that quietly go missing from channels that require a standard category.
Do I need a taxonomy if I only have 30 products?
Probably not yet, and that's an honest answer.
Under about fifty products you can hold the catalog in your head and be right.
The problem is that the day you can't, you'll have three years of inconsistent data to clean up.
Setting the fields and allowed values now costs an afternoon; retrofitting them later costs a lot more.
Will a taxonomy help my Google Shopping feed?
Directly.
The standard category makes it easier to sell on channels that require one, and Shopify maps your category to Google's product taxonomy.
The custom fields you define feed the same product data Google reads. Fixing your organization and fixing your feed turn out to be the same job.
Do I need an app for any of this?
No. Everything in this post is native Shopify.
The standard product category and the category metafields it unlocks are built into the product page in your admin. Your own fields are metafield definitions, which you create in Settings, no app required.
Apps can make the backfill faster (bulk editing, feed management), and a feed app may still be worth it once your data is clean, but not one of them is a prerequisite.
If your product data is a mess, an app will simply broadcast the mess faster. Fix the fields first.
What's a breadcrumb?
It's the category path, written from broadest to most specific, with each level separated by a > symbol.
Home & Garden > Decor > Clocks > Alarm Clocks is a breadcrumb.
It's the same idea as nested folders on your computer: each step narrows to exactly what the thing is.
Shopify uses this format for the standard product category (in a CSV you can submit either the breadcrumb or the category ID), and Google uses the same > format for its own product categories. I
t's called a breadcrumb because it's the trail that leads back to where the product sits in the tree.
Not sure whether your catalog can support one?
That's exactly what a Catalog Health Audit tells you: which fields exist, which are half-filled, and which values are too inconsistent to build a rule on. It's the map you'd want before you start.
Or start free: the 5 Signs Your Shopify Feed Is Leaking Money checklist will show you, in about five minutes, where your product data is already costing you.
I'm Crystal.
I run my own Shopify store, collageandwood.com, where I took the catalog from 322 feed and taxonomy errors to zero and built the audit that tells me the moment it drifts.
Now I do the same for other Shopify stores.
Comments