b2c-hooks

B2C Commerce hooks are registered and managed by defining extension points in hooks.json and implementing the corresponding scripts using standard HookMgr patterns. This ensures consistent coordination across OCAPI, SCAPI, and system hooks.

To safely pass data between custom extension points in SFCC, use the request.custom mechanism. This ensures data persists securely across HookMgr interactions without causing integration friction.

HookMgr coordinates system hooks for basket calculation and order processing by enforcing built-in Status patterns and relying on the SFCC environment. Developers implement these hooks under the scripts/ directory.

Yes, implementing custom extension points in B2C Commerce requires an SFCC environment. The skill enforces reliance on the SFCC environment and uses built-in HookMgr and Status patterns for safe hook behavior.

Built-in Status patterns should be used when implementing OCAPI hooks to ensure consistent behavior and safe hook execution. They provide standardized error handling and coordination across HookMgr interactions within the SFCC environment.

When using request.custom for data passing in B2C hooks, data is scoped to the individual request lifecycle. It does not persist across separate transactions, requiring careful coordination of HookMgr interactions for complex workflows.