OVERVIEW
Magento Development at MareLab
MareLab is a Magento 2 and Adobe Commerce engineering team. We extend and stabilise existing stores, build REST and GraphQL APIs for headless frontends, run version upgrades without breaking custom code, and consolidate multi-store estates. Our work spans global brands including Lindt & Sprüngli, Vivobarefoot, Ajmal Perfumes and MyRacehorse.
PROBLEMS WE SOLVE
Sound Familiar?
The store slows down as the catalog grows
Large catalogs, complex product options and heavy third-party modules push indexing, page generation and checkout response times up — usually first noticed on mobile.
Upgrades keep getting postponed
Custom modules and API consumers make version upgrades risky, so stores fall behind on security patches and PHP support.
The frontend can't keep up with the brand
The default Luma frontend limits app-like experiences. Headless (React, Angular, PWA) needs well-designed Magento APIs behind it.
Too many instances, modules and licences
Regional or brand-specific stores drift apart over time, multiplying licensing, hosting and maintenance cost.
WHAT'S INCLUDED
Our Magento Development Services
Backend & module development
Custom modules, checkout and pricing logic, B2B workflows, and clean-up of conflicting or redundant extensions.
REST & GraphQL API development
APIs designed for headless frontends, mobile apps and third-party systems, with attention to query cost and caching.
Upgrades & maintenance
Version upgrades with module and API compatibility checks and regression testing, followed by ongoing support.
Headless & PWA storefronts
React or Angular frontends backed by custom Magento GraphQL/REST, covering PLP, PDP, cart, checkout and account flows.
Multi-store & multi-instance consolidation
Merging separate Adobe Commerce instances into one codebase while keeping regional configuration and data separation where required.
Performance engineering
Caching, indexing, query tuning and frontend weight reduction, measured against Core Web Vitals.
HOW WE WORK
Our Process
- 1
Technical audit
Review of modules, customisations, integrations, hosting and performance so the scope is based on the real codebase.
- 2
Plan & estimate
A prioritised plan separating quick wins from structural work, with risks and dependencies called out.
- 3
Build in iterations
Work ships in reviewed increments on staging, with regression testing on checkout and integrations.
- 4
Launch & support
Monitored releases, then ongoing development or maintenance as your roadmap needs.
BEFORE YOU START
Things to Consider
Fix or rebuild?
Most slow or unstable stores don't need a re-platform. An audit usually shows whether problems come from a few modules, data volume, hosting, or the frontend.
Headless isn't always the answer
Headless gives frontend freedom but adds an API layer to maintain. For many stores, a lighter theme such as Hyvä delivers most of the speed gain with less complexity.
CASE STUDIES
Projects Where We Delivered This
Adobe Commerce Unification
Lindt & Sprüngli
Consolidated multiple Adobe Commerce instances into one architecture—lower cost, one codebase, all regional stores preserved.
Read the case study
Magento Backend & APIs
Vivobarefoot
Backend and API work for a global minimalist footwear brand—scale, integrations, and sustainable commerce features.
Read the case study
Headless Magento PWA
Ajmal Perfumes
Delivered a high-performance headless storefront: React PWA with custom Magento 2 GraphQL for app-like ecommerce.
Read the case study
Magento Upgrade & APIs
MyRacehorse
Magento 2 upgrades and backend APIs powering fractional racehorse ownership—Angular frontend, real-time data, scale.
Read the case study
Magento 2 Performance & Backend
Australia Luxe Collective
Enhanced and optimized Magento 2 for a global luxury footwear brand—performance, APIs, and premium shopping experience.
Read the case study
Gifting Marketplace on Magento
Papona
Optimized Magento 2 for a multi-vendor-style gifting platform—personalization flows, catalog, and performance.
Read the case studyRELATED SERVICES
Often Combined With
Let's Plan Your Next Stage of Growth
Book a free 30-minute call to review your current setup, identify key opportunities, and outline clear next steps — no obligation.
Frequently Asked
Questions
Yes. We work on Magento 2 Open Source and Adobe Commerce (formerly Magento Commerce), including multi-store and multi-instance enterprise setups such as our Lindt & Sprüngli consolidation.
Yes. We start with a technical audit of the codebase, modules and integrations so we understand the risks before changing anything, then agree a plan for fixes and ongoing development.
It depends on how many custom modules and integrations need to be made compatible. A store with few customisations can be quick; one with custom APIs and a headless frontend, like MyRacehorse, needs careful compatibility work and regression testing. We give an estimate after the audit.
Choose headless when you need app-like experiences or share the backend with mobile apps or other frontends. If the main goal is speed, a Hyvä theme is often simpler and cheaper to run. We can assess which fits your roadmap.