Skip to content
5.0 Upwork, 100+ reviews Adobe Certified since 2021 New: become your own Magento developer Learn more →
Hire me
Toggle Nav
My Cart
Adobe Certified · Hungarian Magento stores

Magento developer in Hungary

I’m Kishan, a freelance Magento developer for Hungary, working from Ahmedabad. In Hungary the checkout is the easy part. The hard part is that every invoice your store issues has to reach the tax authority, NAV, through Online Számla, and that the 27% ÁFA is calculated right on every line. I connect Magento to your invoicing tool so that happens on its own, then set up Barion or OTP SimplePay for payments.

  • Your 9:00 in Budapest is 13:30 my time in winter, 12:30 in summer
  • Barion or OTP SimplePay, the gateways Hungarian buyers recognise
  • Invoices reported to NAV through Számlázz.hu or Billingo
Get my quote Get a quote
Free 30-minute call, no commitment Written quote in 24 hours, HUF figure included

Your morning is my afternoon

09:00Budapest 13:30Ahmedabad

Standard time. I work 10 AM to 7 PM IST, Monday to Saturday.

Hungary at a glance, for your store

  • ÁFA 27% Highest VAT in the EU

    At 27%, a rounding error costs more here than anywhere else in Europe. I set the 27%, 18% and 5% classes per product type and check that line totals and invoice totals agree.

  • Online Számla Invoices go to NAV

    Since 2021 every invoice, B2C included, has to be reported to NAV. I connect Magento to Számlázz.hu or Billingo, which do the reporting, so each paid order produces a reported invoice without anyone retyping it.

  • 4h30 Ahead of Budapest in winter

    Budapest is 4h30 behind me in winter and 3h30 in summer. Calls work best in your morning, 9:00 to 12:00 your time, which is early afternoon in Ahmedabad.

  • Foxpost Lockers at checkout

    Hungarian buyers like parcel lockers. I add a Foxpost or Packeta locker picker next to GLS and MPL home delivery, with the right rate for each.

What you get

The Hungarian details I check on every store

Most problems I find on Hungarian stores are not in the theme. They sit between the order and the invoice: a missing adószám, a wrong tax class, an invoice that never reached NAV. So that is where I start.

  • Barion or OTP SimplePay

    Barion is a Hungarian payment provider and SimplePay belongs to OTP Bank, the largest bank in the country. Buyers trust both. I connect the one you have a contract with, add Apple Pay and Google Pay through it, and make sure the order status changes correctly when a card payment is declined or abandoned.

  • Adószám for business buyers

    A Hungarian company invoice needs the buyer’s adószám, the 11-digit tax number written like 12345678-1-23. I add the field to checkout and the customer account, check the format, pass it to the invoice, and use VIES for buyers from other EU countries.

  • Online Számla through your invoicing tool

    Writing a direct NAV connector inside Magento is possible, but rarely the best idea. Most Hungarian shops already use Számlázz.hu or Billingo, which report to NAV for you. I connect Magento to that tool, so invoices are created on payment or shipment, and credit memos become proper storno invoices.

  • ÁFA 27%, 18% and 5%

    Books and some food sit at 5%, a few product groups at 18%, everything else at 27%. I map each product to the right class, check shipping tax, and handle reverse charge for business buyers from other EU countries with a valid VAT number.

  • A storefront that reads like Hungarian

    Hungarian puts the family name first and uses ő and ű, two letters that break in badly configured emails and PDF invoices. I set the hu_HU locale, fix name order in address forms, validate 4-digit postcodes and translate the order emails.

  • Árukereső and eMAG

    Many Hungarian buyers compare prices on Árukereső.hu before buying, and larger shops also sell on eMAG. I build the product feed from Magento with stock and delivery times, and for eMAG sync stock and pull orders back into Magento.

How I work

Five steps from booking to live

A 10:00 call in Budapest is 14:30 in Ahmedabad in winter and 13:30 in summer. I test invoicing against the NAV test environment and payments in Barion or SimplePay sandbox before anything touches your live store.

