SuiteCommerce Developer flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

SCA vs Site Builder

SuiteCommerce Advanced exposes full source and requires the extension build/deploy workflow, while Site Builder configures content and themes through admin records without source access.

SSP rendering layer

Server-side rendering component that executes the same views and Handlebars templates on the server to return initial HTML, improving first paint and SEO for storefront pages.

Commerce web store record

NetSuite record that defines a storefront: its domains, touchpoints, catalog root, and configuration, linking the site to items, categories, and pricing.

SuiteCommerce Configuration record

Central admin record holding checkout, search, CDN/cache, domain, and feature settings; extensions should read these values instead of hard-coding equivalent constants.

Extension bundle

Packaged unit of customization containing manifest, modules, templates, Sass, and assets; multiple extensions can be enabled per site and are compiled into one deployed distribution.

CDN cache invalidation

Process of purging cached pages and assets so record changes appear on the storefront; saving a record alone does not refresh CDN-cached content.

Touchpoint definition

Binding of a domain, a site, and a presentation (theme and layout); a single site may have several touchpoints serving different domains or audiences.

Theme versus layout

Theme controls colors, fonts, and Sass variables; layout controls regions and where content blocks appear. Changing one does not alter the other.

Publishing tab

Site Builder area where staged content changes are pushed live, including scheduled start and end dates and unpublishing of pages or content types.

URL component

Per-page and per-category SEO field that forms the storefront URL path; it must be unique to avoid routing collisions between records.

Content types in Site Builder

Records such as pages, tabs, tab groups, category and item templates, product lists, carousels, and landing pages, each schedulable and targetable to touchpoints.

Facet configuration

Search settings defining filterable attributes, sort order, and field sets; changes require reindexing before storefront results reflect the new facets.

ServiceController naming

Server file named <Module>.ServiceController.js that dispatches get, post, put, and remove requests for a module and returns the view model to SSP.

RecordView.getView

Commerce API call that builds a view model for a record (item, category, cart) using options such as record type, id, and field set.

SuiteScript 2.x module pattern

Entry point uses define with dependency array and returns an object of handlers; each handler receives a context with request, response, and parameters.

Field set exposure

Custom fields and records must be included in the relevant field set and permissioned for the Commerce role, or services return empty values without erroring.

Search vs record load

Use N/search with result sets and map/reduce for bulk data; loading records one at a time inside loops degrades service response time across the SSR boundary.

Backend deploy scope

Service files must be listed in the extension manifest and redeployed as a bundle; editing a file in the file cabinet alone does not activate the change.

Commerce role permissions

Role assigned to storefront service execution; it must permit read access to items, pricing, customers, and custom records the views depend on.

AJAX service endpoint

Frontend data path where SCA helpers call service endpoints and receive JSON view models; the browser never queries NetSuite records directly.

Extension manifest

manifest.json declaring extension name, vendor, version, dependencies, and which files ship; dependency changes require restarting the local dev server.

AMD module pattern

Frontend code uses define/require to load Backbone views, models, and collections; extensions mount or override these modules rather than editing core files.

Backbone view override

Extension declares a dependency on a core module and patches its prototype or mounts a new view into a CompositeView to change behavior without forking source.

Handlebars escaping

Double braces {{ }} HTML-escape output by default; triple braces {{{ }}} emit raw HTML and must be reserved for trusted content only.

Sass variable override

Extension supplies theme variables that the build compiles with all enabled extensions; conflicts are resolved in extension Sass, not by editing deployed CSS.

Local dev server

Node-based server that serves local extension files while proxying data requests to a NetSuite account, enabling iteration before bundle deployment.

Bundle activation

Deploying a versioned extension bundle to a target domain; rollback means activating the previous version rather than editing live files.

Cache-busted verification

Confirming a deploy using the deployed version number and a fresh browser session, since CDN caching can serve stale assets after a successful release.

Template context helpers

Handlebars helpers and view model fields supplied to templates; logic belongs in the view, and templates should only render provided values.

Extension folder structure

Standard layout of manifest.json, extension.js entry, and Modules, Templates, Sass, and Assets folders that the build compiles into the distribution.

CompositeView mounting

Pattern where an extension adds a child view into an existing Backbone CompositeView region, letting new UI appear without replacing the parent template.

Site Builder Appearance tab

Admin tab for selecting theme, layout, and presentation assets per touchpoint; it changes look and feel records, not application source code.