I created a product-features metaobject. Why is it not attached to any product?

Work through the cause

1. Confirm that the definition contains the needed fields and that the intended entry has approved content. Keep entry names distinct.
2. Inspect the reference metafield on the specific product and select the correct entry using the supported admin workflow.
3. Preview two products with different references and one without a value. Check how the theme handles each case before release.

A concrete case (illustrative)

Illustrative case: a Materials entry and a Care entry exist in Content, but a bottle’s product-features reference is empty. Creating the entries alone does not tell the storefront which one belongs to that bottle.

Acceptance and next action

Pass when each product points to the correct entry and the theme renders the intended fields. Reusable data reduces repeated editing only when its reference scope is deliberate. Do not assume every product should receive the first available entry.

Take this question’s manual review card

The worksheet contains this question’s steps and acceptance condition. Fill in your actual source, observations and decision; blank fields do not mean approval. It does not connect to a store, modify files or automatically approve a result.

Download this review card (CSV)

Source scope: the linked documentation explains relevant tool behavior or technical context. The merchant scenario, review choices and acceptance condition are CartVisual editorial guidance; citation does not imply endorsement.