Case Study
Multi-brand home & personal care merchant
Adobe Commerce (Magento 2)
Presented at Meet Magento Florida 2026 & MageTitans NL 2025
The problem isn't Magento.
It's how we use it.
A multi-brand home & personal care merchant was ready to abandon their Adobe Commerce platform. It was being called "too complex," "not fit for purpose," and "slow." The real issue wasn't the platform or the business: it was the gap between the two. Here's how we closed it.
01
The Mismatch
"They gave me the keys, but no one built the road."
The platform was being blamed for problems the platform didn't cause.
- Core Web Vitals failing on key pages (LCP, FCP, CLS)
- TTFB measured at 2.5to2.9s versus the <0.8s guidance
- Main thread blocked 5+ seconds by render-blocking CSS/JS
- Theme inheritance chain leaking between brands
- No APM, no E2E tests, no delivery safety net
- Business didn't trust releases: outcomes were unpredictable
02
The Rebuild
Less complexity. More context. Fewer WTFs.
Not a re-platform. A realignment between the business and the system.
- Removed over-engineering and accidental complexity
- Aligned platform workflows to business workflows
- Observability first, then automated checks on critical journeys
- Reduced frontend complexity: fewer overrides, less coupling
- Replaced jargon with runbooks and shared definitions of "good"
- Reduced friction for non-technical teams
03
The Shift
Magento is no longer the enemy. It's a teammate.
Outcomes became predictable: so trust followed.
- Teams stopped treating Magento as a black box
- Less fear of releases meant faster iteration, fewer escalations
- Non-technical teams gained autonomy through clearer workflows
- DTC performance started improving
- The roadmap became believable: progress was visible
- Perception shifted from outsider tech to integrated part of work
Treat Magento as a product, not a project. Customisation is a cost that must earn its keep. Every change needs an owner, a support path, and a rollback plan. Performance and security are requirements, not "nice to have."
By Marek Kubacak, "The Problem Isn't Magento" · Meet Magento Florida 2026
Connect on LinkedIn for the full talk →