---
schema_version: "1"
id: 1f13498163842ffb2b6535f93f4d6ce6514e476a44591636b656773edae306dc
title: Supported Domains
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/commerce-cloud/b2c-commerce/guides/commerce-apps/supported-domains.md
canonical_url: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/supported-domains.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: 6a9472c7aafe05163e4741c17dc5efb5a6a5e5bc9f0cee3f3597ea268ec665a0
products:
  - Composable Storefront
  - Salesforce APIs
---
# 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.

| Domain                  | Hub Section      | Description                                   | Example ISVs              |
| :---------------------- | :--------------- | :-------------------------------------------- | :------------------------ |
| `tax`                   | Providers        | Tax calculation and compliance                | Avalara, Vertex           |
| `payment`               | Providers        | Payment processing                            | Stripe, Adyen, PayPal     |
| `shipping`              | Providers        | Shipping and fulfillment                      | ShipStation, EasyPost     |
| `gift-cards`            | Additional Setup | Gift card purchasing, redemption, and balance | Salesforce Gift Cards     |
| `ratings-and-reviews`   | Additional Setup | Product ratings and reviews                   | Bazaarvoice, Yotpo        |
| `loyalty`               | Additional Setup | Loyalty programs and rewards                  | LoyaltyLion, Smile.io     |
| `search`                | Additional Setup | Search and merchandising                      | Algolia                   |
| `address-verification`  | Additional Setup | Address validation and standardization        | Loqate, Smarty            |
| `analytics`             | Additional Setup | Analytics and reporting                       | Google Analytics, Segment |
| `approaching-discounts` | Additional Setup | Approaching discount notifications            | Salesforce                |
| `oms`                   | Additional Setup | Post-purchase order management                | Custom (third-party OMS)  |

## Release Timeline Overview

| Wave   | Release           | Domains                                                                  |
| :----- | :---------------- | :----------------------------------------------------------------------- |
| Wave 1 | April 2026        | Tax, Ratings & Reviews, Loyalty, Search, Address Verification, Analytics |
| Wave 2 | August 2026[^1]   | Shipping, Fraud, Marketing & TOS Consent + SFRA support                  |
| Wave 3 | October 2026[^1]  | Versioning, upgrade support, dependency management                       |
| Wave 4 | February 2027[^1] | Recurring Orders, Surcharges, CMS, CDN/Hosting, SMS, PIM, ERP            |

[^1]: Salesforce future roadmap subject to change and under our [Safe Harbor](https://investor.salesforce.com/financials/safe-harbor/default.aspx) statement.

## 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](/docs/commerce/b2c-commerce/guide/building-your-app.md#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.

![Flowchart showing the sfcc.app.tax.calculate hook triggered on every basket operation, with the platform routing to the registered tax provider](https://developer.salesforce.com/media/b2c-commerce/calculateTax.png)

#### `sfcc.app.tax.commit`

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

![Flowchart showing sfcc.app.tax.commit triggered immediately after order creation with status CREATED, with blocking and non-blocking error paths](https://developer.salesforce.com/media/b2c-commerce/commitTax.png)

#### `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.

![Flowchart showing sfcc.app.tax.cancel triggered when an order is cancelled or failed via OrderMgr.cancelOrder or OrderMgr.failOrder](https://developer.salesforce.com/media/b2c-commerce/cancelTax.png)

### Tax UI Targets

| Feature                | Surface                    | Target ID                            |
| :--------------------- | :------------------------- | :----------------------------------- |
| Tax Product Message    | PDP                        | `sfcc.pdp.tax.productMessage`        |
| Tax Line Item Message  | Cart                       | `sfcc.cart.tax.lineItemMessage`      |
| Tax Line Item Message  | Mini Cart                  | `sfcc.miniCart.tax.lineItemMessage`  |
| Order Summary Tax Line | Order Summary              | `sfcc.orderSummary.tax.line`         |
| Tax Summary            | Order Confirmation         | `sfcc.orderConfirmation.tax.summary` |
| Order Details Tax      | My Account - Order Details | `sfcc.myAccount.orderDetails.tax`    |

## 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](/docs/commerce/b2c-commerce/guide/connect-third-party-oms.md).

**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](/docs/commerce/b2c-commerce/guide/connect-third-party-oms.md#the-hooks) 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](/docs/commerce/b2c-commerce/guide/ucp-order-post-processing-events.md) 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

| Feature         | Surface                    | Target ID                            |
| :-------------- | :------------------------- | :----------------------------------- |
| Star Rating     | PDP                        | `sfcc.pdp.reviews.rating`            |
| Review Summary  | PDP                        | `sfcc.pdp.reviews.summary`           |
| Reviews List    | PDP                        | `sfcc.pdp.reviews.list`              |
| Star Rating     | Shared - Product Card      | `sfcc.productCard.reviews.rating`    |
| Q&A             | PDP                        | `sfcc.pdp.reviews.qna`               |
| Review Purchase | My Account - Order Details | `sfcc.myAccount.orderDetails.review` |
| Manage Reviews  | My Account - Overview      | `sfcc.myAccount.reviews.pending`     |

## 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

| Feature         | Surface               | Target ID                                  |
| :-------------- | :-------------------- | :----------------------------------------- |
| Loyalty Points  | PDP                   | `sfcc.pdp.loyalty.points`                  |
| Loyalty Points  | Product Card          | `sfcc.productCard.loyalty.points`          |
| Points Earned   | Cart                  | `sfcc.cart.loyalty.pointsEarned`           |
| Loyalty Summary | My Account - Overview | `sfcc.myAccount.loyalty.summary`           |
| Enrollment      | User Registration     | `sfcc.userRegistration.loyalty.enrollment` |

## 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](/docs/commerce/b2c-commerce/guide/building-your-app.md#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](/docs/commerce/b2c-commerce/guide/building-your-app.md#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.