Backporting Auto-Apply Promotions to SuiteCommerce Advanced Elbrus

What changed

Starting with the Kilimanjaro release of SuiteCommerce Advanced, auto-apply promotions are supported out of the box. Sites still running the older Elbrus release do not have this capability natively and must apply a manual patch.

Scope of the patch

The backport touches three areas:

1. Existing promotions code — modifications to JavaScript, Template (.tpl), and Sass (.scss) files that already ship with Elbrus.
2. New PromocodeNotifications module — a custom SCA module that must be added to the distribution. This module handles the UI feedback when promotions are auto-applied to a transaction.
3. Promotions record configuration — after code changes are deployed, each promotion record in NetSuite must have the Auto-Apply flag enabled for the feature to take effect.

What is unclear

The source page is a summary hub; the actual file-level diffs and module code live behind two sub-pages (Modifications to Existing Promotions Code and Custom PromocodeNotifications Module). No specific file paths, function signatures, or line-level changes are provided in the top-level content. Developers should follow those linked sub-pages for the precise patch instructions.

What to do

1. Confirm you are running the Elbrus release of SCA. If you are already on Kilimanjaro or later, this patch is unnecessary — auto-apply is built in.
2. Follow Oracle’s linked sub-pages to apply the JavaScript, Template, and Sass modifications to your existing promotions code.
3. Add the custom PromocodeNotifications module to your SCA extension or theme as described in the sub-page.
4. Deploy the updated SCA bundle to your domain.
5. In NetSuite, navigate to the relevant Promotion records and enable the Auto-Apply checkbox. See Promotions in Commerce Web Stores in SuiteHelp for field-level details.
6. Test in a sandbox domain first — verify that qualifying promotions are applied automatically in the cart without the shopper entering a promo code.

Note: Elbrus is a legacy SCA release. If your site is still on Elbrus, consider evaluating an upgrade to a current SCA reference implementation (Aconcagua or later) rather than maintaining an increasingly fragile patch chain.