SuiteCommerce glossary

The terms our guides and reports use, defined once. Where a behavior is NetSuite’s and observed from outside rather than documented, the definition says so.

SuiteCommerce Advanced (SCA): The NetSuite storefront delivered as source code: the merchant installs a bundle, owns the SSP application, the core front end, the theme and the extensions, and upgrades by installing a new release and merging their changes into it.See also: SuiteCommerce Standard (SCS), SSP application
SuiteCommerce Standard (SCS): The managed NetSuite storefront: NetSuite owns the SSP application and the core and upgrades them automatically; the merchant owns the theme and the extensions. Its item URLs come from the canonical URL field rather than the URL component.See also: SuiteCommerce Advanced (SCA)
SSP application: The set of server-side pages that serve a SuiteCommerce storefront — shopping.ssp, checkout.ssp, my_account.ssp and the environment scripts. Its path varies from site to site; it is not always /app/.
Touchpoint: One of the applications a storefront is split into — shopping, checkout and My Account. A link carries data-touchpoint to say which one serves it: home, login, register, logout, customercenter, viewcart or checkout. Core builds the real URL when the link is clicked, so the plain href of a My Account link answers 404 on the shopping application by design.
SEO Page Generator: The NetSuite service that runs a storefront page in a server-side browser and serves the resulting HTML, so a search engine receives the title, canonical, content and status code the JavaScript application would otherwise set in the visitor’s browser.See also: The SuiteCommerce SEO Page Generator and Prerender V2: what search engines receive, Prerender V2
Prerender V2: The Chrome-based renderer NetSuite rolled out for the SEO Page Generator in January 2026. A prerendered response carries the header x-prerender-version: V2. Observed from outside, the copy can be served to any user agent and is cached at the edge for up to seven days — but not to every user agent, and not on every request.See also: The SuiteCommerce SEO Page Generator and Prerender V2: what search engines receive
Application shell: What a SuiteCommerce URL returns when the page was not prerendered: an HTML document with an empty <title>, no canonical and no content, all of which the JavaScript application fills in only in a browser that runs it.See also: Pages served to search engines without prerendering
seodebug and preview: URL parameters for the SEO Page Generator. Oracle documents seodebug=T, which appends the generator’s debug log to the page source, seodebug=V2, which previews Prerender V2, and a changing preview value, which avoids the cached copy. Observed from outside, seodebug=T also stops the site answering with its redirects.See also: The SuiteCommerce SEO Page Generator and Prerender V2: what search engines receive
SC.CONFIGURATION: The storefront’s configuration as the browser receives it: every default from core and from each installed extension, merged with the values saved for the website and domain, minus one captcha field. Anything a developer puts in an extension’s configuration is readable by any visitor.
Site Management Tools (SMT): The content editor for SuiteCommerce pages. Landing pages get their own URL; enhanced pages decorate an existing route’s title, meta tags and banners. Content placed in an area whose scope is global appears on every page.
URL component: The item field a SuiteCommerce Advanced product URL is built from. An item without one is published at /product/<internal id>; two items with the same one get a numeric suffix such as _2.See also: Items published under a /product/<id> URL, Item URLs with a duplicate URL component suffix (_2, _3)
Meta Tag HTML: The item field whose <meta> tags SuiteCommerce copies into a product page’s head. It is the only source of a product page’s meta description unless a Site Management Tools page supplies one.See also: Product pages with no meta description (empty Meta Tag HTML)
Facets SEO limits: The configuration that caps how many facet groups and values a crawlable link may combine. It works by not linking to combinations beyond the limit in the prerendered page; it does not add noindex, and those URLs still answer 200 when requested directly.See also: Facet pages beyond the SEO limits still answer 200
Extension: A packaged customization of a SuiteCommerce storefront, activated per domain in the Extension Manager. Its front-end code ships in the extensions/shopping_<n>.js bundle and its configuration joins SC.CONFIGURATION.