Key takeaways
- Shopify filter values should use one approved shopper-facing label for each meaning, while preserving genuinely different product attributes that affect purchase decisions.
- Duplicate values such as
Navy,Navy Blue, andnavyshould usually be consolidated, but values such asNavyandRoyal Blueshould remain separate when shoppers distinguish between them. - Catalog cleanup must address missing shopper language, not just spelling. An internal value such as
BLKmay be operationally valid but should not become the storefront label. - Every proposed merge needs a product-count check and a spot review. A tidy worksheet is not enough if the change assigns products to the wrong filter value.
Shopify filter values are ready for setup when every source value has an approved label, a decision, an owner, and a validation status. Complete that catalog work before choosing where to configure the filters.
How should you use the worksheet?
Start with an export of the fields that could supply storefront filters. Use one worksheet row per raw value, not one row per product. For example, if 340 products contain navy, record navy once and add 340 as its product count. This makes duplicate meanings and one-off errors easier to see.
Create these columns: filter name, source field, raw value, product count, example SKU, approved label, action, canonical meaning, shopper alias, collection scope, owner, and validation status. Use a controlled action list: keep, rename, merge, split, suppress, or investigate. Avoid free-text actions because combine, consolidate, and map together may describe the same decision.
Work through one attribute at a time. Complete Color before Size, then Material, Fit, Product Type, and category-specific attributes. If the source data itself needs bulk correction, use the Shopify filter data bulk-edit template after the mapping decisions are approved. Do not edit live values while reviewers are still debating what they mean.
Build a source inventory before changing labels
Inventory every field currently feeding, or expected to feed, a filter. Common sources include product type, vendor, variant options, tags, category attributes, and metafields. Record the field and namespace precisely. Two values that look identical can require different treatment when one comes from a variant option and another comes from a product-level metafield.
Include product counts and at least one representative SKU. Counts reveal suspicious values: Black on 1,200 products and Balck on two products is probably a typo, while Blackened Steel on 18 products may be a distinct material or finish. The example SKU lets a category owner make that call without searching the catalog from scratch.
Mark blanks explicitly as missing; do not delete blank rows from the audit. Then segment missingness by collection. If Material is absent from 3% of T-shirts but 70% of gift cards, the first gap deserves catalog work and the second may justify excluding that filter from the gift-card collection. For metafield-based structures, review how Shopify products can be filtered by metafield before finalizing the source field.
Duplicate meanings need one canonical label
Normalize values in passes. First compare capitalization, spacing, punctuation, singular forms, and abbreviations. Extra Large, extra large, Extra-Large, and XL may share one canonical meaning. Second, compare near-synonyms such as Charcoal, Dark Gray, and Graphite. These require merchandising judgment because visual differences may matter even when internal teams use the words interchangeably.
Give each meaning a stable internal key and a shopper-facing label. A size key might be size_xl, with XL as the approved label and Extra Large as an alias. Keeping the key separate from the label makes future wording changes less disruptive to catalog governance.
Do not merge on text similarity alone. Spot-check at least five products for a high-volume value, or every product when the value appears on fewer than five items. Compare product images, specifications, and variant data. If a merge would place visibly different colors or incompatible sizes under one option, retain separate values and document the distinction. For broader filter architecture decisions, use the Shopify search facet best-practices guide.
Missing shopper language is a catalog defect
Translate operational codes into labels shoppers recognize. Values such as W, REG, P, SS, or 18/10 may be meaningful to a supplier or buying team but ambiguous on a collection page. The approved label should match the product and category: Wide Width, Regular Length, Petite, Short Sleeve, or 18/10 Stainless Steel may be appropriate when those meanings are confirmed by the catalog owner.
Add a shopper alias column without automatically displaying every alias as a filter value. Aliases help document search language and future mapping decisions, while the visible filter remains concise. For example, Couch can be recorded as an alias for an approved Sofa label without showing both checkboxes.
Review labels at mobile width before approval. Long values can wrap, push counts out of view, or make a filter drawer difficult to scan. Prefer the shortest label that remains unambiguous. Test the actual interface rather than imposing an arbitrary character limit; layout, font, and count placement all affect readability. The mobile search and filter guide provides the next set of storefront checks.
Seven decisions determine the final value map
Use the same decision criteria for every attribute so catalog teams do not make contradictory calls. As of August 2026, this worksheet treats value governance as a catalog decision first and an app configuration task second.
| Criterion | What to check | Why it matters |
|---|---|---|
| Duplicate meaning | Different strings describing the same option | Prevents repeated choices such as Grey and Gray |
| Distinct meaning | Similar labels attached to meaningfully different products | Prevents incorrect merges |
| Missing coverage | Products lacking a value within a relevant collection | Exposes incomplete filter results |
| Shopper wording | Codes, jargon, abbreviations, and supplier terms | Keeps labels understandable |
| Display consistency | Capitalization, units, punctuation, and number format | Makes the value list easier to scan |
| Collection scope | Whether the value is useful in each collection | Avoids irrelevant controls |
| Ownership | Who approves and maintains the mapping | Stops the same inconsistency returning |
Set an explicit decision for every row. Use merge when several raw values share one meaning, rename when the meaning is correct but the label is poor, split when one source value hides multiple meanings, and suppress when a value is irrelevant or unreliable. Use investigate only as a temporary state with an owner and due date. A worksheet full of unresolved values should not move into implementation.
Validate the map before storefront setup
Test the approved map against products before changing the shopper experience. For each filter, compare the total products in scope with the number carrying an approved value. Investigate differences rather than assuming every product needs every attribute. A service item may not need Color; every shoe variant probably needs Size.
Run combination checks, not only single-value checks. Open representative collections and test pairs shoppers are likely to use, such as Women + Size 8, Navy + Linen, or Laptop Sleeve + 16 inch. If a common combination returns nothing, determine whether the catalog is genuinely missing that assortment or whether the data uses an unmapped value such as 16-inch.
Keep a rollback export and assign one owner to approve publication. After cleanup, assess whether Hyper Search & Filter fits the required filter structure rather than selecting an app before requirements exist. Large or variant-heavy catalogs should also work through the storefront filtering readiness checklist. The implementation decision should account for collection scope, source fields, display requirements, and ongoing ownership.
FAQ
How do Shopify filter values work?
Shopify filter values are the selectable attribute values shoppers use to narrow a collection or search result. The available values depend on the product data, the fields chosen as filters, collection context, and the filtering setup. A Color filter might expose Black, Blue, and Green only when matching products in the current result set carry those values. Consistent source data is therefore essential: Blue and blue can create fragmented labels or mapping work depending on the setup.
How do I filter by product type in Shopify?
Populate a consistent product type for relevant products, then enable or configure product type as a storefront filter in the filtering system you use. Audit the taxonomy first because values such as Tee, T-Shirt, and T-Shirts can split one intended choice into several labels. The product-type taxonomy generator provides a six-action process for deciding what to keep, merge, rename, split, suppress, or investigate.
Is Shopify Search & Discovery free?
Shopify Search & Discovery does not have a separate app subscription fee, but merchants should confirm the current app listing and any applicable plan requirements before implementation. Price should not be the only decision criterion. Compare the required filter sources, merchandising controls, catalog scale, maintenance process, and storefront presentation. The native-versus-third-party filter guide helps structure that assessment.
Should similar color or size values always be merged?
No, similar values should be merged only when they represent the same shopper-relevant meaning. Merge capitalization differences and confirmed aliases, but keep values separate when the distinction affects fit, compatibility, appearance, or purchasing. Gray and Grey are usually candidates for one label; Light Gray and Charcoal may not be. Record the reason and approving owner so later catalog imports do not reverse the decision.
