Commerce Administration
What administration covers
Adobe Commerce administration spans the store configuration tree (Stores > Configuration), user roles and permissions, catalog and price administration, order and invoice handling, and multi-store setup. Candidates should be fluent in how scope works: configuration values can be set at global, website, store, or store-view level, and a value set at a narrower scope overrides the broader one. Understand the difference between Stores > Configuration (settings) and the individual entity screens (products, customers, orders), and know that admin permissions are governed by user roles with resource-level granularity plus role scopes that restrict which websites a role can touch.
Traps to watch for
Questions love to blur scope. A setting changed in the default view will not affect a store view that already has an explicit override - the classic "why didn't my change apply?" trap. Distinguish websites (a sales channel grouping) from stores (a root category and view container) from store views (a locale/language presentation layer). Another trap: indexers and caches. Configuration and catalog changes may require reindexing and cache flushing; admin actions do not always take effect immediately. Also separate admin users from customer accounts - they are entirely different entities.
Worked example
A merchant wants a different currency and base price display on a French store view but the same catalog. Rule of thumb: set the shared catalog at the website level, then override currency and locale at the French store view scope. If a value is grayed out with a "use default" checkbox, it is inherited - unchecking it creates a narrower-scope override that then persists independently of the parent.
Order operations
Know the lifecycle: order placement creates an order, invoices capture payment, shipments fulfill, and credit memos refund. Partial invoices and partial shipments are common question territory.