Daily overlap, standard time, in Budapest time
Your day 09:00 to 18:00
My hours 05:30 to 14:30
  1. 01

    Audit

    Free 30-min audit of your Hungarian store, Barion / OTP SimplePay integration, Online Számla NAV posture, ÁFA configuration, eMAG.hu feed, NAIH compliance, Core Web Vitals. Booked in a CET-friendly slot.

    Day 1
  2. 02

    Quote

    Fixed-price written quote in USD with HUF parity on request. Reserved start date, risk register, written project plan. You sign, we book.

    Day 2
  3. 03

    Build

    Daily review at 4 PM CET typical, right inside your Budapest / Debrecen / Szeged working day. Staging access from day 3 with HU postcode + Barion test cart + NAV sandbox.

    Days 3-14
  4. 04

    Deploy

    Blue-green cutover scheduled for off-peak (3 AM CET typical, lowest HU traffic). Old release stays warm for 72 hours so rollback is one DNS flip.

    Launch night
  5. 05

    Stabilise

    14 days of post-launch coverage in CET business hours. Anything that breaks because of the cutover gets fixed at no extra charge, including NAV invoice-reporting edge cases.

    Days 14-28

Your quote

Get a fixed quote for your project

Send your store URL and describe what you want to change. We can review the requirements and agree a written scope, quote and timeline before work starts.

  • Free first call
  • Written scope, price and timeline
  • You approve every change
Hire on Upwork
What clients say

What clients say about working with me

Reviews from clients I have worked with through Upwork, Clutch and direct referrals.

Magento work and feedback View Upwork profile

  • Illustration of Magento 2 development work for a sports footwear and hockey shop
    Sports footwear and hockey shop, Netherlands
  • Illustration of Magento 2 development work for a photo printing supplies wholesaler
    Photo printing supplies wholesaler, Netherlands
  • Illustration of Magento 2 development work for an educational toys and books shop
    Educational toys and books shop

  • Kishan has done an excellent job in a timely manner. He is very knowledgeable, has a very positive attitude, easy to communicate.

    Z. K.Magento 2 client

  • He is technically strong, approaches problems thoughtfully, and focuses on stable, long-term solutions.

    E. H.Magento 2 client

  • Kishan was a pleasure to work with! He is highly skilled, professional, and delivered outstanding results on time.

    M.Magento 2 client
Read all reviews
FAQ

Honest answers to the questions every Hungarian merchant asks

Magento vs Shoprenter vs Shopify Plus for the Hungarian market, which one?

The three real options for a Hungarian merchant evaluating platforms in 2026:

  • Shoprenter, Hungarian-founded SaaS (Debrecen, 2007). Dominates the HUF 50M, 500M Hungarian SMB segment. Cheap (HUF 15-80k/month), pre-wired for Barion + OTP SimplePay + Online Számla (NAV). Limited customisation, no B2B, capped at ~HUF 1B GMV before perf cracks.
  • Shopify Plus, wins early-stage Hungarian DTC + cross-border CEE brands. Strong on UX and apps. Weak on Online Számla NAV integration (you wire it via 3rd-party apps like Pannon, Számlázz.hu, or Octopus), no native CB scheme, and apps tax compounds quickly past HUF 500M GMV.
  • Magento 2 (Open Source / Adobe Commerce), the right answer when you have HUF 500M+ GMV, B2B with Adószám validation, multi-region CEE (HU + RO + SK + HR), or eMAG.hu marketplace at scale. Native control over Online Számla XML, ÁFA 27% / 18% / 5% per-category tax classes, and unlimited customisation of Hungarian-language admin.

If you’re under HUF 200M GMV and don’t need B2B, Shoprenter is faster. Above HUF 500M GMV, or with B2B / eMAG / multi-country needs, Magento is the long-term cost winner.

Barion vs OTP SimplePay vs Stripe, which Hungarian payment gateway?

