3 Signs Your Shopify Catalog Is a Mess

Nobody's catalog looks like a mess.

That's the whole trouble.

A messy catalog doesn't look messy. It looks like a store.

The products are there, the photos are good, the prices are right, the orders come in.

Nothing is flashing red.

There's no screen in Shopify that says your product data is inconsistent and it's costing you money.

The mess is invisible because it lives in the fields nobody looks at.

And it shows itself indirectly, in three specific symptoms that most owners diagnose as something else entirely.

Here's how to tell, in about ten minutes, whether you have it.

Get the free checklist

Sign 1: You can't answer a simple question about your own products

Try this. Don't open Shopify yet. Just answer out loud: how many of my products are for weddings?

If your honest answer is "I'd have to go look," or worse, "well, it depends what you count," that's the sign.

Not a small one.

That's the whole thing, right there.

A catalog that's organized has an answer. You filter on a field, you get a number, and the number is right.

A catalog that isn't organized has a human who remembers roughly which products are wedding products, and that human is you, and you are not a database.

Now go open Shopify and actually check.

Filter your products by the field that should tell you, your occasion metafield, say.

Count them.

Then think of three wedding products you know you sell, and check whether they're in that count.

They usually aren't.

Not because you're careless, but because the field says wedding on some, weddings on others, Wedding on a few from 2023, and is empty on the ones you added last month when you were in a hurry.

That gap between what you know you sell and what your store can prove you sell is the mess. Everything else in this post is a consequence of it.

Sign 2: New products vanish into thin air

You add a product. You do it properly, or you think you do.

And then it just, doesn't turn up anywhere.

I

t's not in the collection where it belongs.

It doesn't come back when a shopper uses your filters.

It never makes it into Google Shopping.

You only find out weeks later, usually by accident, usually because you went looking for it yourself.

This is what a data gap looks like from the outside.

The product exists.

It's published.

But every system that's supposed to find it, your collections, your storefront filters, your product feed, finds products by reading fields.

The fields on that product are empty or inconsistent, so nothing finds it.

The tell is that it's never all your products.

It's the recent ones, the ones you added during a busy week, the ones you duplicated from an older product and half-edited. The mess is concentrated exactly where you were moving fastest.

If products regularly go missing from your own filters, that's worth its own diagnosis.

If they're missing from Google Shopping specifically, that's a different symptom of the same disease.

Sign 3: Google keeps asking for things you thought you'd given it

The third sign shows up in Merchant Center, and it's the one people take most personally, because it feels like Google is being unreasonable.

It isn't. Google is just reading your fields, and your fields are thin.

Google's product data specification asks for specific attributes, and two of them catch out handmade and custom sellers constantly.

Brand.

Google requires the brand attribute for every product with a clearly associated brand or manufacturer, and for products where the manufacturer is also the merchant, which explicitly includes homemade and custom-made products.

If you make it, you are the brand.

Leaving brand blank because "I'm not a brand" is not the humble answer.

It's a missing required field.

Identifier exists.

If your products genuinely have no GTIN or MPN, because they're custom goods, one-of-a-kind items, or handmade, Google's answer is not "leave it blank and hope."

Its answer is that you submit identifier_exists as no.

Google's own worked example is a hand-knitted scarf. That's a deliberate, correct value that tells Google this product has no barcode, and that's expected.

Silence tells Google nothing, and Google fills silence with warnings.

There's a second-order version of this too.

Google has an optional product_type attribute, which is your own categorization, submitted as a breadcrumb like Home > Gifts > Closing Gifts.

Google recommends sending it, because when it understands what you're selling, it can connect you to the people searching for it.

But you can only send a categorization you actually have.

If your product organization lives in your head instead of in your fields, there's nothing to send.

Every one of these is the same problem wearing a different hat: the data isn't there.

The fourth sign, the one nobody notices

Here's the one I didn't see for two years, and it's the one that actually matters.

Your workarounds have become the system.

You don't experience a messy catalog as a data problem.

You experience it as work.

You hand-pick products into collections, because rules don't work on your data. You rebuild the same seasonal collection every year, because last year's list is stale.

You keep a spreadsheet on the side, or a note on your phone, or a mental list of which products are "the realtor ones."

You re-check the feed by eye before a launch, because you don't trust it.

None of that feels like a symptom.

It feels like running a store. It feels like being diligent.

