Adobe Commerce & Magento
An Adobe Commerce Agency for Catalogs That Outgrew Everything Else
Management, marketing, development and creative for Adobe Commerce and Magento Open Source merchants — large catalogs, multi-store, B2B and the operational complexity that comes with them.
- Indexers, cache and search treated as commercial infrastructure, not sysadmin trivia
- B2B, multi-store and multi-currency configured properly instead of worked around
- Reporting on revenue, contribution margin and repeat rate — not admin panel charts
2.3s
Mobile LCP
48k
SKUs managed
+34%
B2B repeat orders
-41%
Extension count
The Problem
Adobe Commerce challenges we solve
Adobe Commerce can do almost anything, which is exactly the problem. Most stores are carrying complexity they chose years ago for reasons nobody wrote down.
Slow front end
Time to first byte of two seconds before anything renders. Varnish misconfigured or bypassed, and full-page cache hit rates nobody has ever looked at.
Extension conflicts
Thirty third-party modules rewriting the same core classes, so every upgrade turns into an archaeology project.
Upgrade cost that keeps growing
Each version behind makes the next upgrade more expensive, so it gets deferred again, which makes it more expensive again.
Indexers and cron falling over
Stale prices, missing products in category listings and a cron queue nobody monitors until a customer reports it.
Layered navigation SEO problems
Filter and sort parameters generating enormous numbers of crawlable URLs, with canonicals and robots rules left at defaults.
Catalog complexity nobody owns
Attribute sets, configurable products and category rules built by four different people over six years with no standard.
B2B bolted on rather than configured
Company accounts, requisition lists, quotes and payment terms available in the licence and never switched on.
Hosting nobody wants to touch
A stack of Varnish, Redis, OpenSearch and RabbitMQ configured once at launch and never revisited or documented.
Checkout friction
A multi-step checkout with slow shipping-rate calls, no express wallets and a guest flow that quietly discourages guests.
Split vendors
A development partner, a hosting provider and a media agency, each with a plausible explanation for why it is one of the others.
One-and-done customers
Sophisticated acquisition, almost no lifecycle automation, so every order is bought at full price.
Reporting nobody trusts
Magento reports, GA4 and the ad platforms all disagree, so decisions get made on whichever number supports the plan.
What We Do
Our Adobe Commerce services
Eight services covering the whole store. Each links to the specialist page where the method lives — this page is about how they behave on Adobe Commerce specifically.
01
Day-to-day store, catalog, merchandising and operational management across websites and store views.
02
Integrated acquisition and growth across search, paid, social, email and content.
03
Technical, category, product and content optimization — starting with layered navigation control, which is where most Magento SEO is decided.
04
Google Search, Shopping, Performance Max and Meta, running off a feed built from real attribute data.
05
Product pages, layered navigation, cart and checkout optimization, tested rather than assumed.
06
Lifecycle marketing and automation, including B2B reorder and requisition-driven programmes.
07
Custom modules, Hyvä and PWA front ends, upgrades, integrations and performance engineering.
08
Product, campaign and performance creative at the volume a large catalog actually needs.
Not sure where the cost is going? An Adobe Commerce audit covers all eight plus hosting, extensions, indexers and upgrade exposure. Packages are on the pricing page.
Operations
Adobe Commerce store management
On a large catalog the weekly operational work is the difference between a store that compounds and one that slowly degrades. Documented, scheduled and visible to you.
Products & Catalog
- Product updates, launches and end-of-life across websites and store views
- Attribute sets, configurable and bundle products kept to one standard
- Category rules, merchandising and sort logic maintained deliberately
- Catalog price rules, tier pricing and customer-group pricing
Store Operations
- Store, website and store-view configuration, tax and shipping rules
- Cart price rules, promotions and campaign landing pages
- CMS blocks, pages and Page Builder content maintenance
Technical Health
- Indexer and cron monitoring with alerting rather than discovery by complaint
- Cache hit rates, Varnish behaviour and search index health
- 404s, redirects, out-of-stock handling and log rotation
Reporting
- Sales by website, channel, category and product with period comparison
- Store performance — conversion rate, AOV, sessions and repeat rate
- Growth opportunities sized by likely impact and effort
The same operating model as our eCommerce management service, scaled to a multi-website Adobe Commerce estate.
Growth Model
Adobe Commerce marketing & growth
Three lanes, three outcomes. On a large Magento catalog the first lane is mostly an information-architecture problem before it is a content problem.
SEO
Google Ads
Meta Ads
Content
Traffic
Qualified sessions from commercial intent, with layered navigation configured so filters serve shoppers rather than flooding the index.
CRO
UX
Product pages
Conversion
More of that traffic buying, from research-led work on category pages, PDPs, cart and a checkout that can genuinely be rebuilt.
SMS
Retention
Repeat Revenue
Second and third orders won without paying for the click again — and on B2B, reorder programmes built on requisition data.
Detail on each lane sits on eCommerce marketing, CRO and email & retention.
Build
Magento development & technology
Engineering on Adobe Commerce is mostly about restraint: fewer overrides, fewer modules, and an upgrade path that stays open.
Ten areas we work in on Adobe Commerce. The extension audit and the upgrade path are where most engagements start, because deferred upgrades are the most expensive debt on this platform.
- Adobe Commerce and Magento Open Source development and custom modules
- Version upgrades and security patching with a documented regression suite
- Magento 1 and legacy platform migrations with a rankings-protection plan
- Hyvä theme builds and front-end rebuilds where the default theme is the bottleneck
- PWA Studio and headless front ends where the requirement genuinely justifies it
- Multi-website, multi-store-view and multi-currency architecture
- B2B configuration — company accounts, requisition lists, quotes and terms
- Performance engineering — Varnish, Redis, OpenSearch, indexers and cron
- Integrations to ERP, PIM, 3PL, POS and CRM via APIs and message queues
- Extension audit, consolidation and removal of anything duplicating core behaviour
The full engineering process, stack and QA approach sits on our eCommerce development & technology page.
Conversion
Adobe Commerce CRO & customer experience
Every step leaks. On a large catalog the biggest leak is usually discovery — people who cannot find the product they came for do not convert on any of the later steps.
Homepage
Category
Product
Cart
Checkout
Purchase
Discovery
- Navigation and category tree structure
- Layered navigation, filter labelling and search relevance
- Category page layout, content and sort logic
Product
- Product page structure and content order
- Configurable option selection, imagery and stock messaging
- Trust elements — reviews, guarantees, delivery promise
Mobile & Cart
- Mobile UX, tap targets and sticky add-to-cart
- Cart experience, shipping estimator and continue-shopping path
- Upsells, cross-sells and related-product rules
Checkout & Testing
- Checkout steps, rate-call latency, wallets and guest flow
- A/B testing with a stated hypothesis and a stop rule
- Rollout, monitoring and documentation of what changed
On B2B stores the same discipline applies to requisition lists, quick order and quote flows — the method is on the CRO page.
Stack
Extensions & integrations
We are vendor-neutral, and on Adobe Commerce the first question is always whether the core already does it. Every extension is an upgrade liability.
Marketing
- Email & SMS platforms
- Reviews and UGC
- Loyalty and referrals
Analytics
- Tracking and server-side events
- Reporting and BI connections
- Attribution and post-purchase surveys
Operations
- Inventory, MSI and purchasing
- Shipping, rates and labels
- Fulfillment, 3PL and warehouse systems
Customer Experience
- Search relevance and merchandising
- Personalization and recommendations
- Support, helpdesk and returns
Business Systems
- CRM
- ERP and PIM
- Accounting and reconciliation
On the last three Adobe Commerce upgrades we ran, extension count fell by an average of 41% with no loss of function — and the next upgrade got materially cheaper.
How It Works
Our Adobe Commerce growth process
Six steps. On this platform the audit has to include upgrade exposure, because that liability compounds whether or not anyone is looking at it.
01
Audit
Store, catalog, layered navigation, SEO, paid media, CRO, retention, plus hosting, extensions, indexers and upgrade exposure. You keep the document either way.
02
Identify Growth Opportunities
Everything the audit found, sized by likely revenue impact and effort, with technical debt priced honestly alongside the marketing work.
03
Build the Strategy
A twelve-month plan with a detailed first ninety days, named owners, a measurement framework and the numbers we expect to move.
04
Implement
Weekly delivery against a shared board. All development through Git, code review, automated tests and a staging environment that mirrors production.
05
Measure & Optimize
Monthly reporting on revenue, conversion rate, AOV, repeat rate and channel contribution, with what we learned and what changes.
06
Scale
Budget into what proved out, cut what did not, and add websites, markets or B2B capability once the architecture can carry them.
The audit covers store, SEO, paid media, CRO, retention and technology together. On Adobe Commerce the constraint is technical more often than on any other platform we work with.
Fit
Adobe Commerce services by business goal
Start from the outcome you need this quarter. Most stores need two of these, not eight.
Your goal
How we help
Launch or replatform
Design & development — architecture, catalog modelling, build, migration and a launch plan that protects rankings.
Grow organic sales
Magento SEO — layered navigation control first, then category, product and content optimization at catalog scale.
Generate sales quickly
PPC & Shopping — feed built from real attribute data, then Search, Shopping and Performance Max structured for margin.
Improve conversion rate
Adobe Commerce CRO — discovery first, then PDP, cart and checkout, tested with a stated hypothesis.
Increase repeat purchases
Email & retention — lifecycle flows, segmentation, reorder and win-back programmes.
Fix performance
Performance engineering — Varnish, Redis, OpenSearch, indexers, cron and front-end weight.
Sell B2B properly
B2B configuration — company accounts, requisition lists, quotes, terms and the sales-rep experience.
Reduce total cost of ownership
Extension audit, upgrade path, hosting review and consolidation of anything duplicating core behaviour.
Why Us
Why choose us as your Adobe Commerce agency
Eight reasons you can check rather than take on trust. Ask us for evidence on any of them.
eCommerce-First Expertise
Every client sells products online. We are not a systems integrator that also does storefronts.
Management + Marketing + Technology
One team across all three, so the indexer fix and the campaign change do not sit in two different vendors’ backlogs.
We Price Technical Debt Honestly
Upgrade exposure and extension liability appear in the plan with a number against them, not as a footnote.
Revenue-Focused Optimization
We report contribution after ad spend and COGS, not just ROAS. Less flattering, more useful.
Data-Driven Decisions
One agreed measurement setup, reconciled across Magento, GA4 and the ad platforms before anyone argues about performance.
Integrated Specialist Team
Specialists per discipline rather than generalists spread thin, coordinated by one account lead who owns the number.
Real B2B Capability
Company accounts, requisition lists, quoting and terms configured and then actually marketed, rather than switched on and forgotten.
Transparent Reporting
You own the code, the servers and every account. Reporting shows what we did, what it cost and what moved.
Proof
Adobe Commerce results & case studies
Three engagements with the baseline, the work and the outcome. Full write-ups on the case studies page.
Northwind Supply
Adobe Commerce — B2B industrial, US
CHALLENGE
48,000 SKUs across four websites, with B2B features licensed and never configured. Wholesale customers phoning orders through because the site could not take them.
SERVICES USED
Magento development, management and email & retention.
STRATEGY
Switch on and configure what was already paid for, then build reorder programmes on top of the data it produces.
EXECUTION
Company accounts, requisition lists, negotiable quotes and payment terms configured; ERP integration via message queues; then reorder and replenishment flows built on requisition history.
RESULT
B2B repeat orders up 34%, phone-ordered volume down by two thirds, and quote turnaround from four days to under one.
+34%
B2B repeat
48k
SKUs
-66%
Phone orders
Luxury Comforts
Adobe Commerce — home & bedding, US
CHALLENGE
A default Luma theme carrying seven years of customisation. Mobile LCP of 7.4s and a full-page cache hit rate under 40%.
SERVICES USED
Development, CRO and PPC.
STRATEGY
Rebuild the front end rather than optimise around it, since every incremental fix was being undone by the next release.
EXECUTION
Hyvä theme rebuild, Varnish and Redis reconfiguration, extension consolidation removing 41% of modules, then a paid media restructure onto the faster landing experience.
RESULT
Mobile LCP to 2.3s, cache hit rate above 90%, paid conversion rate up 31% and the next upgrade quoted at a third of the previous one.
2.3s
Mobile LCP
+31%
Paid CVR
-41%
Extensions
VAC Vacuums
Magento Open Source — appliances & parts, US
CHALLENGE
Layered navigation generating hundreds of thousands of crawlable URLs on a parts catalog, with compatibility data trapped in attributes nobody surfaced.
SERVICES USED
Magento SEO, management and creative.
STRATEGY
Decide what deserves to be indexable, then turn the compatibility data into the reason those pages rank.
EXECUTION
Layered navigation and canonical rules, category content programme, attribute-driven compatibility tables on PDPs, and internal linking rebuilt around model numbers.
RESULT
Non-brand organic sessions up 2.8x over ten months, with crawlable URLs reduced by 94% and crawl budget redirected to pages that convert.
2.8x
Non-brand traffic
-94%
Crawlable URLs
+37%
Organic revenue
FAQs
Adobe Commerce & Magento FAQs
Eight questions that come up in most conversations on this platform. More on our full FAQ page.
What is the difference between Magento Open Source and Adobe Commerce?
Open Source is the free, self-hosted edition. Adobe Commerce is the licensed edition, adding B2B, advanced merchandising, customer segmentation, staging and preview, and Adobe support — with Adobe Commerce Cloud as a hosted option on top. If you are not using the B2B module, staging, or segmentation, the licence is frequently the largest line item delivering the least. We will tell you honestly which one your business needs.
Should we stay on Adobe Commerce or move to something simpler?
It depends on catalog complexity, B2B requirements, multi-store needs and how much engineering capacity you have. Adobe Commerce earns its cost on complex catalogs, real B2B and multi-website estates. If your store is 400 SKUs on a single site, you are almost certainly paying for capability you do not use, and we will say so rather than defend a bigger retainer.
How risky is a version upgrade?
Risk scales with how far behind you are and how many extensions override core behaviour. We start with an audit that lists every override and every extension’s compatibility status, then upgrade against a documented regression suite covering the paths that earn money. The genuine risk is deferring it — each skipped version makes the next one more expensive.
Do you work with Hyvä?
Yes, and often. On stores where the default Luma theme has accumulated years of customisation, a Hyvä rebuild is usually cheaper and faster than continuing to optimise around the existing front end. It is not automatically the right answer, and we will scope both before recommending one.
Can you take over from our current development partner?
Yes. Onboarding is a code and infrastructure audit: module inventory, override map, custom code review, hosting and cache configuration, indexer and cron health, security patch status, and a documented list of what we inherited. You get that document regardless of what happens next.
Can you fix our layered navigation SEO?
Yes, and it is one of the most common reasons Magento stores come to us. The work is deciding which filter combinations deserve to be indexable, configuring canonicals and robots rules accordingly, then building content on the category pages that survive. It is usually the single biggest organic lever on a large Magento catalog.
Do you handle hosting?
We specify and manage it but do not resell it, whether you are on Adobe Commerce Cloud or self-hosted with a specialist provider. That keeps the recommendation about what the store needs rather than about our margin. You hold the account; we hold responsibility for it performing.
Who owns the code and the accounts?
You do, always. The repository, the servers, the licence, the ad accounts. We work under our own logins and commit to your repository. If the relationship ends, we hand over documentation and remove our access.
Find out what your Adobe Commerce store really costs to run
Book an audit. We will review the store, catalog, layered navigation, extensions, upgrade exposure, hosting, SEO, paid media, conversion and retention — and tell you what to fix first, whether or not you hire us.