If these are theme-specific metafields, use a dedicated namespace instead of custom. A clean and scalable setup would be:
| Definition Name | Namespace | Key | Type |
|---|---|---|---|
| Cutline | theme | cutline | Single line text |
| Siblings Color | theme | siblings_color | Single line text |
| Siblings | theme | siblings_collection | Single line text |
| Sibling Products | theme | sibling_products | Product (List) |
Recommended descriptions
Cutline
A label that identifies the sibling attribute, such as Color, Flavor, Size, or Pack Size.
Namespace: theme
Key: cutline
Siblings Color
Specifies the current product’s color value for the sibling selector. Used to highlight the active color swatch.
Namespace: theme
Key: siblings_color
Siblings
Enter the collection handle that contains all sibling products. The theme uses this collection to automatically display related products.
Namespace: theme
Key: siblings_collection
Sibling Products
Select specific products that belong to the same product family. The theme displays these products as sibling options on the product page.
Namespace: theme
Key: sibling_products
Even better (recommended)
Instead of the Siblings text field (collection handle), you can make it a Collection reference:
- Definition Name: Siblings Collection
- Namespace:
theme - Key:
siblings_collection - Type: Collection
This is safer because merchants select a collection directly instead of typing its handle manually.