Talk to us about your Magento project.
A free, no-obligation half-hour introductory call. We listen to your current situation, ask pointed questions and give direction you can use, even if the outcome is that Magento isn't the right choice.
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 an ecosystem of modules that has been growing for twenty years. We build, migrate and optimise Magento 2 (Adobe Commerce) for merchants who need room to grow.
When Magento makes sense and Shopify no longer does.
Most merchants start on Shopify or WooCommerce, and rightly so. Then the requirements become specific: several websites sharing one catalogue, B2B price lists per customer, layered tax rules by region, or a product configurator that simply doesn't fit out of the box. The stack then hits its limits, whether in extensions, costs or the platform itself. We recognise the symptoms: a checkout you can't change without a workaround, a product database maintained in spreadsheets because the admin can't handle it, or a separate Belgian webshop running apart from the main store.
Magento 2 (since 2018 under Adobe as Adobe Commerce) was built for exactly this situation. An open-source core with a comprehensive enterprise edition, an ecosystem of modules that has been expanding since 2008, and native support for multi-store and B2B. The architecture is deliberately modular: products, customers, orders, pricing and promotions are decoupled into service contracts, so custom work does not need to touch the core. We work with merchants making the move to Magento, or those on Magento 1 or an outdated 2.x version who need to get moving again. Our Magento practice is part of our wider web development offering, alongside headless commerce and custom-built portals.
What sets our work apart from an average Magento partner: we see Magento as one possible outcome of a conversation, not as the answer in advance. A considerable share of the clients we speak with end up on Magento. Others are better served by a lighter platform, or by a headless stack with a thin core. We give that advice without any commercial interest in the platform.
What we do on Magento 2.
From a complete new build to a targeted migration or performance overhaul. We recommend the right approach once we have seen your current situation.
Build a new Magento 2 store
A brand-new Adobe Commerce environment that suits your catalogue, audience and operational reality. We set up Magento, configure multi-store where needed, connect the ERP and PIM, and build the theme and checkout to measure. 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
Migrate 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 developers phasing out their M1 extensions. We migrate M1 to M2, or Shopify Plus, WooCommerce or SAP Commerce to Magento 2 when your current stack reaches its limits. A migration is more than moving data: it is an opportunity to clean up your catalogue structure, remove dead SKUs and standardise attributes. This falls within our wider platform migration practice: data conversion, URL redirects to preserve SEO, rebuilding integrations and a planned cutover with dry runs.
M1 → M2Shopify → MagentoSEO redirectsData migration
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 & caching
What you get at the end.
A working Magento 2 environment and everything you need to manage it further, either yourself or with us.
- Production and staging environmentsIdentical 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 moves to production.
- Integrations live and documentedERP, PIM, OMS, payment providers, shipping services: everything that communicates with the store, described in full, including auth tokens, retry behaviour, failover 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 a communication channel of your choice, so we know before you do, and before your IT team does.
- Management contract (optional)Security patches, Magento upgrades, monitoring and ongoing development. Agreed response times for production incidents and a transparent monthly hour budget for improvements.
Who we build Magento for.
Magento isn't right for every webshop, but it suits 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 customers and to dealers, or brands active in several European countries that need to honour local pricing, VAT rules and payment preferences.
A second large group is the B2B merchants. Magento was set up for business commerce long before many other platforms: account structures, contract pricing, quote flows and quick order via SKU lists are built into the Adobe Commerce edition natively. We integrate that functionality with the ERP systems where the actual stock, credit limits and order history live. The webshop thereby becomes a sales interface on top of your business systems, rather than a second source of truth that drifts out of sync.
Finally, we see clients within the Adobe stack: organisations already working with Adobe Experience Cloud for analytics, personalisation or content (AEM). For them, Adobe Commerce is a natural extension, because the integrations between those products are stronger in the short term than between standalone platforms. For organisations outside that ecosystem, this argument carries less weight.
When Magento 2 is the right choice.
Four patterns in which we guide merchants. If you recognise one of these, we would be happy to talk further.
Complexity
Multiple stores, one catalogue
You sell under several brands or across several countries, but you want one product database, one inventory and one back end. Magento's multi-website architecture is designed for exactly that: one installation, multiple domains, shared or split catalogues, and language and currency variants, rather than separate Shopify stores you have to synchronise by hand.
B2B
Different prices per customer
Customer-specific price lists, account managers acting for multiple buyers, quote workflows and bulk orders. Magento has B2B functionality built in natively; on most other platforms you have to bolt it on through apps or custom development. For deeper B2B requirements, we pair Magento with a dedicated B2B e-commerce portal.
Migration
Still on Magento 1 or an old 2.x
Magento 1 no longer receives patches and falls outside PCI DSS compliance, which is a direct risk if you handle card data. An outdated Magento 2.3 or 2.4 without maintenance lags behind on security, Composer dependencies and PHP versions. Migration is not trivial, but the risks of waiting, such as data breaches, loss of customer trust and an unmaintainable codebase, compound every quarter.
Scale
Shopify becomes too restrictive
The checkout is locked down, the catalogue hits its limits, or transaction fees pile up as your revenue grows. For large catalogues with many SKU attributes, complex product relationships (bundles, configurables, kits), or custom logic in the checkout, Magento offers room to manoeuvre that Shopify does not provide on principle. We mostly see this migration among merchants who have grown their catalogue from a few hundred to several thousand SKUs.
Not yet sure about a large project?
Test your idea first: a working prototype in 1 day
With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.
Explore OneDayBuild →Integrations and compliance.
A webshop rarely stands alone. Magento is strong because it integrates well, provided that is done with care.
- ERP integrationsExact Online, AFAS, Microsoft Dynamics, SAP Business One, Odoo. Two-way synchronisation of products, inventory, 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.
- Built-in complianceGDPR-compliant data handling, PSD2-compliant payment flows, PCI DSS scope minimisation through tokenisation, ePrivacy cookie management, and logging that can be audited. 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, catalogue, integrations and the pain points. For a migration, we review the Magento 1 or Shopify database; for a new build, we look at where your product and customer data originates. We also map out which decision-makers need to be involved and how much manual process can be automated.
2
Architecture and planning
We outline the Magento architecture: which stores, which modules, which integrations, and which hosting choice (Adobe Commerce Cloud, your own cloud or managed hosting with us). We benchmark open-source Magento against Adobe Commerce (B2B module, page builder, search) based on your specific needs. The result: a clear scope, sprint planning 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 way, your marketing team gets used to the admin, and your IT team gets used to the deployment flow. We schedule demo moments in advance and break the scope 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 point, dry runs, 301 redirects to preserve SEO, DNS cutover and monitoring from the first traffic onwards. After go-live, a period of active stabilisation in which we closely track the first few hundred orders for anomalies. Afterwards, we move on to routine management or further development in a second phase.
5
Management, optimisation and further development
Magento is not a project but a platform: security patches, Adobe quarterly releases, PHP upgrades, module updates and performance work are ongoing. Optionally, we can formalise this as a management contract with clear SLAs for production incidents and a quarterly development budget.
Frequently asked questions.
What merchants usually want to know before getting started.
Magento 2 or Shopify: what suits you?
Shopify is quicker to set up, has a lower entry threshold and works well for catalogues of up to a few thousand products with a standard B2C flow. Magento becomes the better fit once you need multi-store, customer-specific B2B pricing, a large catalogue with many attributes, or substantial customisation in the checkout. A rule of thumb we use: if your product data fits in a spreadsheet and your checkout can be standard, Shopify Plus is likely sufficient. If you need a number of exceptions built into your business rules, you're ready for Magento. We give honest advice: if Shopify Plus is enough, we 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 staging. URL structure is redirected one-to-one so that SEO rankings are retained. We rebuild the theme from scratch, as a Magento 1 theme cannot be carried over to Magento 2. Magento 1 modules often have a different paid version for Magento 2 from the same vendor; for each module we weigh whether to adopt, replace or rebuild it. The actual cutover takes place in a planned maintenance window, ideally outside peak traffic.
What is PWA Studio and when is it worthwhile?
PWA Studio is Adobe's framework for placing a headless React/GraphQL frontend on top of Magento: Magento handles the catalogue, pricing and checkout logic, while React powers the storefront. It is worthwhile if you want speed on mobile, an app-like experience with service workers, or a frontend that is entirely separate 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 clear gains; in that case we recommend the native Luma stack or a Hyvä theme, which already achieves sub-second page loads. We outline the trade-offs using your own figures.
What determines the cost of Adobe Commerce Cloud?
Adobe Commerce Cloud (the managed hosting variant) is priced based on GMV (expected annual revenue), number of SKUs and the number of environments. On top of this 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 specialised host such as Hypernode) is usually more cost-efficient. We model scenarios based on your expected traffic, order volume and growth curve so that you can make an informed choice.
How do you handle custom modules and the marketplace ecosystem?
The Adobe Marketplace offers thousands of modules, but far from all of them are production-ready. We weigh each case individually: a reputable module from, for example, Amasty, Mageworx or Mirasvit can save time on common problems, whereas an unknown module is often more technical debt than gain, such as a hacked autoloader, missing tests, or a closed licence that catches you out at upgrade time. We build custom modules according to Magento's coding standards and the service contract pattern, with dependency injection, plug-ins on public methods and unit tests, so they survive Adobe's quarterly releases. We document module choices so that 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, including multiple PHP workers, MySQL, Elasticsearch, Redis, RabbitMQ and Varnish, that doesn't suit every merchant. If your catalogue is small, you don't do B2B, and you don't need multi-store, a lighter platform may be the better choice. In such cases we recommend a headless commerce stack built on a lighter core (commercetools, Saleor, Medusa) or a Shopify Plus setup. For those who do fit Magento, we help make it profitable; for those who don't, that is our advice too, even if it means we lose the project.
Do you work together with our internal IT or marketing teams?
Almost always. We carry out knowledge transfer in every sprint, not just at the end. IT gets deployment rights and monitoring access from day one, and marketing learns the admin while the build is underway. We deliver documentation, incident runbooks and, optionally, an SLA for production support. Some clients take over management entirely after go-live, and we ensure a clean handover. Others keep us on for ongoing development and upgrades, with their own IT as first line. Both models work well; we agree in advance which suits your organisation best.
How do you handle Magento upgrades and security patches?
Adobe releases a version every quarter with security fixes, bug fixes and sometimes new features. In between, security-only patches appear for reported CVEs. Under a maintenance contract we apply at least the security patches within the agreed timeframe, and we schedule minor upgrades to fit your release calendar. Major upgrades (for example, 2.4 to 2.5 when it arrives) we handle as a separate project with a testing budget. For stores without a maintenance contract, we provide an upgrade path on request.