Magento 2 webshop development and maintenance

Implementing a Magento 2 webshop typically costs between €5,000 and €170,000 (+ VAT). A store built on standard foundations with a customised ready-made theme costs €5,000–€17,000, a webshop with a custom design or migrated from another platform €17,000–€50,000, and a complex B2B or multistore system starts from €50,000. The price is determined by the number of products, the volume of data to migrate and the number of integrations, not the design. Every project is based on an individual assessment.

You'll find the full webshop market price ranges in our Webshop development costs 2026 article.

A Magento 2 webshop built on standard foundations takes 3–9 weeks to launch, a custom implementation or migration 9–20 weeks, and a complex B2B or multistore system 3–9 months. The timeline is most often extended not by development itself, but by data migration and integration with external systems (invoicing, ERP, courier services).

Ongoing Magento 2 maintenance typically costs between €170 and €3,000 a month (+ VAT). The lower tier covers security updates, backup checks and monitoring, the middle tier adds version tracking and priority bug fixes, and the top tier also includes a monthly development allowance and a quarterly technical audit.

WooCommerce suits smaller, simpler webshops: it launches faster and more cheaply, and works well up to a few hundred products and lower traffic. Magento 2 has the edge where you need thousands of products, multiple warehouses, multiple languages or currencies, complex pricing and Magento B2B permission management. The practical cut-off point is roughly where WooCommerce can only keep up by stacking plugin after plugin.

Hungarian hosted ecommerce platforms such as Shoprenter and UNAS offer a quick launch and cheap hosting, but limited development freedom: business logic the platform doesn't support simply can't be built. It's worth switching to Magento 2 when you need a custom checkout, your own business logic, an ERP connection, multiple stores or international sales, or once the platform's limits are already costing you revenue.

Magento Open Source is a free, open-source edition with no licence fee, though you still pay for development, hosting and maintenance. Adobe Commerce is a paid edition with an annual licence fee that adds a built-in B2B module, content staging, advanced segmentation and vendor support. For most Hungarian small and medium-sized businesses, the Open Source edition is enough.

Magento 2 doesn't run reliably on shared hosting; it needs a dedicated VPS or server. For a new webshop, 4 CPU cores, 8–16 GB RAM and SSD/NVMe storage are a reasonable minimum, alongside Varnish caching, Redis session and cache handling, and an OpenSearch search engine. For a larger catalogue and higher traffic, these requirements grow accordingly.

In the right server environment, Magento 2 handles several hundred thousand products reliably. The practical limit isn't the product count but the number of attributes and variants, the indexing strategy and the search engine configuration. Above ten thousand products, it's worth using OpenSearch-based search, Varnish caching and scheduled indexing.

Magento 2 is developed and supported by Adobe, with regular security and feature releases. Keeping up with versions isn't optional: outdated versions run with known security vulnerabilities and PHP compatibility becomes limited too. A well-maintained Magento 2 system runs for years without a major rebuild. That's precisely the system's biggest advantage over hosted platforms.

A good extension adds little and lasts long. In practice, a handful of trusted families come back on every project: ElasticSuite for search and layered navigation, the Amasty module family for admin-side add-ons and data-protection features, plus Hungarian invoicing and courier modules.

What's worth avoiding: ten cheap extensions stacked on top of each other. Every installed module means slower performance, a larger security surface and one more obstacle at the next version upgrade. Before implementation, we always check whether a given feature can be handled with Magento's own tools instead.

Yes, and for a larger webshop this is where you save the most. The typical flows: stock and price from the ERP into the webshop, orders and customer data from the webshop into the ERP, and invoice and delivery status back to the customer.

The connection can be built via REST API, scheduled import/export or a middleware layer, depending on the other system's capabilities. The key question is always which system is authoritative for a given piece of data: once that's settled, most conflicts disappear.

Yes. The core Magento 2 system doesn't include Hungarian invoicing, but Hungarian invoicing services (such as Számlázz.hu and Billingo) can be connected via API, and NAV Online Számla data reporting then happens automatically through them. VAT rates, reverse charge and intra-EU sales are configured within Magento's own tax rule system.

On the payment side, Barion, SimplePay, Stripe and PayPal are the most common choices, and a Magento 2 module or custom integration exists for each. For delivery, GLS, FoxPost and MPL can be connected with automatic label printing and parcel locker selection, and custom shipping logic (weight thresholds, free-shipping limits, zoning) can also be built.

Migration has three stages: extracting and cleaning the data from the old system, mapping it onto Magento's data model (products, variants, categories, customers, orders), then loading and verification. Most of the work is usually not the loading itself but tidying up the old database. Old URLs need to be preserved with 301 redirects, otherwise you lose your existing search engine rankings.

