Salesforce B2C Commerce 24.7 > Developing Your Site > SFRA

SFRA Features and Components

SFRA is carefully architected so that it's easy to use as a blueprint for your own storefront. Built-in features and components provide a range of options for customizing the site to meet your needs.

  • SFRA Architecture
    SFRA provides an app_storefront_base cartridge and a server module. A storefront site uses the SFRA base cartridge and overlay plugin, LINK, and custom cartridge functionality to create a cartridge stack. Define the order of the cartridge stack by configuring the cartridge path in Business Manager.
  • SFRA Standard and Optional Features
    SFRA implements standard features in the base cartridge and optional features in overlay cartridges.
  • SFRA Hooks
    Use hooks to configure functionality to be called at a specific point in your application flow or at a specific event.
  • SFRA Modules
    You can access JavaScript/B2C Commerce script modules that conform to the Modules 1.1.1 CommonJS specification within your storefront script code.
  • SFRA Standards Compliance
    SFRA supports standard industry technologies and browsers.
  • SFRA Testing Technologies
    Include integration, unit, and functional tests in your SFRA development process.
  • Consent Tracking in SFRA
    You can implement consent tracking on a storefront based on SFRA. Merchants can track personal information about their shoppers to improve the shopping experience. The merchant can collect and honor shoppers’ consent preferences when they are using the site.
  • Download Shopper Information in SFRA
    When you implement an SFRA-based storefront, consider providing your shoppers with a mechanism to download their data. The plugin_datadownload cartridge provides a sample implementation of this capability.

Infocenter Retirement: On June 30, 2023, the Infocenter was retired, and documentation currently hosted on the Infocenter will be published to Salesforce Help, Commerce Cloud Developer Center, and Salesforce B2C Commerce Developer Documentation Resources. For more information, see the release note.