SuiteCommerce vs SuiteCommerce Advanced: Which to Pick

SuiteCommerce vs SuiteCommerce Advanced: the short version

Oracle sells two web store products on NetSuite. SuiteCommerce "lets you create, customize, and configure dynamic and engaging web stores without requiring in-depth development", and SuiteCommerce Advanced (SCA) "provides full permissions to the front-end code, so you can fully customize your web store" (Oracle, Commerce documentation summary). Both run inside NetSuite, both include the shopping, checkout and My Account experiences for B2B and B2C, and both use the same themes and extensions. The two real differences are who can touch the source code and who applies updates.

Direct answer: choose SuiteCommerce if your storefront can be built with Oracle's themes, the Extension Manager and the Extensibility API, because Oracle applies updates to it automatically on a schedule. Choose SuiteCommerce Advanced only if you need to modify the front-end source itself, and budget for manual migrations every release, since the SCA bundle is unmanaged.

Everything below is verified on docs.oracle.com as of October 2026; the sources are linked inline.

Decision table: SuiteCommerce vs SCA

The SuiteApp table on Oracle's install page shows the difference in one column: SuiteCommerce (bundle 596070) is listed as Managed: Yes, SuiteCommerce Advanced 2026.1.20 (bundle 596543) as Managed: No (Install Your Commerce Website Applications).

What is the same in both

A lot of the comparison content online was written before 2018, when SuiteCommerce and SCA were architecturally different products. Since the Aconcagua release they share the same customization layer:

• Themes. Oracle's theme developer tools and its six supported Commerce themes work on SuiteCommerce and on SCA Aconcagua or later. A theme is HTML, Sass and Handlebars templates; Oracle lists those as the only skills a theme requires (What Resources Do I Need?).
• Extensions. The Extension Manager "helps you manage themes and extensions for each domain linked to your Commerce website", and Oracle states that these tools "are available for SuiteCommerce and the Aconcagua release of SuiteCommerce Advanced and later" (Management Resources for Themes and Extensions).
• Extensibility API, Commerce API and Item Search API. Oracle's support table marks all three as available for SuiteCommerce; the Extensibility API needs SCA Aconcagua or later, the other two work on all SCA releases.
• Site Management Tools. SMT requires "either the SuiteCommerce or SuiteCommerce Advanced feature" to be enabled; it is not an SCA-only tool.
• B2B features. Customer-specific pricing, quantity pricing, payment terms, credit limits, quotes and invoice payment come from NetSuite records, not from the storefront product. Both editions expose them; what SCA adds is the ability to change how they behave in the front end.
• Multi-site, multi-language, multi-currency, SEO. All of these are platform features of Commerce web stores, shared by both editions.

If your project list is "a custom theme, a few extensions, SMT landing pages and the standard checkout", nothing on that list needs SCA.

What only SCA gives you

Oracle's guidance on when to use the SCA developer tools is narrow: "you should not need to use the SCA developer tools unless you are customizing a site that implements the Kilimanjaro release of SCA or earlier or you need to customize JavaScript, SuiteScript, or Configuration objects that are not accessible via the Extensibility API." That sentence is the real boundary between the two products.

You need SCA when you have to:

• Change a checkout step, a cart rule or a My Account page in a way the Extensibility API does not expose (custom validation across steps, a non-standard order flow, conditional fields that depend on back-end logic).
• Override or extend a core module: SCA follows the Model-View-Controller pattern and "uses the Backbone.js libraries" for routers, views and models (MVC and Backbone.js). Extending those modules is only possible with source access.
• Modify server-side SuiteScript service files (the .ss and .ssp files that return JSON to the single-page application).
• Keep a site on a specific release because a downstream integration was tested against it. The version lock that makes SCA harder to maintain is also what some teams want.

The cost of that access is the upgrade model. When you update the SCA bundle, "all files in the existing SCA Source directory [are] replaced with the updated set of files", your customizations "must be re-deployed from your local environment", and "you must still re-link your site record and domain to the updated SSP application" (Migrate SuiteCommerce Advanced). On a heavily modified core that is a project, not a task.

When to pick SuiteCommerce

• Your storefront is a catalog, a cart and the standard checkout, with branding handled by a custom theme.
• Your customizations can be written as extensions: new content types for SMT, product-page widgets, integrations with reviews or search tools, custom My Account tabs.
• You do not have, and do not want to hire, a developer who owns a release migration twice a year.
• You want Oracle's security and feature updates without a regression-test cycle on your side.

The limitation to accept: if a requirement later turns out to need source access, you will move to SCA, so write the requirements list before you license.

When to pick SuiteCommerce Advanced

