Edge cases, what if I’m a single-designer boutique? What if I’m a full-range bridal retailer?

Two ends of the wedding-DTC spectrum, two different Magento builds:

Single-designer boutique (30-200 SKUs, $200k, $2M GMV):

• Keep it simple. Skip the full vendor marketplace, skip multi-region day-1.
• Focus: gorgeous PDPs (lookbook + video + AR if eyewear/headpieces), made-to-measure flow with cart-block on lead-time, one registry integration (pick Zola if US-focused or Honeyfund if cash-funds matter to your audience), Klaviyo multi-event journey scaffold.
• Personalization (monogram + custom-color) lifts AOV ~25%, worth doing even at small scale.
• Build budget: $4,999 sprint + ~$1.5k/mo retainer through the first season.
• Hyvä mandatory, mobile traffic is 75%+ of bridal organic, and a slow site at this scale loses you the customer to BHLDN search ads.

Full-range bridal retailer (2,000-25,000 SKUs, $5M, $50M+ GMV):

• All 3 registries + Amazon Wedding integrated. Group-order module mandatory if you carry bridesmaid lines.
• Multi-region sizing if you ship internationally. Multi-source inventory (MSI) for stock-by-warehouse.
• B2B layer for wholesale to boutique bridal stores (15-30% of revenue for most full-range retailers).
• PIM (Akeneo / Pimcore) as the catalog of truth if you carry >5 designers / brands. Magento pulls from PIM; same feed pushes to registries, marketplaces, and wholesale channels.
• Local-vendor marketplace if you have audience that exceeds your inventory (e.g. you’re known for bridal jewellery but couples ask you for photographer referrals).
• Build budget: $25k, $80k all-in (custom enterprise scenario). 16-28 weeks. Ongoing retainer $3k, $5k/mo.

Either end of the spectrum, Magento + Hyvä handles it. The architecture decisions are different; the underlying platform is the same. I’ve shipped both ends and the playbook is robust.