SuiteCommerce
NetSuite 2024.1
2024-02-14

SuiteCommerce 2024.1: Clear Cart Button, MyAccount Checkout Flows, and Configuration Record Reshuffling

The 2024.1 SuiteCommerce release adds a Clear Cart button, enables configurable checkout flows for SuiteCommerce MyAccount (reorders only), and reorganizes several tabs/subtabs on the SuiteCommerce Configuration record. Node.js 20.10.0 remains the required version for developer tools.

Affects:SuiteCommerceSuiteCommerce AdvancedSuiteCommerce MyAccountSuiteCommerce Configuration RecordSuiteCommerce Extension Management (Bundle 521562)

What Changed

Clear Cart Button (SC, SCA)

A new Clear Cart button is now rendered in the shopping cart area, allowing customers to empty their cart in a single click instead of removing items individually. This is enabled out-of-the-box — no configuration property was added to toggle it.

Checkout Flows for SuiteCommerce MyAccount (SCMA)

SCMA merchants can now select from three checkout flows: standard checkout, one page checkout, or billing first checkout. Note that in SCMA, checkout flows apply only to reordering items, not to initial purchases.

To support this, Oracle reorganized the SuiteCommerce Configuration record (the custom record you access at Setup > SuiteCommerce > Configuration):

  • The Checkout tab is now visible to SCMA users.
  • A new subtab, Checkout Experience, was created under the Checkout tab. It is hidden from SCMA users and contains properties exclusive to SC/SCA.
  • Payment-related properties moved to a new top-level tab: Payment Instruments & Methods (visible to SC, SCA, and SCMA).
  • Several subtabs under the Integrations tab are now hidden from SCMA users: Twitter, Pinterest, Facebook, Google Universal Analytics, and Categories.

If you have any automations, scripts, or saved searches that reference SuiteCommerce Configuration record fields by their subtab path, verify that the field IDs you rely on still resolve correctly after the tab reshuffling.

Configuration Properties

No new properties were added in 2024.1.0. However, one property introduced in 2023.2.4 is noted:

  • Show Quantity Available on the Out-of-Stock Error Message — Property ID: checkoutApp.showItemRemainingQuantity, located under Checkout > Quantity Stock Message.

Node.js Requirement

Developer tools (Theme, Extension, core SCA) continue to require Node.js 20.10.0. No change from the prior release — if you are already on 20.10.0, no action is needed.

Third-Party Library Updates

No library updates were made in this release.

SuiteCommerce Extension Management (Bundle 521562)

Version 2024.2.0 of the Extension Management SuiteApp includes:

  • A new required parameter in the Suitelet's external URL: &ns-at=<VALUE>. This is an authentication/anti-CSRF token. Any custom integrations or scripts that construct the Extension Management Suitelet URL programmatically must now include this parameter.
  • Improved asset deployment when deploying a theme locally via the gulp command.
  • Minor internal library updates.

What to Do

  1. Review SuiteCommerce Configuration record layout. If you have documentation, training materials, or scripts that reference specific Configuration record tabs/subtabs, verify the paths still match after the reorganization. Pay special attention to checkout and payment properties.
  2. Update Extension Management Suitelet URLs. If you call the Extension Management Suitelet externally (e.g., from a custom integration or a link in a SuiteScript), add the &ns-at=<VALUE> parameter. Without it, the Suitelet call will likely fail with an authentication error.
  3. Test the Clear Cart button. If you have customized the cart template or overridden cart behavior via an extension, confirm the new button does not conflict with your customizations. Look for template overrides in cart_lines.tpl or similar.
  4. SCMA checkout flow selection. If you run SuiteCommerce MyAccount, evaluate whether one page checkout or billing first checkout better fits your reorder workflow. Configure this under the newly visible Checkout tab in the Configuration record.
  5. Confirm Node.js version. Run node -v in your dev environment. If you are not on 20.10.0, update before using 2024.1 developer tools.