Service · Web development

Custom Magento 2 website development.

A mature e-commerce platform for brands that have outgrown Shopify or WooCommerce. Multi-store, native B2B, deep ERP integrations and a module ecosystem that has been growing for twenty years. We build, migrate and optimise Magento 2 (Adobe Commerce) for merchants who need room to grow.

Adobe CommerceMulti-storeNative B2BPWA Studio

Magento fits when Shopify no longer does.

Most merchants start on Shopify or WooCommerce, and rightly so. Until the requirements become specific: multiple websites under a single catalogue, B2B price lists per customer, stacked tax rules per region, or a product configurator that doesn't fit anywhere out of the box. Then the stack gets stuck on extensions, on costs or on the limits of the platform itself. We know the symptoms: a checkout that can't be changed without a workaround, a product database maintained in spreadsheets because the admin can't cope, or a second webshop for Belgium that lives separately from the main store.

Magento 2 (part of Adobe since 2018, as Adobe Commerce) is built for exactly this situation. An open-source core with an extensive enterprise edition, an ecosystem of modules that has been growing since 2008, and native support for multi-store and B2B. The architecture is deliberately modular: products, customers, orders, prices and promotions are decoupled through service contracts, so custom work doesn't have to touch the core. We work with merchants who are making the move to Magento, or who are on Magento 1 or an outdated 2.x version and need to get moving again. Our Magento practice is part of our broader web development, alongside headless commerce and custom-built portals.

What makes our work different from hiring the average Magento partner: we see Magento as one possible outcome of a conversation, not as the answer. A considerable share of the clients we talk to end up with Magento. Others end up on a lighter platform, or on a headless stack with a thin core. We give that advice with no commercial interest in the platform.

What we do on Magento 2.

From a complete new build to a targeted migration or performance breakthrough. We advise which approach fits once we've seen your current situation.

Greenfield · new build from scratch

Building a new Magento 2 store

A completely new Adobe Commerce environment that fits your catalogue, target audience and operational reality. We set up Magento, configure multi-store where needed, integrate your ERP and PIM, and build the theme and checkout to your requirements. For the frontend we often choose Hyvä Themes, a modern rebuild of the Magento theme in Tailwind that dramatically improves performance compared with the standard Luma theme. Not an out-of-the-box package that only half fits, but a foundation that grows with your catalogue, channels and regions.

Multi-store setupTheme developmentCustom checkoutERP/PIM integration
Migration · from M1, Shopify or legacy

Migrating to Magento 2

Magento 1 has been end-of-life since June 2020: no more security patches, no official support, PCI-DSS risks and module makers phasing out their M1 extensions. We migrate M1 to M2, or Shopify Plus / WooCommerce / SAP Commerce to Magento 2 when your current stack hits its limit. A migration is not just a data transfer: it's an opportunity to clean up the catalogue structure, remove dead SKUs and standardise attributes. This falls within our broader platform migration practice: data conversion, URL redirects to preserve SEO, rebuilding integrations and a planned cutover with dry runs.

M1 → M2Shopify → MagentoSEO redirectsData migration
Further development · extending and optimising

Custom modules & performance tuning

The marketplace has tens of thousands of modules, but the truly distinctive functionality always lies in custom work. We build custom modules: a product configurator for composite products, a dedicated pricing engine for tiered and contract pricing, an exceptional checkout flow for those who want multiple delivery moments or split shipments, or a dedicated payment platform for those who want to orchestrate multiple payment flows. We also tackle performance bottlenecks: full-page cache, image optimisation, ElasticSearch tuning, database indexes and the Varnish stack, right down to the critical path in the checkout. A Magento store that is tuned in the right places achieves sub-second Time to First Byte, even with a large catalogue and a complex theme.

Custom modulesPerformance auditElasticSearchVarnish & cache

What you get at the end.

A working Magento 2 environment and everything you need to keep managing it, on your own or with us.

  • Production and staging environmentIdentical environments for live traffic and for testing, plus a development environment for sprint work. Runs on Adobe Commerce Cloud, your own GCP/AWS stack, or a specialist host such as Hypernode.
  • Theme and frontend in your own codebaseFull source code for the theme, custom modules and configuration. Organised in Git, with a CI/CD pipeline and review gates that automatically test every change before it goes to production.
  • Integrations live and documentedERP, PIM, OMS, payment providers, shipping services: everything that talks to the store, documented including auth tokens, retry behaviour, fail-over and an endpoint overview.
  • Admin training and runbookSessions for the marketing team (catalogue management, content staging, promotions, customer segments) and for IT (deployments, indexers, cache management, message queues, monitoring).
  • Monitoring and observabilityApplication-level metrics (response times, conversion, error rates), infrastructure monitoring, and alerts linked to the communication channel of your choice, reaching us and your IT team alike.
  • Support contract (optional)Security patches, Magento upgrades, monitoring and ongoing development. Fixed agreements on response times for production incidents and a transparent monthly hours budget for improvements.

