Magento 2 | Adobe Commerce
Custom module development, multi-store architecture, B2B workflows and the performance work that follows. Nine years on the platform, most of it on stores where the catalogue size is the architecture problem.
In one paragraph
Custom module development against the platform rather than around it, multi-store and multi-currency architecture, B2B quote and approval workflows, integration with ERP, CRM, payment and logistics systems, and the caching, indexing and database work that keeps a large catalogue fast. On the record: 12+ multi-store Magento 2 platforms carrying 500K+ SKUs and 1M+ monthly users, with site speed improved by 60% through Varnish, Redis, full-page cache, CDN and database tuning, and 90% of B2B order and quote processing automated.
What this is
Magento stops being a product and starts being a system at a point most businesses can name precisely: the catalogue grows past what the default indexers handle comfortably, or the second store view arrives, or someone asks for an approval chain. After that, what you have is an application, and it needs to be treated like one.
The work here is building inside that application properly. Modules that follow the platform rather than fight it, so an upgrade is a Tuesday rather than a project. Multi-store setups where the shared logic is actually shared. B2B workflows that model how the business really buys, including the parts nobody documented.
What this page is not
This page is about building. If you have not decided yet whether Magento is the right platform, or you want an opinion on a proposal from someone else, that is a different conversation and a cheaper one.
What usually brings this in
The catalogue grew and everything got slow.
Reindexing takes hours, category pages time out, and the fix keeps being described as "more servers".
Every upgrade breaks something.
Customisation was written around the platform instead of through it, so each release is a week of regression hunting.
B2B customers are handled by email and spreadsheet.
Quotes, approvals and account-specific pricing live outside the system, so nothing is auditable and nothing scales.
The ERP and the store disagree about stock.
Oversells, manual reconciliation, and a support team doing data entry.
What gets built
- Custom modules that survive upgrades
- Built against the plugin and preference system, with dependency injection used as intended. The test is simple and it is applied: a minor version upgrade should not require touching your code.
- Multi-store and multi-currency architecture
- Website, store and store view structured so shared logic is shared and the differences are configuration rather than forks. Localisation, tax and pricing handled per market.
- B2B quote and approval workflows
- Company accounts, role-based permissions and multi-level approvals. Five-level approval chains covering development, orders, quotes and vendor management are on the record.
- Performance engineering
- Varnish, Redis, full-page cache, Elasticsearch tuning, database indexing and query work, measured before and after rather than asserted.
- Integration with the systems behind the store
- ERP, CRM, payment gateways, logistics and PIM, over REST and GraphQL, with the retry and reconciliation behaviour defined rather than assumed.
Technologies
- Platform
- Magento 2
- Adobe Commerce
- Magento B2B
- MSI
- Language & data
- PHP
- MySQL
- GraphQL
- REST APIs
- Performance
- Varnish
- Redis
- Elasticsearch
- RabbitMQ
- Cloudflare
- Infrastructure
- AWS EC2
- RDS
- S3
- Docker
- Jenkins
- GitLab CI
How delivery runs
Scope, in writing
What the work is, and what it explicitly is not. The second half is the one that protects both of us, and it is written before anything is quoted.
Architecture before code
The data model, the integration points and the failure modes, agreed on paper. Most of the expensive mistakes in commerce are made here and discovered six weeks later.
Build in reviewable slices
Work lands in increments you can see running, not in one drop at the end. You find out early if something is going the wrong way, which is when it is still cheap.
Test against the real thing
Production-shaped data, production-shaped traffic. A checkout that works on twelve test products tells you nothing about one carrying a hundred thousand.
Deploy, document, hand over
Release process written down, documentation aimed at your team rather than at me, and a defined window afterwards where fixes are mine.
Relevant builds
- Custom platform · B2B
Procurement and approvals platform
Scalable B2B procurement platform streamlining purchase requests and approvals.
- B2B workflows
- Approvals
- Integrations
- Magento 2 · Marketplace
Multi-category marketplace
A scalable Magento 2 platform powering a wide multi-category retail catalogue.
- Magento 2
- Multi-category
- Scale
- Web platform · Manufacturing
Engineering manufacturer platform
A modern engineering brand platform built for discovery and enquiry.
- Web platform
- Technical SEO
- Content
Questions
- Do you work on Magento 2 or Adobe Commerce?
- Both. They are the same platform with a different licence and a different feature set on top, and most of the architecture work is identical. Adobe Commerce B2B, staging and content staging are the parts that genuinely differ.
- Can you work on an existing Magento build you did not write?
- Yes, and that is most of this work. It starts with reading the code rather than quoting on it, because the honest estimate on an unfamiliar codebase comes after a few days inside it, not before.
- Our Magento is on an old version. Is upgrading or rebuilding cheaper?
- It depends on how the customisation was written, not on how old the version is. Code written through the platform upgrades; code written around it often costs more to carry forward than to replace. That assessment is a few days of work and it is the one thing worth paying for before committing to either.
- Do you do Magento performance work on its own?
- Yes, and it is one of the more satisfying engagements because the result is measurable. It starts with finding out where the time actually goes, which is frequently not where the team assumes.
Describe what is in front of you and you get a written scope and a figure, usually within a few days of a short call. No charge for either.