You usually want two of these wired in parallel, not one:

  • Barion, Hungarian-origin PSP (founded 2014 in Budapest), white-label friendly, strong on installments, e-money license. Native Magento 2 module, supports Mastercard / Visa / Maestro. Best for Hungarian-led brands that want a domestic-feel checkout. Fees ~1.7%, 2.4% + HUF 8.
  • OTP SimplePay, OTP Bank’s gateway. OTP is the largest bank in Hungary (and CEE), so SimplePay carries weight with conservative Hungarian shoppers who recognise the OTP brand. Strong on B2B + invoice-pay. Fees competitive, native Magento module.
  • Stripe, Hungary-supported since 2018 (Stripe HU). Best for cross-border CEE or international DTC. Apple Pay + Google Pay support out of the box. Fees 1.4% + HUF 8 for EEA cards, 2.9% + HUF 8 for international.
  • Klarna, native BNPL, growing fast in Hungary 2024+. Pair with one of the above for AOV lift.
  • K&H / CIB / Raiffeisen direct-bank, legacy bank-direct gateways for large retailers. Lower fees but heavier integration.

Typical Magento HU stack: Barion (or OTP SimplePay) as primary + Stripe for international + Klarna BNPL + PayPal fallback. We wire all four with a unified card form and route by BIN.

How do I validate Adószám (Hungarian tax-ID) + VIES for EU B2B in Magento?

Two Hungarian B2B identifiers, two validators:

  • Adószám, the 11-digit Hungarian tax-ID, format 12345678-1-23 where the first 8 digits are the unique taxpayer ID, the middle digit is the ÁFA status (1-5), and the last 2 digits are the regional code. Validated against NAV’s public taxpayer register (free SOAP / REST API).
  • EU VAT (HU prefix), Hungarian EU VAT format HU + 8-digit core. Validated via the VIES VAT service (EU-wide) for cross-border B2B.

For Magento B2B we:

  1. Add Adószám + EU VAT fields to the customer entity (or B2B company on Adobe Commerce).
  2. Validate Adószám against NAV’s register on registration, rejects invalid / suspended / closed entities, auto-fills company name + ÁFA status.
  3. Validate EU VAT against VIES for cross-border zero-rated B2B sales (intra-EU reverse charge).
  4. Apply 0% ÁFA on B2B intra-EU sales with a valid VIES-validated EU VAT number; 27% on HU-domestic B2C and HU→HU B2B without VIES; 5%/18% for reduced-rate categories.
  5. Cache validations 30 days, re-validate on any address change.
What’s Online Számla (NAV) and how does the 5-minute real-time invoice reporting work?

Online Számla is the Hungarian government’s mandatory real-time invoice reporting system run by NAV (Nemzeti Adó- és Vámhivatal), the Hungarian tax authority. Every invoice issued by a Hungarian taxpayer must be reported to NAV via XML within 5 minutes of issue.

Timeline:

  • 2018, mandatory for B2B invoices > HUF 100k ÁFA content.
  • 2020, expanded to all B2B invoices (no threshold).
  • 2021, expanded to B2C invoices, every invoice now reports to NAV.

How Magento integrates:

  1. Build a Magento invoice (sales_invoice) on order placement or shipment.
  2. Serialize the invoice to Online Számla XML 3.0 schema (Számla 3.0).
  3. POST to NAV’s invoiceService REST endpoint with your tech-user signature + HMAC.
  4. Receive a transaction ID, poll status until DONE or ABORTED.
  5. Store the NAV transaction ID against the Magento invoice for audit.

Non-compliance fine: HUF 500,000 per missing or late invoice. Most merchants route through certified middleware (Számlázz.hu, Pannon, Octopus, Billingo) rather than direct, because the middleware handles XML schema updates + NAV downtime queueing.

How do I configure ÁFA 27% / 18% / 5% multi-rate (EU highest VAT) in Magento?

Hungary has the highest standard VAT in the EU at 27%, with two reduced rates:

  • 27%, standard ÁFA (most goods + services).
  • 18%, reduced (accommodation / hotel stays, dairy event services).
  • 5%, super-reduced (bread, dairy, medicine, books, newspapers, internet access, district heating, residential housing under 150 m², restaurant food + non-alcoholic drinks since 2017).

