Enterprise Commerce Engineered
for Complexity, Scale, and
Control.
Magento now Adobe Commerce at the enterprise tier and Magento Open Source at the community tier remains the most powerful open-source commerce platform available, and the right choice for organisations that have outgrown SaaS commerce platforms, need a level of customisation that no hosted solution supports, or require a B2B commerce architecture sophisticated enough to handle complex account structures, custom pricing, and procurement workflows that consumer-oriented platforms cannot accommodate. Adobe Commerce's native B2B module, its multi-store and multi-website architecture, its highly extensible plugin system, and its growing headless commerce capability via the PWA Studio and App Builder make it the platform of choice for manufacturers, distributors, and complex D2C brands that need commerce technology to bend to their business model rather than constraining it. SourceMash's Adobe Commerce practice delivers custom Magento 2 development, Adobe Commerce B2B implementations, headless PWA Studio builds, module development, ERP and CRM integration, Magento 1 to 2 migrations, performance engineering, and the managed growth programmes that keep Adobe Commerce stores competitive and revenue-growing year after year.
The Most Configurable Commerce Platform. For Those Who Need It.
Magento and Adobe Commerce are not the right platform for every business and being honest about that distinction is part of what makes our platform advisory credible. The brands for whom Magento and Adobe Commerce is the right choice share a common characteristic: their commerce requirements have outgrown what a SaaS platform can accommodate without excessive workarounds, or they need a level of data sovereignty and infrastructure control that a multi-tenant SaaS model cannot provide. A manufacturer with 80,000 SKUs, 12 customer price tiers, complex configurable products, and a procurement system that places orders via EDI is not well served by Shopify Plus. A D2C brand with a complex subscription model, a custom configurator that calculates prices from 30 variables, and a requirement to run their commerce platform within an on-premise data centre for regulatory reasons is not well served by any SaaS platform. For these organisations, Adobe Commerce provides the technical foundation for a commerce system that works exactly as the business requires not a set of platform constraints that the business must accommodate.
SourceMash's Adobe Commerce practice covers every edition and use case from Magento Open Source for mid-market brands seeking maximum flexibility at lower licensing cost, through Adobe Commerce (formerly Magento Commerce) for enterprise brands requiring the B2B module, advanced reporting, and Adobe support SLA, to headless Adobe Commerce implementations using PWA Studio and GraphQL API for brands prioritising performance and frontend flexibility.
Which Adobe Commerce Edition?
Partner Credentials
Service 01
Magento Store Build, Configuration & Platform Migration
A Magento / Adobe Commerce store build is an engineering project of a different order of complexity than a Shopify or WooCommerce implementation because the platform's flexibility is not delivered by a visual admin but by the intersection of PHP 8 object-oriented programming, Magento's dependency injection framework, the declarative schema system for database customisation, the plugin (interceptor) architecture for modifying core behaviour, and the EAV (Entity-Attribute-Value) data model that makes Magento's product attribute system so flexible and its database queries so complex. Getting a Magento store architecturally right at build stage correct dependency injection configuration, appropriate use of plugins vs. observers vs. preferences, proper EAV attribute design, database indexer management, and the caching architecture that is essential for Magento performance determines whether the store performs well and remains maintainable over time or accumulates the technical debt that characterises most mid-quality Magento implementations.
Migrations to Magento 2 from Magento 1 (officially end-of-life since June 2020 but still running in a significant number of production stores), from other platforms (Shopify, WooCommerce, PrestaShop, custom-built), or from Magento 2 to Adobe Commerce are complex data migration and architectural projects that require systematic catalogue data mapping, redirect management, and functionality parity planning before a single line of code is written.
Architecture & Discovery
Structured discovery covering product catalogue complexity (attribute sets, configurable product option dimensions, custom product types), multi-store and multi-website requirements, B2C vs. B2B or hybrid model, payment gateway and tax jurisdiction requirements, ERP integration scope and data flow, fulfilment model, and the custom module development scope that the business requirements necessitate. Architecture document specifying the store tree (websites, stores, store views), attribute set design, module dependency map, integration data flow diagrams, and the hosting stack configuration produced before development begins to prevent the costly scope changes that arise when requirements surface during implementation.
Catalogue Architecture & EAV Design
Magento's EAV (Entity-Attribute-Value) product data model is its most powerful and most misunderstood feature correctly designing attribute sets (groupings of product attributes for different product types), attribute scopes (global vs. website vs. store view), input types (text, select, multiselect, price, boolean, image), and indexer behaviour (whether an attribute is filterable, searchable, comparable, and used in layered navigation) determines catalogue management efficiency, search quality, and database query performance across the entire store lifetime. SourceMash architects the EAV structure before populating a single product, including the flat catalogue configuration and the attribute indexer settings that control query performance at scale.
Magento 1 to Magento 2 Migration
Magento 1 to Magento 2 migration the most technically complex e-commerce platform migration type, because Magento 2 is not an upgrade of Magento 1 but a rewritten platform with a fundamentally different architecture. The migration involves: database migration using the official Magento Data Migration Tool for catalogue, customers, and orders; custom module re-architecture (M1 extensions cannot be ported to M2 they must be rewritten to M2 module standards); theme rebuild from scratch (M1 themes are incompatible with M2's UI component and layout system); payment and shipping integration reconfiguration; and redirect mapping for every URL that has changed between the M1 and M2 URL structure.
Checkout & Payment Configuration
Magento checkout configuration and optimisation guest checkout, address validation, one-step vs. multi-step checkout (Magento's default two-step checkout vs. third-party one-step checkout extensions), payment method integration (Razorpay, PayU, Cashfree, CCAvenue, Stripe, PayPal via Magento payment gateway adapters), BNPL integration (Simpl, LazyPay, Afterpay via custom payment module), GST-compliant tax calculation and invoice generation for Indian market stores, and the checkout UX optimisations (field count reduction, autocomplete, progress indicators) that improve checkout completion rates in Magento's notably complex default checkout flow.
Hosting & Infrastructure Setup
Magento requires significantly more infrastructure configuration than SaaS platforms to achieve good performance the hosting stack must include: PHP-FPM 8.2+ with OPcache, Nginx or Apache with Magento-specific rewrite rules, MySQL 8 or MariaDB with the query optimisation configuration Magento's EAV queries require, Redis for both the default cache (database queries, layout XML, block HTML) and the session cache, Elasticsearch or OpenSearch for catalogue search (Magento has deprecated MySQL search for catalogues above a few thousand products), and a CDN (Cloudflare, Fastly, or AWS CloudFront) for static asset delivery. Adobe Commerce Cloud includes pre-configured Fastly CDN and a managed hosting environment; self-hosted implementations require this stack to be configured by a DevOps engineer.
Multi-Store & Multi-Website Architecture
Magento's three-tier store hierarchy (Website → Store → Store View) is the most flexible multi-brand and multi-market architecture in open-source commerce enabling multiple brand websites sharing a product catalogue, multiple currency and language combinations under a single installation, market-specific pricing and tax configuration, and store-view-level content localisation with shared operational data. SourceMash architects the website/store/store-view hierarchy to match the client's brand portfolio and international market requirements, configuring the scoped attribute values (store-view-scoped product descriptions for localisation), website-scoped pricing (different base prices by website for market-specific pricing), and the Magento URL rewrite management that keeps international SEO clean across the multi-site structure.
Service 02
Custom Magento Theme Development & Frontend Engineering
Magento 2 theme development uses a frontend architecture that is fundamentally different from WordPress/WooCommerce or Shopify theme development — Magento's layout XML system (defining the structural organisation of blocks on each page type), the PHTML template system (PHP templates rendering individual blocks), the KnockoutJS-based UI component framework (for dynamic frontend interactions), the Less CSS preprocessor, and the RequireJS module loader all combine into a frontend system that has significant power and flexibility but a steep learning curve and a performance overhead that requires careful configuration to overcome. Magento's frontend compilation pipeline (grunt or Magento's built-in deploy:static-content command) must be correctly configured for development workflow efficiency, and the static content deployment process must be managed as part of the CI/CD pipeline for production deployments.
SourceMash builds Magento themes as child themes of the Magento Luma or Blank parent themes (following Magento's theme inheritance system that allows targeted overrides without duplicating the full parent theme) for development efficiency and upgrade safety, and as fully custom standalone themes where the brand's design system requires complete control over the rendered HTML structure.
Magento Layout XML & Template Overrides
Magento 2 layout XML architecture the declarative system that defines which blocks appear on each page type (catalog_category_view, catalog_product_view, checkout_cart_index, checkout_index_index), in what order, and with what data. Custom layout XML files in the theme override or extend default layouts without modifying core files adding, removing, and reordering blocks; passing arguments to block classes; and referencing containers to build custom page structures. PHTML template overrides in the theme's templates directory shadow core templates for the specific blocks whose rendered output needs customisation following Magento's template fallback mechanism that checks the theme directory before the module's view directory.
UI Components & KnockoutJS
Magento 2 UI component development the KnockoutJS-based declarative frontend framework that powers Magento's dynamic interfaces (checkout steps, product configurator, customer account forms, layered navigation, mini-cart). Custom UI components extending Magento's base component library for store-specific interactive features custom checkout steps injecting additional data collection between the standard address and payment steps, custom product configurator displaying pricing that updates in real time as the customer selects configurable option combinations, and the customer-facing account dashboard components that B2B buyers use to manage their company account, requisition lists, and order history.
Adobe Page Builder & Content Types
Adobe Commerce Page Builder implementation the drag-and-drop content management system (available on Adobe Commerce, not Magento Open Source) that enables merchandising teams to build CMS pages, category landing pages, and product description sections without developer involvement. Custom Page Builder content type development each content type is a combination of a form.xml configuration (editable properties in the Page Builder panel), a preview.js component (live preview in the Page Builder canvas), and a master.html template (rendered output in the storefront). Custom content types for the brand's specific content needs: countdown timer, product carousel with custom data source, editorial lookbook, video background hero, and store locator map embed.
Layered Navigation & Product Search
Magento layered navigation configuration and customisation attribute-based faceted filtering on category and search result pages, price range slider, in-stock filter, rating filter, and custom attribute filters for the specific product attributes relevant to the catalogue category. Magento's built-in Elasticsearch / OpenSearch integration for full-text product search with relevance ranking, search suggestions, and search term management (redirects for brand name queries, synonyms for product terminology variations). Third-party search integration for stores requiring AI-powered search (Algolia, SearchPie, Searchanise) delivering instant results, personalised ranking, and semantic search that Magento's native search cannot match.
Mobile-First Responsive Theme
Mobile-first Magento theme development addressing the significant performance challenges that Magento's default Luma theme creates on mobile (Luma is not performance-optimised and scores consistently below 40 on Google PageSpeed Insights mobile). Custom mobile-first theme architecture: critical CSS inlined to prevent render-blocking, Less compilation configured for minimal output, RequireJS bundles split for per-page loading rather than global loading, product gallery using a lightweight swipe-gesture carousel replacing Magento's jQuery-heavy default gallery, and the mobile navigation pattern (off-canvas menu, collapsible category tree) that works efficiently on touch devices.
Product Page Architecture
Magento product page as a conversion engineering discipline above-fold layout with hero image gallery (zoom, 360°, video), configurable product option selectors (swatch-based for colour/pattern, button-based for size, dropdown for other dimensions) with price update on option selection, stock status and availability messaging, add-to-cart with quantity selector and wishlist, breadcrumb navigation. Below-fold: tabbed content sections (description, specifications, reviews, shipping information), related products, cross-sell and upsell product blocks configured via the Magento admin or dynamic rules. Structured data (Product JSON-LD) in the page head for Google rich results eligibility.
Service 03
Custom Magento Module Development & Extension Engineering
Magento 2's modular architecture every feature is a module, including core platform features means that custom module development is the primary mechanism for extending the platform with business-specific functionality. Unlike WordPress plugins or Shopify apps, Magento modules interact with the core through a disciplined system of dependency injection, service contracts (PHP interfaces that define the API for core functionality), plugins (interceptors that modify the behaviour of public methods without changing their source code), observers (event-driven reactions to Magento events), and preferences (interface implementations that replace core implementations). This architecture makes Magento highly customisable while maintaining upgrade safety when the approach is followed correctly. When it is not when core files are modified directly, when business logic is placed in controller actions instead of services, when database tables are added without declarative schema the result is a store that breaks on every minor Magento update and cannot be maintained without the original developer's involvement.
Dependency Injection & Service Contracts
Magento 2 dependency injection architecture the ObjectManager-based DI container that resolves dependencies from di.xml configuration, enabling constructor injection of services without direct instantiation. Service contracts (PHP interface + implementation pairs) for all custom business logic following Magento's pattern where interfaces define the API, implementations provide the logic, and di.xml maps interfaces to implementations. This architecture makes custom logic testable, swappable, and upgrade-safe. Preferences (alternative implementations replacing core service contracts via di.xml) used sparingly and only where plugins cannot achieve the modification preferences break on core upgrades that change the replaced class.
Plugins & Interceptors
Magento 2 plugin (interceptor) development for modifying core and third-party module behaviour without editing source files the correct mechanism for the majority of Magento customisations. Around plugins (wrapping a method to modify both input and output, or change flow control entirely), before plugins (modifying input arguments before a method executes), and after plugins (modifying the return value after a method executes). Plugin priority management when multiple plugins target the same method. Observer-based event handling for Magento's event/dispatch system reacting to commerce events (checkout_submit_all_after, catalog_product_save_after, sales_order_place_after) without modifying the code that dispatches the event.
Custom Pricing & Discount Logic
Custom pricing module development for complex pricing requirements that Magento's built-in catalog price rules and cart price rules cannot express customer-group-based pricing with complex tier structures (not just quantity tiers but customer attribute-based tiers), configurable product pricing calculated from the combination of selected options (not just the sum of option price adjustments), time-decay pricing for perishable or seasonal inventory, and contract pricing for B2B accounts with negotiated product-level prices stored in a custom pricing table. Custom cart price rule conditions extending Magento's condition system with business-specific eligibility criteria not available in the default condition library.
Custom Product Types
Custom Magento product type development extending the AbstractType class for product models that Magento's six standard product types (Simple, Configurable, Grouped, Bundle, Virtual, Downloadable) cannot accommodate. Use cases: rental and booking products with date-range availability, per-day pricing, and calendar-based inventory management; subscription products with recurring billing and delivery scheduling; made-to-order products that collect manufacturing specifications at checkout and create a production work order; and composite product types that dynamically calculate price from a configurable set of components, each with their own inventory and pricing.
Custom Shipping & Fulfilment Modules
Custom Magento shipping carrier module development extending the AbstractCarrier class for shipping rate calculation logic that Magento's built-in carriers (FlatRate, FreeShipping, TableRate) and available third-party extensions cannot accommodate. Real-time rate API integration with Delhivery, Shiprocket, Ezyslips, or Dunzo for carrier-calculated shipping rates at checkout; multi-origin shipping calculation routing orders from the nearest warehouse or store to the delivery address; product-dimension-based rate calculation for freight items; delivery date promise calculation from the selected shipping method and the warehouse's cut-off time; and the pincode serviceability check that blocks checkout for delivery addresses outside the serviceable area.
Custom Payment Gateway Modules
Custom Magento payment gateway module development for payment providers without existing Magento 2 extensions implementing the Magento Payment Gateway SDK (the structured abstraction layer for payment integrations introduced in Magento 2.1). Payment gateway modules cover: authorize/capture/void/refund API integration, the vault tokenisation system for saving payment methods for guest and registered customer checkout, 3D Secure handling, webhook receiver for asynchronous payment status updates, and the order status state machine integration that correctly transitions Magento orders through pending → processing → complete states based on payment gateway events.
Service 04
Adobe Commerce B2B
Adobe Commerce's B2B module available exclusively on the Adobe Commerce (paid) edition is one of the most comprehensive native B2B commerce feature sets available on any open-source platform. Company account management (multiple buyers under a single company account with role-based purchasing permissions), shared catalogues (product and pricing catalogues exposed exclusively to specific company accounts or groups of accounts), negotiated price lists (account-specific price books defined by the sales team and applied automatically when the company buyer logs in), purchase order workflow (buyer places order, it enters a pending approval state, designated approvers approve or reject it before it processes), and requisition lists (the B2B equivalent of wishlists saved product lists for quick reorder by buyers who replenish the same items regularly) are all native platform features rather than third-party extensions.
The Adobe Commerce B2B module's primary advantage is its maturity and native integration with the rest of the Magento platform promotions, product data, inventory, and order management all work consistently across B2B and B2C contexts on the same installation, enabling hybrid commerce models (a manufacturer operating both a D2C consumer storefront and a wholesale trade portal from the same Magento instance) that require significantly more integration effort on other platforms.
Company Account & Role Architecture
Adobe Commerce company account configuration company creation workflow (admin-created or self-registration with admin approval), company hierarchy (parent company with subsidiary companies, each with their own buyer accounts and purchasing authority), buyer role definition (roles controlling which storefront actions each buyer type can perform buyer can add to cart and view products but cannot checkout without manager approval; purchaser can checkout up to their authority limit; admin can manage company users and view all company orders), credit limit management (the maximum outstanding balance a company account can carry before new orders are blocked or flagged for credit review).
Shared Catalogues & Negotiated Pricing
Adobe Commerce shared catalogue implementation creating custom catalogues that expose a subset of the master product catalogue with account-specific pricing to specific company accounts or customer groups. Negotiated price list configuration for key accounts the sales team uploads a product-level price list for each account (price per SKU, optionally with quantity tier pricing), and the system applies the negotiated price automatically when that company's buyers are logged in and shopping. Shared catalogue pricing is independent of the standard tier pricing and catalog price rules that apply to other customer groups, enabling completely flexible per-account pricing without affecting other customers' pricing.
Purchase Order & Approval Workflow
Adobe Commerce purchase order workflow configuration purchase order creation when a buyer attempts to place an order (instead of direct order placement, a purchase order is created in pending-approval status), approval rule configuration (orders above ₹50,000 require manager approval; orders above ₹2,00,000 require director approval; all orders with delivery to a new address require admin approval), approver notification and approval/rejection action from the company account dashboard, automatic order processing when the final required approval is granted, and the PO number collection workflow that links the Magento order to the buyer's internal procurement system reference.
Requisition Lists & Quick Order
Adobe Commerce requisition list implementation buyer-maintained saved product lists for rapid reorder of regularly purchased items (the B2B equivalent of a standing order template). Multiple requisition lists per buyer (one for each product category or regular order type), add-to-requisition-list from the product page and from previous order history, add entire requisition list to cart for checkout. Quick Order the SKU-based order entry interface for experienced B2B buyers who know their product codes and prefer to enter SKU + quantity directly rather than browsing the catalogue. CSV order upload for buyers managing large orders in procurement software and exporting an order file.
Quote Management & Negotiation
Adobe Commerce quote negotiation workflow buyers can request a formal quote for a cart (submitting a proposed price and a note to the sales team), the sales team reviews and responds with a counter-offer or approved price from the admin, and the buyer accepts or re-negotiates before converting the approved quote to an order. Useful for large non-standard orders where the buyer expects to negotiate pricing, shipping terms, or payment terms before committing to the order. Quote expiry date management (quoted prices are valid until a defined date), quote comments thread (buyer and seller negotiate within a structured comment workflow), and PDF quote generation for orders that require a formal document for internal approval.
ERP & Procurement Integration
Adobe Commerce B2B integration with ERP and procurement systems bidirectional order sync (Magento purchase orders transmitted to SAP, Oracle, or Dynamics for fulfilment and invoicing; ERP-generated invoices pulled back into Magento for buyer-facing invoice download), real-time inventory availability from the ERP warehouse management system displayed in the shared catalogue and on product pages, credit limit synchronisation from the ERP accounts receivable module displayed in the buyer portal, and EDI (Electronic Data Interchange) integration for enterprise buyers that transmit purchase orders via EDI 850 and receive order acknowledgements via EDI 855 without logging into the portal.
Service 05
Headless Magento — PWA Studio, GraphQL & React Storefronts
Headless Adobe Commerce decoupling the customer-facing storefront from the Magento PHP backend and serving it via the Magento GraphQL API to a React or Next.js frontend is the path to the performance scores that Magento's traditional PHP-rendered theme architecture cannot reliably achieve. Magento's Luma theme consistently scores below 40 on Google PageSpeed Insights mobile; a well-built PWA Studio or Next.js headless frontend targeting the same backend can achieve scores above 90, with LCP under 1.5 seconds and sub-200ms INP. For brands where Magento is the right backend (complex B2B, complex product configuration, large catalogue, multi-store) but the frontend performance of traditional Magento theming is commercially unacceptable, headless Adobe Commerce is the architecture that combines Magento's backend power with modern frontend performance.
Adobe's own PWA Studio (using the Venia reference storefront) is the officially supported headless development framework for Adobe Commerce but many implementations use Next.js with the Magento GraphQL API directly, or third-party headless frameworks (Vue Storefront, Scandipwa) that provide a more mature component library at the cost of closer coupling to those frameworks' conventions.
PWA Studio & Venia Storefront
Adobe PWA Studio is the official React-based PWA framework for Adobe Commerce providing the Peregrine hooks library (React hooks for cart, checkout, product, and user management that abstract Magento GraphQL API calls), the Venia UI component library (pre-built React components for the most common storefront patterns), and the Buildpack build pipeline (Webpack configuration for optimal PWA output). Venia storefront customisation extending or replacing Venia components via the extensibility system (targetable components that can be wrapped, swapped, or have content injected without forking the source). PWA features: offline browsing of recently visited pages via service worker caching, add-to-home-screen for installed PWA experience on mobile.
Magento GraphQL API
Magento 2.3+ native GraphQL API covering the full storefront data requirements products, categories, cart, checkout, customer account, wishlist, order history, and CMS content. Custom GraphQL resolvers for business-specific data extensions exposing custom product attributes, custom customer data, and custom business logic through the GraphQL schema so the headless frontend can access all required data through a single API endpoint. GraphQL schema stitching for combining Magento's native schema with third-party service GraphQL APIs (a review service, a loyalty points API, a personalisation engine) in a unified GraphQL layer the frontend queries without knowing which backend system provides each data type.
Next.js Headless Storefront
Next.js App Router headless storefront with Magento GraphQL backend React Server Components for statically generated and incrementally regenerated product and category pages; Client Components for the interactive cart, checkout, and account experience; and Apollo Client or urql for GraphQL data fetching with normalised caching that minimises redundant API calls. Vercel deployment with ISR (Incremental Static Regeneration) for product pages product pages are statically generated at build time but can be regenerated on-demand when product data changes via Magento's webhooks. Edge caching for category and CMS pages with cache invalidation triggered by Magento admin publishing events.
Adobe App Builder & API Mesh
Adobe App Builder Adobe's serverless extensibility platform for building integrations and UI extensions for Adobe Commerce without modifying the Magento codebase. App Builder applications run in Adobe's cloud infrastructure (AIO Runtime, based on Apache OpenWhisk) and integrate with Magento via the Commerce Eventing framework and Admin UI SDK. API Mesh (Adobe's managed GraphQL gateway) combining the Magento GraphQL API with third-party GraphQL APIs (Algolia, Yotpo, Contentful, Bazaarvoice) into a single unified GraphQL endpoint that the PWA Studio or Next.js frontend queries. Eliminates the need to manage multiple API clients in the frontend and enables API-level caching and transformation.
Service 06
Adobe Commerce Integrations — ERP, CRM, WMS, 3PL & Marketing
Magento / Adobe Commerce's open REST and GraphQL APIs, its robust event system (observers for the full order lifecycle, product data changes, and customer events), and its native integration with Adobe Experience Cloud (Adobe Analytics, Adobe Target, Adobe Experience Manager, Marketo Engage) make it one of the most integrable commerce platforms in the enterprise market. For brands already invested in the Adobe Experience Cloud, Adobe Commerce's native integrations with Adobe Analytics for commerce event tracking, Adobe Target for A/B testing and personalisation, and Adobe Real-Time CDP for unified customer data are the integrations that justify the platform's licensing cost at enterprise scale.
Systems We Integrate with Adobe Commerce
Native Adobe integrations, certified Marketplace extensions, and custom connectors for the full enterprise commerce ecosystem
Service 07
Magento Performance Engineering & Security Hardening
Magento performance is the most frequently cited operational challenge for brands on the platform and with good reason. Magento's EAV database model produces some of the most complex SQL queries of any commerce platform; its full-page cache requires careful configuration to deliver high cache hit rates without serving stale price or inventory data; its JavaScript compilation pipeline (RequireJS bundling, Less compilation) adds complexity to the performance optimisation process that does not exist on simpler platforms; and its codebase, with hundreds of modules and thousands of PHP classes, produces a PHP bootstrap process that is meaningfully slower than a simpler PHP application without caching. But Magento's performance problems are diagnosable and fixable a properly configured Magento installation with Redis caching, Elasticsearch, Varnish or Fastly full-page cache, a CDN for static assets, and correct indexer configuration can achieve sub-2 second LCP for product and category pages and handle thousands of concurrent users without degradation.
Full-Page Cache & Varnish / Fastly
Magento full-page cache (FPC) configuration the caching layer that serves pre-rendered HTML pages to anonymous visitors without executing PHP or querying the database, producing the sub-200ms server response times that Magento cannot achieve with PHP rendering on every request. Varnish VCL configuration for self-hosted implementations (cache key structure, bypass rules for cart, checkout, and account pages, ESI configuration for the dynamic blocks within cached pages mini-cart, recently viewed, customer name that must be personalised even when the page skeleton is cached). Fastly configuration for Adobe Commerce Cloud implementations Fastly is Adobe Commerce Cloud's built-in CDN and FPC, and its Magento-specific VCL snippets must be correctly deployed and maintained as the platform is updated.
Database Performance & Indexers
Magento database performance the slow query log analysis for identifying EAV queries that are producing full table scans on large attribute sets, the indexer management that keeps Magento's flat catalogue tables (the denormalised view of the EAV product data that makes category and search queries fast) current with product data changes, and the indexer scheduling configuration (Update by Schedule vs. Update on Save) that prevents large reindexation jobs from blocking the front-end during peak hours. Magento's MSI (Multi-Source Inventory) indexer configuration for multi-warehouse stores. Database read replica configuration for separating read-heavy catalogue queries from write-heavy checkout and order processing.
JavaScript Optimisation & Compilation
Magento JavaScript performance RequireJS bundle configuration to reduce the number of separate JavaScript file requests (Magento's default unbundled state loads 50–100 separate JS files per page); JavaScript merging and minification in production mode; critical JavaScript identification and inline injection to prevent render-blocking; removing RequireJS modules loaded globally that are only needed on specific page types (checkout JS loaded on product pages, customer account JS loaded on all pages); and the JavaScript profiling with Chrome DevTools to identify which of Magento's UI components are the primary sources of TBT (Total Blocking Time) on product and category pages.
Security Hardening & Patch Management
Magento security is a continuous programme Adobe releases security patches for Magento 2 on a defined schedule (monthly security patches for critical vulnerabilities, quarterly security-focused releases), and stores running unpatched Magento versions are among the most commonly compromised e-commerce sites in the Magecart payment skimming attacks that affect thousands of Magento stores annually. Security hardening: Magento admin URL changed from the default /admin path, two-factor authentication enforced for all admin users, Content Security Policy (CSP) headers configured to prevent XSS and script injection attacks, file permissions audit, Magento Scan Tool audit, and the composer.lock file management that ensures third-party dependency versions are pinned and auditable.
Managed Updates & Maintenance
Adobe Commerce patch management service security patch assessment (evaluating the risk profile of each patch against the store's specific configuration and extension set before applying), patch application to a staging environment with regression testing of the checkout flow, payment processing, and B2B functionality, and production deployment during a low-traffic maintenance window with pre-update snapshot. Minor version upgrade management (Magento 2.4.x point release upgrades) including composer dependency resolution, extension compatibility verification, and the theme and module regression testing that identifies breaking changes. Adobe Commerce Cloud CLI deployment workflow management.
CRO & Conversion Engineering
Magento conversion rate optimisation Hotjar heatmap and session recording analysis for identifying Magento-specific friction (checkout step abandonment, layered navigation dead ends where filter combinations return zero products, product configurator confusion for complex configurable products), A/B testing via Adobe Target (native Adobe Commerce integration) or Google Optimize for product page and checkout layout variants, and the checkout flow simplification that Magento's complex default checkout makes necessary one-step checkout extension evaluation and implementation where the multi-step checkout is a measurable conversion barrier.
Service 08
Adobe Commerce Growth — SEO, Paid Ads, Email & Commerce Analytics
Magento's open-source architecture and complete URL control make it one of the strongest SEO platforms available with full control over URL structure, canonical tag implementation, hreflang for international multi-stores, structured data injection via PHTML templates, and the layered navigation URL management that prevents the duplicate content issues that faceted navigation creates on most platforms. Adobe Commerce's native integration with Adobe Analytics and Adobe Target gives brands invested in the Adobe Experience Cloud the most comprehensive analytics and personalisation capability available on any commerce platform, with the ability to define A/B tests and personalised experiences in Adobe Target and serve them to Magento store visitors without additional third-party integration overhead.
Magento-Specific SEO
Technical SEO for Adobe Commerce canonical tag configuration for layered navigation URLs (ensuring filtered category pages use canonical tags to avoid duplicate content penalties), XML sitemap configuration and submission (Magento's built-in sitemap generator configured with correct update frequencies and inclusion rules), URL key management and redirect handling for catalogue changes, category URL rewrites, and the schema.org Product JSON-LD implementation injected via PHTML template for Google rich result eligibility across the product catalogue.
Google Shopping & Performance Max
Magento product feed for Google Merchant Center via Feedonomics, DataFeedWatch, or the Magento Google Shopping extension attribute mapping from Magento's product data structure (configurable products sending parent + child variant data, custom attribute mapping to Google's required attributes), title keyword enrichment from Google Search Console query data, GTIN and MPN from custom product attributes, custom label configuration for campaign segmentation by margin, clearance status, and season. Performance Max campaign management with product-level ROAS targets by category.
Meta Dynamic Product Ads
Magento product catalogue integration with Meta Commerce Manager automated product feed sync via Magento's Meta extension or a third-party feed management tool, pixel implementation via GTM with Magento data layer integration for ViewContent, AddToCart, InitiateCheckout, and Purchase events, Conversions API (CAPI) server-side event deduplication using Magento webhooks, and Advantage+ Shopping Campaigns with Magento catalogue as the product source. Custom audience creation from Magento customer segments for retargeting and lookalike expansion.
Klaviyo & Email Automation
Klaviyo integration with Adobe Commerce via the official Klaviyo extension syncing Magento customers, orders, product catalogue, and event data (Added to Cart, Started Checkout, Placed Order, Fulfilled Order, Cancelled Order) to Klaviyo for the full e-commerce flow set: welcome series, abandoned cart recovery, post-purchase cross-sell, back-in-stock alerts, replenishment reminders, B2B re-engagement for dormant trade accounts, and win-back for lapsed D2C customers. For Adobe Experience Cloud clients: Marketo Engage integration via the Magento Marketo extension for B2B lead nurture triggered by B2B Commerce quote and company account events.
Adobe Target Personalisation
Adobe Target integration with Adobe Commerce for server-side and client-side A/B testing and personalisation product page variant testing (hero image, value proposition framing, review placement), checkout experience variant testing (one-step vs. two-step, field count reduction), and customer segment-based personalisation (returning VIP customers see a different homepage hero than new visitors, based on their Adobe Real-Time CDP segment membership). Auto-Allocate and Auto-Target for traffic allocation optimisation that moves beyond simple 50/50 splits as statistical evidence accumulates.
Analytics & Commerce Intelligence
Adobe Analytics implementation for Adobe Commerce via the Adobe Commerce Integration (native) product impression, click, add to cart, checkout, and purchase events with the full product data layer required for Adobe Analytics e-commerce reports. For non-Adobe Analytics clients: GA4 enhanced e-commerce via GTM with Magento's data layer. Adobe Commerce Reporting (the rebuilt Magento Business Intelligence) for cohort analysis, LTV modelling, and revenue attribution dashboards that connect Magento order data with marketing channel data. Magento's native sales reports and custom AdminHTML grid reports for operational teams.
Adobe Commerce by Industry
Adobe Commerce's configurability makes it the platform of choice for industries and use cases where standard SaaS commerce platforms impose constraints that the business cannot accept.
- Multi-dimensional configurable products (colour × size × length × wash) with correct inventory per SKU
- Swatch-based variant selectors via Visual Swatch attribute type for colour and pattern options
- Adobe Page Builder lookbook and editorial collection pages managed by merchandising team
- B2B wholesale portal with shared catalogue and negotiated pricing for retail buyers
- Multi-store architecture for sub-brand storefronts sharing a single product catalogue
- Headless PWA Studio for performance-first mobile experience on high-traffic collections
- Adobe Commerce B2B company accounts, shared catalogues, purchase order workflow
- SAP S/4HANA or Oracle ERP bidirectional integration for real-time pricing and inventory
- Configurable product with real-time price calculation from material, dimension, and finish options
- EDI integration for enterprise buyers submitting purchase orders without portal login
- Multi-website architecture D2C consumer store and B2B trade portal on same instance
- Requisition lists and CSV quick order for high-frequency replenishment buyers
- Complex product attribute sets with compatibility filtering (component compatibility by model)
- Bundle product type for custom configuration (choose processor, RAM, storage combinations)
- Tiered pricing for quantity breaks in component purchasing for business buyers
- Extended warranty add-on as virtual product upsell at product page and cart
- Real-time inventory from warehouse management system via MSI (Multi-Source Inventory)
- B2B government and enterprise procurement portal with PO and net payment terms
- Product-level prescription requirement gating requiring uploaded prescription before checkout
- AYUSH and drug regulatory compliance for health claims displayed on product pages
- Age verification gate and adult-content modal for regulated health products
- B2B distribution portal for pharmacy chains and hospital procurement with volume pricing
- Cold chain shipping module enforcing carrier eligibility by product temperature requirement
- Batch and expiry date tracking via custom product attributes and ERP integration
- Postcode-based delivery slot booking with calendar picker in checkout
- FSSAI nutritional information, allergen labelling, and best-before date per product
- Weight-based pricing and variable-weight product management (price per kg)
- Delivery zone management with minimum order value and delivery charge per zone
- Subscription boxes with customisable contents and flexible delivery frequency
- Multi-vendor marketplace for local food brands with per-vendor fulfilment routing
- Vehicle compatibility filter make/model/year fitment data integrated with layered navigation
- Parts finder widget on the homepage enabling shoppers to filter by their vehicle before browsing
- Complex attribute sets for technical specification data (OEM part number, compatibility list)
- B2B workshop and dealer portal with trade pricing and bulk ordering capability
- ERP integration for real-time parts availability across multiple warehouse locations
- Core charge management for reman parts with returnable core deposit at checkout
Latest from SourceMash
Perspectives, research, and practical guidance from our enterprise technology experts.
What Our Adobe Commerce Clients Say
We had been on Magento 1 since 2013 which means we were running a nine-year-old, officially end-of-life platform with no security patches being released by the vendor, a PageSpeed score of 22, and a checkout that broke every third month because one of our 40 installed extensions had a conflict with another. We had delayed the Magento 2 migration for five years because every agency we spoke to quoted us 18–24 months and a budget that felt impossible to justify. SourceMash scoped the project differently they identified that we had three brand websites running on the same M1 instance that could all be migrated simultaneously to a multi-store M2 setup rather than three separate migration projects. They managed the data migration tool for catalogue and customer data, rebuilt our five custom M1 extensions as proper M2 modules, and handled the redirect mapping for 85,000 URLs across three domains. We went live in 22 weeks with zero organic traffic loss our GSC data shows the same keyword rankings the week after migration as the week before. PageSpeed is now 78. And we are on a properly supported, patchable platform for the first time in years.
We chose Adobe Commerce for our B2B distribution portal because our pricing model is genuinely complex we have 240 trade customers, each with negotiated prices for their specific mix of products, and within each account we have volume break pricing that applies different discounts at different quantity thresholds per product category. No Shopify app or WooCommerce plugin could handle this without creating a maintenance nightmare. The Adobe Commerce B2B module with Shared Catalogues and Negotiated Prices handled the pricing architecture natively once SourceMash configured it correctly. The SAP S/4HANA integration they built pulls real-time inventory from our three warehouses and pushes every online purchase order to SAP without any manual intervention. ₹95 crore of online B2B orders in the first year. Our sales team spends their time winning new accounts. Our accounts team no longer has to manually enter orders. The ROI calculation was positive at month four.
Our Magento 2 store had a PageSpeed score of 28 on mobile. We had had three previous agencies tell us that this was expected for Magento and that we should just accept that Magento is a slow platform. SourceMash's performance audit disagreed and they had the diagnostic evidence. The problems were specific and fixable: our Varnish FPC had never been correctly configured so every anonymous visitor was getting a PHP-rendered response; we had RequireJS loading 73 separate JavaScript files on every product page; our images were being served at desktop sizes to mobile visitors; and our Redis installation was there but not actually being used for the right cache types. The performance engineering programme took 10 weeks. PageSpeed is now 91 on mobile. LCP is 1.6 seconds. The Core Web Vitals improvement recovered Google organic positions we had been losing to competitors for 18 months organic traffic is up 62% year-on-year. Conversion rate improved 2.4 percentage points on the same traffic. The headless PWA Studio storefront we built simultaneously is now serving as the mobile and home page experience while SFRA handles the long-tail category pages a hybrid approach that got us most of the headless performance benefit at significantly lower cost than a full replatform.