It's better to plan Magento 2 development around a project or a monthly retainer than an hourly list price. A full implementation typically costs between €5,000 and €170,000 (+ VAT) depending on complexity, while ongoing development and maintenance are usually covered by a monthly retainer. Hourly rates for Magento developers in Hungary run well above WordPress-market levels, because the system demands deeper PHP, data-model and hosting expertise. Every project is based on an individual assessment and agreement.

There are four things worth asking. One: do they have a live Magento 2 webshop they can show as a reference, not just WooCommerce work. Two: how do they handle version upgrades: if they edit core files, the next upgrade grinds to a halt. Three: who hosts the server, and what happens during an overnight outage. Four: who owns the code and documentation if the working relationship ends. If there's no clear answer to these, the project ends up costing more later.

Yes, it's a task we handle regularly. A takeover starts with a technical audit: we review the Magento version, installed and custom modules, core modifications, the server environment and the backup routine. This produces a risk list and a prioritised plan: what needs fixing straight away and what can wait. Even an inherited, undocumented codebase can be stopped from deteriorating further; it just needs a realistic schedule.

With a template-based or hosted platform, the system dictates what's possible: business logic that falls outside the available settings simply can't be built. With Magento webshop development, it's the other way round: the system adapts to your business process, not the reverse. The price for that is a higher entry cost and the need for a dedicated server, but in return you get custom pricing, Magento B2B permission management, your own checkout and deep ERP integration.

Slowness can rarely be traced back to a single cause. The most common factors: missing or poorly configured Varnish caching, session handling without Redis, database-based search instead of OpenSearch, unoptimised images, too many installed third-party modules, and a live system left in developer mode. The fix starts with measurement: profiling reveals whether the bottleneck sits on the server, in the application or on the frontend.

Magento 2 comes with a strong SEO toolset out of the box: custom URL keys, canonical handling, meta templates, structured data and sitemap generation. In practice, the problem usually isn't the platform itself but the duplicate URLs generated by layered navigation, slow category pages and missing product descriptions. These can be addressed through configuration and content work, while improving Core Web Vitals comes down to server-side caching.

Yes. Magento 2 can generate a product feed for Árukereső, Árgép, Google Merchant Center and the Meta catalogue, with custom field mapping, category matching and scheduled updates. For measurement, GA4 ecommerce event tracking and server-side Measurement Protocol can also be connected, which noticeably improves advertising conversion accuracy.

Yes, Magento 2 is a multilingual system, and a Hungarian language pack can translate both the storefront and the admin panel. The community translation isn't complete, so on live projects we typically refine missing or mistranslated strings in a custom language file, especially the checkout and order email text, since these directly affect conversion.

Hyvä is a modern frontend layer that replaces Magento's default Luma theme: it swaps the heavy Knockout and RequireJS stack for Alpine.js and Tailwind CSS, giving substantially better Core Web Vitals and faster development. It comes with a licence fee, and the frontend of existing third-party modules often needs porting to it. For a new Magento 2 webshop it's worth using in almost every case; for an existing store, it's a judgement call.

A headless or PWA frontend is justified when the goal is an app-like customer experience, multiple presentation layers (web, mobile app, kiosk) or a very bespoke frontend. In return, you need to develop and host two separate layers, which is noticeably more expensive. For most Hungarian webshops, the Hyvä theme offers the better trade-off: a modern, fast frontend without headless complexity.

Yes, and it's actually urgent: support for Magento 1 ended in 2020, and it's been running with known security vulnerabilities ever since, putting both card data and customer data at risk. The migration process is the same as for other systems: data extraction, mapping onto the Magento 2 data model, loading, and 301 redirects. The old theme and modules can't be carried over, but product and customer data can be migrated in full.

Adobe Commerce's cloud package bundles the licence and the infrastructure together, but its annual fee is high relative to the scale of a Hungarian SME. In practice in Hungary, Magento Open Source plus a dedicated, tuned VPS is the proven route: lower cost, full control, a Hungarian data centre. We provide the server hosting in managed form, so you get the convenience of the cloud without the licence fee.

A dedicated VPS for Magento 2 from a Hungarian provider typically starts from around €100 a month, growing in proportion to the size of your catalogue and traffic. That's just the price of the hardware itself.

On top of that comes managed hosting, which covers tuning Varnish, Redis and the search engine, backups, monitoring and security updates. The two need to be read together: a server that's been bought but never tuned is the most common cause of slow Magento stores. You can read more about the server on our Ubuntu VPS hosting page.

Multistore is a built-in Magento 2 capability: a single installation can run multiple webshops with separate domains, languages, currencies and even different pricing, sharing a common product catalogue and admin panel. It's worth it when you're serving multiple brands or multiple countries: one maintenance effort, one stock pool, several stores. It's substantially cheaper than running separate systems.