Metaobjects and their entries
A metaobject is a content type you define. Not an attribute of a product — a thing in its own right, with its own fields, that many products can point at.
An author. A size chart. A care symbol with an icon and an explanation. A store location with opening hours. Each is defined once as a type, and then created as many times as you need.
Where it lives
Section titled “Where it lives”Custom data sits in the sidebar’s Content section, next to pages and the blog, because a type is defined once and then written into every week like any other content. The page has two parts: Metafields, one row per kind of record (products, variants, categories, collections, pages, blog posts, customers, orders) with the number of fields defined on it, and Metaobjects, your content types.
Custom data used to be under Settings. Old /settings/custom-data/... addresses, including
bookmarks to a single entry, forward to the same screen under /content/custom-data/.
Who can do what
Section titled “Who can do what”Writing entries is content work, so it follows the content permissions. Defining a type changes how every one of its entries is stored and where it appears on your site, so it stays a settings task.
| You hold | What you can do in Custom data |
|---|---|
| Settings (owners and admins have it) | Everything: define, change and delete types and their fields, set their address, search listing, schema and map settings, define metafields, and write entries — including publishing them. |
| Content with Approve content | Add, edit, publish, reorder, rename, delete and import entries. Types and their fields are shown read-only. |
| Content only (the Content editor role) | Add and edit draft entries, duplicate entries as drafts, and check an import file. Types and their fields are shown read-only. |
A Content editor cannot put a change on the live site by themselves, exactly as with pages: publishing or scheduling an entry, and changing, renaming, reordering or deleting an entry that is already live, needs Approve content (or Settings). The editor saves a draft and someone with that permission publishes it. In a type that is not Publishable every entry is live as soon as it is saved, so a Content editor cannot add or change entries of that type at all.
Formatted text that a Content editor writes is cleaned the same way as the text of a content page (scripts and similar code are removed when it is saved). The Metafields part of the page, the settings cards on a type’s page (search listing, scale, schema mapping) and Add definition are shown only to people who hold Settings (or Settings (view only), read-only).
Type first, entries after
Section titled “Type first, entries after”The work happens in two stages, and not everything in the first is reversible.
- Define the type. Its name, its handle, its fields, and its capabilities.
- Add entries. One per author, per size guide, per location.
🔴 A type’s handle cannot be changed after it is created. The form says so: “Lowercase, url-safe. Can’t be changed later.” The handle is the type’s address segment and its theme template’s key, so pick it before you save.
The fields stay editable. On the type’s page, Edit fields lets you add, rename, reorder or remove fields later, with three limits:
- A saved field’s key and type cannot change. Every entry stores its value under them; to change either, add a new field instead.
- A new field cannot be required while the type has entries. Save it as optional, fill it in on the existing entries, then make it required.
- Removing a field hides its values; it does not erase them at once. Add the field back with the same key and type and they reappear, but any entry saved in the meantime drops them.
Capabilities decide what a type can do
Section titled “Capabilities decide what a type can do”| Capability | What it gives every entry |
|---|---|
| Publishable | A publish state — draft, live, or scheduled for later. Without it, entries are always live. |
| Translatable | Entries appear in the translation workspace alongside the rest of your content. |
| Renderable | Entries carry SEO fields and can enter your sitemap. |
| Online store page | Each entry gets its own URL, rendered from its own template. |
One rule is enforced rather than suggested: a type with an online store page must also be renderable. A page with no title, no description and no sitemap entry is a page no search engine can find, so the admin switches Renderable on and locks it while Online store page is on.
The creation form says capabilities “can’t be changed later”, but the type’s Edit dialog does let you change the name, the description and the capabilities afterwards. One change is refused: turning Publishable off while the type has entries that are not live. That would put every draft live at once, so publish those entries first. To delete entries, select them in the Entries list and choose Delete.
Delete on the type’s page removes the type and all of its entries permanently.
The entry behavior that can overwrite work — read this before you start
Section titled “The entry behavior that can overwrite work — read this before you start”Entries are addressed by a handle you choose, like summer-tee. Once an entry exists, its
handle cannot be changed.
🔴 Saving a new entry under a handle that already exists replaces that entry. The form says so under the handle box: “Saving over an existing handle replaces that entry.” There is no “this handle is taken” warning. Before you create an entry, search the Entries list on the type’s page for the handle you are about to use.
A handle convention that cannot collide — author-a-yilmaz, guide-womens-tops — is worth more
here than a tidy one.
The Entries list shows each entry’s state, can be searched, and pages through long lists. Move up and Move down set the type’s order, which is the order a theme renders the entries in. The arrows are not offered while a search is active, because a filtered list does not show true positions.
Entries carry more than their fields
Section titled “Entries carry more than their fields”Beyond the type’s own fields, an entry can carry:
- Translations of its text and image fields, if the type is translatable: pick a Language, and each field shows the Original beside its Translation. A field you leave untranslated shows the original; Leave empty in this language makes it show nothing in that language instead.
- A search engine listing — title and description, falling back to the handle — if the type is renderable.
- Visibility — draft, live, or scheduled — if the type is publishable.
A field that points at another record opens a picker where you search by name, rather than asking you to paste an id. A file field opens your media library.
What this page does not say
Section titled “What this page does not say”- It does not walk through the entries list or the entry form field by field. That needs a current screenshot first.
- It does not cover linking entries to products. A reference-typed metafield is what points a product at an entry.
- It does not describe how entries render. What a theme does with a renderable entry, or with an entry’s own page, is a theme question, not a custom-data one.