Supported Domains

This section documents each commerce domain supported by the Commerce Apps framework, organized by release wave. Each domain entry covers the architecture(s) available, extension points and UI targets, and anchor partners.

Domain Registry

Every Commerce App must declare a domain field. Domains use hyphen-case. The Cart & Checkout Hub in Business Manager organizes domains into two sections:

• Providers (tax, payment, shipping): Display under "Providers" in the hub. Multiple apps in the same provider domain appear as alternative choices under one tile.
• Additional Setup (all other domains): Display under "Additional Setup" in the hub.

Release Timeline Overview

Tax Domain

Tax is the first domain with a platform-defined adapter interface. The platform provides the front-end components for collecting shipping addresses and calculating tax in the order summary, and defines back-end extension points. You implement the script API contract.

Extension points (triggers summarized below; see Tax Extension Points for full contracts including parameters, return values, and error semantics):

• sfcc.app.tax.calculate — every basket operation (adding items, changing quantities, updating shipping address, and so on); not only at checkout
• sfcc.app.tax.commit — immediately after successful order creation (status CREATED)
• sfcc.app.tax.cancel — on order cancellation or failure (OrderMgr.failOrder() or OrderMgr.cancelOrder())

Extension Point Flows

sfcc.app.tax.calculate

Fires during every basket calculation (add item, change quantity, update shipping address, and so on). The platform selects the tax hook based on registration and whether hooks are enabled for the request.

sfcc.app.tax.commit

Fires inside the order creation transaction immediately after the order is created with status CREATED.

sfcc.app.tax.cancel

Fires when an order is cancelled (OrderMgr.cancelOrder()) or failed (OrderMgr.failOrder()). The platform invokes this hook after inventory release and other critical operations complete.

Tax UI Targets

OMS Domain

OMS is a backend-only domain with a platform-defined adapter interface. There are no storefront UI targets: the platform already exposes order data through Shopper Orders, Shopper Customers, and Universal Commerce Protocol (UCP) order lifecycle updates. You implement the script API contract so a third-party OMS can serve that data.

Declare "domain": "oms" in commerce-app.json. For the full hook contracts, inbound oms-status-events API, and worked examples, see Connect a Third-Party OMS.

Architecture: Backend-only (extension point hooks). All four core hooks must be registered together or the platform falls back to its default order store.

Extension points (triggers summarized below; see Connect a Third-Party OMS for full contracts including parameters, return values, and error semantics):

• sfcc.app.oms.order.retrieve — provide a single order (pre-populated when the platform still holds the order locally, empty when the platform doesn't hold it)
• sfcc.app.oms.order.list — provide orders for a single customer (order history)
• sfcc.app.oms.order.cancel — cancel a whole order in the OMS
• sfcc.app.oms.order.return — start a return for specific order items
• sfcc.app.oms.order.accessControl (optional) — override the default shopper-owns-order check
• sfcc.app.oms.order.reasonCodes (optional) — supply cancel and return reason codes

The platform also exposes an inbound Admin API (POST .../oms-status-events) so the OMS can push fulfillment and adjustment events. See Order Post-Processing Events in the UCP Order Lifecycle for how those events become signed UCP snapshots.

Ratings & Reviews Domain

Ratings & Reviews is a fullstack domain. Storefront Next provides mocked UI components out of the box that you replace with your own extensions. You build a custom SCAPI for the backend and provide Storefront Next components that consume it.

SCAPI interface: No platform-defined interface. ISV builds custom SCAPI (Get Star Rating exists as a platform API needing extension; Get Reviews and Submit Review are ISV custom SCAPI).

sfNext components: Available in April 2026. UI targets available in May 2026.

Ratings & Reviews UI Targets

Loyalty Domain (Wave 1, Fullstack)

Loyalty is a fullstack domain. You build a custom SCAPI for points calculation and redemption and provide Storefront Next components.

Loyalty UI Targets

Additional Wave 1 Domains (Fullstack)

The following domains are available in Wave 1 as fullstack (custom SCAPI + Storefront Next extensions). Detailed UI target catalogs will be published as target IDs are finalized.

• Address Verification: UI targets in May 2026. Features include Address Auto Suggest and Address Validation Confirmation across Checkout, User Registration, and My Account.

• Search: UI targets still being defined. Features include Search Input and Search Results Grid.

• Analytics: UI targets pending discovery. Primarily script/beacon-based, minimal UI. See Injecting External SDK Scripts for guidance on loading analytics SDKs using contextProviders.

Wave 2 Domains (264, Backend-Only: Extension Points)

These domains will introduce platform-defined extension points similar to Tax. You implement the adapter interface contract. Documentation for specific extension points and interface specifications will be published as they are finalized.

• Shipping: Anchor partner Zenkraft/Navar. Extension points for rate calculation, delivery estimation. SCAPI interface in 264.

• Fraud: Anchor partner Forter/Signifyd. Extension points for pre-auth and post-auth fraud checks. SCAPI interface in 264. Fraud beacons can be injected today using contextProviders — see Injecting External SDK Scripts.

• Marketing & TOS Consent: Native + ISV. SCAPI interface in 264.

Wave 4 and Beyond

Domains planned for 266 and beyond include Recurring Orders, Surcharges, CMS, CDN/Hosting, SMS, PIM, and ERP. These aren't documented in detail in this guide. Documentation will be published as each domain becomes available.