For catalogues other platforms can’t express
Magento earns its complexity when you have tiered B2B pricing, customer groups, multiple stores or tens of thousands of products. Below that, it’s a heavy answer to a light question — and we’ll say so.
What we take on
Store builds
Catalogue structure, attribute sets, customer groups and the pricing rules that made you choose Magento in the first place.
B2B pricing and rules
Tiered pricing, customer-group catalogues, quote workflows and account hierarchies — the things that don’t fit elsewhere.
Multi-store setups
Multiple storefronts, currencies and languages from one installation, sharing a catalogue where it makes sense to.
Custom modules
Extending Magento where no extension does it properly — see plugins & integrations.
ERP and system integration
Connecting the store to the systems that actually run the business: stock, accounting, fulfilment, CRM.
Performance work
Indexing, caching, image delivery and extension conflicts — the four things that make a Magento store slow.
Be honest about the cost
Magento is powerful and expensive to own. Worth knowing before you commit:
- Hosting is not shared hosting. It needs real resources, and that’s a recurring cost line, not a one-off.
- Upgrades are projects. Major version upgrades aren’t a button press; budget for them rather than discovering them.
- It needs a developer. Day-to-day catalogue work is fine for your team, but structural change isn’t.
- Extension quality varies wildly. Half the slow Magento stores we see are slow because of what was bolted onto them.
If your catalogue is straightforward, WooCommerce or Shopify will cost you far less over three years.
Migrations
Both directions, and both are common:
- Onto Magento, when a growing catalogue outgrew its platform
- Off Magento, when the ownership cost stopped being worth it
- Magento 1 to Magento 2, which is a rebuild rather than an upgrade
- Products, attributes, customers and order history mapped across
- A full URL map, so category and product rankings survive
- Rehearsed on staging before anything moves
Product and category URLs are usually where an established store’s search traffic lives — more under SEO & technical marketing.
Common questions
We’re on Magento 1 — what are our options?
Magento 1 is end of life and unsupported, which is a security problem rather than a nice-to-have. The realistic options are a Magento 2 rebuild or a move to another platform. Which is right depends on whether you still need what Magento gives you.
Can you take over a store another agency built?
Yes. It starts with an audit of what’s installed and what’s been customised — Magento stores accumulate extensions, and we need to know what’s load-bearing before changing anything.
Why is our Magento store slow?
Usually indexing configuration, caching not being used properly, unoptimised images, or an extension doing something expensive on every page load. An audit names which one rather than guessing.
Do you do Adobe Commerce as well as Open Source?
Tell us which licence you’re on and what you need — we’ll be straight about whether it’s a fit before quoting.
Tell us about the catalogue
How many products, what the pricing rules look like, and what it integrates with. We’ll tell you whether Magento is worth its cost for you.