Magento 2 webshopdevelopment and maintenance

Rolling out a Magento 2 webshop runs between €5,000 and €150,000 net. A store on standard foundations with a customised ready-made theme is €5,000–15,000, a shop with custom branding or migrated from another system is €15,000–45,000, and a complex B2B or multistore system starts at €45,000. The price is set by the product count, the volume of data to be migrated and the number of integrations, not by the design. Every project is quoted after an individual survey.

The price ranges of the whole webshop market in one place, in our webshop development prices 2026 article.

A Magento 2 webshop on standard foundations is up in 3–9 weeks, a custom rollout or migration takes 9–20 weeks, and a complex, B2B or multistore system 3–9 months. What usually stretches the timeline is not development but the data migration and the integration of external systems (invoicing, ERP, courier).

Ongoing Magento 2 maintenance typically runs between €150 and €2,500 net per month. The lower band covers security updates, backup checks and monitoring, the middle one version tracking and prioritised bug fixing, and the upper one also includes a monthly development budget and a quarterly technical audit.

WooCommerce is for smaller, simpler webshops: it starts faster and cheaper and works excellently up to a few hundred products and moderate traffic. Magento 2 gains the advantage where thousands of products, several warehouses, multiple languages or currencies, complex pricing and B2B permissions are the requirement. The practical boundary is roughly where WooCommerce can only keep going by piling on plugins.

Hungarian hosted shop engines (Shoprenter, Unas) give a fast start and cheap operation, but development freedom is limited: business logic the platform does not support cannot be implemented. It is worth moving to Magento 2 when a custom checkout, your own business logic, an ERP connection, several stores or international selling is the goal, or when the limits of the platform are already costing you revenue.

Magento Open Source is the free, open-source edition with no licence fee, but with the cost of development, servers and maintenance. Adobe Commerce is the paid edition with an annual licence, which adds a built-in B2B module, content staging, advanced segmentation and vendor support. For the vast majority of Hungarian small and medium businesses the Open Source edition is enough.

Magento 2 does not run reliably on shared hosting; it needs a dedicated VPS or server. For a starting webshop 4 CPU cores, 8–16 GB RAM and SSD/NVMe storage is the sensible minimum, alongside a Varnish cache, Redis for sessions and caching, and the OpenSearch search engine. With a larger catalogue and high traffic these scale up proportionally.

In the right server environment Magento 2 handles hundreds of thousands of products reliably. The practical limit is not the product count but the number of attributes and variants, the indexing strategy and the search engine configuration. Above ten thousand products it is worth using OpenSearch-based search, a Varnish cache and scheduled indexing.

Magento 2 is developed and supported by Adobe, with regular security and functional releases. Version tracking is not optional: outdated versions run with known security holes and PHP compatibility becomes limited too. A maintained Magento 2 system runs for years without a major rebuild. That is precisely its main advantage over hosted platforms.

Yes. The Magento 2 core does not include Hungarian invoicing, but the local invoicing tools (Számlázz.hu, Billingo and others) can be connected over their APIs, and the NAV Online Invoice reporting then happens automatically through them. VAT rates, reverse charge and intra-EU sales are configurable in the Magento tax rule system.

On the payment side Barion, SimplePay, Stripe and PayPal are the most common choices, and each has a Magento 2 module or a custom integration. For shipping, GLS, FoxPost and MPL can be connected with automatic labelling and a pickup point selector, and custom shipping logic (weight limits, free shipping thresholds, zoning) can be built as well.

A migration has three stages: extracting and cleaning the data from the old system, mapping it onto the Magento data model (products, variants, categories, customers, orders), then importing and verifying. Most of the work is usually not the import but tidying up the old database. The old URLs have to be preserved with 301 redirects, otherwise the rankings achieved in search are lost.

