Shopify metafields give food and beverage merchants a structured, low-maintenance way to manage the product data that drives comparison decisions — flavors, ingredients, nutritional profiles, allergens, and certifications. The food and beverage comparison tables overview covers the full picture — this page focuses on the metafield architecture that keeps these tables accurate without manual upkeep.
Why metafields are the right approach for food and beverage comparison tables
Food and beverage product data changes. Formulations are updated, new flavors are introduced, nutritional values are revised, certifications are added or renewed. If your comparison tables are built from static HTML or maintained separately from your product catalog, every change requires finding and updating every affected table page. Miss one and a comparison table is showing incorrect nutritional data or omitting a new certification.
Shopify metafields store each attribute as a structured field on the product. A change in Shopify propagates to every comparison table that reads from that metafield automatically. No parallel content workflow needed.
The metafield schema for food and beverage products
For food and beverage comparison tables, useful metafields to define include flavor or variety name (single-line text), primary ingredients (text or list), calories per serving (integer), protein per serving in grams (integer), carbohydrates per serving (integer), sugar per serving (integer), fat per serving (decimal), allergens present (list of strings), serving size (text), format — powder, ready-to-drink, liquid concentrate, snack bar (single-line text) — and certifications (list of strings — vegan, kosher, gluten-free, organic). Define these in Shopify’s Custom Data settings under a namespace like food, then map the fields to columns in SimplyCompare.
How your data flows from Shopify into the comparison table
SimplyCompare queries the Shopify Storefront API for current metafield values at the time each shopper loads the table. The data is always current because the query happens at render time, not at publish time. A reformulation, a new certification, or a revised nutritional value in Shopify is immediately reflected in every comparison table that includes that product — no table republishing, no cache clearing, no editorial workflow for the table itself.
Frequently asked questions
How should I handle products in the same line with different nutritional profiles per flavor?
The best approach depends on your Shopify structure. If each flavor is its own product, define individual product metafields for nutritional values and each product in the comparison table pulls its own live values. If flavors are variants of one product, use variant metafields for the values that differ per flavor.
Can I include allergen information in a food and beverage comparison table?
Yes. Storing allergens as a list-of-strings metafield lets you display an allergen summary in a comparison column. For food labelling compliance, ensure your primary allergen declarations are on the product page and packaging in accordance with your applicable regulations.
Does SimplyCompare require a specific metafield naming convention?
No. SimplyCompare connects to your metafields by namespace and key. You can use whatever naming structure already makes sense for your catalog team.
Can I display certifications like vegan or kosher in the comparison table?
Yes. Store certifications as a list-of-strings metafield and map it to a column in SimplyCompare. They appear as a comma-separated list in the comparison cell — for example, “Vegan, Gluten-Free, Kosher.”