SuiteCommerce
NetSuite 2019.1
2019-02-01

2019.1 SuiteCommerce & SCA Release — Bundle IDs and Install Requirements

The 2019.1 release of SuiteCommerce and SuiteCommerce Advanced ships as a set of SuiteApp bundles that require a NetSuite 2019.1 account. The page lists bundle IDs but provides no technical detail on specific feature changes.

Affects:SuiteCommerceSuiteCommerce AdvancedSuiteApp Bundles

Oracle's 2019.1 release page for SuiteCommerce (SC) and SuiteCommerce Advanced (SCA) is essentially a landing page. It lists the SuiteApp bundles that ship with this release and states the account-version prerequisite, but contains no technical detail on individual features, API changes, or configuration differences.

What's listed

The following SuiteApp bundles are associated with the 2019.1 release:

  • SuiteCommerce — Bundle ID 267288
  • SuiteCommerce Advanced 2019.1 — Bundle ID 273662
  • SuiteCommerce Configuration — Bundle ID 267359
  • SuiteCommerce Extension Management — Bundle ID 269415
  • SuiteCommerce Base Theme — Bundle ID 267294
  • SuiteCommerce Google Tag Manager Editor — Bundle ID 250341
  • Reference Product Lists Records — Bundle ID 53051

Key constraint

SCA 2019.1 bundles must be installed into a NetSuite 2019.1 account. Many features carry hard dependencies on 2019.1 platform changes, so installing into an older account version will fail or produce undefined behavior.

What to do

  1. Verify your account version. Before installing or upgrading, confirm your target account is on NetSuite 2019.1 (Setup > Company > Company Information, or check the release displayed in the footer).
  2. Install bundles via SuiteApp Marketplace or Managed Bundles. Use the bundle IDs above to locate and install each component. If you are on SCA, bundle 273662 is the core implementation bundle.
  3. Migrate customizations (SCA only). Oracle directs SCA implementers to follow the Migrate SuiteCommerce Advanced guide to pull new features into existing custom codebases. This typically means diffing the new reference implementation against your fork and cherry-picking relevant module changes.
  4. Check downstream integrations. Because the source page is vague on what actually changed in 2019.1, review the child release-note pages for specifics on any SC/SCA module, extension, or theme changes that could affect custom extensions, payment integrations, or SEO configurations.

Note: This page is a high-level table of contents. For actionable technical detail — new SC modules, deprecated APIs, theme-engine changes — consult the individual feature pages linked from Oracle's full 2019.1 release notes.