Search page filters ignore metafield-only updates that are correctly reflected in collection page filters

We added a product metafield as a Search & Discovery filter and filled it in on every product through the Admin API. Collection pages filtered correctly within minutes. The search page didn’t: a product only showed up under the filter once something else on it was edited, like a tag or the title.

Our setup

  • Product metafield definition “Department”, filterable.department, type list.single_line_text_field, limited to the choices Women / Men / Kids.
  • Definition options: “Filter on the product list and in the Admin API” on, “Use as a condition in collections” on, “Storefront API access” on, “Filter or group data in Analytics” off.
  • Added as a filter in Search & Discovery, which applies to both collections and search.
  • Values written as JSON lists, e.g. ["Women"] or ["Women","Men"], with metafieldsSet.
  • Our theme doesn’t show this filter in its filter panel; we apply it through the filter.p.m.filterable.department URL parameter, the same way on collection and search pages.

Steps to reproduce

  1. Create the product metafield definition exactly as listed under “Our setup” above (filterable.department, all four options as shown) and add it as a filter in Search & Discovery.
  2. Write a value on an in-stock product with metafieldsSet. We wrote 55,750 products, 25 per call, with no errors.
  3. Open a collection containing it, with ?filter.p.m.filterable.department=Women. It’s there within minutes.
  4. Open /search?q=<its title>&filter.p.m.filterable.department=Women. It’s missing, though the same search without the filter finds it.
  5. Add and remove any tag on the product and reload step 4. It shows up within a minute or two.

Expected: search applies the filter the way collections do, without step 5.

Actual: about 8 hours after our backfill, filtered search still returned none of the products whose metafield we’d only written through the API.

What we tested

All on in-stock products, checking /search with and without the filter:

  • Waited it out. Four products written by the backfill were still missing from filtered search 5.5 hours later, while a filtered collection had shown them all along.
  • Rewrote the value with productUpdate (changed it, then set it back). Still missing 40 minutes later.
  • Added and removed a tag on another. In filtered search within a minute.
  • Changed a third product’s title and changed it back. In filtered search within 1.5 minutes.
  • Changed an existing value from Women to Men on a product search already had under Women. Search kept it under Women for as long as we watched, until a tag edit moved it to Men within 30 seconds. So it isn’t just the first write.

Untouched products checked alongside the tag, title and productUpdate tests stayed missing, so it’s the edit that makes the difference, not time passing.

Both metafieldsSet and productUpdate bump the product’s updatedAt, so it isn’t simply that the product wasn’t updated. Once a product did refresh, search also held on to its old value for a few minutes (it matched both Women and Men).

Impact

This is easy to miss. Admin shows the values, collection filters work and plain search finds the products, so nothing looks wrong. The only sign is that people searching with the filter never see those products.

High-volume and heavily customised stores are the most likely to hit this. They update metafields in bulk through imports, apps, Flow and scripts rather than by editing products one at a time, so their writes are exactly the metafield-only kind that search ignores. With thousands of products nobody spot-checks filtered search either. Meanwhile shoppers silently miss products they’re looking for: they apply the filter, get fewer results, and have no way to know what’s missing.

We only noticed because we were rebuilding our search around this filter, so it was a core feature and nearly our whole catalogue was missing from it. A smaller change, like adding or correcting values on a few dozen products, would leave those few products quietly missing, and nobody would ever notice.

For now we’re adding and removing a throwaway tag on every in-stock product. Doing this appears to cause a reindex within 30 to 90 seconds, judging by how soon products showed up in our checks. That’s about 14,000 extra writes, each one firing our product-update webhooks.

We’d expect metafield writes to refresh search filters the way they already refresh collection filters.

Hi @abosworth, thanks for the thorough post! Your results are consistent with a known search-refresh issue affecting metafield-only updates. I reproduced the collection/search mismatch on a test store. Adding a tag to one of two products refreshed only that product in search, while the untouched product kept its old filter value.

Metafield-only updates aren’t reliably reflected in search filters in real time. A separate product edit can trigger reindexing, but it isn’t a guaranteed workaround. Given the extra writes and webhook traffic you’ve described, I wouldn’t recommend catalogue-wide tag edits as a routine fix.

The filter troubleshooting guidance recommends allowing 24–48 hours for automatic reindexing. I’ve raised your report with the relevant team, but I don’t have a fix ETA to share. I’ll follow up here once I have more details to share, thanks again for sharing your findings!