Magento development: Adobe Commerce, multi-store and scalable enterprise shops

Magento Open Source suits shops with clear feature needs and an in-house team or agency—no licence fees, but enterprise features (B2B, staging, Page Builder Pro) are missing or come as extensions. Adobe Commerce fits B2B scenarios with quote workflows, extended staging, Adobe SLA and larger marketing teams. We recommend the edition after a workshop: which B2B features are must-haves?

Magento 2 needs dedicated resources: sufficient RAM (production often 16 GB+), PHP 8.x, MySQL/MariaDB or Aurora, Redis for session and cache, Elasticsearch/OpenSearch for catalogue search, optionally Varnish for full-page cache. Shared hosting is not enough for enterprise shops. We recommend managed cloud (Adobe Commerce Cloud, AWS, Hetzner dedicated) with staging, automated backups and monitoring. Before go-live we run load tests—not when Black Friday traffic arrives.

Yes. We extract catalogue, customers and order history in a structured way, map attributes and categories to the Magento data model and define SEO redirects for existing rankings. Extensions and themes are not ported but re-conceived—normal for platform changes and avoids technical debt. Typical migration duration: 10–18 weeks depending on data quality and integration scope. Parallel operation on staging enables sign-off before the DNS switch.

Magento publishes regular security patches and quarterly releases. We run staging with production-like masked data, test extensions before each update and use deployment pipelines (Composer, static content deploy, cache warmup). Critical checkout and price flows are tested automatically. SLAs for response times and patch windows are agreed in the maintenance contract—so updates stay planned rather than reactive after a CVE notice.

Magento offers native B2B features (Adobe Commerce): company accounts with multiple buyers, shared catalogues, quote and approval workflows, quick order by SKU, credit limits and individual price lists per customer group. For pure B2B merchants with complex framework contracts this is often the decisive advantage over standard B2C platforms. We configure roles, price rules and approval processes so ERP and shop do not need double maintenance.

Elasticsearch/OpenSearch for search, Redis and Varnish for caching, CDN for static assets, image optimisation (WebP/AVIF) and targeted index and query tuning. With 100,000+ SKUs we review catalogue flat index, category anchor and unnecessary EAV attributes. Before launch we run load tests and Core Web Vitals checks—checkout and category pages under load, not just the homepage.

One Magento installation can map multiple websites, store groups and store views—per market its own currency, tax rules, language and pricing logic. We define early which content is global and which is local, and implement hreflang and canonical URLs cleanly. Faulty multi-store setups are a common cause of duplicate content and wrong prices—so we plan store architecture in the workshop, not at go-live.