Adobe Commerce Guide 2026: Features, Pricing & Platform Comparison
[Updated: January 29, 2026]
Adobe Commerce offers powerful B2B and B2C capabilities with deep customization. Pricing is quote-based and not publicly disclosed. This guide covers realistic pricing expectations, AI features, and comparisons with Shopify Plus and BigCommerce for 2026.
What is Adobe Commerce?
Adobe Commerce (formerly Magento) = Enterprise ecommerce platform for complex B2B and B2C operations. Offers extensive customization but requires significant investment.
Perfect for: Businesses with $5M+ revenue, complex B2B requirements, multi-brand operations, companies needing deep customization.
Not ideal for: Startups, businesses under $1M revenue, teams without technical resources, companies needing quick time-to-market.
Adobe Commerce is the enterprise tier of the Magento platform, acquired by Adobe in 2018. It integrates with Adobe Experience Cloud for advanced personalization, analytics, and content management.
The platform comes in two editions:
- Adobe Commerce (On-Premises): You host and manage the infrastructure
- Adobe Commerce Cloud: Adobe-managed PaaS with automatic scaling and updates
Adobe Commerce Market Position
Adobe Commerce is a leading enterprise ecommerce platform, though exact market statistics are difficult to verify.
| Metric | Estimate | Source & Notes |
|---|---|---|
| Live Storefronts (all Magento) | ~116,000 | Store Leads Q1 2026 (includes Open Source) |
| Total Detected (incl. inactive) | ~153,000+ | BuiltWith Trends Jan 2026 (includes Open Source) |
Critical Context: These numbers include both Adobe Commerce (paid) and Magento Open Source (free). Adobe Commerce (the paid enterprise edition) represents only a fraction of this total; exact breakdown is not publicly available. The majority are Magento Open Source installations.
Adobe does not publish official platform statistics for active Adobe Commerce (paid) stores or GMV. Third-party estimates aggregate all Magento installations without clear differentiation between paid and free versions.
Geographic Distribution (estimated): North America (~34%), Europe/Middle East (~31%), Asia-Pacific (~24%), Latin America (~8%).
Adobe Commerce Pricing 2026
Adobe Commerce pricing is strictly quote-based. Adobe does not publish pricing information publicly. Pricing depends on:
- Gross Merchandise Value (GMV)
- Average Order Value (AOV)
- Transaction volume
- Required features and integrations
- Business size and complexity
No public pricing is available from Adobe: neither ranges nor estimates. Contact Adobe directly for customized quotes.
Traditional Licensing (PaaS/On-Premises)
Traditional Adobe Commerce is available as:
- PaaS (Platform as a Service): Adobe-managed infrastructure with scaling and updates
- On-Premises: Self-hosted infrastructure you manage
Pricing: Quote-based only. Adobe does not disclose pricing publicly. Pricing varies significantly based on GMV, business requirements, and negotiation.
Adobe Commerce as a Cloud Service (ACCS) - Since June 2025
ACCS is Adobe's multi-tenant SaaS offering:
- Tiered SaaS model: Based on GMV, transaction volume, and feature access
- Pricing: Quote-based; no public pricing available
- Potential benefits: Managed infrastructure may reduce operational overhead for businesses fitting standard tiers
- Trade-off: Reduced customization flexibility compared to PaaS/On-Premises
(Source: Adobe Business Blog, June 2025; Adobe Commerce Product Pages)
Recommendation: Contact Adobe directly to compare pricing between Traditional (PaaS/On-Prem) and ACCS based on your specific requirements.
Total Cost of Ownership Factors
License fees are the starting point. Budget for:
- Implementation: Costs vary significantly by project complexity, business size, and customization requirements. Consult implementation partners for quotes.
- Extensions: Variable; complex integrations add substantial cost
- Ongoing maintenance: Security patches, updates, support contracts
- Hosting: (On-Premises) Infrastructure, scaling, monitoring; (ACCS) included in license
- AEP Integration: Significant additional cost if using advanced AI/personalization features
Note on TCO: Total cost of ownership varies widely based on business requirements, customization needs, and chosen deployment model (PaaS/On-Prem vs. ACCS). Multi-tenant SaaS (ACCS) may reduce infrastructure costs but limits customization. Request detailed quotes from Adobe and implementation partners to understand full TCO for your specific situation.
Key Features of Adobe Commerce
1. B2B and B2C Unified Platform
Adobe Commerce is a unified commerce solution that handles both business models from a single installation:
B2B Features:
- Custom pricing per customer/company
- Quote negotiation workflows
- Purchase approval processes
- Company account hierarchies
- Bulk ordering and quick order forms
- Requisition lists and shared catalogs
B2C Features:
- Personalized shopping experiences with dynamic content
- Multiple payment gateways
- Seamless checkout optimization
- Customer segmentation for targeted campaigns
- Loyalty program integration
2. AI-Powered Features (Adobe Sensei)
Adobe Sensei powers search and recommendation features in Adobe Commerce:
Live Search:
- Real-time search results as customers type
- Learns from customer behavior to improve relevance
- Handles spelling mistakes and synonyms
- Merchandising rules for promotional products
Product Recommendations:
- "Customers also bought" suggestions
- Personalized "Recommended for you" sections
- Trending and recently viewed products
- Visual similarity recommendations (computer vision)
Sensei GenAI (2025-2026):
Sensei GenAI is available for Product Recommendations and Content Generation assistance within Adobe Commerce. Implementation requires setup, configuration, and potentially additional licensing costs depending on usage and deployment.
Agentic AI Status (2026):
Agentic AI capabilities (autonomous pricing updates, automated content tagging, self-learning task automation) are not natively available in Adobe Commerce. These features require a separate Adobe Experience Platform (AEP) license and AEP Agent Orchestrator access.
Critical limitation for Adobe Commerce: Commerce-specific autonomous features are entirely AEP-dependent. Without AEP integration, Adobe Commerce does not offer production-ready agentic AI capabilities. You're limited to Sensei-powered Live Search and Product Recommendations.
Cost implications: To leverage agentic AI for Commerce in 2026, you need:
- Adobe Commerce license (quote-based, not publicly disclosed)
- Adobe Experience Platform license (significant additional cost, often matching or exceeding Commerce license fees)
- AEP Agent Orchestrator access (included in AEP but requires setup and integration)
Total AI stack cost: Combining Adobe Commerce with AEP for agentic AI can double or triple your total Adobe software investment compared to Commerce alone.
(Source: Adobe AI Documentation, Experience League 2026)
3. Multi-Store Management
Manage multiple brands, regions, and currencies from one admin panel:
- Unlimited store views per installation
- Separate catalogs per store or shared inventory
- Currency and language localization
- Region-specific pricing and tax rules
- Centralized order management
4. Page Builder
Create and edit pages without developer assistance:
- Drag-and-drop content blocks
- Pre-built templates for common layouts
- Real-time preview across devices
- Content staging and scheduling
- No coding required for basic changes
5. Scalability
Adobe Commerce handles enterprise-scale operations:
- Supports catalogs from 20 to 500,000+ SKUs
- Handles thousands of concurrent users
- Auto-scaling available on Cloud edition
- Performance optimized for high-traffic events
Adobe Commerce vs Shopify Plus vs BigCommerce (2026)
| Factor | Adobe Commerce | Shopify Plus | BigCommerce Enterprise |
|---|---|---|---|
| Annual License | Quote-based (traditional PaaS/On-Prem); ACCS tiered SaaS | $24k - $28k | Variable (quote-based) |
| Setup Time | 4-12 months | 2-8 weeks | 2-4 months |
| Customization | Extensive (PaaS/On-Prem); Moderate (ACCS) | Limited | Moderate (Open SaaS) |
| B2B Features | Excellent | Basic | Good |
| Technical Skill Required | High | Low | Medium |
| Transaction Fees | None | 2% (3rd party) | None |
| App Ecosystem | 4,000+ | 13,000+ | 1,200+ |
TCO Comparison (3 years):
- Adobe Commerce (PaaS/On-Prem): Typically highest TCO due to development, customization, and maintenance. Shopify Plus TCO often 30-50% lower for simpler setups.
- Adobe Commerce (ACCS): May reduce TCO compared to traditional Adobe Commerce due to managed infrastructure, but still higher than Shopify Plus for most use cases.
- Trade-off: For businesses requiring deep customization and complex B2B workflows, Adobe's flexibility (PaaS/On-Prem) may justify the investment. ACCS offers a middle ground with lower infrastructure costs but limited customization.
(Sources: OnTap, Qualimero 2026; ACCS estimates based on June 2025+ data)
When to Choose Adobe Commerce
- Revenue exceeds $5M annually
- Complex B2B requirements (custom pricing, approvals)
- Need extensive customization
- Multi-brand or multi-region operations
- Already using Adobe Experience Cloud
- Have technical team or agency partnership
When to Choose Alternatives
Shopify Plus: Fast time-to-market, simpler operations, DTC brands BigCommerce: Mid-market B2B, no transaction fees, moderate customization needs
Security & Upgrade Best Practices 2026
Keeping Adobe Commerce secure requires ongoing vigilance.
Patch Schedule (January 2026 Changes)
Adobe now releases monthly isolated security patches (security fixes only, no quality/feature updates). Annual full patches continue in May with comprehensive updates.
- Apply isolated security patches monthly
- Plan for annual May full patch releases
- Monitor Adobe Security Bulletin for critical updates
Version Recommendations
| Version | Support Ends | Recommendation |
|---|---|---|
| 2.4.8 | April 11, 2028 | Recommended for new projects |
| 2.4.7 | April 9, 2027 | Supported; plan upgrade to 2.4.8 |
| 2.4.6 | August 11, 2026 | Upgrade urgently |
| 2.4.5 | Not supported since 2026 | Upgrade immediately (no longer supported) |
(Source: Adobe Experience League Lifecycle Policy, January 2026)
PHP Requirements
| Adobe Commerce Version | PHP Requirement |
|---|---|
| 2.4.7 | PHP 8.3 only (production) |
| 2.4.8 | PHP 8.3 or 8.4 required |
Critical Warning: PHP 8.2 reached end of life in December 2025 and no longer receives security updates. For 2.4.7: use PHP 8.3 exclusively in production. PHP 8.2 is only tolerated for upgrade purposes and must not be used in production environments. For new projects, use 2.4.8 with PHP 8.3 or 8.4.
(Source: Adobe System Requirements, January 2026)
Security Hardening 2026
Monthly Security Patches (since January 2026):
- Apply isolated security-only patches monthly (non-cumulative)
- Annual full patches in May include quality and feature updates
- Monitor Adobe Security Bulletin for critical vulnerabilities
Composer & Dependencies:
- Keep Composer at version 2.9+ (supported in Adobe Commerce 2.4.7/2.4.8+ as of January 2026)
- Regularly update vendor packages via
composer update - Review
composer.lockfor known vulnerabilities
Essential Security Measures:
- Enforce 2FA: Two-factor authentication for all admin users (mandatory)
- IP Whitelisting: Restrict admin access to known IP addresses
- Web Application Firewall (WAF): Block SQL injection, XSS, and automated attacks
- Bot Management: Protect against credential stuffing and DDoS
- Content Security Policy (CSP v3): Enforce strict CSP headers to prevent XSS
-
Custom admin path: Adobe recommends using a unique Admin URL instead of the default
/adminas a security best practice (Adobe Security Docs 2026). While this is "security by obscurity" and provides minimal protection against modern attacks, it should be combined with 2FA, WAF, and IP whitelisting.
Search Engine Requirements
- 2.4.7 and earlier: OpenSearch 2.x or Elasticsearch 8.x (Elasticsearch deprecated)
- 2.4.8+: OpenSearch 2.x only (Elasticsearch removed and no longer compatible)
Important: Elasticsearch support was fully deprecated and removed in Adobe Commerce 2.4.8 (released April 2025). If you're currently using Elasticsearch, you must migrate to OpenSearch before upgrading to 2.4.8. Adobe Commerce is now optimized for OpenSearch 2.19+.
(Source: Adobe Commerce 2.4.8 Release Notes, August 2025)
Performance Best Practices
- Consider Hyvä frontend: Modern, lightweight theme with better Core Web Vitals than default Luma
- Enable full-page cache: Varnish or built-in cache
- Use Valkey or Redis: For session and cache storage (Valkey 8.x is the Redis fork recommended for new projects)
- CDN integration: Distribute static assets globally
- Choose the right hosting: Performance depends heavily on your hosting infrastructure and provider
Database & Infrastructure Best Practices 2026
Database Requirements:
- MariaDB 11.4 or MySQL 8.4 (default for 2.4.8)
- Default collation: utf8mb4 (required for full Unicode support)
- Foreign key constraints: MySQL 8.4 enforces stricter foreign key restrictions; test thoroughly before upgrading
Session & Cache Storage:
- Valkey 8.x (recommended Redis fork) or Redis 7.x
- Use separate instances for session storage and cache
- Configure persistent connections for better performance
Adobe Commerce 2026 Roadmap
Release Schedule
Starting January 2026:
- Monthly: Isolated security patches (security fixes only)
- Annually (May): Full patches with quality and feature updates
- Support window: 3 years per major version
Upcoming Developments
| Feature | Status | Description |
|---|---|---|
| Real-time AEP Integration | 2026 | Native data sharing with Adobe Experience Platform |
| App Builder Database | H1 2026 | Managed document DB for extensions |
| Commerce as a Cloud Service (ACCS) | Expanding | Multi-tenant SaaS architecture (since June 2025) |
ACCS Multi-Tenant Limitations:
While ACCS offers potential cost savings and managed infrastructure, the multi-tenant SaaS architecture has trade-offs compared to PaaS or On-Premises:
- Reduced customization flexibility: Shared infrastructure limits deep custom integrations
- Extension compatibility: Some third-party extensions may not be compatible with multi-tenant constraints
- Deployment control: Limited control over deployment timing and infrastructure configuration
Recommendation: For complex B2B requirements or extensive customizations, evaluate whether PaaS or On-Premises better suits your needs before committing to ACCS.
Support Timeline
| Version | Regular Support Ends | Notes |
|---|---|---|
| 2.4.8 | April 11, 2028 | Current recommended version |
| 2.4.7 | April 9, 2027 | Plan upgrade |
| 2.4.6 | August 11, 2026 | Urgent upgrade needed |
(Source: Adobe Experience League, January 2026)
Upgrade Path 2026
Planning an upgrade? Use this matrix to identify your required PHP and database versions.
| Adobe Commerce Version | Support Ends | PHP Requirements | Database Requirements | Search Engine |
|---|---|---|---|---|
| 2.4.8 | April 11, 2028 | PHP 8.3 or 8.4 | MySQL 8.4 / MariaDB 11.4 | OpenSearch 2.x only |
| 2.4.7 | April 9, 2027 | PHP 8.3 (production) | MySQL 8.0 / MariaDB 10.6 | OpenSearch 2.x or Elasticsearch 8.x (deprecated) |
| 2.4.6 | August 11, 2026 | PHP 8.1 or 8.2 | MySQL 8.0 / MariaDB 10.6 | OpenSearch 1.2 or Elasticsearch 7.17 |
| 2.4.5 | Not supported since 2026 | PHP 8.1 | MySQL 8.0 / MariaDB 10.4 | OpenSearch 1.2 or Elasticsearch 7.17 |
Key Upgrade Considerations:
-
From 2.4.6 or earlier → 2.4.8:
- Upgrade PHP to 8.3 or 8.4
- Migrate to MySQL 8.4 or MariaDB 11.4
- Migrate from Elasticsearch to OpenSearch (Elasticsearch removed in 2.4.8)
- Test thoroughly due to multiple breaking changes
-
From 2.4.7 → 2.4.8:
- Upgrade PHP to 8.3 or 8.4 if using 8.3
- Consider upgrading to MySQL 8.4 / MariaDB 11.4 (recommended, not required)
- Migrate from Elasticsearch to OpenSearch if still using Elasticsearch
-
From 2.4.5 or earlier:
- Upgrade urgently (no longer supported)
- Plan for multi-step upgrade (2.4.5 → 2.4.6 → 2.4.7 → 2.4.8 for large projects)
- Budget for extensive testing and potential refactoring
(Source: Adobe Experience League Lifecycle Policy, January 2026)
Adobe Commerce Features by Function
Marketing & Personalization
- Storefront design customization
- Product recommendations (AI-powered, requires setup)
- Promotions, coupons, and cart rules
- Abandoned cart recovery
- Customer reviews and ratings
- SEO tools (sitemaps, meta tags, URL rewrites)
- Note: Meta keywords have zero SEO impact (Google ignores them since 2009)
- Title optimization: Keep meta titles 55-65 characters (~580-620 pixels depending on device) to avoid truncation in SERPs
- A/B testing capabilities
Product Catalog
- Unlimited products and categories
- Configurable, bundled, and virtual products
- Advanced product search and filtering
- Content staging for scheduled updates
- Adobe Experience Manager integration (additional license)
- Digital asset management
Order Management
- Streamlined checkout process
- Multiple shipping carriers
- Tax calculation and display
- Payment gateway integrations (100+)
- Order tracking and status updates
- Returns and refunds management
- Inventory management across sources
Headless Commerce
- Decoupled frontend architecture
- REST and GraphQL APIs
- PWA Studio for progressive web apps
- Data orchestration layer
- Extensibility framework
Who Should Use Adobe Commerce?
Ideal Customers
| Business Type | Why Adobe Commerce |
|---|---|
| Enterprise B2B | Custom pricing, approval workflows, company accounts |
| Multi-brand Retailers | Single platform for multiple storefronts |
| International Operations | Multi-currency, multi-language, tax compliance |
| High-volume Merchants | Scalability, performance optimization |
| Adobe Ecosystem Users | Native integrations with AEM, Analytics, Target |
Not Recommended For
| Business Type | Better Alternative |
|---|---|
| Startups under $1M revenue | Shopify, WooCommerce |
| Simple D2C operations | Shopify Plus |
| Limited technical resources | BigCommerce, Shopify |
| Need launch in weeks | Shopify Plus |
| Budget under $50k/year | Open source alternatives |
Implementation Considerations
Timeline Expectations
| Phase | Duration | Activities |
|---|---|---|
| Discovery | 2-4 weeks | Requirements, architecture planning |
| Design | 4-8 weeks | UX/UI, theme development |
| Development | 8-16 weeks | Custom features, integrations |
| Testing | 2-4 weeks | QA, performance, security |
| Launch | 1-2 weeks | Migration, go-live |
Total: 4-8 months typical; complex B2B implementations can exceed 12 months.
System Requirements (2.4.8)
| Component | Requirement |
|---|---|
| PHP | 8.3 or 8.4 |
| Database | MySQL 8.4 or MariaDB 11.4 |
| Search | OpenSearch 2.x |
| RAM | 32GB+ recommended |
| Storage | SSD 500GB+ |
(Source: Adobe System Requirements, January 2026)
FAQs
1. How much does Adobe Commerce cost per year?
Adobe Commerce pricing is strictly quote-based and not publicly disclosed by Adobe. Pricing varies significantly based on GMV (Gross Merchandise Value), transaction volume, business size, and required features. Both Traditional (PaaS/On-Premises) and Adobe Commerce as a Cloud Service (ACCS, since June 2025) are quote-based. Total cost of ownership (including implementation, extensions, and ongoing maintenance) varies widely by project complexity. Contact Adobe directly for customized 2026 pricing quotes.
2. What is the difference between Adobe Commerce and Magento Open Source?
Magento Open Source is the free, community version with basic ecommerce features. Adobe Commerce adds B2B functionality, Page Builder, advanced reporting, customer segmentation, and Adobe support. Adobe Commerce Cloud includes managed hosting.
3. Is Adobe Commerce suitable for small businesses?
Adobe Commerce is designed for mid-market to enterprise businesses, $5M+ annual revenue. Small businesses often find the costs and complexity prohibitive. Shopify, WooCommerce, or BigCommerce are more appropriate for smaller operations.
4. How long does it take to implement Adobe Commerce?
Typical implementations take 4-8 months. Simple storefronts may launch in 3-4 months; complex B2B implementations can exceed 12 months. Shopify Plus implementations often complete in 4-8 weeks.
5. What AI features does Adobe Commerce include?
Adobe Commerce includes Sensei-powered Live Search and Product Recommendations. Sensei GenAI assists with recommendations and content generation, but requires setup, configuration, and potentially additional licensing costs. Agentic AI (autonomous pricing, automated tagging) is not natively available in Commerce. It requires a separate Adobe Experience Platform (AEP) license and AEP Agent Orchestrator. This can double or triple your total Adobe software investment. Without AEP, Commerce does not offer production-ready agentic AI.
6. Can Adobe Commerce handle B2B and B2C on the same platform?
Yes. Adobe Commerce natively supports both from a single installation. B2B features include custom pricing, quote negotiation, approval workflows, and shared catalogs. B2C includes personalized promotions and streamlined checkout.
7. What PHP version does Adobe Commerce require?
For 2.4.7: PHP 8.3 only in production (PHP 8.2 reached EOL December 2025 and is tolerated only for upgrade purposes, forbidden in production). For 2.4.8: PHP 8.3 or 8.4 required. New projects should use 2.4.8 with PHP 8.3 or 8.4.
8. How does Adobe Commerce compare to Shopify Plus?
Adobe Commerce (PaaS/On-Prem) offers extensive customization and superior B2B features but has higher TCO and longer implementation. Adobe Commerce as a Cloud Service (ACCS) may reduce TCO but limits customization. Shopify Plus provides faster time-to-market and 30-50% lower TCO for most use cases. Choose Adobe PaaS/On-Prem for complex B2B with deep customization; ACCS for managed infrastructure with moderate customization; Shopify Plus for speed and simplicity.
9. What did Adobe Commerce used to be called?
Adobe Commerce was formerly known as Magento Commerce. Adobe acquired Magento in 2018 for $1.68 billion and rebranded it to Adobe Commerce in 2021. The free, open-source version remains named "Magento Open Source."
Summary
Adobe Commerce is a powerful enterprise ecommerce platform for businesses requiring complex B2B functionality, extensive customization, and multi-brand operations.
Key considerations for 2026:
- Pricing: Quote-based, not publicly disclosed; ACCS (SaaS since June 2025) may reduce TCO vs. traditional PaaS/On-Prem but limits customization
- Version: Use 2.4.8 with PHP 8.3 or 8.4 (PHP 8.3 only for 2.4.7 (PHP 8.2 EOL and forbidden in production))
- Search: Elasticsearch removed in 2.4.8. Migrate to OpenSearch 2.x before upgrading
- Security: Monthly isolated patches (Jan 2026+), enforce 2FA, WAF, Bot Management, CSP v3, Composer 2.9+, custom admin path (Adobe best practice)
- AI Features: Sensei for search/recommendations (requires setup/config); agentic AI requires separate AEP license (can double/triple total cost)
- Infrastructure: Use Valkey/Redis, MariaDB 11.4/MySQL 8.4, utf8mb4 collation
- Alternatives: Shopify Plus offers lower TCO and faster time-to-market for simpler requirements
For businesses with $5M+ revenue and complex B2B requirements, Adobe Commerce (PaaS/On-Prem) provides the flexibility to support long-term growth. Evaluate ACCS for managed infrastructure with moderate customization needs. Consider Shopify Plus or BigCommerce for simpler operations and lower TCO.
