sfcc-cartridge-development

Extend an SFRA controller by referencing the base controller with `module.superModule`, calling `server.extend(page)`, then adding logic with `server.append` or `server.prepend`. Use `res.getViewData()` and `res.setViewData()` to inject extra data without replacing the original route.

Create a job step script under `cartridge/scripts/jobs/` that exports `module.exports.execute` and returns a `dw/system/Status` object in all code paths. Configure parameters like API URLs through job step parameters in Business Manager rather than hardcoding them.

Custom Object writes fail silently when not wrapped in `Transaction.wrap()`, since SFCC requires explicit transactions for all persistent changes. Also verify the Custom Object type is defined in Business Manager under Administration > Site Development > Custom Objects.

ISML templates are aggressively cached by SFCC. Clear the template cache in Business Manager under Administration > Sites > Manage Sites > Cache, and confirm your cartridge appears before the base cartridge in the site's cartridge path.

Register an OCAPI hook by creating a `hooks.json` file in the cartridge with a hooks array mapping a hook name like `dw.ocapi.shop.order.afterPOST` to your script path. The hook function must return a `new Status(Status.OK)` object.

Use `server.append` whenever extending existing routes, because it preserves the original controller logic and other cartridge extensions in the chain. `server.replace` breaks the override chain and should be avoided for additive customizations.