Metafields Modeling Guide

Map the data

• List every piece of content your products need beyond the standard fieldsUnlisted needs turn into one-off app installs, scattering data across tools you do not control.
• Mark which items describe one product and which are shared across manyThis split decides between metafield and metaobject, and getting it wrong means rework.
• Use a metafield to add typed data to an existing objectModeling a simple attribute as its own record adds complexity with no benefit.
• Use a metaobject for a new kind of record, like a size guide or brandCopying shared content into each product means editing it in dozens of places.
• Flag needs that require an interface or external calls, not just dataThose are the cases where an app is still the right tool, so separate them early.