Aconcagua Release: SuiteCommerce Moves to Themes, Extensions, and the Extensibility API

What changed

New theme and extension architecture

The Aconcagua release fundamentally changes how SuiteCommerce and SuiteCommerce Advanced (SCA) customizations are built and deployed. You no longer edit distro files and compile code for deployment. Instead, themes and extensions are self-contained packages deployed to a NetSuite account and activated via the new Manage Extensions Wizard, which is added by installing the SuiteCommerce Extensions Management SuiteApp.

The Source and Development distributions in the File Cabinet no longer contain HTML templates or Sass files. All HTML template and Sass development must now go through themes.

Required SuiteApps for SuiteCommerce:

• SuiteCommerce
• SuiteCommerce Extensions Management
• SuiteCommerce Base Theme
• SuiteCommerce Configuration

Extensibility API and Extension Framework

A new Extensibility API provides a component-based interface for building extensions. Custom developer code calls API components that interact with the application, separating customizations from the SCA core. Extensions are built with JavaScript, SuiteScript, or configuration objects exposed through the API.

Important for SCA developers: If you are customizing objects not accessible through the Extensibility API, you must still use the core SCA developer tools and standard module customization practices. Oracle does not enumerate the full component list in this note; see the Extensibility API Components documentation for the definitive list.

Theme Customizer — Sass variable exposure

Theme developers can expose Sass variables to the Site Management Tools (SMT) Theme Customizer by wrapping them in an editable() function call inside a Sass comment. A JSON schema controls how each variable renders in the SMT UI. Themes can also ship skins—JSON files defining preset values for exposed variables.

Copy Configuration

The SuiteCommerce Configuration SuiteApp now supports copying a configuration record from one domain to another via Setup > SuiteCommerce Advanced > Configuration. Domains can be on different SCA releases (e.g., Kilimanjaro → Aconcagua); fields common to both releases are copied and new fields receive defaults.

Intercompany Cross-Subsidiary Fulfillment

OneWorld accounts with multiple subsidiaries can now fulfill web store orders from a related subsidiary's inventory when the ordering subsidiary lacks stock. Applies to ship and pickup-in-store orders. Requires Intercompany Cross-Subsidiary Fulfillment configuration in NetSuite before it surfaces in the web store.

Free Gift Promotion

SuitePromotions Free Gift is now available in the web store. Qualifying orders automatically receive the free gift. Known limitations:

• Incompatible with Multi Ship To.
• Best Offer logic does not apply.
• Parent matrix items and items with options cannot be selected as free gifts.

Third-party library upgrades

Major version bumps in distro.json-tracked libraries. If you are migrating to Aconcagua, audit your code for deprecated methods before upgrading.

• Backbone 1.1.2 → 1.3.3 (breaking changes in event handling, view lifecycle)
• underscore 1.7.0 → 1.8.3
• Bignumber 1.5.0 → 4.0.4 (major semver jump; API differences likely)
• RequireJS 2.1.15 → 2.3.5
• twitter-bootstrap-sass 3.3.1 → 3.3.7
• Backbone.Stickit 0.8.0 → 0.9.2
• jQuery-Zoom 1.7.13 → 1.7.20
• Almond 0.3.0 → 0.3.3
• html5shiv 3.7.2 → 3.7.3
• json2 2.0.1 → 2.0.2

Standard header/footer in checkout

A new option on the Configuration record > Checkout Tab lets you display the standard website header and footer on checkout pages instead of the default simplified checkout chrome.

What to do

1. Install required SuiteApps. If you are adopting SuiteCommerce, install the four required SuiteApps listed above. SCA sites need at minimum the Extensions Management SuiteApp to access themes and extensions.
2. Migrate Sass and HTML out of distro files. Create a theme using the Base Theme SuiteApp as your starting point (Manage Extensions Wizard > activate Base Theme > fetch theme files via developer tools). Move all custom HTML templates and Sass into the theme structure.
3. Refactor custom JS/SuiteScript into extensions where possible. Use the Extensibility API components to build portable extensions. Reserve core SCA module customization for objects not yet exposed through the API.
4. Audit for deprecated library methods. The Backbone 1.1 → 1.3 and Bignumber 1.x → 4.x jumps are significant. Search your codebase for removed or changed APIs before deploying to Aconcagua. Pay particular attention to Backbone view and model event changes.
5. Test Intercompany Fulfillment end-to-end if you run a OneWorld account with multiple subsidiaries. Verify inventory sourcing logic, tax implications, and subsidiary-specific pricing.
6. Review Free Gift Promotion limitations if you use SuitePromotions. Confirm no active promotions target matrix parent items, items with options, or Multi Ship To scenarios.
7. Update bookmarks and CI scripts. Although Oracle states most documentation URLs are preserved, the content has been reorganized into Storefront (admin) and Developer Documentation sections. Verify any automated doc-scraping or onboarding links still resolve correctly.