What changes between a Tallinn-local store, an e-Residency-international store, and a Baltic 3-country expansion?

Three very different Magento configurations — we always align on which one you are in the audit step:

• Tallinn-local Estonian — single storefront in Estonian (+ optional Russian for Ida-Viru), EUR currency, Käibemaks 22% / 9%, Bank-link via Maksekeskus + Klarna + Stripe, Omniva + DPD + SmartPost shipping, AKI banner, Directo / Merit accounting integration. Customer base ~95% in Estonia. Typical timeline 8–12 weeks for a full Hyvä build.
• e-Residency-international from EE entity — storefront in English (often with EE / RU / DE / FR mirrors), multi-currency display (EUR + USD + GBP + others), settles in EUR via LHV / Wise / Revolut Business, Stripe + PayPal + Klarna for non-EE customers, optional Bank-link for the few EE buyers, Käibemaks 22% to EE customers only + 0% reverse-charge for EU B2B + 0% for non-EU exports + MOSS / OSS for digital goods. Customer base ~80–90% outside Estonia. International shipping via DHL Express / FedEx / UPS, often dropshipped from an EU 3PL (Netherlands / Germany).
• Baltic 3-country (EE + LV + LT) — one Magento, 3 store views, 3 languages (et / lv / lt), 3 VAT rates (22% / 21% / 21%), country-specific payment + shipping per store. Customer base ~30% EE, ~35% LV, ~35% LT typical. Adds complexity to product translation + customer support + payments but unlocks ~3x the addressable market.

Tell us which one in the booking form (or all three if you’re mid-evolution) and we’ll scope accordingly.