Shopify product bundle metafield missing? Prove the owner, value, API path, and one add-to-cart.

Use this page when the value itself never lands: a definition never receives component metadata, an app shows blank data, or cart/ops tools never see the field. If the bundle builder, discount, or product page never shows the bundle at all, use the bundles not showing playbook instead. Combined Listings parent-child and cart-transform function bugs are separate paths.

Do not add a second metafield or install another bundle app yet. Capture the shop, bundle product, components, cart, and exact surface where the value should be stored or displayed.

Open Settings → Custom data and confirm the definition is owned by the resource your implementation writes — often a Product (bundle parent), Variant, Cart line, or app-owned resource. Record the exact namespace and key, for example bundle.components, the type, validations, and whether it is a plain value, list, reference, or JSON value.

Open the exact bundle product used on the live storefront. Save a short unmistakable test value (or complete one bundle configuration that should write it), refresh, and confirm it survives. A filled definition with no write, a value on a draft product, or a label that only looks right is not proof.

Compare the saved definition with the bundle app, cart-transform function, or Admin API mutation that should write the field, and with the read query used by theme, checkout, or ops. The write and read must use the same namespace.key on the same resource, and the app must have the intended access scope. A successful add-to-cart can still omit metafields, write another owner, or serialize component JSON differently than the code expects.

Verify the published Online Store theme and the active bundle / cart-transform app version. Log field presence without logging secrets. If a plain text test arrives but the intended structured component payload does not, fix type-specific parsing rather than changing discounts.

Bundles are context-sensitive. Record the market, currency, catalog publication, component availability, inventory, and whether the bundle product is published to Online Store. Confirm the metafield belongs to that bundle context and that the current theme/cart path is the one buyers use.

Keep the diagnosis distinct from the Combined Listings metafield and bundle discount not applying paths. They can affect related merchandising while reading different resources and fields.

Use one published bundle and one component combination. Record the resource ID, namespace.key, type, saved test value, app/theme version, write success, read presence, and cart/line-item output. Repeat logged out if the result is customer-facing, then test a second component set only after the first path is proven.

If the field is still missing, classify it as definition/value, access/write, resource context, unpublished theme/app, or type parsing. Do not call a “bundles not showing” failure until a bundle exists and the write path is demonstrably attempted.

Stay DIY when one definition, write path, read query, or published-version check explains the missing field. Keep the proof packet so future bundle changes are reversible.

Pay for the $997 one-time install when several Shopify surfaces, apps, cart transforms, 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.