SuiteCommerce 2023.2: Commerce API Cart Calls, gulp theme:create, and Breaking Library Updates

What changed

Cart quantity updates now use the Commerce API

When a shopper changes an item's quantity in the cart, the front end now calls the Commerce API directly to update the quantity in place. Previously, the item was removed from the cart and re-added — a heavier round-trip that could cause visual flicker and extra server load.

Exception: matrix items still use the old remove-and-re-add behavior when quantity is updated.

Out-of-stock error messages now itemized

The checkout out-of-stock error now lists the specific line items that are unavailable, rather than showing a generic message. This applies to SC and SCA storefronts only.

New theme architecture and gulp theme:create

A new gulp command, gulp theme:create, lets you scaffold a custom theme that inherits from the Base Theme. Files you do not override are pulled from the Base Theme at runtime; files you customize take precedence. This means Base Theme updates (new features, patches) are picked up automatically when you reactivate your theme — no manual merge required.

The Extension Manager (bundle version 2023.2) now supports this architecture and shows on-screen alerts when:

• The Base Theme has been updated — prompting you to reactivate your custom theme.
• A new version of your custom theme is available — prompting you to update.

Base Theme visual and structural changes

• Header, footer, and MyAccount areas received appearance updates (fonts, backgrounds, search field).
• New CMS content areas added to the footer and MyAccount sections.
• Four new skins shipped: Aqua, Dark Mode: Green, Deep Sea, Earth.

Third-party library version changes

The following libraries changed in distro.json. The node-sass bump to 8.x is a major version change with potential breaking API differences. Note that uglify-js was actually downgraded from 3.14.3 to 3.12.4.

• uglify-js: 3.14.3 → 3.12.4 (downgrade)
• is-my-json-valid: 2.20.4 → 2.20.6
• @typescript-eslint/eslint-plugin: 1.13.0 → 2.34.0 (major bump)
• node-sass: 7.0.0 → 8.0.0 (major bump)

Node.js requirement unchanged

Developer tools still require Node.js 14.19.0. No change from 2023.1.

What to do

1. Audit your Sass build pipeline. node-sass 8.0.0 drops support for some older Node.js ABIs and may change output for certain edge-case Sass syntax. Rebuild your themes and extensions locally and diff the CSS output before deploying.
2. Check for deprecated methods. Oracle explicitly warns that SCA migrations must verify no deprecated methods exist in your implementation before upgrading. Grep your custom modules for any deprecation warnings logged in previous releases.
3. Review @typescript-eslint/eslint-plugin 2.x rules. The jump from 1.13 to 2.34 may introduce new lint errors or change rule defaults. Run your linter against existing extension code and resolve any new failures before building on 2023.2.
4. Test matrix-item cart behavior separately. Matrix items still use the old remove/re-add path. If you have custom cart event handlers or analytics hooks that fire on item-add/item-remove events, confirm they still behave correctly for both matrix and non-matrix items.
5. Evaluate the new theme inheritance model. If you maintain a heavily customized theme, consider migrating to the gulp theme:create workflow. You will only need to keep your overrides in version control, and future Base Theme updates will flow through automatically.
6. Check CMS content in footer and MyAccount. The new CMS areas may surface empty content blocks on your live site if you have not populated them. Review your CMS configuration after activating the 2023.2 Base Theme or any theme that inherits from it.