Magento for Cosmetics + Beauty: 12 questions answered.
Frequently asked questions about Magento + Hyvä for cosmetics + beauty brands, shade matching, subscriptions, loyalty, compliance, influencer tracking, UGC.
Cost + timeline for a beauty Magento build?
Honest fixed-price tiers, no per-hour surprises. All three include pre-project audit, regression QA, blue-green deploy, Lighthouse 90+ guarantee, and 14 days of post-launch bug-fix coverage.
- Beauty Express ($12k, $25k, 6-8 weeks), Hyvä storefront + ingredient/allergen filters + quiz-based shade finder + Mageworx Subscriptions + Smile.io loyalty integration. Single region (US or EU or IN).
- Beauty Standard ($25k, $60k, 10-14 weeks), everything in Express + AR shade matcher (Modiface / YouCam) + tier-based loyalty (LoyaltyLion or custom Amasty) + Refersion influencer tracking + Yotpo UGC. Two regions (e.g. US + EU).
- Beauty Enterprise ($60k, $150k+, 14-24 weeks), everything in Standard + multi-region compliance (FDA + EU CPNP + India CDSCO) + Akeneo PIM + B2B salon supply layer + Aspire / Impact partnership platform + custom loyalty engine. Three+ regions, multi-brand.
Hyvä licence (€1,000 one-time or €100/yr) is paid separately to Hyvä Themes. Subscription / loyalty / AR / PIM SaaS fees are passed through (no markup).
EU CPNP registration + INCI, what’s the workflow?
EU Cosmetic Products Notification Portal (CPNP) is required before any cosmetic product is placed on the EU market. The workflow:
- Responsible Person designated, an EU-based legal entity. Many brands appoint a third-party RP service (Obelis, Cosmetics Europe, etc.).
- Cosmetic Product Safety Report (CPSR), Part A (data) + Part B (assessor sign-off). Lives outside Magento.
- CPNP notification per SKU, SKU-level data submitted to CPNP. Confirmation reference number stored as a Magento product attribute (
cpnp_ref). - INCI list in EU local language(s), per-storefront translation in Magento. INCI names follow EU Cosmetic Ingredients (CosIng) database.
- Per-storefront PDP block, renders EU-compliant ingredient list, RP address, batch code, MoS / PAO icon.
I’ve done this for 4 EU beauty brands. Magento handles the storefront-rendering side cleanly; the regulatory workflow lives in your QA / RA tooling outside Magento.
FDA cosmetics labeling, can Magento auto-render the right PDP block?
Yes, with the right attribute model. Under MoCRA (Modernization of Cosmetics Regulation Act, 2022), US cosmetics need:
- Facility registration with FDA (one-time, you handle directly)
- Product listing per SKU (one-time per SKU, you submit to FDA via Cosmetics Direct portal)
- Adverse-event reporting workflow (15-day SAE rule)
- Ingredient list (INCI) on product label + PDP
- “Professional use only” flag where applicable
Magento setup: each product gets fda_listed, inci, warnings, professional_use_only, net_quantity attributes. A small Hyvä component on the US storefront renders the FDA-compliant label block from those attributes. The PDF label generator (PrinceXML / Dompdf) consumes the same attributes for physical labels. One source of truth.
India CDSCO compliance for cosmetics, what’s required?
Cosmetics in India fall under the Drugs and Cosmetics Act 1940 + Cosmetics Rules 2020 (replaced 1945 rules). Key requirements:
- Form COS-1 Import Registration for any imported cosmetic (Schedule D-III). Issued by CDSCO; valid 3 years; SKU-level.
- Manufacturing licence if produced in India (state-level Drug Controller).
- Hindi-language ingredient list on label is encouraged (not strictly required for English-literate markets but required for retail in many states).
- Net quantity in metric units (g / ml).
- Manufacturer / importer name + address + batch + manufacturing date + best-before date on label.
Magento setup: India storefront gets a separate website / store-view with cdsco_reg, hindi_inci, importer attributes. Hyvä PDP block renders Hindi INCI alongside English. Currency in INR, GST tax class. Razorpay / PayU / Cashfree as primary gateways, Stripe doesn’t play well with INR + GST + UPI in 2026.
Influencer + affiliate tracking, Refersion vs Aspire vs Impact?
Three credible paths for beauty brands:
- Refersion, affiliate-first, mid-market. Magento integration via API / pixel. Tracks per-influencer sales by promo code or unique link. Best for under $10M GMV with tier rewards (1-5%, 5-10%, 10%+ commission brackets).
- Aspire (formerly AspireIQ), influencer-first, full lifecycle (discovery + outreach + brief + approve + track + pay). Pricier but pays back fast for brands running 50+ influencer relationships. Magento integration via UTM + promo-code attribution.
- Impact (impact.com), enterprise, mature partnership platform. Best for $20M+ brands with diverse partner mix (influencer + affiliate + B2B referrer + content site).
- Magento Affiliate Pro / Mageworx Affiliate, Magento-native extension. Cheapest, weakest UX. OK as a starting point if you want full data ownership.
I usually recommend Refersion or Aspire for Magento-first beauty brands. UGC integration via Yotpo or Bazaarvoice runs alongside, influencer-driven UGC pulled into PDPs is a 12-18% conversion lift.
How do ingredient + allergen filters work on PLPs?
Magento layered nav handles this cleanly with the right attribute design:
- Per-ingredient boolean attributes,
contains_paraben,contains_sulfate,contains_fragrance,contains_gluten,contains_silicone, etc. Layered nav exposes “Free from” filters. - Positive flags,
is_vegan,is_cruelty_free,is_reef_safe,is_pregnancy_safe,is_clean_beauty. These tend to outperform “free from” framing for SEO and conversion. - Customer profile allergens, logged-in customers save up to 5 allergens. Magento auto-warns on PDPs that contain them (red banner). Wishlist / cart adds blocked with a confirmation modal.
- INCI catalogue as a structured attribute (one source of truth for ingredient list, allergen flags, regulatory fields).
Performance note: with 30+ filter attributes on a 5,000 SKU catalogue, you’ll need Elasticsearch / OpenSearch (not MySQL native search). Magento ships ES out of the box from 2.4.x.
Loyalty programs, Smile vs LoyaltyLion vs Magento native?
Beauty brands need tier-based loyalty (Sephora Beauty Insider model). Three credible paths:
- Smile.io, integrates with Magento via API. Best UX, best onboarding flow, weakest customisation. Good for under $10M GMV.
- LoyaltyLion, deeper feature set (referrals + reviews + tier-locked products + partner rewards). Stronger Magento-side admin. Best for $5M, $50M brands.
- Mageworx Reward Points / Amasty Reward Points + custom tier engine, Magento-native, fully owned. Best for $20M+ brands wanting full data + flow control. We typically build the tier engine on top of Amasty.
If loyalty is >30% of your revenue today, lean toward Magento-native, the platform owns customer + order + spend data, so tier rules + earn / redeem + birthday rewards live where they belong instead of via a webhook round-trip.
Magento vs Shopify for beauty specifically, when does each win?
Honest take. Shopify wins for beauty brands when: catalog is <100 SKUs, single region, no subscription program, no tier-based loyalty, low-volume influencer relationships, ops team is 1-2 people. The Shopify app ecosystem has the best beauty-native apps (Klaviyo, Recharge, Smile, Yotpo) wired together cleanly.
Magento wins when any of these are true: catalog >200 SKUs with shade variants, subscription + loyalty stacked on top of D2C, multi-region compliance (FDA + EU CPNP + India CDSCO), influencer programs with tier rewards, want full data ownership over customer + skin profiles, multi-brand or multi-store on shared inventory, B2B salon supply alongside D2C.
The crossover point I see in practice is around $5M, $10M GMV. Below that, Shopify pays for itself in ops simplicity. Above that, the Shopify app stack starts costing $5k, $15k/mo in app fees + the data-fragmentation tax bites, and Magento + Hyvä comes out cheaper at scale even with the higher dev cost.
Sample-then-buy flow, how is it implemented in Magento?
Three layers:
- Sample box product type, a Magento bundle product where the customer picks 4-6 sample-size variants from a curated pool. $10, $20 box price, free with subscription.
- Sample-to-full mapping, each sample SKU links to its full-size SKU via a Magento product attribute (
full_size_sku). Drives the post-box email automation. - Conversion automation, 14 days after the sample box ships, an email triggers per-sample “loved it? get the full size at 20% off” with a one-click upsell that drops the full-size SKU into the cart with the discount applied via Magento cart price rule.
Magento implementation: bundle + custom attribute + Klaviyo / Mailchimp transactional flow listening to a custom event from Magento on box-shipped. Sample-to-full conversion runs 22-38% in beauty data I’ve seen, which is wildly profitable because the sample box CAC is already paid down.
What shade-matching tools work with Magento, quiz-based vs AR (Modiface / YouCam)?
Three patterns work, in increasing complexity and cost:
- Quiz-based shade finder, 5-7 questions on undertone, depth, finish, climate. Built natively in Magento with custom product attributes + a thin Alpine.js quiz UI on Hyvä. Conversion lift typically 0.8-1.4x baseline. Cost: ~$3k, $8k.
- AR try-on (Modiface / YouCam Makeup / Perfect Corp), live camera overlay on PDP. Integration via REST + JS SDK. Conversion lift 1.4-2.8x on PDPs with AR. Cost: ~$8k, $20k integration + $1k, $5k/mo licence to the AR vendor depending on traffic.
- Hybrid (quiz → AR confirm), quiz narrows to 3 shades, AR confirms the pick. Best conversion in my data.
For brands under ~$5M GMV, start quiz-only. AR pays for itself above ~$5M because the licence amortises across volume.
Subscription box on Magento, Recharge vs Bold vs native?
None of the “Shopify-native” subscription apps run on Magento directly. The viable options:
- Recharge, offers a Magento integration via API, but it’s thinner than the Shopify version. Best for hybrid brands already running Recharge on a Shopify D2C site.
- Bold Subscriptions, same caveat. API-level integration, not native admin.
- Mageworx Subscriptions / Aheadworks Subscriptions / Amasty Subscriptions, Magento-native extensions. These are the recommended path for Magento-first brands. Native admin, native checkout, native customer account dashboard. Mageworx is the most feature-complete in 2026.
- Custom build on Magento subscription product type, viable for $50M+ brands with unique flows (sample-then-buy + tier-locked products + skip-a-month + swap).
For most cosmetics + beauty Magento builds, Mageworx Subscriptions + a custom sample-then-buy flow on top is the right call.
UGC reviews on PDP, Yotpo vs Bazaarvoice integration?
Both ship Magento extensions and both work cleanly. Decision criteria:
- Yotpo, mid-market, $1M, $50M GMV sweet spot. Strong photo / video review collection (post-purchase email + SMS). Loyalty + referrals bundled. Good Magento extension, native admin. Cheaper than Bazaarvoice.
- Bazaarvoice, enterprise, $50M+ GMV. Stronger syndication (push reviews to Walmart / Amazon / Sephora retailer channels). Better moderation tooling for high-volume brands. Pricier per-review.
- Stamped.io / Trustpilot, budget alternatives. Stamped is fine; Trustpilot is too generic for beauty (no shade / skin-type filtering on reviews).
Beauty-specific feature to ask about: review filtering by skin tone / skin type / age range. Yotpo and Bazaarvoice both support it; Stamped doesn’t. This filter is a 8-15% conversion lift on foundation / serum PDPs because customers find reviews from people who match them.
Not answered above?
Send the question as a brief; the answer comes back in writing within 24 hours, with a quote if it needs work.