Magento 2 webshop development and maintenance

A Magento 2 webshop implementation costs between €5,000 and €170,000 net. A shop built on standard foundations with a customised off-the-shelf theme costs €5,000 – €17,000, a webshop with a bespoke design or migrated from another system €17,000 – €50,000, while a complex B2B or multistore system starts at €50,000. The price is driven by the number of products, the volume of data to migrate and the number of integrations, not by the design. Every project is based on an individual assessment.

A Magento 2 webshop built on standard foundations is up and running in 3–9 weeks, a bespoke implementation or migration takes 9–20 weeks, and a complex B2B or multistore system 3–9 months. The timeline is most often stretched not by development but by data migration and the integration of external systems (invoicing software, ERP, courier service).

Ongoing Magento 2 maintenance typically costs between €170 and €3,000 net per month. The lower band covers security patches, backup checks and monitoring, the middle band adds version upgrades and priority bug fixing, and the upper band also includes a monthly development allowance and a quarterly technical audit.

WooCommerce is suited to smaller, simpler webshops: it launches faster and at lower cost, and works very well up to a few hundred products and moderate traffic. Magento 2 comes out ahead where thousands of products, multiple warehouses, multiple languages or currencies, complex pricing and B2B permission management are required. The practical threshold is roughly the point where WooCommerce can only keep working by piling up extensions.

Hungarian SaaS webshop platforms (Shoprenter, Unas) offer a quick launch and low running costs, but development freedom is limited: business logic the platform does not support cannot be implemented. Switching to Magento 2 makes sense when the goal is a custom checkout, your own business logic, an ERP connection, multiple stores or international sales, or when the platform's limitations are already costing you revenue.

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

Magento 2 does not run reliably on shared hosting – it needs a dedicated VPS or server. For a new webshop, 4 CPU cores, 8–16 GB of RAM and SSD/NVMe storage are the sensible minimum, together with a Varnish cache, Redis for session and cache handling, and an OpenSearch or Elasticsearch search engine. With a larger catalogue and high traffic, these resources scale up proportionally.

In the right server environment, Magento 2 reliably handles hundreds of thousands of products. The practical limit is not the number of products but the volume of attributes and variants, the indexing strategy and the search engine configuration. Above 10,000 products, OpenSearch or Elasticsearch based search, Varnish caching and scheduled indexing are worth using.

Magento 2 is developed and supported by Adobe, with regular security and feature releases. Keeping up with new versions is not optional: outdated versions run with known security vulnerabilities, and PHP compatibility becomes limited as well. A well-maintained Magento 2 system runs for years without a major rebuild – which is precisely its main advantage over SaaS platforms.

Yes. The Magento 2 core does not include Hungarian invoicing, but Hungarian invoicing software (for example Számlázz.hu or Billingo) can be connected via API, and invoice data reporting to NAV Online Számla (the Hungarian tax authority's system) then happens automatically through it. VAT rates, reverse charge and intra-EU sales can be configured in Magento's 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 integrated with automatic label printing and a pick-up point selector, and custom shipping logic (weight limits, free shipping threshold, zones) can also be implemented.

Migration has three stages: extracting and cleansing data from the old system, mapping it to the Magento data model (products, variants, categories, customers, orders), then importing and verification. Most of the work usually lies not in the import but in tidying up the old database. Old URLs must be preserved with 301 redirects, otherwise the search rankings you have earned are lost.

Magento 2 development is best planned per project or on a monthly allowance, not at an hourly list rate. A full implementation costs between €5,000 and €170,000 net depending on complexity, while ongoing development and maintenance are usually covered by a monthly framework agreement. Magento developer hourly rates are considerably higher than WordPress market rates, because the system demands deeper PHP, data model and operations expertise. Every project is based on an individual assessment and agreement.

Four things are worth asking. One: whether they have live Magento 2 webshops they can show as references, not just WooCommerce projects. Two: how they handle version upgrades – where the core files have been modified, the next upgrade grinds to a halt. Three: who runs the server, and what happens during a night-time outage. Four: who owns the code and the documentation if the partnership ends. If there is no clear answer to these, the project will cost more later.

Yes, this is a common task. A takeover starts with a technical audit: we review the Magento version, the installed and custom modules, core modifications, the server environment and the backup regime. From this we produce a risk list and a prioritised plan – what needs fixing immediately and what can wait. Even with an inherited, undocumented codebase, further deterioration can be stopped; it just has to be scheduled realistically.

With a template-based or SaaS system, the platform dictates what is possible: business logic beyond its configuration options cannot be implemented. When building a Magento webshop, the situation is reversed – the system adapts to your business processes, not vice versa. The price is a higher entry cost and the need for a dedicated server, but in return bespoke pricing, B2B permission management, 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 search instead of OpenSearch or Elasticsearch, unoptimised images, too many third-party modules installed, 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 in the frontend.

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

Yes. Magento 2 can generate product feeds for Árukereső and Árgép (Hungarian price comparison sites), Google Merchant Center and the Meta catalogue, with custom field mapping, category matching and scheduled updates. For measurement, GA4 e-commerce event tracking and the server-side Measurement Protocol can also be connected, which noticeably improves the accuracy of ad conversion data.

Yes, Magento 2 is a multilingual system, and with a Hungarian language pack both the storefront and the admin panel can be translated into Hungarian. The community translation is incomplete, so on live projects we usually refine missing and mistranslated strings in a custom language file – especially the checkout and order e-mail texts, because these have a direct impact on conversion.

Hyvä is a modern frontend layer that replaces Magento's default Luma theme: the heavy Knockout and RequireJS stack is replaced by Alpine.js and Tailwind CSS, which delivers considerably better Core Web Vitals scores and faster development. It carries a licence fee, and the frontend of existing third-party modules often has to be ported to it. For a new Magento 2 webshop it is almost always worth it; for an existing shop it is a matter of weighing up the pros and cons.