Who we build Magento for.

Magento isn't right for every webshop, but it suits some very specific profiles. We mainly work with mid-market e-commerce merchants who combine complex product data, multiple markets or B2B relationships. Think of retailers with a D2C arm alongside a wholesale portal, manufacturers who sell directly to end users and to dealers, or brands active in several European countries that need to handle local prices, VAT rules and payment preferences.

A second large group is B2B merchants. Magento was built for business commerce before many other platforms were: account structures, contract pricing, quote flows and quick order via SKU lists are native to the Adobe Commerce edition. We connect that functionality to the ERP systems where your real stock, credit limits and order history live. The webshop then becomes a sales interface on top of your business systems, not a second version of the truth that drifts out of sync.

Finally, we see clients in the Adobe stack: organisations that already use Adobe Experience Cloud for analytics, personalisation or content (AEM). For them, Adobe Commerce is a natural extension, because the integrations between those products are better in the short term than between separate platforms. If you're not in that ecosystem, that argument carries less weight.

When Magento 2 is the right choice.

Four patterns in which we support merchants. If you recognise one of these, we'd be happy to talk further.

Complexity

Multiple stores, one catalogue

You sell under multiple brands or in multiple countries, but want one product database, one stock and one backend. Magento's multi-website architecture is designed for exactly that: one installation, multiple domains, shared or split catalogues, language and currency variants, with no separate Shopify stores to synchronise by hand.

B2B

Different prices per customer

Customer-specific price lists, account administrators with multiple buyers, quote flows and bulk orders. Magento has B2B functionality built in natively, whereas on most other platforms you have to bolt it on through apps or custom work. For deeper B2B needs, we pair Magento with a dedicated B2B e-commerce portal.

Migration

Still on Magento 1 or an old 2.x

M1 no longer receives patches and falls outside PCI DSS compliance, a direct risk if you process card data. An outdated Magento 2.3 or 2.4 without maintenance falls behind on security, Composer dependencies and PHP versions. Migration isn't trivial, but the risks of waiting (data breaches, customer trust, an unsaleable codebase) pile up every quarter.

Scale

Shopify is becoming too limiting

The checkout is locked down, the catalogue is hitting limits, or transaction fees are piling up as your revenue grows. With large catalogues with many SKU attributes, complex product relationships (bundles, configurables, kits), or custom checkout logic, Magento offers room to manoeuvre that Shopify fundamentally doesn't. We mainly see this migration among merchants who have grown their catalogue from a few hundred to a few thousand SKUs.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Integrations and compliance.

A webshop rarely stands alone. Magento is strong because it connects well with other systems, provided it's done with care.

  • ERP integrationsExact Online, AFAS, Microsoft Dynamics, SAP Business One, Odoo. Two-way synchronisation of products, stock, customers and orders via REST, GraphQL or Magento's message queue.
  • PIM integrationAkeneo, Pimcore or your own product database as the source for the catalogue. Magento remains the sales channel, while the PIM is the source of truth for product data.
  • Payments and fraud preventionMollie, Adyen, Stripe, MultiSafepay, Buckaroo. Including Strong Customer Authentication (PSD2), tokenised recurring payments and 3D Secure 2.
  • Logistics and OMSSendCloud, Monta, PostNL, DHL, or your own Order Management System if you run your own warehouses. Real-time carrier rates in the checkout, label creation and track & trace pushed to Magento.
  • Compliance built inGDPR-compliant data handling, PSD2-compliant payment flows, PCI DSS scope minimisation through tokenisation, ePrivacy cookie management, and auditable logging. Not an afterthought but part of the build.

How a Magento project works with us.

1

Introduction and quick scan

A conversation about your current store, the catalogue, the integrations and what's causing pain. For a migration, we look at the M1 or Shopify database; for a new build, at the source of product and customer data. We also map out which decision-makers need to be on board and how many manual processes can be automated away.

2

Architecture and planning

We outline the Magento architecture: which stores, which modules, which integrations, and which hosting option (Adobe Commerce Cloud, your own cloud or managed by us). We benchmark the choice between open-source Magento and Adobe Commerce (B2B module, page builder, search) against your specific needs. The result: a concrete scope, a sprint plan and a go/no-go moment at which we commit.

3

Building in sprints

Every sprint, we deliver a testable build on staging. Catalogue, checkout, integrations and theme run in parallel. You test along, the marketing team gets used to the admin, and IT gets used to the deployment flow. We schedule demo moments in advance and break scope down into epics that can go live independently: no big-bang go-live at the end, but phased validation along the way.

4

Migration, go-live and stabilisation

Data migration at an agreed freeze moment, dry runs, 301 redirects to preserve SEO, DNS cutover and monitoring from the first visitor. After go-live, a period of active stabilisation in which we closely track the first few hundred orders for anomalies. Then we move on to regular maintenance or further development in a second phase.

5

Maintenance, optimisation and further development

