Shopify metafields give beauty merchants a structured, maintainable way to power comparison tables without manual updates. The beauty and skincare comparison tables overview covers what these tables do for shoppers — this page goes into the metafield architecture that makes them accurate and low-maintenance.
Why metafields are the right approach for beauty comparison tables
Beauty product data is detailed and changes. Skin type suitability, active ingredient percentages, formula type, SPF, certifications, size, and benefits all matter to well-informed shoppers. Keeping that data accurate in comparison tables built from static HTML is a constant editing burden — every reformulation, certification update, or product range addition requires finding and updating every affected table page.
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. The table is as current as your product data without any additional publishing work.
The metafield schema for beauty products
For beauty comparison tables, useful metafields to define include skin type suitability (list of strings — oily, dry, combination, sensitive), key active ingredients (text or list), formula type (single-line text — serum, moisturizer, toner, cleanser), SPF (integer or text), finish (matte, dewy, natural), certifications (list of strings — cruelty-free, vegan, COSMOS organic), fragrance-free status (true/false), and product size in millilitres (integer). Define these in Shopify’s Custom Data settings under a namespace like beauty, then map the relevant 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. There is no static snapshot to keep in sync. A formulation update, new certification, or size change in Shopify is immediately reflected in every comparison table that includes that product. For beauty brands running regular reformulations or expanding into new product ranges, comparison table accuracy is maintained automatically as a byproduct of keeping your product catalog current.
Frequently asked questions
How do I handle beauty products with multiple skin type values in one metafield?
A list-of-strings metafield in Shopify works well here. SimplyCompare displays the list as a comma-separated string in the comparison table column — for example, “Oily, Combination” — which keeps the cell readable without wrapping.
Can I show SPF and finish in separate comparison columns?
Yes. Each column in SimplyCompare maps to one metafield. Keeping SPF and finish as separate columns is recommended — it makes it easier for shoppers to scan and compare those attributes independently across multiple products.
Does SimplyCompare require a specific metafield naming convention?
No. SimplyCompare connects to your metafields by namespace and key, whatever names you have used. If your metafields already follow a different naming scheme, you can map them directly to table columns without renaming anything.
What if I add a new product range and want it in existing comparison tables?
Add the new products to your Shopify catalog, populate their metafield values, then add them to the relevant comparison tables in the SimplyCompare app admin. The table will start displaying the new products’ live data immediately.