Edge cases, niche AA-cup specialty vs full-range mass-market lingerie, anything different?

Both edges have specific Magento patterns worth flagging:

Niche AA-cup specialty (e.g. Lulalu, Pepper, Little Bra Company):

• Narrow size range (AA, A, B only) but deep colorway + style breadth per size. Variant explosion is in the style axis, not the size axis.
• Underwire-vs-wireless as a primary filter, not a side filter. AA-cup customers care about petite-specific construction (shorter underwires, narrower gore, lower band heights).
• “Trying-it-on-club” mechanic, try 3 bras at home, send 2 back free. Wired via Loop Returns with a custom flow. Cuts “wrong size” abandonment to near-zero because the customer can physically compare.
• Subscription model rarely makes sense at this scale, the customer cohort is small and brand-loyalty is already high.

Full-range mass-market (e.g. ThirdLove, Knix, Aerie Real, Skims, Adore Me):

• Cup range AA through K, band 28 through 46-14×13 = 182 theoretical combos per SKU. Sparse availability is the norm; the PDP must handle “greyed out but visible” cleanly.
• Multi-region from day one. US/UK/EU/AU sizing matrix is non-negotiable.
• Subscription model + VIP tier is the growth lever. ReCharge + Klaviyo + complex pricing rules.
• Body-positive imagery rotation across 5-10 model body types per SKU. Heavy UGC ($10 store credit per approved photo).
• Returns automation is mission-critical, 40-55% return rates at $50, $80 AOV without automation is unsustainable margin.

Plus-size specialty (e.g. Lane Bryant Cacique, Curvy Kate, Elila):

• Full cup range G through K is the differentiator. Smaller catalog but premium AOV ($60, $120 per bra).
• Sister-size lookup is even more important, finding the right band/cup combo is harder, the customer is already disenfranchised, and getting fit-quiz suggestions right closes the sale.
• Inclusive imagery is the brand promise, if a plus-size brand uses only thin models in marketing, the brand dies in the reviews.

In all three cases, Magento + Hyvä handles the architecture cleanly. The pieces that change are which integrations to prioritize (returns vs quiz vs subscription vs UGC) and how much custom code the storefront needs.