Magento configuration:

  1. Create 3 tax classes in Stores → Tax Zones & Rates (ÁFA-27, ÁFA-18, ÁFA-5).
  2. Create 3 tax rules per rate, scoped to HU (or EU + auto-detect via destination).
  3. Assign each product’s tax class based on its category, we wire this via the category_id → tax_class mapping in a custom CategoryAttribute observer so admins don’t set it per product.
  4. For B2B intra-EU with valid VIES TVA, override to 0% (reverse charge).

Tax-inclusive prices on storefront (mandatory in EU B2C); tax-exclusive on B2B if explicitly opted-in. ÁFA 27% impacts perceived price dramatically, for cross-border shoppers a HUF 12,700 price (HUF 10k + 27% ÁFA) feels heavier than the same EUR equivalent elsewhere, so storefront price-presentation matters.

How do I integrate Vatera + Jófogás + eMAG.hu marketplace feeds?

The three Hungarian marketplaces with meaningful e-commerce volume:

  • eMAG.hu, the dominant marketplace in Hungary. Romanian-origin (Bucharest, 2001), expanded to HU 2013, now > 40% of Hungarian online retail. Full marketplace (3P) + retail (1P). Feed-in via XML / API, pricing rules, category mapping, fulfilment-by-eMAG option. eMAG performance score matters, low scores get delisted.
  • Vatera, Allegro-owned auction + buy-now site. ~3M active users. Good for collectibles, electronics, fashion overstock. Feed-out via Vatera Connect API; lower margin but steady volume.
  • Jófogás, classifieds (Schibsted/Adevinta-owned). C2C-heavy but B2C section growing. Less integrated, often manual posting.

Magento integration:

  1. Build a per-marketplace XML feed, product, price, stock, category, images. Cron-refresh hourly.
  2. Map your Magento categories to each marketplace’s taxonomy (eMAG has ~5,000 categories, mapping matters for visibility).
  3. Pull orders back via marketplace API into sales_order with a marketplace_id custom attribute.
  4. Update stock + price across all 3 from a single Magento source-of-truth (with safety margins for slow-syncing marketplaces).
  5. For eMAG specifically: monitor performance score, cancel-rate, and delivery-time metrics, bad scores hurt rankings.
How do you handle Hungarian-language admin + Magyar diacritics (ő, ű, á, é) in Magento?

Hungarian (Magyar) is a Uralic language, very different from neighbouring Slavic/Germanic neighbours, with a 44-letter alphabet including the diacritics ő, ű, á, é, í, ó, ú (and the digraphs cs, dz, dzs, gy, ly, ny, sz, ty, zs). Magento support is mostly fine but needs careful setup:

  • Database collation must be utf8mb4_unicode_ci (or utf8mb4_hungarian_ci for Hungarian-specific sort). Default utf8mb4_general_ci works but sorts ő after z, not what HU shoppers expect.
  • Hungarian language pack, composer require mageplaza/hungarian-language-pack-magento-2 or community pack. Covers admin + frontend strings (~85% coverage). We patch the missing ~15% for customer-facing UI (checkout, account dashboard, emails).
  • Postcode validation, Hungarian postcodes are 4 digits (e.g., 1051 Budapest), not 5 like DE/IT/ES. Magento’s default validator accepts this but we add stricter regex.
  • Address format, HU uses reverse name order (Family-name First-name) and reverse address (Postcode City, Street Number, Floor/Door). We override customer_address formatters.
  • Hungarian customer-service strings, emails, transactional copy, error messages translated and reviewed by a native HU speaker.
  • Date / number / currency formatting, Hungarian uses 2026. máj. 18. (with period and trailing dot), 1 234,56 Ft (space thousands, comma decimal, “Ft” suffix).

We deliver a Magento where every diacritic renders correctly, sorts correctly, and emails-correctly to name@kovács.hu domains.

eMAG.hu is dominant, how deep should the integration go?

