What happens if a hook fails?

If a hook returns a Status object with an ERROR level or throws an uncaught exception, the current transaction is typically rolled back to ensure data integrity.

What is the purpose of HookMgr?

The dw.system.HookMgr class is a server-side API used to programmatically check for the existence of registered hooks and trigger their execution within the B2C Commerce environment.

What are OCAPI/SCAPI hooks?

They are extension points that allow developers to run custom scripts before, after, or to modify the response of Salesforce Commerce Cloud API calls.

Can I share data between different hooks in the same request?

Yes, you can use the request.custom object to store and pass data between before, after, and modifyResponse hooks during a single request lifecycle.

How do I register a hook in SFCC?

Hooks are registered in a hooks.json file located within your cartridge's scripts folder, which must then be referenced in the cartridge's package.json file.

B2C Commerce Hooks

Name: B2C Commerce Hooks
Author: SalesforceCommerceCloud

bySalesforceCommerceCloud

•

Soluciones de Comercio Electrónico

Customizes Salesforce B2C Commerce business logic by registering and managing OCAPI, SCAPI, and system extension points.

Acerca de

This skill provides comprehensive guidance for implementing and managing hooks in Salesforce B2C Commerce (SFCC). It facilitates the registration of OCAPI/SCAPI hooks for extending API resources, system hooks for core business logic like order calculations and payments, and the creation of custom extension points using the HookMgr API. This is a critical tool for developers who need to customize storefront behavior, integrate third-party services within the transaction lifecycle, and ensure consistent business logic across both legacy and modern Salesforce commerce interfaces.

Características Principales

4 GitHub stars
Data persistence patterns between hooks using request.custom and RESTResponseMgr
Implementation of system hooks for order calculation, shipping, and tax logic
Standardized patterns for payment authorization, capture, and refund hooks
Custom extension point creation and execution via HookMgr
Registration of OCAPI and SCAPI hooks for API resource extension

Casos de Uso

Adding custom validation or data transformation to OCAPI/SCAPI basket and checkout requests
Overriding default order calculation or tax logic with third-party service integrations
Implementing custom payment service provider (PSP) logic for authorization and settlement

Acerca de

Características Principales

4 GitHub stars
Data persistence patterns between hooks using request.custom and RESTResponseMgr
Implementation of system hooks for order calculation, shipping, and tax logic
Standardized patterns for payment authorization, capture, and refund hooks
Custom extension point creation and execution via HookMgr
Registration of OCAPI and SCAPI hooks for API resource extension

Casos de Uso

Adding custom validation or data transformation to OCAPI/SCAPI basket and checkout requests
Overriding default order calculation or tax logic with third-party service integrations
Implementing custom payment service provider (PSP) logic for authorization and settlement