Adobe Commerce Features: What the Platform Actually Ships

Feature lists are where commerce platforms all sound identical — every vendor has "powerful catalog management" and "seamless integrations." This tour of Adobe Commerce is different: it walks the features that actually carry implementations, with a practitioner's notes on where each earns its keep and where discipline decides whether it delivers.

The catalog engine: the foundation everything stands on

Commerce's catalog is the platform's center of gravity, and its depth is what complex merchants are actually buying:

• Attribute architecture — unlimited attributes and attribute sets, driving layered navigation, search facets and merchandising rules; design this well and everything downstream inherits the order
• Product types — simple, configurable, bundle, grouped, virtual, downloadable — modeling real assortments without workarounds
• Price rules — catalog and cart rules composing promotions, tier pricing and customer-group pricing into governed logic
• Multi-store — one instance, many websites/stores/views: brands, regions and currencies sharing services while separating what must separate

Implementation note from years of Commerce builds: catalog architecture is the decision you live with longest. Attribute sprawl and product-type misuse are the technical debt we most often find in audits — the feature is deep, but it rewards design and punishes improvisation.

B2B: the machinery, briefly

The B2B suite — company accounts, buyer roles, shared catalogs with negotiated pricing, quotes, requisition lists, approval workflows — is native platform machinery and the sharpest differentiator against SaaS rivals. It gets a dedicated deep-dive; here the point is simply that these are not apps bolted on but first-class features sharing the catalog, pricing and customer foundations.

Content and merchandising: Page Builder and staging

Page Builder gives merchandisers drag-and-drop control over content — landing pages, category content, promotional blocks — without developer tickets. Content staging and preview lets teams schedule campaigns (prices, content, promotions) and preview the future site before it goes live: the operational feature that turns holiday-season chaos into a calendar. Enterprises pairing Commerce with AEM push content operations further still, with Commerce owning transaction surfaces and AEM owning brand storytelling.

AI-driven discovery: Live Search and Product Recommendations

Both ship with Commerce and learn from shopper behavior automatically. The practitioner's note: they are starting points that reward tuning — search merchandising rules aligned to margin priorities, rec placements tested rather than sprayed. Deployed thoughtfully, they replace a third-party search/rec stack and its integration tax.

Headless and extensibility: the modern architecture

Three pieces define modern Commerce builds:

1. GraphQL APIs — full storefront coverage for headless front ends, decoupling storefront releases from the commerce core
2. API Mesh — orchestration layer combining Commerce with other services (ERP, PIM, CMS) into one queryable graph for the front end
3. App Builder — serverless extensions running outside the core against APIs and events, so customizations survive upgrades instead of blocking them

Together they answer the platform's historical criticism — that deep customization made upgrades painful. The modern pattern keeps the core clean and pushes bespoke logic to the edges; implementations that follow it upgrade routinely, while those that recreate 2015-era core hacking recreate 2015-era pain.

Operations: performance, deployment, scale

Commerce on Adobe's cloud infrastructure brings managed hosting, environments and deployment pipelines; performance work centers on caching architecture (full-page cache, Varnish), asset delivery and peak-readiness testing — unglamorous engineering that decides Black Friday. The honest operational note: this platform is run, not just used. Budget the running — in-house platform engineering or a managed service — as part of the feature set, because uptime and speed are features shoppers experience more directly than any capability on this page.

Integration surface: where Commerce meets the stack

Commerce's enterprise value multiplies at its edges: ERP and OMS integrations for inventory and order truth, PIM feeds for catalog governance, Analytics for measurement, RTCDP audiences for personalization, payment and tax services for compliance. Integration count is the honest predictor of implementation scope — the storefront is the visible tenth; the connective tissue is the project.

Reading a feature list like a practitioner

Three questions turn any feature checkbox into a real evaluation: Does our selling model need it? (B2B machinery matters enormously or not at all), Who will operate it? (Live Search tuning, staging calendars and price rules all want owners), and What does it replace? (native search/recs/B2B versus a stack of point solutions is a real economic comparison). Commerce's feature depth is genuine — the Shopify comparison shows where it decides evaluations — but depth converts to value only through architecture and operation.

For a feature-by-feature mapping against your actual requirements — or an audit of how much licensed capability your current implementation leaves unused — talk to a consultant. Pricing drivers live in the pricing guide.