Metafields
A handful of features read metafields. All of them are optional — skip the lot and the theme still works, those parts simply do not appear.
Metafields are created under Settings → Custom data, then filled in on each product or collection.
Two settings that matter
Type. The theme expects a particular type for each metafield below. A rich text field where a list is expected renders nothing.
Storefront access. Only needed if the metafield will be used as a filter. Liquid reads a metafield without it, so collection content works either way — but a filter will never appear, and nothing tells you why.
Collection
These drive the content below the product grid. The collection page guide covers how they interact with blocks.
| Key | Type | Drives |
|---|---|---|
custom.about | Rich text | The About block. The key is a section setting, so you can point it elsewhere. |
custom.benefits | List of metaobject references | Benefit cards |
custom.faqs | List of metaobject references | FAQ items |
custom.related_collections | List of collection references | Related collections |
custom.hide_sections | List of single line text | Hides about, benefits or faq on one collection |
Metaobject entries created through the API default to draft. They must be active or nothing renders.
Product
Reviews
The theme reads Shopify's standard keys and four apps directly, so ratings work without mapping anything.
| Source | Keys |
|---|---|
| Shopify standard | reviews.rating, reviews.rating_count |
| Judge.me | judgeme.badge |
| Loox | loox.avg_rating, loox.num_reviews |
| Yotpo | yotpo.reviews_average, yotpo.reviews_count |
| Stamped | stamped.badge |
A product with no reviews shows nothing. Empty grey stars are never rendered.
Specifications
The specifications panel takes a list, one per line, written as Label:namespace.key:
Material:shopify.material
Volume:custom.volume
Origin:custom.origin
Any metafield works, including Shopify's own category ones. A row whose metafield is empty is skipped, so a partly filled table has no blank rows.
FAQs
| Key | Type | Drives |
|---|---|---|
custom.faq | Multi-line text | Product FAQ accordion and FAQPage schema |
Written as plain Q: ... / A: ... lines — the theme splits on those markers, so no special formatting is needed beyond that convention. The metafield key is a section setting (FAQ metafield for search engines), so point it elsewhere if you'd rather use a different key.
Filters
Any product metafield can become a filter. See Filters.
Blog posts
| Key | Type | Drives |
|---|---|---|
custom.reading_time | Single line text | "5 min read" beside the author and date |
The theme does not calculate it. Write the number in, and only the number.
When something does not appear
In this order. Most cases are one of the first three.
- The metafield has no value on that product or collection.
- The block is switched off in the section settings.
custom.hide_sectionsnames it on that collection.- The type does not match what the theme expects.
- Metaobject entries are still drafts.
- Storefront access is off, if it is being used as a filter.