SuiteCommerce Developer key terms

SuiteCommerce is the e-commerce platform running on NetSuite records and SuiteScript; Site Builder is the legacy CMS-style storefront toolset. Knowing which features belong to each prevents choosing the wrong extension point during design questions.

A NetSuite record that defines a SuiteCommerce web store: domains, tabs, categories, and configuration. It is the top-level container developers reference when scoping site-level settings and deployment targets.

Configuration that maps a custom domain to a SuiteCommerce site, including DNS records, SSL certificates, and the NetSuite-hosted or externally hosted options. Errors here cause checkout and asset-loading failures that are not code bugs.

SuiteCommerce serves compiled frontend assets through a content delivery network with cache-busting based on build versions. Understanding caching explains why code changes appear stale until a new bundle is deployed or the cache is invalidated.

The SuiteCommerce service layer application that exposes RESTlets and services to the storefront, handling cart, checkout, and product data requests. Backend customizations often extend or wrap these services rather than editing frontend code.

The JavaScript-based NetSuite scripting API used across SuiteCommerce backend customization, including user event, scheduled, RESTlet, and client scripts. Version choice affects module syntax, promises, and which APIs are available at runtime.

A server script that runs beforeLoad, beforeSubmit, and afterSubmit around record create, edit, or delete. In SuiteCommerce it commonly enforces pricing, inventory, or customer rules before data reaches the storefront.

A SuiteScript entry point callable over HTTP that returns JSON or text. Storefront extensions use RESTlets to expose custom server logic when the standard SSP services do not cover a requirement.

A custom route added to the SuiteCommerce service layer so the frontend can call backend logic through the same request pipeline as built-in services. It keeps authentication, error handling, and caching consistent with platform behavior.

NetSuite's data model of standard records such as items, customers, and sales orders, plus custom fields and custom records. SuiteCommerce reads this model directly, so field-level changes ripple into product detail and checkout behavior.

Items are sellable records; matrix items group child items by size, color, or other options. Storefront product pages, option selectors, and cart line generation all depend on how the matrix is configured.

A record that binds a script to a record type, event, or schedule and controls status, audience, and logging. Misconfigured deployments are a frequent cause of custom logic not firing in production.

NetSuite's execution limits and logging tools, including usage units, governance thresholds, and execution logs. Custom SuiteCommerce logic must stay within these limits because storefront requests run under the shopper's session.

A packaged customization containing frontend modules, templates, services, and configuration that is deployed to a site. Extensions are the supported way to add features without forking core source code.

The compiled, deployable artifact produced when an extension is built, including JavaScript modules, templates, and assets. Deployment activates the bundle on a site and is required before changes appear to shoppers.

A NetSuite record and toolset for installing, activating, and configuring extensions on a web store. It controls which extensions are available per site and per domain, which matters when managing multiple storefronts.

The frontend framework SuiteCommerce uses for models, collections, and views that bind data to templates. Customizing behavior usually means extending a view or overriding a method rather than editing HTML directly.

SuiteCommerce organizes frontend code as asynchronous modules with dependencies declared in define blocks. Correct dependency lists and module paths determine whether an extension loads and can inject into a page.

The manifest-style configuration declaring which modules an extension depends on and where it hooks into the application. Wrong entry points are a common reason custom code compiles but never executes.

Replacing or extending a Handlebars template used by a view so markup changes without editing core files. Overrides must match the data context the view passes or rendering breaks silently.

The templating language used to render SuiteCommerce pages, supporting helpers, partials, and context variables. Developers customize markup through templates and must understand escaping and context scope.

A set of CSS, images, and template overrides that controls a site's visual appearance. Skins are applied per site and are the primary lever for branding without touching functional code.

SuiteCommerce styles are authored in Sass and compiled into CSS during the build. Variables and mixins in the theme control colors, spacing, and typography, so recompiling is required after style edits.

The legacy theme system for Site Builder storefronts, using HTML/CSS templates and content-managed pages. It differs from SuiteCommerce themes and is tested mainly to distinguish legacy capabilities from current ones.

Content types such as landing pages, categories, and tabs managed through the site's content tools. Understanding where content lives explains routing behavior and why some pages are not code-driven.

How SuiteCommerce builds product, category, and search URLs, including canonical tags, redirects, and friendly URL settings. Routing changes affect search rankings and must be coordinated with content and marketing.

The page rendering a single item, including options, pricing, images, availability, and add-to-cart controls. It is the most commonly customized page and depends on item data, templates, and views together.

The sequence of frontend and backend calls that validates an item and adds it to the cart, including option checks and pricing. Customizations here often break quantity or matrix handling if validation is bypassed.

The frontend components and service calls that manage cart lines, promotions, shipping, and order submission. Checkout is heavily regulated and tightly coupled, so extensions should hook in rather than replace.

The site search system that indexes items and exposes filters, sorting, and keyword results. Customizing facets or result ranking requires understanding both indexing configuration and frontend search views.

The account area where shoppers register, log in, view orders, and manage profiles. Extensions touching authentication must respect session handling and the customer record model.

Measuring page load and request timing to find slow services, oversized assets, or excessive script calls. SuiteCommerce performance is sensitive to backend governance limits and frontend bundle size alike.

Non-production environments used to test customizations against upcoming NetSuite releases. Because platform updates can change APIs, validating extensions in a sandbox before production deployment is standard practice.

The workflow of versioning extension code and running the build that produces deployable bundles. A reproducible pipeline is essential because manual edits on a live site are overwritten by the next deployment.

Managing locale-specific strings, currencies, and content in the storefront. SuiteCommerce uses translation files and locale settings, and extensions must supply strings for every active language to avoid fallback text.

Handling tokens, API credentials, and shopper sessions safely in scripts and services. Secrets belong in secure storage rather than frontend code, and service endpoints must validate caller identity.