SuiteCommerce CDN Caching Now Respects Subsidiary Date Formats

What changed

2026.1.20 — Subsidiary Date Formats Respected with CDN Caching

SuiteCommerce and SuiteCommerce Advanced web stores that have CDN caching enabled previously could serve a cached date string rendered in the wrong locale format. If Subsidiary A used MM/DD/YYYY and Subsidiary B used DD/MM/YYYY, a shopper on Subsidiary B could see the cached Subsidiary A format.

Starting in 2026.1.20, the CDN layer is now subsidiary-aware for date rendering. Date fields — Oracle specifically calls out Supply Required By, but the fix likely applies to any date field surfaced through the Commerce API — are formatted per the Date Format preference on the shopper's subsidiary record (Setup > Company > Subsidiaries > [subsidiary] > Date Format).

Under the hood this means the CDN cache key (or vary strategy) now factors in the subsidiary's date-format setting so that different subsidiaries are no longer served the same cached date string. Oracle's note is light on implementation detail; if you run a heavily customized theme or have custom cacheable fragments that format dates client-side, verify that your logic still works after the patch.

2026.1.10 — Background Processing Updates

Oracle describes this as internal background-processing changes only. No shopper-facing or admin-facing behavior was modified. No specific records, scripts, or APIs are called out.

What to do

1. Multi-subsidiary SuiteCommerce stores with CDN caching — After the 2026.1.20 patch rolls out to your account, spot-check date fields (e.g., Supply Required By, order dates) on storefronts served to different subsidiaries. Confirm dates render in each subsidiary's configured format.
2. Custom theme or extension date formatting — If your SuiteCommerce theme overrides date formatting (for example, via a Handlebars helper or a custom SC.Configuration date-format key), test that the CDN-served pages still apply your override correctly. The platform fix targets the subsidiary preference, but custom client-side formatting could conflict.
3. CDN cache invalidation — If you see stale date formats after the patch, trigger a CDN cache clear from Setup > SuiteCommerce Advanced > Cache Management (or the equivalent in your SuiteCommerce configuration) to flush pre-patch cached pages.
4. 2026.1.10 — No action required. The background-processing changes are internal and have no documented impact on scripts, integrations, or shopper experience.