SuiteCommerce
NetSuite 2025.1
2025-04-09

2025.1 SuiteCommerce: Assembly Item Returns, Extension Management Improvements

SuiteCommerce 2025.1 adds customer-facing returns for assembly items and ships Extension Management bundle 521562 with improved error handling and broader DevTools domain support.

Affects:SuiteCommerceSuiteCommerce AdvancedSuiteCommerce MyAccountSuiteCommerce Extension Management (Bundle 521562)

What changed

Assembly item returns

Customers can now initiate returns (RMAs) for assembly items through the SuiteCommerce storefront and MyAccount portal. Previously, only non-assembly item types were eligible for customer-initiated returns. This applies to all three SuiteCommerce flavors: SC, SCA, and SCMA.

Under the hood, this means the return-request flow now recognizes assemblyitem record types and renders them in the return-eligible items list. If you have customizations that filter or manipulate the return-eligible item set — for example, a SuiteScript beforeLoad user event on the Return Authorization record or client-side SC extensions that override the return item selection component — verify they handle assembly items correctly.

SuiteCommerce Extension Management (Bundle 521562) — v2025.1.0

  • Clearer error messages — Error responses from the extension management framework now include more contextual detail, which should reduce debugging time when activations or deployments fail.
  • Broader DevTools domain support — Developer tools are now compatible with additional domain configurations. The release notes do not specify which domains were previously unsupported, so test against any non-standard or subsidiary domains you use.
  • Activation origin trigger handling — Improved internal logic for how extension activation origin triggers are processed. No specifics are given; watch for changes in activation behavior if you rely on programmatic or event-driven extension activations.

Node.js requirement — unchanged

The developer toolchain (Theme, Extension, and core SCA dev tools) still requires Node.js 20.10.0. No change from 2024.2.

Configuration properties and third-party libraries

No new configuration properties were added. No third-party library updates were made. This is a quiet release on both fronts.

Bug fixes

All minor-release fixes, security patches, and improvements from the 2024.2.x line are rolled into this major release. Oracle does not itemize them here — refer to the 2024.2.x Minor Releases notes for the full list.

What to do

  1. Review return-flow customizations. If you have SuiteScript user event scripts on the returnauthorization record, client scripts, or SC/SCA extensions that customize the returns UI, confirm they now accommodate assemblyitem types. Test a return for an assembly item end-to-end in your sandbox.
  2. Update Extension Management bundle. Verify bundle 521562 is at version 2025.1.0 in your account (Customization > SuiteBundler > Search & Install Bundles > List). If you manage extensions programmatically, regression-test activation workflows — the trigger-handling changes are not fully documented.
  3. Validate Node.js version. Confirm your local and CI/CD build environments are on Node.js 20.10.0. Other versions are not supported by the 2025.1 developer tools.
  4. Test on non-standard domains. If you run SuiteCommerce on subsidiary or region-specific domains, verify that DevTools works correctly after the update, since domain compatibility was expanded.
  5. Review 2024.2.x minor-release notes. If you skipped any 2024.2.x minor patches, audit those notes now — their fixes are baked into this release and may alter behavior you depend on.