Adobe Commerce Business Practitioner Expert cheat sheet
Adobe Commerce Business Practitioner Expert · Keep the key ideas within reach.
Commerce Architecture and Platform Fundamentals
Adobe Commerce uses a three-tier logical model: presentation (storefront/theme), application (modules in app/code and vendor), and data (MySQL plus Redis/Varnish/Elasticsearch or OpenSearch).
Configuration scope hierarchy from broadest to narrowest is Default Config, Website, Store, Store View; a value set at a narrower scope overrides broader scopes unless the field is locked.
Websites map to distinct domains or brands, stores group catalog roots and root categories, and store views control locale and currency presentation for a single store.
Magento Open Source and Adobe Commerce share the same codebase core; Adobe Commerce adds cloud hosting, B2B, staging/production, and advanced marketing modules.
Indexers (Catalog Product Price, Catalog Search, Stock, Category Product) run in Update by Schedule or Update on Save mode; scheduled indexing is recommended for large catalogs.
Cron drives indexers, email queue, sitemap generation, and scheduled operations; a missing cron causes stale prices, stock, and search results.
Modes are default, developer, and production; production mode enables static file compilation and disables on-the-fly materialization and verbose errors.
The service contract layer (Repository interfaces and interfaces in Api namespaces) defines the supported extension points; direct table access bypasses these contracts.
Business Requirements and Solution Design
A requirement is testable when it states actor, action, data, and acceptance criterion; vague adjectives (fast, user-friendly) must be converted into measurable criteria.
Functional requirements describe behavior; non-functional requirements cover performance, availability, security, accessibility, and compliance targets.
Scope decisions follow a build vs. configure vs. buy rule: native configuration first, marketplace extension second, custom module last, each with cost and upgrade-risk tradeoffs.
A traceability matrix links each business requirement to a design component and a test case; unlinked requirements are gaps in coverage.
Gap analysis compares out-of-the-box Adobe Commerce capability against requirements and classifies each gap as configurable, extension, or custom development.
Multi-store and multi-site requirements must be resolved early because they determine website/store/store-view topology and shared vs. separate catalogs.
B2B requirements (company accounts, quotes, requisition lists, shared catalogs) require Adobe Commerce, not Open Source, and affect customer and pricing design.
Acceptance criteria written in Given/When/Then form map directly to automated and manual test scripts during UAT.
Catalog and Product Management
Product types: Simple, Virtual, Downloadable, Configurable, Grouped, Bundle; Configurable and Bundle create child relationships that drive pricing and stock behavior.
Attribute types are dropdown, multiselect, text, textarea, date, boolean, price, media image, and fixed; the input type determines admin UI and frontend filtering.
Attribute scope (Global, Website, Store View) controls whether a value can differ per store view; Global attributes cannot be translated per store view.
Configurable products use super attributes (typically size and color); each combination is a child simple product with its own SKU, price, and stock.
Bundle products offer fixed or dynamic pricing and can use fixed, radio, checkbox, or multi-select option input types.
Categories form a tree with one root category per store; a product can be assigned to multiple categories, and anchor categories inherit products from child categories.
Stock is managed per source under Multi-Source Inventory; salable quantity derives from source item quantities minus reservations.
Product relations include related products, up-sells, and cross-sells, each rendered in different storefront locations and configured per product or via rules.
Customer Management and Personalization
Customer groups drive pricing and tax behavior; the NOT LOGGED IN group applies to guests, and each customer group can be assigned a tax class.
Customer attributes can be system or custom, and forms (customer_register_address, customer_address_edit, customer_edit) control which attributes appear.
Customer segments (Adobe Commerce) are built from conditions on attributes, orders, cart, and products; they feed Cart Price Rules, Dynamic Blocks, and related promotions.
Dynamic Blocks target content to customer segments via a widget or banner and require the segment to be created and active.
Customer lifetime value = average order value x purchase frequency x customer lifespan; segmentation by RFM (recency, frequency, monetary) supports targeting.
VAT number validation and tax-exempt groups support B2B tax handling; the customer group's tax class determines whether tax is applied.
Company accounts (B2B) group users under a company with roles and permissions, a shared catalog, and optionally company credit payment.
GDPR tooling includes customer data export and anonymization; anonymization removes personal data while preserving order records.
Marketing, Promotions, and Merchandising
Cart Price Rules apply to the cart with conditions on items, subtotal, customer group, or coupon; Catalog Price Rules apply to product prices before the cart.
Coupon codes attach to Cart Price Rules; multiple coupons can be allowed per order via the Multiple Coupons setting, and coupon usage limits can be per coupon or per customer.
Free shipping is a Cart Price Rule action with an optional minimum order amount or item quantity condition.
Rule processing order is determined by priority and the Stop Further Rules Processing flag; lower priority numbers run first.
Related Products Rules, Up-sell Rules, and Cross-sell Rules generate product relationships by condition rather than manual assignment.
Search merchandising uses search synonyms, redirects, and (Adobe Commerce) search terms and merchandising rules to shape catalog search results.
Catalog promotions include Special Price with date range, Tier Price by quantity or customer group, and Catalog Price Rules for scheduled discounts.
Email marketing integrates via newsletter subscription, abandoned cart emails, and transactional email templates configured per store view.
Checkout, Payments, and Order Management
Checkout is a multi-step process (shipping, review and payments, success) with a one-page checkout default; guest checkout is controlled by a configuration flag.
Payment methods include offline (checkout/purchase order, cash on delivery), integrated gateways, and vaulted stored payment tokens for repeat purchases.
Authorize and Capture takes funds immediately; Authorize only places a hold and requires a separate capture or invoice action.
Order workflow states: Pending, Processing, On Hold, Complete, Closed, Canceled; invoices, shipments, and credit memos drive transitions.
An invoice can be created with capture (online) or without (offline); a credit memo issues a refund and can be online or offline.
Partial invoices and partial shipments are supported; each invoice and shipment records quantities and updates order status accordingly.
Shipping methods include flat rate, table rate, free shipping, and carrier integrations (UPS, USPS, FedEx, DHL); table rate uses CSV conditions on weight, price, or destination.
Multi-Source Inventory reservations reduce salable quantity at order placement and release on cancellation or credit memo.
Content and Storefront Experience
Themes inherit from a parent theme; a child theme overrides templates, layouts, and styles without modifying the parent, preserving upgradeability.
Layout XML files (default.xml, catalog_product_view.xml) define blocks and containers; a block renders via a template (phtml) or a UI component.
Widgets insert CMS content (blocks, products, banners) into pages and blocks; widget type and parameters determine rendered output.
Page Builder (Adobe Commerce) provides content types: Row, Column, Text, Heading, Buttons, Image, Video, Banner, Slider, Products, and HTML.
CMS hierarchy organizes pages into a tree with URL paths; CMS pages and blocks are scoped per store view for localized content.
The storefront uses a mobile-first responsive theme (Luma/Blank); design configuration sets logo, favicon, colors, and header/footer layout per store view.
URL rewrites control SEO-friendly paths; category and product rewrites can be generated automatically or set manually, and 301 redirects preserve link equity.
Analytics, Reporting, and Business Metrics
Conversion rate = orders / sessions (or visits) x 100; it measures the share of storefront visits that result in an order.
Average order value (AOV) = total revenue / number of orders; it is used to gauge basket size and promotion impact.
Customer acquisition cost (CAC) = total marketing spend / new customers acquired; compare with customer lifetime value for payback.
Adobe Commerce reports include Sales (Orders, Tax, Invoiced, Shipping, Refunds, Coupons, Bestsellers), Customers, Products, and Marketing (Cart, Search Terms).
Google Analytics and Adobe Analytics integrate via tags or the Commerce integration; ecommerce tracking sends product, cart, and order events.
The Abandoned Carts report lists carts with items and no order; conversion funnel analysis uses cart, checkout, and order data.
Business Intelligence (Adobe Commerce) provides dashboards and report exports over consolidated data; advanced reporting requires configuration.
Cohort and RFM analysis segment customers by purchase recency, frequency, and monetary value to target retention campaigns.
Integrations, Data Flow, and Extensibility
Integration types: REST (JSON over HTTP), SOAP (WSDL), GraphQL (storefront and headless), and message queues (RabbitMQ) for asynchronous flows.
REST endpoints are defined by webapi.xml and service contracts; authentication uses OAuth 1.0a (integrations) or token-based customer/admin tokens.
GraphQL is read-oriented and recommended for headless/PWA storefronts; mutations handle cart, checkout, and customer operations.
Message queues (RabbitMQ) decouple bulk operations such as inventory updates and B2B company credit; consumers run via cron.
Webhooks and events allow external systems to react to Commerce events; observers subscribe to dispatched events in di.xml.
Data flow patterns include import/export (CSV), API sync, and ETL; the Import feature handles products, customers, and advanced pricing.
Plugins (before, after, around) and preferences extend behavior without modifying core code; di.xml declares them.
ERP/CRM/PIM integrations typically sync catalog, inventory, pricing, and orders; idempotent operations and retry logic are required for reliability.
Project Governance and Launch Readiness
A RACI matrix assigns Responsible, Accountable, Consulted, Informed roles for each deliverable; a single accountable owner per workstream is required.
Change control requires a documented request, impact assessment, approval, and scheduled release; scope changes after design freeze need re-estimation.
UAT entry criteria: code complete, environment stable, test data loaded, and test cases approved; exit criteria: agreed pass rate and no open critical defects.
Go-live readiness checklist covers performance/load testing, security review, SEO redirects, payment gateway certification, and rollback plan.
Deployment pipeline stages: build (composer, static content deploy), test, staging, production; production mode and compiled static assets are required.
Post-launch hypercare monitors error rates, order success rate, page load time, and support ticket volume against baseline thresholds.
Risk register tracks likelihood, impact, owner, and mitigation; high-impact/high-likelihood items require contingency plans.
Launch metrics (KPI baseline) are captured pre-launch so post-launch performance can be measured against a defined target.
Commerce Architecture and Platform Fundamentals
Adobe Commerce uses a three-tier logical model: presentation (storefront/theme), application (modules in app/code and vendor), and data (MySQL plus Redis/Varnish/Elasticsearch or OpenSearch).
Configuration scope hierarchy from broadest to narrowest is Default Config, Website, Store, Store View; a value set at a narrower scope overrides broader scopes unless the field is locked.
Websites map to distinct domains or brands, stores group catalog roots and root categories, and store views control locale and currency presentation for a single store.
Magento Open Source and Adobe Commerce share the same codebase core; Adobe Commerce adds cloud hosting, B2B, staging/production, and advanced marketing modules.
Indexers (Catalog Product Price, Catalog Search, Stock, Category Product) run in Update by Schedule or Update on Save mode; scheduled indexing is recommended for large catalogs.
Cron drives indexers, email queue, sitemap generation, and scheduled operations; a missing cron causes stale prices, stock, and search results.
Modes are default, developer, and production; production mode enables static file compilation and disables on-the-fly materialization and verbose errors.
The service contract layer (Repository interfaces and interfaces in Api namespaces) defines the supported extension points; direct table access bypasses these contracts.
Business Requirements and Solution Design
A requirement is testable when it states actor, action, data, and acceptance criterion; vague adjectives (fast, user-friendly) must be converted into measurable criteria.
Functional requirements describe behavior; non-functional requirements cover performance, availability, security, accessibility, and compliance targets.
Scope decisions follow a build vs. configure vs. buy rule: native configuration first, marketplace extension second, custom module last, each with cost and upgrade-risk tradeoffs.
A traceability matrix links each business requirement to a design component and a test case; unlinked requirements are gaps in coverage.
Gap analysis compares out-of-the-box Adobe Commerce capability against requirements and classifies each gap as configurable, extension, or custom development.
Multi-store and multi-site requirements must be resolved early because they determine website/store/store-view topology and shared vs. separate catalogs.
B2B requirements (company accounts, quotes, requisition lists, shared catalogs) require Adobe Commerce, not Open Source, and affect customer and pricing design.
Acceptance criteria written in Given/When/Then form map directly to automated and manual test scripts during UAT.
Catalog and Product Management
Product types: Simple, Virtual, Downloadable, Configurable, Grouped, Bundle; Configurable and Bundle create child relationships that drive pricing and stock behavior.
Attribute types are dropdown, multiselect, text, textarea, date, boolean, price, media image, and fixed; the input type determines admin UI and frontend filtering.
Attribute scope (Global, Website, Store View) controls whether a value can differ per store view; Global attributes cannot be translated per store view.
Configurable products use super attributes (typically size and color); each combination is a child simple product with its own SKU, price, and stock.
Bundle products offer fixed or dynamic pricing and can use fixed, radio, checkbox, or multi-select option input types.
Categories form a tree with one root category per store; a product can be assigned to multiple categories, and anchor categories inherit products from child categories.
Stock is managed per source under Multi-Source Inventory; salable quantity derives from source item quantities minus reservations.
Product relations include related products, up-sells, and cross-sells, each rendered in different storefront locations and configured per product or via rules.
Customer Management and Personalization
Customer groups drive pricing and tax behavior; the NOT LOGGED IN group applies to guests, and each customer group can be assigned a tax class.
Customer attributes can be system or custom, and forms (customer_register_address, customer_address_edit, customer_edit) control which attributes appear.
Customer segments (Adobe Commerce) are built from conditions on attributes, orders, cart, and products; they feed Cart Price Rules, Dynamic Blocks, and related promotions.
Dynamic Blocks target content to customer segments via a widget or banner and require the segment to be created and active.
Customer lifetime value = average order value x purchase frequency x customer lifespan; segmentation by RFM (recency, frequency, monetary) supports targeting.
VAT number validation and tax-exempt groups support B2B tax handling; the customer group's tax class determines whether tax is applied.
Company accounts (B2B) group users under a company with roles and permissions, a shared catalog, and optionally company credit payment.
GDPR tooling includes customer data export and anonymization; anonymization removes personal data while preserving order records.
Marketing, Promotions, and Merchandising
Cart Price Rules apply to the cart with conditions on items, subtotal, customer group, or coupon; Catalog Price Rules apply to product prices before the cart.
Coupon codes attach to Cart Price Rules; multiple coupons can be allowed per order via the Multiple Coupons setting, and coupon usage limits can be per coupon or per customer.
Free shipping is a Cart Price Rule action with an optional minimum order amount or item quantity condition.
Rule processing order is determined by priority and the Stop Further Rules Processing flag; lower priority numbers run first.
Related Products Rules, Up-sell Rules, and Cross-sell Rules generate product relationships by condition rather than manual assignment.
Search merchandising uses search synonyms, redirects, and (Adobe Commerce) search terms and merchandising rules to shape catalog search results.
Catalog promotions include Special Price with date range, Tier Price by quantity or customer group, and Catalog Price Rules for scheduled discounts.
Email marketing integrates via newsletter subscription, abandoned cart emails, and transactional email templates configured per store view.
Checkout, Payments, and Order Management
Checkout is a multi-step process (shipping, review and payments, success) with a one-page checkout default; guest checkout is controlled by a configuration flag.
Payment methods include offline (checkout/purchase order, cash on delivery), integrated gateways, and vaulted stored payment tokens for repeat purchases.
Authorize and Capture takes funds immediately; Authorize only places a hold and requires a separate capture or invoice action.
Order workflow states: Pending, Processing, On Hold, Complete, Closed, Canceled; invoices, shipments, and credit memos drive transitions.
An invoice can be created with capture (online) or without (offline); a credit memo issues a refund and can be online or offline.
Partial invoices and partial shipments are supported; each invoice and shipment records quantities and updates order status accordingly.
Shipping methods include flat rate, table rate, free shipping, and carrier integrations (UPS, USPS, FedEx, DHL); table rate uses CSV conditions on weight, price, or destination.
Multi-Source Inventory reservations reduce salable quantity at order placement and release on cancellation or credit memo.
Content and Storefront Experience
Themes inherit from a parent theme; a child theme overrides templates, layouts, and styles without modifying the parent, preserving upgradeability.
Layout XML files (default.xml, catalog_product_view.xml) define blocks and containers; a block renders via a template (phtml) or a UI component.
Widgets insert CMS content (blocks, products, banners) into pages and blocks; widget type and parameters determine rendered output.
Page Builder (Adobe Commerce) provides content types: Row, Column, Text, Heading, Buttons, Image, Video, Banner, Slider, Products, and HTML.
CMS hierarchy organizes pages into a tree with URL paths; CMS pages and blocks are scoped per store view for localized content.
The storefront uses a mobile-first responsive theme (Luma/Blank); design configuration sets logo, favicon, colors, and header/footer layout per store view.
URL rewrites control SEO-friendly paths; category and product rewrites can be generated automatically or set manually, and 301 redirects preserve link equity.
Analytics, Reporting, and Business Metrics
Conversion rate = orders / sessions (or visits) x 100; it measures the share of storefront visits that result in an order.
Average order value (AOV) = total revenue / number of orders; it is used to gauge basket size and promotion impact.
Customer acquisition cost (CAC) = total marketing spend / new customers acquired; compare with customer lifetime value for payback.
Adobe Commerce reports include Sales (Orders, Tax, Invoiced, Shipping, Refunds, Coupons, Bestsellers), Customers, Products, and Marketing (Cart, Search Terms).
Google Analytics and Adobe Analytics integrate via tags or the Commerce integration; ecommerce tracking sends product, cart, and order events.
The Abandoned Carts report lists carts with items and no order; conversion funnel analysis uses cart, checkout, and order data.
Business Intelligence (Adobe Commerce) provides dashboards and report exports over consolidated data; advanced reporting requires configuration.
Cohort and RFM analysis segment customers by purchase recency, frequency, and monetary value to target retention campaigns.
Integrations, Data Flow, and Extensibility
Integration types: REST (JSON over HTTP), SOAP (WSDL), GraphQL (storefront and headless), and message queues (RabbitMQ) for asynchronous flows.
REST endpoints are defined by webapi.xml and service contracts; authentication uses OAuth 1.0a (integrations) or token-based customer/admin tokens.
GraphQL is read-oriented and recommended for headless/PWA storefronts; mutations handle cart, checkout, and customer operations.
Message queues (RabbitMQ) decouple bulk operations such as inventory updates and B2B company credit; consumers run via cron.
Webhooks and events allow external systems to react to Commerce events; observers subscribe to dispatched events in di.xml.
Data flow patterns include import/export (CSV), API sync, and ETL; the Import feature handles products, customers, and advanced pricing.
Plugins (before, after, around) and preferences extend behavior without modifying core code; di.xml declares them.
ERP/CRM/PIM integrations typically sync catalog, inventory, pricing, and orders; idempotent operations and retry logic are required for reliability.
Project Governance and Launch Readiness
A RACI matrix assigns Responsible, Accountable, Consulted, Informed roles for each deliverable; a single accountable owner per workstream is required.
Change control requires a documented request, impact assessment, approval, and scheduled release; scope changes after design freeze need re-estimation.
UAT entry criteria: code complete, environment stable, test data loaded, and test cases approved; exit criteria: agreed pass rate and no open critical defects.
Go-live readiness checklist covers performance/load testing, security review, SEO redirects, payment gateway certification, and rollback plan.
Deployment pipeline stages: build (composer, static content deploy), test, staging, production; production mode and compiled static assets are required.
Post-launch hypercare monitors error rates, order success rate, page load time, and support ticket volume against baseline thresholds.
Risk register tracks likelihood, impact, owner, and mitigation; high-impact/high-likelihood items require contingency plans.
Launch metrics (KPI baseline) are captured pre-launch so post-launch performance can be measured against a defined target.