Advanced customizations
Beyond Theme settings — metafields, templates, and when to involve a developer.
Most stores launch with Theme settings, sections, and metafields. Use this guide when you need templates, liquid-level changes, or app architecture beyond the editor.
Sales channels > Online Store > Themes > Customize (settings) · Settings > Custom data (metafields)
Metafields and metaobjects
- Product metafields power service duration, artist cards, and “Starting at” overrides.
- Define definitions in Settings → Custom data before merchants fill values.
- Theme docs for product pages list which namespaces Studio Arcana reads.
Alternate templates
- product.service.json — service-oriented PDP
- Assign templates per product in Admin → Products → theme template
- Keep one clear CTA pattern per template (cart vs booking)
When to involve a developer
- New section types or Liquid logic
- Checkout extensibility and Shopify Functions
- Headless or Hydrogen storefronts (separate from this Liquid theme)
- Complex app orchestration across Engine, Sentinel, or Reserve
Preserve upgrade safety
- Avoid editing core theme files when a setting exists.
- Document any forked snippets.
- Test on a duplicate theme before publishing.
Was this page helpful?
Content is maintained by Arcanum Hollow Labs. For internal engineering notes, see the docs/ folder in the monorepo.