Magento 2 development is better planned per project or on a monthly budget than from an hourly rate card. A full rollout runs between €5,000 and €150,000 net depending on complexity, while ongoing development and maintenance is usually covered by a monthly retainer. Hungarian Magento developer rates are considerably higher than the WordPress market level, because the system demands deeper PHP, data model and operations knowledge. Every project is quoted after an individual survey and agreement.

There are four things worth asking. One: do they have a live Magento 2 webshop to show as a reference, not just WooCommerce work. Two: how do they handle version upgrades — where the core files get rewritten, the next upgrade is where it stops. Three: who runs the server and what happens during a night-time outage. Four: who owns the code and the documentation when the collaboration ends. If there is no clear answer to these, the project gets more expensive later.

Yes, this is a common job. A takeover starts with a technical audit: we go through the Magento version, the installed and custom modules, the core modifications, the server environment and the backup regime. From that we produce a risk list and an ordered plan: what has to be fixed at once and what can wait. Even with an inherited, undocumented code base the further decay can be stopped; it just has to be scheduled realistically.

With a template-based or hosted system the platform decides what is possible: business logic outside the configuration options cannot be implemented. Building a Magento webshop is the other way round: the system adapts to the business process, not the reverse. The price of that is a higher entry cost and a dedicated server, and in return custom pricing, B2B permissions, your own checkout and deep ERP integration all become possible.

Slowness rarely comes down to a single cause. The most common factors are a missing or misconfigured Varnish cache, 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 shows whether the bottleneck is on the server, in the application or on the front end.

Magento 2 ships with a strong SEO toolkit: custom URL keys, canonical handling, meta templates, structured data and sitemap generation. In practice the problem is usually not the system but the duplicate URLs generated by layered navigation, slow category pages and missing product descriptions. These can be handled with configuration and content work, while improving Core Web Vitals comes down to server-side caching.

Yes. Magento 2 can generate product feeds for price comparison sites, Google Merchant Center and the Meta catalogue, with custom field mapping, category matching and scheduled refreshes. For measurement, GA4 e-commerce event tracking and the server-side Measurement Protocol can be connected as well, which noticeably improves the accuracy of ad conversions.

Yes, Magento 2 is a multilingual system: with a Hungarian language pack both the storefront and the admin can be localised. The community translation is incomplete, so on live projects we refine the missing and mistranslated strings in a custom language file, especially in the checkout and the order e-mails, because those affect conversion directly.

Hyvä is a modern front-end layer replacing the default Luma theme: Alpine.js and Tailwind CSS take over from the heavy Knockout and RequireJS stack, giving considerably better Core Web Vitals scores and faster development. It carries a licence fee, and the front end of existing third-party modules often has to be ported to it. For a new Magento 2 build it is almost always worth it; on an existing store it is a judgement call.

A headless or PWA front end is justified when an app-like shopping experience, several presentation surfaces (web, mobile app, kiosk) or a highly custom front end is the goal. In return two layers have to be built and operated, which is noticeably more expensive. For most Hungarian webshops the Hyvä theme gives the better ratio: a modern, fast front end without headless complexity.

It is possible, and urgent: support for Magento 1 ended in 2020, and it has been running with known security holes ever since, which puts card and customer data at risk. The migration follows the same route as from other systems: extraction, mapping onto the Magento 2 data model, import, 301 redirects. The old theme and modules cannot be carried over, but the product and customer data can, in full.

The Adobe Commerce cloud package bundles the licence and the infrastructure, but its annual fee is high for the scale of a Hungarian SME. In local practice Magento Open Source plus a dedicated, tuned VPS is the proven route: lower cost, full control, a Hungarian data centre. We provide server operation as a managed service, so the convenience of the cloud is there without the licence fee.

Multistore is a built-in capability of Magento 2: one installation can run several webshops with separate domains, languages, currencies and even different pricing, on a shared product base and admin. It pays off when you serve several brands or several countries: one maintenance stream, one stock pool, several stores. It is considerably cheaper than running separate systems.