Edge cases, single-texture specialty vs full multi-origin retailer?
Both are valid hair-ecom shapes; Magento handles both, but the build differs.
Single-texture specialty brand (e.g. Mayvenn serving primarily textured-hair / 4A, 4C, Hergivenhair for kinky-curly, Naturalgirl Wigs for coily textures): catalog is smaller (200-800 SKUs), shade range is curated (8-12 shades), texture is deep but narrow (3A, 4C only). Build scope is leaner:
- Configurable-product schema simpler (texture × length × method, no origin filter needed because texture is the brand promise).
- Educational content is the moat, install guides, care routines, before/afters, customer photos. Magento CMS pages + Hyvä-themed lookbook component.
- Community is the marketing channel, Instagram UGC integration (Foursixty), reviews with photos (Yotpo, Stamped), referral program (Mention Me, Talkable).
- B2B salon trade is optional but often natural, textured-hair stylists are an underserved pro segment with high loyalty when respected.
- Cost: $20k, $40k build, 6-10 weeks.
Full multi-origin retailer (e.g. BellaMi, Indique Hair, Bombshell Beauty): catalog is large (1,500-8,000 SKUs across origin × texture × shade × length × method), B2B salon trade is a major channel, medical-wig channel may be present, multi-region inventory. Build scope is heavy:
- Configurable-product schema is the cross-product (origin × texture × shade × highlight × length × method).
- B2B salon portal with license verification is mandatory.
- Multi-region inventory + customs / tax wiring needed.
- PIM (Akeneo, Pimcore) often master catalog because the variant count strains Magento admin UX.
- Cost: $50k, $150k build, 12-24 weeks.
Tiny startup (under $100k GMV): stay on Shopify Basic + a subscription app + a virtual-try-on app until you outgrow the 100-variant-per-product ceiling. Migration to Magento makes sense when shade range × highlight pattern × length passes the ceiling or when B2B salon trade emerges as a real channel.
Huge brand ($25M+ GMV): probably already on Magento, Salesforce Commerce Cloud, or a custom stack. The conversation shifts to incremental optimization, shade-range expansion ROI, B2B portal UX iteration, medical-wig channel growth, rather than full replatform. Happy to take that on as an ongoing retainer.