Connected variant option connector does not surface custom namespace metafield definitions — undocumented limitation

Store Design
,
1

I’ve been setting up connected variant options using metaobjects and ran into an undocumented platform limitation that cost significant time to diagnose.

What I did:

  1. Created a custom metaobject definition (e.g. “Condition”) with 6 entries
  2. Created a variant metafield definition under custom.condition typed as “Metaobject entry” pointing to that definition
  3. Enabled Storefront API access on the definition
  4. Attempted to connect it via the variant option connector on the product page

Result: “No compatible metafields found” — the definition does not appear in the connector dropdown at all.

Root cause (after testing): The connected variant option connector appears to only surface metafield definitions under the shopify namespace. Custom namespace definitions (custom.*) are silently excluded with no error or explanation.

Why this matters:

  • The shopify namespace is reserved and throws “This namespace is reserved for standard definitions” when you attempt to create there
  • Category metafields (also shopifynamespace) are locked to taxonomy-defined attributes
  • This leaves no supported path to connect a custom metaobject-backed variant option

Request:

  1. Document this namespace restriction explicitly in the connected variant options help docs
  2. Consider exposing custom namespace metafield definitions in the connector, or provide an official supported workaround

Store plan: Basic. Tested June 2026.

2

There are a lot of possible ways to screw up metafields on the merchant’s end. Not enough information to determine what exactly is the problem, but I’d say you made a mistake somewhere. Custom namespace shouldn’t be an issue. Here are some things to think about.

When creating the metafield, did you choose list type? Or did you leave that as “one”? That makes a huge difference. You created a variant metafield but are trying to connect the product? The product page connector can only see product metafields, not variant metafields.

3

@serafinibooks I think the confusion may be between a variant option and a variant metafield.

This feature is used when adding/configuring variants, but the “connector” is for connecting a variant option to a compatible product/category metafield, not for connecting an individual variant metafield.

Shopify’s documentation for linked product options says the metafield definition should be:

Owner type: Product
Type: list.metaobject_reference

So custom.* may not be the issue here. The issue is more likely the owner/type combination.

From your description, it sounds like you created:

Owner: Variant
Namespace/key: custom.condition
Type: Metaobject entry

But the connector is looking for:

Owner: Product
Namespace/key: custom.condition
Type: List of metaobject references
Reference: Condition metaobject definition

Then, on the product page, the product-level metafield would hold the available Condition entries for that product, and the variant option connector would use those entries as the option values.

Tested and confirmed, with screenshots pasted below for reference.

Variant connected to Product metafield “Condition”

condition-options
condition-options1177×640 34.3 KB

Product metafield using Type: List of metaobjects (using a custom namespace)

product-metafield
product-metafield1319×516 16.3 KB

In conclusion, custom.* may not be the issue here. The issue is more likely the owner/type combination.

5

First, ensure you didn’t leave the field set to a single entry instead of selecting the list type, as that makes a huge difference.

Second, verify your field level if you created a variant metafield but are using the product page connector, it won’t show up. The product connector can only pull product-level metafields.

6

Thank you everybody! I solved this based on your advice as follows:

  1. Created the Metaobject definition as “one” single line text
  2. Created the Product Metafield definition as a “list” of metaobjects
  3. Immediately visible, linked to custom metaobject.

Store consistency achieved! Thank you all!