Adobe Commerce Business Practitioner Expert key terms

A setting that determines how broadly a configuration value or product attribute applies, such as global, website, store, or store view. Scope controls where an override takes effect across a multi-store installation.

The three-level structure Adobe Commerce uses to organize a single installation into separate sales channels. A website holds stores, and each store holds one or more store views that serve different languages or presentations.

A single Adobe Commerce installation configured to serve several websites, stores, or languages from shared code and catalog data. It reduces duplication but requires careful planning of scope, pricing, and currency.

A value set at a narrower scope, such as a store view, that replaces the inherited value from a broader scope like global or website. Administrators use overrides to vary behavior per channel without duplicating settings.

Two editions of the same platform. Open Source provides core commerce features, while Adobe Commerce adds cloud hosting options, advanced marketing tools, B2B functionality, and enterprise support. Feature availability often depends on edition.

Adobe's managed hosting offering for Adobe Commerce, providing infrastructure, deployment tooling, and environment management. It includes starter and professional plans with differing infrastructure and support levels.

The process of flattening catalog and pricing data into optimized tables so storefront queries and layered navigation run quickly. Indexers can update on save or on schedule, and stale indexes cause missing or incorrect storefront data.

Controls that store rendered pages, blocks, and configuration data to reduce server load and speed responses. Different cache types can be enabled or flushed independently, and incorrect flushing often explains stale content.

A caching layer that stores complete rendered HTML responses for anonymous visitors. It relies on cache tags and invalidation rules, and personalized or dynamic blocks are handled separately to avoid serving incorrect content.

A scheduled task mechanism the platform uses for background jobs such as index updates, email sending, sitemap generation, and abandoned cart notices. Missing or misconfigured cron causes many automated features to fail silently.

An asynchronous communication mechanism that lets the platform hand off work, such as exports or integrations, to background consumers. It improves responsiveness and reliability for long-running or external operations.

A written statement of what a business needs a solution to accomplish, including goals, scope, assumptions, and success criteria. It guides design decisions and provides a baseline for validating delivered functionality.

A short description of a feature from the perspective of the person who needs it, usually phrased as a role, a goal, and a reason. Stories are broken into tasks and validated against acceptance criteria.

Specific, testable conditions that a feature must satisfy to be considered complete. They remove ambiguity from requirements and form the basis for quality assurance and sign-off.

A comparison of desired business capabilities against what native platform features already deliver. The result identifies where configuration suffices and where custom development or an extension is required.

A classification that determines how a product behaves in pricing, inventory, and cart logic. Common types include simple, configurable, virtual, downloadable, bundle, and grouped, each with distinct rules.

A parent product that lets shoppers choose among variations such as size and color. Each variation is a simple product with its own SKU, price, and stock, and the parent presents them as selectable options.

A build-your-own product assembled from several child items, offered at a fixed or dynamically calculated price. Shoppers select options, and the cart contains the parent bundle with its chosen components.

A parent product that displays a set of related simple products on one page so shoppers can add quantities of several items at once. Each child is ordered and priced independently.

A named collection of attributes assigned to products, defining which fields appear on the product form. Different sets let categories of goods capture different information without cluttering unrelated products.

The input control used for an attribute, such as text, dropdown, multiselect, or price. The source model determines how values are captured, validated, and stored for a product field.

Multi-source inventory lets a merchant define physical locations as sources and assign them to sales channels through stocks. This enables accurate per-location quantities and source selection during order fulfillment.

The tree structure used to organize products for browsing and navigation. Categories affect storefront menus, URL paths, layered navigation, and can drive promotional rules and pricing.

A classification of shoppers used to vary pricing, promotions, tax classes, and catalog visibility. Groups are often aligned to segments such as retail, wholesale, or VIP tiers.

A dynamic or manually defined audience built from shopper attributes such as orders, cart value, or location. Segments drive targeted promotions, content, and cart price rules for specific audiences.

An Adobe Commerce B2B feature that assigns a curated set of products with custom pricing to specific companies. It controls which items each business customer can see and buy.

An organizational account structure where multiple buyers belong to one company with roles, permissions, and approval rules. It supports purchasing workflows typical of business buyers rather than individual consumers.

A promotional rule applied to items in the shopping cart based on conditions such as subtotal, customer group, or coupon code. It defines discounts and can restrict usage by date, quantity, or audience.

A scheduled discount applied to products before they reach the cart, based on attributes, category, or website. Because the price changes in the catalog, it affects listings and product pages directly.

A code a shopper enters to unlock a promotion defined by a cart price rule. Rules can generate batches of unique codes and limit how often each code or customer may redeem them.

Merchandising relationships that surface additional items to shoppers. Related products suggest complements, up-sells promote higher-value alternatives, and cross-sells appear in the cart to increase order size.

Filterable attribute facets on category and search pages that let shoppers narrow results by price, brand, size, or other attributes. It depends on properly configured filterable attributes and current index data.

The sequence of steps a shopper completes to convert a cart into an order, covering address, shipping method, payment, and review. Customizations must preserve totals accuracy and guest or registered options.

The mechanism used to collect funds during checkout, such as an integrated gateway, offline method, or stored payment token. Each method has its own capture timing, authorization rules, and refund behavior.

The operational process of picking, packing, and shipping ordered items, including partial shipments and backorders. It links inventory sources, shipment records, and customer notifications.

Documents that record money owed and money returned. An invoice captures payment for shipped or ordered items, while a credit memo records a refund and can restock returned products.

A B2B approval process where a company buyer submits an order for authorization before it is placed. It enforces spending controls through company roles and configurable approval rules.

A scheduling feature that lets teams prepare and preview changes to content, promotions, and catalog data, then publish them automatically at a set time. It supports campaigns without manual switching.

A drag-and-drop editing tool for building storefront pages and blocks without code. It provides content types such as rows, banners, and product carousels that merchandisers can arrange visually.

A reusable content component that can be placed into pages or blocks to display dynamic information, such as recently viewed items or promotional lists. Widgets are configured by placement and parameters.

The share of storefront sessions that result in a completed order. It is a core commerce health metric and is influenced by traffic quality, pricing, checkout friction, and site performance.

Total revenue divided by the number of orders in a period. Merchants track it to evaluate merchandising and promotion effectiveness and to compare performance across segments or channels.

A cart that a shopper leaves without completing checkout. Merchants monitor abandonment and may trigger reminder emails or incentives to recover the potential sale.

A configured connection between the platform and an external system, such as an ERP or payment provider. Integrations define access credentials and permissions for data exchange through APIs.

A defined interface that lets external systems read and write platform data programmatically. REST and GraphQL endpoints support operations for products, orders, customers, and other entities.

An automated HTTP notification sent to an external endpoint when a specified event occurs. Webhooks let systems react to changes in near real time without polling the platform continuously.

A packaged add-on that adds or changes platform functionality. Extensions may be vendor-supplied or custom-built and require compatibility review before upgrades.

A self-contained unit of platform code that organizes features, configuration, and dependencies. Modules can be enabled or disabled and are the building blocks for both native and custom functionality.

The process of moving products, customers, orders, and other records from a legacy system into the platform. It requires mapping, cleansing, validation, and reconciliation to ensure data integrity at launch.

The process of moving code and configuration from a development environment into staging and production. It includes build steps, static content generation, and database changes that must be sequenced correctly.

A structured review confirming that functionality, content, integrations, performance, security, and support processes are prepared for go-live. It typically ends with a documented sign-off and rollback plan.

A final validation phase where business stakeholders confirm that delivered functionality meets requirements in realistic scenarios. It relies on acceptance criteria and produces a go or no-go recommendation.