Halal + Kosher + Hindu-veg + Jain certifications per SKU, how is it modeled?

Magento product attributes, four parallel cert dimensions, each backed by a multi-select attribute storing the certification body + cert ID.

• Halal: IFANCA / Halal Watch / Halal Transactions of America / Crescent Star Foods. Cert ID example: IFANCA-HMC-1234. Renders as a green crescent badge on PDP with the cert authority + ID, linkable to IFANCA’s verification page.
• Kosher: OK Kosher / OU (Orthodox Union) / KSA / Star-K. Cert ID e.g. OU-D (dairy), OU-Pareve. Similar badge + verification link.
• Hindu-veg, no meat / egg / fish. Self-flagged by the brand (no third-party cert body for this); rendered as a green-dot badge.
• Jain, no onion / garlic / root vegetables (potato, carrot, ginger). Stricter than Hindu-veg. Self-flagged; rendered as a distinct badge.

Filtering: Magento layered nav exposes each cert as a filterable facet on category pages. A Muslim-American shopper on a pan-Asian grocer filters “Halal: IFANCA” and sees only the ~30-50% of SKUs that carry it. PDP renders the cert ID prominently above the add-to-cart button, ~40% of South Asian / Middle Eastern diaspora customers refuse to buy from stores that don’t show the cert ID.

Compliance-aware bundles: Magento bundle products check cert compatibility before allowing the combo. You can’t auto-bundle a Hindu-veg curry kit with a non-veg masala. Same logic on recommended products, a Jain shopper doesn’t see onion-containing “related items.”

This is the single biggest reason ethnic-food brands move off Shopify, Shopify metafields support cert IDs but the layered-nav filter UX is bolted-on, slow, and breaks at >500 SKUs.