Adobe Commerce Business Practitioner cheat sheet

Scope hierarchy runs Global → Website → Store View; a value set at a narrower scope overrides broader scope for that field.

Configuration fields marked with a 'use default' checkbox inherit from the parent scope; unchecking it creates a scope-specific override.

Admin roles are defined by Role Resources plus Role Scopes; a user's effective permissions are the intersection of both.

Product types: Simple, Configurable, Grouped, Bundle, Virtual, Downloadable; only physical types require weight and affect shipping.

Attribute input types and 'Use in Layered Navigation' settings control whether a facet appears on category pages.

Order workflow states: Pending → Processing → Complete; invoices, shipments, and credit memos are separate documents tied to the order.

Indexers run in 'Update on Save' or 'Update by Schedule' mode; schedule mode relies on cron and can show stale data until the cron runs.

Price scope (Global vs Website) is set per instance and determines whether product prices can differ by website.

Adobe Commerce uses an MVC pattern: controllers in modules, blocks and templates render output, view models supply presentation logic.

Modules live under app/code, are declared in registration.php and etc/module.xml, and are enabled via bin/magento module:enable.

di.xml drives dependency injection; preferences map an interface to a concrete class, virtual types configure shared class instances.

Plugins (interceptors) run before, after, or around public methods; the around type must call the proceed callable.

Events (etc/events.xml) and observers provide a one-to-many extension point; plugins are preferred for modifying behavior.

Layout XML (default.xml, catalog_product_view.xml) composes blocks and containers; .phtml templates render the block output.

The service contract layer (Api/*Interface.php, etc/webapi.xml) exposes REST/SOAP endpoints and is the supported integration surface.

Cron groups (default, index, consumers) are declared in crontab.xml; message queue consumers process async operations.

Gross margin = (Revenue − Cost of Goods Sold) / Revenue; it measures profitability before operating expenses.

Customer acquisition cost (CAC) = total sales and marketing spend / number of new customers acquired in the period.

Customer lifetime value (CLV) ≈ average order value × purchase frequency × customer lifespan (or margin-based variant).

Conversion rate = orders / sessions; average order value (AOV) = revenue / number of orders.

Cart abandonment rate = 1 − (completed purchases / carts created).

B2B vs B2C differ on pricing (negotiated, tiered, quote-driven), account structure (company accounts, shared catalogs), and approval workflows.

Merchandising levers: cross-sells, up-sells, related products, bundle pricing, and catalog price rules.

Payment and shipping methods are business decisions constrained by region, currency, tax rules, and fulfillment capability.

Customer groups drive pricing (group price, tier price), tax class, and catalog/cart price rules.

Shared catalogs assign custom pricing and product sets to specific company accounts in B2B.

Segments (customer segments) combine attributes such as sales, demographics, and behavior to target content and promotions.

Related products rules, up-sell rules, and cross-sell rules generate recommendations from catalog attributes.

Customer attributes are added via EAV setup; 'Used in Customer Grid' and forms settings control admin visibility.

Company accounts include roles and permissions that restrict which users can place orders or manage quotes.

GDPR tooling includes data export, anonymization, and cookie restriction mode for consent.

Wish lists, compare lists, and recently viewed products are persistent personalization features tied to the customer session.