Tags vs. metafields vs. collections - when to use what

Shopify gives you three ways to attach information to a product: tags, metafields, and collection membership. Most stores lean far too hard on tags, because tags were there first and they're easy. Here's what each is actually for.

Tags: quick, flat, and fragile

Tags are free-text labels. "summer", "linen", "new-in", "SS26-drop2". They're fast to add and Shopify's automated collections can use them, which is why they end up doing everything.

The problem: tags have no structure. "Linen", "linen", and "100% linen" are three different tags. There's no validation, no types, no relationship between them. A tag system maintained by three people over two years becomes an archaeology project. Use tags for what they're good at - temporary, operational labels like campaign markers - not as your product data model.

Metafields: structured data that means something

Metafields are typed, named fields: material (text), care_instructions (rich text), fit (single choice from a list), heel_height_mm (number). They're where real product attributes belong.

The difference is that metafields have definitions. A "material" metafield restricted to a predefined list can't drift into fourteen spellings of linen. Themes can display metafields, filters can use them (via Shopify Search & Discovery), feeds can map them, and structured data can expose them to search engines and AI assistants. Tags can do some of this, badly. Metafields do it reliably.

Collections: grouping, not describing

Collections group products for customers to browse. They answer "show me all the dresses," not "what is this dress made of." The confusion happens because automated collections use tags as rules, so people start tagging products to control collections - and suddenly tags carry navigation logic, attribute data, and campaign flags all at once, and nobody dares delete one.

The clean split

Describe the product with metafields. Group products with collections. Mark temporary operational states with tags. When you see a tag that describes a permanent property of the product - a material, a fit, a color family - that's a metafield wearing a tag costume, and it's worth migrating.