Magento is not a project but a platform: security patches, quarterly Adobe releases, PHP upgrades, module updates and performance work never stop. Optionally, we take this on as a maintenance contract with clear SLAs for production incidents and a quarterly development budget.

Frequently asked questions.

What merchants usually want to know before we start.

Magento 2 or Shopify: which suits us?
Shopify is quicker to set up, has a lower barrier to entry and works well for catalogues of up to a few thousand products with a standard B2C flow. Magento fits once you need multi-store, customer-specific B2B pricing, a large catalogue with many attributes, or substantial custom work in the checkout. A rule of thumb we use: if your product data fits in a spreadsheet and your checkout can be standard, you can stay with Shopify Plus. If your business rules need a second and third "unless" clause, you're ready for Magento. We advise honestly: if Shopify Plus is enough, we'll say so.
How does a migration from Magento 1 to Magento 2 work?
Magento 2 is a rewritten platform, not an upgrade. We build the new environment alongside the old one, migrate products, customers and orders using Adobe's data-migration tool plus our own scripts for custom fields, and test exhaustively on a staging environment. The URL structure is redirected one-to-one so your SEO rankings are preserved. We rebuild the theme from scratch, as an M1 theme cannot be carried over to M2. M1 modules often have a different codebase in M2 from the same vendor; for each module, we weigh up whether to keep it, replace it or rebuild it ourselves. The actual cutover takes place in a planned maintenance window, ideally outside peak traffic.
What is PWA Studio and when does it make sense?
PWA Studio is Adobe's framework for putting a headless React/GraphQL frontend on top of Magento: Magento handles the catalogue, pricing and checkout logic, while React takes care of the storefront. It makes sense if you want speed on mobile, an app-like experience with service workers, or a frontend that is completely decoupled from the Magento theme (for example, to run the same frontend on top of different commerce backends). For a standard B2C store it adds complexity without a clear benefit, so we stick with the native Luma stack or a Hyvä theme, which already achieves sub-second page loads. We outline the trade-off using your own figures.
What determines the cost of Adobe Commerce Cloud?
Adobe Commerce Cloud (the managed hosting variant) is priced on GMV (expected annual revenue), the number of SKUs and the number of environments. On top of that come licence fees for the B2B module or headless features. At higher GMV tiers, Adobe Commerce Cloud is often cheaper than self-hosting with dedicated DevOps, because 24/7 monitoring, scaling, security patches and the Adobe relationship are included. For smaller stores, open-source Magento on your own cloud (GCP, AWS, Azure or a specialist host such as Hypernode) is usually more cost-efficient. We run through scenarios based on your expected traffic, order volume and growth curve so you can make an informed choice.
How do you handle custom modules and the marketplace ecosystem?
The Adobe Marketplace has thousands of modules, but far from all of them are production-ready. We weigh it up case by case: a reputable module from the likes of Amasty, Mageworx or Mirasvit can save time on standard problems, whereas an unknown module often brings more technical debt than benefit, such as a hacked autoloader, missing tests or a locked-down licence that you hit later during an upgrade. We build custom modules to Magento's coding standards and service contract pattern, with dependency injection, plugins on public methods and unit tests, so they survive Adobe's quarterly releases. We document every module choice, so the chain of responsibility stays clear in the event of a security incident.
And what if Magento turns out to be too heavy?
That happens. Magento has an infrastructure footprint (multiple PHP workers, MySQL, Elasticsearch, Redis, RabbitMQ, Varnish) that doesn't suit every merchant. If your catalogue is small, B2B isn't relevant and you don't need multi-store, a lighter platform may be the better choice. In those cases we recommend a headless commerce stack on a lighter core (commercetools, Saleor, Medusa) or a Shopify Plus setup. If you do fit Magento, we help you make it profitable; if you don't, that is our advice, even if it means losing the project.
Do you work with our in-house IT or marketing team?
Almost always. We hand over knowledge in every sprint, not just at the end. IT gets deployment rights and monitoring access from day one, and marketing learns the admin while we build. We deliver documentation, incident runbooks and, optionally, an SLA for production support. Some clients take over management entirely after go-live, in which case we make sure the handover is clean. Others keep us on for further development and upgrades, with their own IT as the first line. Both models work; we agree up front which one suits your organisation best.
How do you handle Magento upgrades and security patches?
Adobe releases an update every quarter with security fixes, bug fixes and sometimes new features. Between those, security-only patches appear when CVEs are reported. Under a maintenance contract, we apply at least the security patches within the agreed timeframe, and we schedule minor upgrades at a pace that fits your release calendar. We treat major upgrades (for example 2.4 to 2.5, when it arrives) as a separate project with its own testing budget. For stores without a maintenance contract, we provide an upgrade path on request.

Talk to us about your Magento project.

A half-hour introductory call, no obligation. We listen to your current situation, ask sharp questions and give you direction you can use, even if the outcome is that Magento isn't the best choice.

Edit content