• A requirement has already been checked against the Extensibility API and it cannot be met there.
• Checkout is not the standard flow (split shipments with different payment capture rules, custom approval steps, non-standard address or tax handling).
• You run an older SCA release (Kilimanjaro or earlier) and the migration to a current release is cheaper than re-platforming.
• You have an in-house or agency developer who will test and migrate the site every time Oracle ships a release you want.

The limitation to accept: there is no automatic update path. Our migration work shows the same pattern Oracle's docs describe: effort depends on which release you start from and whether the core was modified.

How migration between them works

SuiteCommerce to SCA. An administrator enables the SuiteCommerce Advanced feature under Setup > Company > Enable Features, Web Presence subtab, and installs the SCA bundle from the Commerce website applications list. Themes and extensions built on the Extensibility API are the same artifacts on both editions, so they are re-activated through the Extension Manager rather than rewritten. The site record and domain are then linked to the SCA SSP application. The work is in testing, not in rebuilding.

SCA to SuiteCommerce. This is the harder direction. Any customization that lives in the SCA source has to be re-implemented as a theme or extension before the switch, because SuiteCommerce gives you no place to put it. Oracle notes that for SCA 18.2 or earlier "you must contact professional services to upgrade to a newer version of SuiteCommerce Advanced or to SuiteCommerce" (Install Your Commerce Website Applications). For Aconcagua and later, an audit of what is in core versus extensions decides the effort.

Older SCA to current SCA. Oracle keeps two procedures, "Migrate from Aconcagua and Later" and "Migrate From Kilimanjaro and Earlier", because the Kilimanjaro-and-earlier path requires moving customizations to the Extensibility API first. If you are on Kilimanjaro or earlier, the migration is effectively a re-implementation of the customization layer.

How to check which one you have

Go to Setup > Company > Enable Features > Web Presence and look at which of SuiteCommerce or SuiteCommerce Advanced is checked. Then open Customization > SuiteBundler > List and read the SuiteCommerce Advanced bundle version if it is installed. The current SCA release listed by Oracle in October 2026 is 2026.1.20. If you cannot log in, our older guide on how to tell SuiteCommerce from Site Builder and SCA from the browser still works.

Where Site Builder fits

Site Builder is neither of the two products above. Oracle describes it as "the legacy commerce solution delivered by NetSuite" and keeps a separate feature set for it, with its own categories, templates and tax limitations ("SuiteTax is not supported for SiteBuilder tax calculation") (Site Builder versus Commerce Web Store Sites). Oracle's own recommendation for stores that need 3D Secure 2 is to "migrate your website to SuiteCommerce or the latest version of SuiteCommerce Advanced (SCA)" (Migrating from 3D Secure 1 to 3D Secure 2). Oracle does not publish an end-of-support date for Site Builder, so plan the move on your own timeline, not on a rumored one. The NetSuite website builder guide compares Site Builder with both SuiteCommerce editions in one table, and our SiteBuilder migration service covers the project itself.

Licensing: what Oracle says and what it does not

Both SuiteCommerce and SuiteCommerce Advanced are features of your NetSuite account, enabled per account and licensed on top of the ERP subscription. Oracle does not publish list prices for either, and we do not sell licenses, so we cannot quote them. What we can say from scoping projects: SCA is quoted higher than SuiteCommerce, and the larger gap is usually implementation, because source-level work takes more hours than theme and extension work. For the ranges clients have shared with us during scoping, see the pricing section of What is SuiteCommerce.

Frequently asked questions

What clients ask before signing

What is the difference between SuiteCommerce and SuiteCommerce Advanced?expand_more

Is SuiteCommerce Advanced version locked?expand_more

Do I need SuiteCommerce Advanced for B2B?expand_more

Can SuiteCommerce use extensions and custom themes?expand_more

Can I move from SuiteCommerce to SuiteCommerce Advanced later?expand_more

How much does SuiteCommerce Advanced cost?expand_more

Is Site Builder the same as SuiteCommerce?expand_more

Sources

• Commerce Documentation Summary, Oracle NetSuite Help
• Enabling Commerce Web Site Features, Oracle NetSuite Help
• Install Your Commerce Website Applications, Oracle NetSuite Help
• 2025.1 Release of SuiteCommerce, SuiteCommerce MyAccount, and SuiteCommerce Advanced, Oracle NetSuite Help
• Migrate SuiteCommerce Advanced, Oracle NetSuite Help
• Available Commerce Themes and Supported Features, Oracle NetSuite Help
• Management Resources for Themes and Extensions, Oracle NetSuite Help
• What Resources Do I Need? and Customize with SCA Tools, Oracle NetSuite Help
• Site Builder versus Commerce Web Store Sites and Migrating from 3D Secure 1 to 3D Secure 2, Oracle NetSuite Help