Shopify Product Bundles API metafield missing? Prove bundle GID, API field, and one write.

Use this page when Product Bundles Admin/GraphQL (or a Bundles / cart-transform app that reads via Admin API) should return a metafield on a bundle or component GID but the field is null or omitted. If the miss is only the Online Store bundle UI ignoring a theme/metafield dynamic source, use product bundle metafield missing. If the Bundles app widget or components will not show, use bundles not showing or bundle builder not showing.

Do not rebuild every bundle yet. Capture the shop, bundle GID, component GIDs, namespace.key, Bundles 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 the app-owned bundle resource your query expects). Record whether the missing field should live on the parent bundle product or a specific component, the exact namespace and key (for example bundles.component_map), the type, and whether the Bundles 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 Product Bundles API queries.

Confirm the Admin GraphQL selection names the metafield correctly (namespace.key and type) on the bundle or component Product node, the app token can read products and metafields (and Bundles-related scopes if the app requires them), and one GraphiQL read of the same GID returns the resource that should carry the field.

Compare custom apps and native Bundles admin: a query that never selects metafields on the bundle parent will look "missing" even when GraphiQL has the value on a component. Soft-link Cart Transform API metafield blank when the miss is cart-transform function config rather than Bundles Admin API. 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 bundle or component GID. Prove the same value in Admin GraphiQL, then re-run the Bundles-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 Combined Listings API metafield blank and kit inventory wrong. Those touch Combined Listings parent/child API fields and kit stock math, not Product Bundles API metafield reads.

Use one test shop, one bundle product, and one component set. Record namespace.key, type, bundle and component GIDs, GraphiQL value after write, Product Bundles 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 bundle snapshot.

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

Stay DIY when one definition, GID mapping, scope, or write explains the miss. Keep the proof packet so future Product Bundles API changes stay grounded in real bundle 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.