eMAG is roughly 40%+ of Hungarian online retail, if you sell physical goods in HU, you almost certainly need an eMAG channel. Integration depth depends on volume:

  • Light (under 500 SKUs), XML feed + manual order fulfilment. Magento exports product/price/stock daily via cron to an eMAG-format XML the eMAG seller dashboard pulls. Orders managed in the eMAG dashboard, shipped from your warehouse, tracking pasted back. Good enough for under HUF 50M GMV on eMAG.
  • Medium (500-5k SKUs), full API integration. eMAG Marketplace API (REST, OAuth2) for products, orders, stock, returns, invoices. Real-time inventory sync. Performance score monitoring. Magento ↔ eMAG bidirectional sync via a Magento module (we build custom or use a Mirakl/Channable connector).
  • Heavy (5k+ SKUs or > HUF 500M GMV on eMAG), full integration plus: dynamic repricing (auto-match competitors within margin floors), Genius / FBE (Fulfilled By eMAG) integration, eMAG advertising API (sponsored products), returns automation, eMAG-specific Online Számla NAV reporting (eMAG invoices on behalf of you in some cases, but the NAV report still owes to you).

Critical: monitor your eMAG performance score daily, cancel-rate, on-time-delivery, response-time. Below 4.5/5 you get demoted in rankings; below 4.0 you get suspended. Magento dashboard + Slack alerts keep this visible.

What’s NAIH (Hungarian DPA) + GDPR cookie banner compliance for HU?

NAIH (Nemzeti Adatvédelmi és Információszabadság Hatóság) is the Hungarian Data Protection Authority, the body that enforces GDPR in Hungary, on top of 2011. évi CXII. törvény (Hungarian Information Act). NAIH is moderately strict but more pragmatic than France’s CNIL or Germany’s DSK.

Concrete Magento checklist:

  • Cookie consent, granular, per-purpose opt-in. Pre-ticked checkboxes prohibited. “Reject all” button must be as accessible as “Accept all”.
  • Hungarian-language banner, legally required to be in Hungarian for HU-targeted sites. Tools: Cookiebot, Axeptio, CookieFirst, or NAIH-vetted local providers.
  • Privacy policy, in Hungarian, naming NAIH as supervisory authority, including the controller’s Adószám.
  • DSAR routing, right-to-access, right-to-erasure, right-to-portability per GDPR Art. 15-20. We wire Magento’s native GDPR module (or extend) so HU customers can self-serve in Hungarian.
  • Breach notification, NAIH expects notification within 72 hours of a breach, in Hungarian, via their portal.
  • Data localisation, not strictly required for HU, but NAIH prefers EU-region hosting (Cloud99 / Maxer / OVHcloud / AWS Frankfurt all qualify).

NAIH fines have been moderate compared to CNIL (largest ~HUF 100M / ~€250k), but they trigger reputational damage with HU media.

Should I host on Cloud99, Maxer, or AWS Frankfurt for Hungarian data residency?

Depends on your volume + DevOps tolerance + data-residency posture:

  • Cloud99, Hungarian managed-hosting (Budapest DCs). Strong on Hungarian customer support (HU + EN), familiar with Online Számla / NAV + ÁFA setups. Good for HUF 50M, 500M Magento stores. Less auto-scaling than hyperscalers; more hands-on DevOps from us.
  • Maxer Hosting, another Hungarian provider, popular with Shoprenter migrants. Hungarian-language admin + invoice in HUF. Mid-tier reliability, good price/perf.
  • AWS Frankfurt (eu-central-1), not technically Hungarian residency but Frankfurt is the closest hyperscaler region (latency ~10-15ms to Budapest), GDPR-compliant, NAIH-acceptable. Best for HUF 500M+ stores wanting auto-scaling, Cloudfront, RDS, ElastiCache.
  • Adobe Commerce Cloud (Frankfurt region), best if you’re already on Adobe Commerce license. Fully managed, 24/7 Adobe support, Fastly CDN. Costs €25k+/yr.
  • OVHcloud / Hetzner Helsinki, budget EU options, work fine for Hungary if you don’t need ms-level latency.

NAIH doesn’t mandate HU-only hosting, but some conservative Hungarian B2B clients (especially in regulated sectors) prefer HU-soil residency for optics, in that case Cloud99 / Maxer win on the procurement-questionnaire alone.

