Magento Developer Estonia FAQ
All 11 answers
Magento vs Shopify vs e-Pood for the Estonian market, which one wins?
Estonia is a small but very digital market: most people use online banking and digital ID daily, and the state runs services on X-Road. Platform choice depends on what you need:
- Local SaaS shop builders (for example Voog), affordable, with an Estonian admin and local payment links. Limited for B2B, multi-store and custom integrations.
- Shopify, good for early-stage DTC. Estonian bank payments come through a payment provider app, and local tax or B2B rules may need extra apps.
- Magento, the right fit when you need B2B with payment terms, multi-store EE, LV and LT, KMKR and VIES checks, multi-currency sales from an Estonian company, ERP integration with Directo, Merit or Standard Books, or custom catalogue logic.
Start simple if your needs are simple; move to Magento when B2B, multi-country or integration needs show up.
How do I integrate Bank-link (Swedbank + SEB + LHV + Coop Pank) in Magento?
Bank links (pangalink) are Estonia's account-to-account payment method: the shopper is sent to their own internet bank (for example Swedbank, SEB, LHV or Coop Pank), signs in with Smart-ID, Mobile-ID or ID card, and approves the transfer. Estonian shoppers are very used to paying this way, so a local store should offer it.
Magento integration options:
- Direct bank links, a merchant agreement with each bank and signed requests and responses. More work and contracts, sometimes lower fees at high volume.
- Maksekeskus (MakeCommerce), one contract and one Magento module for the main Estonian banks plus cards, Apple Pay and Google Pay.
- Paysera, a payment provider that also bundles Baltic bank payments.
Starting with an aggregator is usually fastest; direct bank contracts can come later if volume justifies them. Compare current fees with each provider.
What payment-gateway stack should an Estonian Magento store run?
A typical Estonian Magento payment stack:
- Bank links via an aggregator such as Maksekeskus, covering the main Estonian banks in one module.
- Stripe, for international cards, Apple Pay and Google Pay, useful for companies selling outside Estonia.
- Klarna or another BNPL option, if it fits your products and basket size.
- Paysera, a Lithuanian provider with Baltic bank payments and cards, useful for EE, LV and LT together.
- PayPal, still expected by many international buyers.
For a local store, an aggregator plus Stripe is often enough. For an international store run from an Estonian company, add PayPal and BNPL. For all three Baltic countries, one Baltic-wide provider keeps it simple.
How do I validate KMKR (Estonian VAT-ID) + VIES for EU B2B in Magento?
The Estonian VAT number (KMKR number) has the format EE plus 9 digits. It is issued by the Estonian Tax and Customs Board (Maksu- ja Tolliamet, EMTA).
Two layers of checks for Magento B2B:
- Estonian registration and status, checked against EMTA's public data (and the business register for company name and address).
- VIES, the EU-wide check for cross-border B2B. For intra-EU B2B supplies the buyer's VAT number must be valid, and you report the sale on the VD annex.
For Magento I:
- Add a KMKR or VAT number field to the customer (or company on Adobe Commerce B2B).
- For EE numbers, fetch the company data on registration; for other EU numbers, check VIES.
- Apply the intra-EU 0% treatment with reverse charge for valid EU B2B buyers, and Estonian VAT (standard 24% since 1 July 2025) for B2C and domestic B2B.
- Store the check results and re-check on address changes.
I run an e-Residency-founded company, can Magento handle international multi-currency from an EE entity?
Yes. e-Residency lets non-Estonians start and run an Estonian company (usually an OÜ) online. The company follows Estonian tax law but often sells worldwide.
Magento setup:
- Multi-currency display, EUR as base currency with USD, GBP or others as display currencies through Magento's currency switcher.
- VAT per customer type, Estonian VAT (standard 24% since 1 July 2025) where Estonian VAT applies, reverse charge for valid EU B2B buyers, 0% on exports outside the EU, and the EU OSS (which replaced MOSS in July 2021) for EU B2C sales above the distance-selling threshold.
- Settlement, even if you charge in USD, your provider may settle in EUR to your business account; Magento's payment data should pass the settled amount to your accounting software (Directo, Merit or similar).
- Invoices, with your KMKR number, registry code and address, and the VAT amount shown in a way your accountant can report in EUR. Check the exact invoice rules for foreign-currency sales with your accountant.
- Tax reporting, the monthly VAT return (KMD) is done by your accountant; I make sure Magento's sales data exports cleanly.
What’s X-Road and when does my Magento store need to integrate with it?
X-Road is Estonia's secure data exchange layer between state and private information systems, developed with the Nordic Institute for Interoperability Solutions (NIIS).
Most e-commerce stores do not need a direct X-Road integration. Typical cases where it, or a service built on it, comes up:
- Selling to the public sector, Estonian public bodies expect e-invoices, which you send through an e-invoice operator rather than building your own X-Road link.
- Company data on B2B registration, company name, address and status from the business register, usually through the register's own services.
- High-volume or special integrations, where a direct X-Road membership and security server make sense.
Becoming an X-Road member means registering, running or renting a security server and following the X-Road rules. Before that, check whether an existing e-invoice operator or register service already gives you what you need.
How do you handle Estonian-language storefront + Russian layer for Ida-Viru?
Estonian (eesti keel) is a Finnic language, close to Finnish and unrelated to Latvian or Lithuanian. It uses non-ASCII letters such as õ ä ö ü š ž, so the whole stack must use UTF-8 (utf8mb4 in MySQL) to keep emails and invoice PDFs correct.
For stores serving the whole country, a Russian-language layer is worth considering: a large Russian-speaking minority lives in Estonia, especially in Ida-Viru county (including Narva) and parts of Tallinn.
Magento setup:
- Two store views:
et(Estonian, default) andru(Russian). - Translated product names, descriptions, categories, CMS pages and email templates per store view.
- An Estonian admin and storefront language pack, with missing strings checked and filled.
- Customer emails and notifications translated by a native speaker, not machine translation.
- EUR for both store views.
What does AKI compliance look like for Magento, and how strict is it vs other EU DPAs?
AKI (Andmekaitse Inspektsioon) is Estonia's Data Protection Inspectorate, the local GDPR supervisor. Estonia applies the GDPR together with the Personal Data Protection Act (isikuandmete kaitse seadus).
The basics for a Magento store:
- Cookie consent, opt-in for non-essential cookies with a standard consent manager (for example Cookiebot or OneTrust) or a Magento consent module. No pre-ticked boxes, “Reject all” as easy as “Accept all”.
- Privacy policy, in Estonian for Estonian storefronts, ideally also in Russian and English, naming AKI as the supervisory authority.
- Data subject requests, answered within one month under the GDPR; a privacy request form in the store helps track them.
- Records of processing, under GDPR Article 30, with limited exemptions for small organisations.
- Breach notification, to AKI within 72 hours where a breach risks people's rights.
- EU hosting, keeps data transfers simple.
For help on your store, message me on WhatsApp.
Can I run a single Magento for Estonia + Latvia + Lithuania?
Yes, and it is a practical move for a Baltic store, because all three countries use EUR and share many shopping habits:
- One Magento backend, three store views,
ee,lv,lt. Shared catalogue, separate domains or one domain with a country selector. - VAT per store, standard rates of 24% in Estonia (since 1 July 2025), 21% in Latvia and 21% in Lithuania, each with its own reduced rates. Tax rules per store.
- Payments per store, local bank payments in each country through a Baltic provider (for example Maksekeskus or Paysera), plus cards and BNPL.
- Shipping per store, parcel lockers are very popular across the Baltics; Omniva, DPD and SmartPost (Itella) are common choices.
- Language per store, Estonian, Latvian and Lithuanian are three different languages, plus an optional Russian layer.
- Legal pages per store, consumer rules and the data protection authority per country: AKI (EE), DVI (LV), VDAI (LT).
Architecture: one backend, three store views, shared catalogue. Timeline and price are quoted after a short brief via /hire-me or WhatsApp.
What does it cost, how long does it take, and what are your credentials?
Every Estonian project is quoted after a short brief via /hire-me or WhatsApp. You get a fixed written quote with scope, price and timeline before any work starts. Typical scopes: a written audit (bank link setup, KMKR and VIES checks, AKI cookie setup, VAT rates per category, Core Web Vitals and SEO), a full build or Hyvä migration with Estonian payments, Estonian and optional Russian storefront, or a larger project with Baltic stores, multi-currency or ERP integration (Directo, Merit, Standard Books).
Credentials: I am an Adobe Certified Magento developer (2021). I work solo, so you deal with me directly on every task.
What changes between a Tallinn-local store, an e-Residency-international store, and a Baltic 3-country expansion?
Three different Magento setups, which I confirm with you in the audit step:
- Tallinn-local Estonian store: an Estonian storefront (optionally with Russian), EUR, Estonian VAT (standard 24% since 1 July 2025, with reduced rates by product), bank links through an aggregator plus cards, parcel locker and courier shipping, an AKI-compliant cookie banner and accounting integration (Directo, Merit).
- International store run from an Estonian e-Residency company: an English storefront (often with other languages), multi-currency display, settlement in EUR, Stripe, PayPal and BNPL for international buyers, Estonian VAT only where it applies, reverse charge for EU B2B, 0% on exports outside the EU and OSS for EU B2C. International shipping, often from an EU warehouse.
- Baltic three-country store (EE, LV, LT): one Magento, three store views, three languages, VAT of 24% (EE) and 21% (LV and LT), and payments and shipping per country.
Tell me which one fits (or if you are moving between them) on WhatsApp and I will scope it.
Related FAQ topics
All FAQ topics-
Magento Upgrade
Common questions about upgrading Adobe Commerce / Magento Open Source. -
Hyvä Development
Common questions about Hyvä theme development, migration from Luma, and Hyvä Checkout.
-
Magento Performance
Common questions about Magento performance optimization, Lighthouse... -
Emergency Bug Fixing
Common questions about emergency e-commerce bug fixing across... -
Hiring a Freelance Magento Developer
Questions about Magento project scope, quotes, start dates... -
Magento B2B Development
Common questions about Adobe Commerce B2B, Magento B2B development...