Connecting Metaobjects in OS 3.0 Theme Editor

Metaobjects are store-level, reusable data records that can be connected to components on any page of your store, making them ideal for content shared across many products, such as size guides, ingredient libraries, or care instructions. Unlike product or collection metafields, Metaobjects are not tied to a specific page. 

This guide explains how to connect a Metaobject entry to a component in the OS 3.0 Theme Editor, use nested Metaobject references, and apply Metaobjects across real store scenarios.

Prerequisites for Connecting Metaobjects in OS 3.0

Before you begin:

• Your store must be running an OS 3.0 theme. Metaobject dynamic sources are an OS 3.0-exclusive feature.
• You must have created a Metaobject definition and added at least one entry in the admin panel. If you haven't done this yet, see "Customizing Your Store Content with Metaobject" before following the steps below.

Understanding Metaobjects as Store-Level Dynamic Sources

A Metaobject is a standalone, reusable data record you create and manage in your admin panel. Because Metaobjects exist at the store level, not attached to any specific product or page, you can pull their data into any component that supports dynamic sources, on any page of your store.

This makes Metaobjects especially useful for content that is shared across many products or pages, such as:

• A size guide used by an entire clothing line
• An ingredient library referenced across a beauty catalog
• A designer profile shared across all products in the same furniture collection

Connecting a Metaobject Entry to a Theme Editor Component

Once you have created your Metaobject definition and added entries in the admin panel, follow these steps to bind a Metaobject field to a component in the Theme Editor.

To connect a Metaobject:

1. In the Theme Editor, click the block you want to bind (e.g., Rich text section).
2. Click the Add dynamic source icon next to the content input field.
   
3. In the dynamic source panel, select Metaobject.
4. From the first list, select the Metaobject type (the definition name, e.g., "Ingredient" or "Size Chart"). 
5. From the second list, select the specific entry you want to display (e.g., "Niacinamide" or "Women's Tops").
6. From the third list, select the field whose value you want to show (e.g., "Benefits" or "Measurement Table"). Click Save to confirm the binding.

Advanced: Using Nested Metaobject References in OS 3.0

OS 3.0 supports up to two levels of Metaobject nesting. When selecting a field to display (Step 6 of "Connecting a Metaobject Entry to a Theme Editor Component" — where you choose the specific field whose value to show), if that field is itself a reference to another Metaobject, the editor lets you click into it to reach the inner object's fields.

Example: A "Product Story" Metaobject contains a "Photographer" field that references a separate "Team Member" Metaobject. You can drill in to display the photographer's name or profile image directly from the Product Story component.

Real-World Use Cases for Metaobjects

The following examples show how different store types use Metaobjects to keep content consistent without repeated manual updates.

Fashion: Shared Size Guide

A clothing store creates a "Size Chart" Metaobject with fields for Category, Image, and Measurement Table. Multiple products share the same size chart entry. When the measurements change, the store updates the entry once, and the change reflects on every product page automatically.

Health & Beauty: Ingredient Library

A skincare brand creates an "Ingredient" Metaobject with fields for Ingredient Name, Benefits, Description, and Scientific Reference. Entries include Niacinamide, Hyaluronic Acid, and Retinol. Each product page connects to the relevant entries to display a structured Key Ingredients section, sourced from one central library.

Furniture: Designer Collection

A furniture retailer creates a "Designer" Metaobject with fields for Designer Name, Portrait, Bio, and Design Philosophy. Entries include designers such as Thomas Berg and Clara Voss. Multiple products in each designer's collection reference the same entry, so when a designer updates their bio or a new portrait photo is added, the change reflects instantly across every product page in that collection.

Frequently Asked Questions about Metaobjects

Q 1 Can I use Metaobjects on pages other than product pages?

Yes. Because Metaobjects are store-level sources, you can connect them to components on any page, homepages, custom pages, collection pages, and more.

Q 2 What is the difference between a metafield and a Metaobject?

A metafield is a custom attribute attached directly to a resource such as a product or collection. A Metaobject is a standalone, reusable data record that can be referenced across multiple products, pages, or components. Use metafields for product-specific data and Metaobjects for shared content libraries. For more on metafields and dynamic source dimensions, see "Configuring Dynamic Sources (Metafields) in OS 3.0 Theme Editor."

Q 3 How do I create a Metaobject definition and add entries?

Metaobject creation and management is covered in "Customizing Your Store Content with Metaobject." Complete that setup first, then return to this guide to connect entries to your storefront.