What does a Magento build cost and how long does it take for Hungarian merchants?

Two scenarios published:

  • Pricing is a fixed written quote for your scope. Send the details on WhatsApp and I reply within one working day. HUF parity ~HUF 180,000 at current FX. Deliverable: a written audit of your existing Hungarian Magento store covering Barion / OTP SimplePay setup, Online Számla (NAV) reporting health, ÁFA 27% / 18% / 5% tax-class correctness, NAIH cookie compliance, eMAG.hu feed if applicable, Core Web Vitals, and a 90-day improvement roadmap. Delivered in 3-5 business days.
  • Contact me for a quote. HUF parity ~HUF 1,800,000 at current FX. Deliverable: full Magento 2 build or migration from Shoprenter / Shopify / WooCommerce / Magento 1, with Hyvä storefront, Barion + OTP SimplePay + Stripe + Klarna checkout, Online Számla NAV real-time XML integration, ÁFA multi-rate rebuild, Adószám + VIES validation, NAIH cookie banner, eMAG.hu / Vatera / Jófogás feeds, Hungarian admin + storefront with full Magyar diacritics. Delivered in 4-8 weeks.
  • Custom Enterprise, for multi-region HU+RO+SK+HR, full Online Számla pipeline at high invoice volume, B2B with Adószám + KATA/KIVA awareness, or eMAG-Marketplace seller at scale. Quoted on scope.

Credentials: Adobe-Certified Magento 2 Developer + Hyvä partner-tier, 10+ years of CEE Magento builds (HU + RO + PL + CZ + SK), 200+ stores shipped, 5-star Upwork track record. Hungarian Adószám + invoice on request via my Indian Kft-equivalent for VIES-validated cross-border B2B.

Edge cases, Budapest boutique vs Debrecen B2B vs eMAG-Hungary marketplace-seller, what changes?

The three Hungarian Magento personas, with what changes per persona:

  • Budapest boutique (DTC fashion / beauty / wine), small SKU count, brand-led, mobile-first traffic. Focus: Hyvä Lighthouse 95+, Barion + Klarna + Apple/Google Pay, NAIH cookie banner, Hungarian + English bilingual storefront, eMAG.hu lifestyle category feed. Online Számla NAV via Számlázz.hu middleware. Budget HUF 1.8M, 5M.
  • Debrecen B2B (industrial / parts / wholesale), large SKU count (10k+), Adószám-validated B2B customers, Net-30 terms, ÁFA reverse-charge for EU intra-Community, KATA/KIVA-aware invoicing. Focus: company-account hierarchies, quote-builder, BoQ uploads, MOQ enforcement. Online Számla NAV with direct XML (high volume justifies the integration). Cloud99 or Maxer hosting for HU-soil B2B optics. Budget HUF 5M, 25M.
  • eMAG-Hungary marketplace-seller (multi-channel retail), Magento as inventory + order hub, eMAG.hu as primary sales channel (60%+ of revenue), own .hu store as secondary, occasional cross-listing on Vatera. Focus: eMAG Marketplace API depth, real-time stock sync, dynamic repricing, eMAG performance score monitoring, returns automation. Online Számla NAV reporting handles both Magento and eMAG orders (eMAG invoices on the seller’s behalf but the NAV obligation is the seller’s). Budget HUF 5M, 15M.

The audit step pins down which persona you are before quoting, the deliverables look different for each.

Reserve your slot

Tell me about your Hungarian Magento store

Send me a short WhatsApp message about the project. I reply within 24 business hours with a written quote in USD and the HUF figure next to it.

Message me on WhatsApp

No form to fill. Send me a quick message. I reply during 10 AM to 7 PM IST, Monday to Saturday.

Helpful to mention

  • Company
  • Current platform
  • Store URL
  • Annual GMV (HUF)
  • Product category
  • Compliance focus

These are already in the message for you. Just add your answers.

Message me on WhatsApp

Or save my number: +91 84012 70422

Your hours, my overlap Online 10 AM to 7 PM IST Get my quote