Salesforce Commerce Server-Side JavaScript

Before Writing Code

Always fetch the latest official documentation BEFORE building server-side logic:

1. Web-search: "Salesforce B2C Commerce server-side JavaScript Script API 2026"
2. Web-search: "Salesforce PWA Kit server-side rendering 2026"
3. Web-search: "Salesforce Commerce SDK Node.js 2026"
4. Web-fetch: https://developer.salesforce.com/docs/commerce/b2c-commerce/references/b2c-commerce-script-api
5. Web-fetch: https://developer.salesforce.com/docs/commerce/pwa-kit-managed-runtime/guide/getting-started.html
6. Web-fetch: https://www.npmjs.com/package/@salesforce/commerce-sdk

Verify API methods, module paths, and runtime constraints against current documentation before writing any code.

Conceptual Architecture

CRITICAL: SFCC Server-Side JavaScript is NOT Node.js

WARNING: SFCC uses a Rhino-based JavaScript engine, NOT V8/Node.js. Code that works in Node.js will fail in SFCC. Never assume Node.js APIs or patterns are available.

Common SFCC Mistakes to Avoid

dw.* Namespace Purposes

All SFCC server-side functionality is provided through the dw.* namespace:

Transaction Handling

All database modifications in SFCC must be wrapped in Transaction.wrap() for atomicity. If any statement inside the transaction throws, all changes are rolled back. Transactions are implicit for job steps but must be explicit in controllers and hooks.

SFCC Script Module Pattern

Scripts live in cartridges at cartridge/scripts/ and export functions via module.exports. Use the */cartridge/ prefix for cross-cartridge imports that follow the cartridge path overlay. The cartridge path is configured in Business Manager and determines module resolution order.

SFCC Controller Pattern

Controllers in SFRA (Storefront Reference Architecture) live at cartridge/controllers/ and use the server module to define routes. Controllers handle HTTP verbs (get, post, use) and render templates or return JSON.

PWA Kit Backend

PWA Kit runs on actual Node.js (V8) via Salesforce Managed Runtime. It uses an Express-like server created with @salesforce/pwa-kit-runtime. Full modern JavaScript (async/await, ESM, npm packages) is available.

Commerce SDK

The @salesforce/commerce-sdk npm package provides TypeScript-typed clients for all Shopper APIs:

It handles SLAS authentication automatically via helpers.getShopperToken(). All SDK methods return Promises. Use Commerce SDK typed clients instead of raw HTTP calls to SCAPI for type safety and automatic auth management.

Code Examples

Pattern: SFCC script module

var ProductMgr = require('dw/catalog/ProductMgr');
var Transaction = require('dw/system/Transaction');
module.exports.execute = function(params) {
    // Fetch live docs for dw.catalog.ProductMgr API
};

Pattern: PWA Kit getProps server-side fetch

ProductDetail.getProps = async ({ params, api }) => {
    const product = await api.shopperProducts.getProduct({
        parameters: { id: params.productId }
    });
    return { product };
};

Pattern: SFCC HTTPClient callout

var httpClient = new (require('dw/net/HTTPClient'))();
httpClient.open('POST', endpoint);
httpClient.send(JSON.stringify(payload));
// Fetch live docs for dw.net.HTTPClient response handling

Pattern: SFCC Transaction.wrap

var Transaction = require('dw/system/Transaction');
Transaction.wrap(function() {
    // All database modifications are atomic here
    // Fetch live docs for Transaction rollback behavior
});

Best Practices

SFCC Server-Side

• Use var (not let/const), function expressions (not arrows), and try/catch (not Promises)
• Always wrap data mutations in Transaction.wrap()
• Use dw/system/Logger for logging -- never console.log (it does not persist)
• Place third-party libraries directly in cartridge/scripts/lib/ -- no npm available

PWA Kit Backend

• Use getProps() for SSR data fetching, Commerce SDK hooks for client-side data
• Configure environments via config/default.js and environment-specific overrides
• Use Commerce SDK typed clients instead of raw HTTP calls to SCAPI
• Deploy to Managed Runtime for auto-scaling and CDN integration

Error Handling

• SFCC: synchronous try/catch with dw.system.Logger error logging at appropriate levels
• PWA Kit: async try/catch, structured logging, implement retry with exponential backoff
• Both: validate all inputs, handle null/missing data gracefully, never expose stack traces to clients

Performance

• Minimize external callouts (SFCC has per-request time limits)
• Cache frequently accessed data (SFCC: custom cache, PWA Kit: HTTP cache headers)
• Use parallel Promise.all() in PWA Kit for independent API calls
• Batch operations where supported by Commerce A