SuiteCommerce 2026.1: Rehydration, Payment Status Messaging, and Third-Party Library Bumps

What changed

Rehydration (SC, SCA)

Prerendered (server-side rendered) pages now hydrate in place instead of replacing the DOM. The browser paints the static HTML immediately, then the SPA bootstraps on top of the existing DOM nodes. This eliminates the visible flash/re-render that previously occurred when the client-side Backbone app tore down and rebuilt the page. Net effect: faster First Contentful Paint and fewer Cumulative Layout Shift events.

Font-display swap

Custom web fonts now load with font-display: swap. Text renders immediately with a system fallback font and swaps to the brand font once the @font-face resource finishes downloading. If you have custom CSS that overrides font-display, verify your rules still take precedence.

Standardized image height on PLP

Product List Page (PLP) images now use a fixed height, reducing layout shift during lazy-load. If your theme or extensions inject custom image markup or override the item cell template, test that the new dimensions do not clip or distort your images.

Payment Status Messaging on Thank You Page (SC, SCA 2026.1+)

The checkout Thank You page now renders conditionally based on the sales order payment status:

• Approved — standard confirmation with order number (no change).
• Pending — informs the shopper payment is still being confirmed; directs them to order history.
• On Hold — informs the shopper payment requires review; directs them to wait for email or contact support.

If you have customized the order_wizard_paymentdone_module templates or overridden the Thank You view, your customizations may mask or conflict with this new conditional logic.

Third-Party Library Updates

Three bundled libraries were bumped. Check distro.json for the canonical versions:

• immutables: 4.3.5 → 4.3.8
• underscore: 1.13.1 → 1.13.8
• handlebars: 4.7.7 → 4.7.9

These are minor/patch bumps, but breaking changes can still hide in patch releases. Notably, Handlebars 4.7.8+ tightened prototype-access restrictions; if your templates or helpers reference constructor or prototype properties, they may throw at runtime.

Node.js Requirement

The developer toolchain (Theme Developer Tools, Extension Developer Tools, core SCA build) still requires Node.js 20.10.0. No change from the previous release, but worth confirming via node -v before upgrading.

Configuration Properties

No new configuration properties were added in 2026.1.0.

Bug Fixes

This release rolls up all fixes and security patches shipped in the 2025.2.x minor releases. Oracle does not itemize these in the 2026.1 notes; refer to the 2025.2.x Minor Releases page for the full list.

What to do

1. Audit Thank You page customizations. If you override the confirmation/thank-you templates or the OrderWizard.Module.PaymentDone view, test against all three payment states (approved, pending, on hold). Use a sandbox with a payment gateway in test mode to trigger each status.
2. Test rehydration with custom modules. Rehydration changes how the SPA attaches to the DOM. Any extension that manipulates the DOM on afterAppendView or afterAppendToDom events should be regression-tested. Watch for duplicate event listeners or double-rendered components.
3. Verify library compatibility. Search your extensions and themes for direct imports of underscore, handlebars, or immutables. Run your test suite against the new versions. For Handlebars, specifically test any custom helpers that iterate over object properties.
4. Check image overrides on PLP. If your theme sets explicit width/height on item-cell images or overrides the item cell template, verify images render correctly after the standardized-height change.
5. Confirm Node.js version. Run node -v in your SCA development environment. The required version remains 20.10.0.
6. Review 2025.2.x fix list. The rolled-up bug fixes are not detailed here. Check Oracle's 2025.2.x Minor Releases notes for anything relevant to your implementation.