Shopify Storefront Filter API metafield missing? Prove filter GID, API field, and one write.

Use this page when Storefront Filter Admin/GraphQL (or a filter app that reads via Admin API) should return a metafield on a product or collection GID but the field is null or omitted. If the miss is only the Online Store collection facet ignoring a theme/metafield value that exists in Admin, use storefront filter metafield blank. If filters click but do not narrow results while values exist, use collection filters not working.

Do not rebuild every filter definition yet. Capture the shop, product GID, collection GID, namespace.key, filter app ownership, and whether any metafield mutation runs on the resource the API query selects.

Open Settings → Custom data and confirm the definition is owned by Product (or Collection, if that is what the Filter API reads). Record the exact namespace and key (for example filters.api_material), the type, validations, and whether the filter app owns the definition.

Manually save a short test value on the correct GID in Admin, refresh, and confirm it survives. If Admin cannot store the field on that GID, fix the definition or ownership before debugging Storefront Filter API queries.

Confirm the Admin GraphQL selection names the metafield correctly (namespace.key and type) on the product or collection node, the app token can read products/collections and metafields, and one GraphiQL read of the same GID returns the resource that should carry the field.

Compare custom apps and Search & Discovery filter config: a query that never selects metafields on the product will look "missing" even when GraphiQL has the value. Soft-link Search & Discovery filters broken when filter sync itself is broken with populated values. Log query name and field keys only — never log personal data beyond what the shop already stores.

After a stable definition, run one authenticated metafieldsSet for the namespace.key you recorded on the known product or collection GID. Prove the same value in Admin GraphiQL, then re-run the Storefront Filter-aware API query. If GraphiQL shows the test value but the app API does not, fix the query selection or GID mapping — not the definition alone.

Keep the diagnosis distinct from Storefront API metafield blank and Search & Discovery filters empty. Those touch Storefront API publication and S&D empty states, not Storefront Filter API fields.

Use one test shop, one collection, and one filter definition. Record namespace.key, type, product and collection GIDs, GraphiQL value after write, Storefront Filter API / app result, and whether the admin UI that depends on the field respects it. Clear app caches between trials so the shop is not left with a stale filter snapshot.

If the field is still missing, classify it as definition/value, query never selecting the field, wrong product vs collection GID, missing read scope, write never ran on the API-owned resource, or app cache lag. Do not rebuild the filter tree until one write and one API read clean on one collection.

Stay DIY when one definition, GID mapping, scope, or write explains the miss. Keep the proof packet so future Storefront Filter API changes stay grounded in real product/collection fields.

Pay for the $997 one-time install when several Shopify surfaces, apps, catalogs, and ops alerts need to be wired and documented on one live store. Nico at Latch AI Ops can connect the agreed workflow in a 72-hour window after collaborator access. No earnings claim, conversion guarantee, or theme rebuild is included; owner passwords are not requested.