But add it up: every one of those habits exists to compensate for a field that should have been filled in.

You built a set of manual routines to route around missing data, and then you forgot the data was ever supposed to be there. The routines became the job.

That's why the catalog never gets fixed.

Not because it's hard, but because the pain has been fully absorbed by you, personally, on an ongoing basis, forever.

What the mess is actually made of

When you go looking, it's almost always the same four things.

Fields that don't exist. There's no field for the thing you actually sort by. You sell gifts by occasion, but there's no occasion field, so occasion lives in the product title and in your memory.

Fields that exist but are half-filled. Product type is set on 60% of products. Vendor is set on the ones you added when you were being careful. The rest are blank, and blank never matches a rule.

Values that don't agree with each other. Wedding, weddings, wedding-gift, bridal. Four values, one meaning. To you they're the same idea. To a rule, a filter, and Google, they're four unrelated things, and whichever one you didn't think of is the one your product is filed under.

No agreed list of what the values can even be. This is the root of the other three. If nobody ever decided that occasion can only be wedding, closing, housewarming, or birthday, then every new product is a fresh invitation to invent a value.

That's not a catalog. That's a suggestion box.

A defined field with a defined set of allowed values is the only thing that stops the drift, and it's the whole reason you define the field before you fill it.

How to check in ten minutes

You don't need an audit to find out whether you have this. You need ten minutes and a willingness to look.

Pick the one attribute your business actually runs on.

• Occasion.

• Audience.

• Material.

• Room.

Whatever a customer would say out loud when they describe why they need the thing.

Ask Shopify how many products have it. Filter on it. Write the number down.

Ask yourself how many products should have it. Write that number down too.

Compare.

The gap between those two numbers is your mess, quantified.

It's the count of products that are invisible to every rule, every filter, and every feed that depends on that attribute.

Most people are shocked by the gap. That reaction is useful. Keep it.

Then look at the values inside the field you just filtered.

If you see the same idea spelled three ways, that's your second number, and it's usually worse than the first.

What fixing it actually looks like

It isn't a big-bang cleanup weekend. That's how people burn out and quit on it.

It's this: decide on a small, fixed set of fields, and a small, fixed set of allowed values for each.

Write them down somewhere that isn't your head.

Then make one rule for yourself: no product goes live without them.

That single rule stops the bleeding.

Your catalog stops getting worse the day you adopt it, which is more than most stores can say.

The backfill comes after, and it comes in pieces.

Fix the field that costs you the most first, usually the one you filter on constantly.

The rest can wait for the next quiet afternoon.

The point isn't a perfect catalog.

The point is a catalog a rule can read, so your collections, your filters, and your Google feed all stop depending on you remembering things.

Frequently asked questions

How do I know if my Shopify product data is bad?

Pick the one attribute your business runs on (occasion, audience, material) and filter your products by it. Compare the number Shopify gives you to the number you know is true.

If those two numbers disagree, your product data has gaps, and the size of the disagreement is the size of the problem.

Why do my new products keep disappearing from collections?

Almost always missing or inconsistent field values. Collections and filters find products by reading fields. A product added in a hurry, with a blank field or a value spelled a way nothing else uses, matches nothing, so nothing shows it.

There's no error message for this, which is why it goes unnoticed for months.

Does Google need a brand for handmade products?

Yes. Google requires the brand attribute for products where the manufacturer is also the merchant, and it names homemade and custom-made products specifically. If you make it, you are the brand.

Leaving it blank isn't modesty, it's a missing required field.

What do I do about GTINs if my products don't have barcodes?

Don't leave the field blank and hope. Google provides the identifier_exists attribute for exactly this case: set it to no for custom, handmade, or one-of-a-kind products.

Google's own documentation uses a hand-knitted scarf as the example.

Why isn't my metafield available as a collection condition?

Because the metafield definition has a setting that must be switched on before Shopify will offer the field as a condition. It's a checkbox on the definition, not on the product.

Until you tick it, the field won't appear in the conditions dropdown at all, which is why people conclude Shopify can't do this when it can.

Get the free checklist

Want to find out in five minutes whether you have this?

The 5 Signs Your Shopify Feed Is Leaking Money checklist walks the same diagnosis, in order, so you can see exactly where your product data breaks down.

And if you'd rather have someone else count the gap for you, a Catalog Health Audit does exactly that: which fields are populated, which are half-done, and which values are too inconsistent to build anything on.

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.