Edge cases, Prague boutique vs Brno B2B exporter vs Alza-scale retailer, what changes?

The Czech Magento landscape splits into three patterns, each with very different priorities:

• Prague boutique / DTC fashion, CZK 5M, 50M / year, mobile-first, Heureka.cz feed mandatory, Hyvä for Lighthouse 95+, GoPay + Apple Pay + Google Pay primary, “Ověřeno zákazníky” badge for trust. Typical engagement: \$4,999 Build tier, 4-6 weeks.
• Brno B2B industrial exporter, CZK 50M, 500M / year, ARES-validated IČO auto-fill on registration, VIES-validated DIČ for cross-border zero-rated B2B, Net-30 / Net-60 terms, ERP integration (Pohoda / Money S5 / Helios), reverse-charge DPH on EU B2B invoices, multi-region CZ + SK + DE + PL. Often deeper than \$4,999, quoted custom enterprise.
• Alza-scale electronics retailer, CZK 500M+ / year. Magento Adobe Commerce or Shopsys Framework territory. Marketplace feeds to Heureka + Zboží + Aukro + Alza Marketplace, automated stock + price sync, real-time Heureka feed updates, edge caching via Varnish + Fastly, Adobe Commerce Cloud Frankfurt or AWS Frankfurt hosting, dedicated DevOps. Custom-quoted, multi-month engagements.

The common thread: every Czech build needs GoPay (or ComGate), Heureka.cz feed, IČO + DIČ validation, ÚOÓÚ-compliant cookies, and Czech-language storefront. The scale dictates how much else gets layered on top.