Metafield architecture for stores that scale past $50M

How to model metafields so your storefront doesn’t become unmaintainable.

Metafield architecture for stores that scale past $50M

Metafield architecture is the most under-discussed scaling problem on Shopify Plus. Get it wrong early and you’ll be migrating it for years.

Three rules

  • Use definitions, not free-form keys. Free-form metafields become technical debt the moment more than one app touches them.
  • Reference, don’t denormalize. Reference other metaobjects when relationships exist. Don’t copy data between metafields.
  • Namespace by domain. marketing.*, logistics.*, compliance.*. Keep apps in their lanes.

Metaobjects vs metafields

Metaobjects for entities (like "ingredient", "collection_lookbook"), metafields for product/variant attributes (like "serving_size", "made_in_country").

If you’re storing structured data inside a single metafield string, you owe yourself a metaobject.
← Back to all articlesWork with us