Maintaining Themes and Extensions in SuiteCommerce

Understand how to manage themes and extensions in SuiteCommerce, including version control, manifest files, and delivery options.

·2 min read·View Oracle Docs

When developing and maintaining themes and extensions in SuiteCommerce, it's crucial to utilize specific resources and strategies effectively. This article delves into key aspects of management, particularly focusing on manifest files, version control, and delivery options.

What is a Manifest File?

The theme and extension developer tools automatically generate a manifest.json file for each theme and extension created. This file contains essential information for compiling resources related to that theme or extension, including its name, description, version, and other metadata that appears in the SuiteCommerce Extension Manager within NetSuite.

Note: Typically, there is no need to manually alter this manifest file; however, in cases where new Sass files are added, you may need to introduce corresponding Sass entry points. Also, if you wish to exclude certain local assets during testing or deployment, manual edits can be made. If you opt to alter the manifest, keep in mind that updates made through gulp commands will overwrite these changes unless you employ the --preserve-manifest flag.

Why Implement Version Control?

Version control is vital when deploying themes and extensions to NetSuite. Each time a deployment occurs, developers are prompted to specify a version number, which is then stored in the manifest. NetSuite conducts a version check during deployment:

  • If the version already exists, any existing files will be overwritten.
  • If it doesn't exist, NetSuite will create new records for the theme or extension.

Having a robust version control mechanism helps ensure that stable versions are maintained and prevents accidental overwrites of working themes or extensions.

Delivery Options for Themes and Extensions

Apart from deploying themes and extensions to your NetSuite account, these can be bundled as SuiteApps. This feature allows distribution to other NetSuite accounts, broadening the reach and usability of your custom themes and extensions.


By focusing on the effective management of themes and extensions, developers can greatly enhance their SuiteCommerce implementations, ensuring a seamless and functional user experience.

Key Takeaways

  • Manifest files serve as vital resources for compiling themes and extensions.
  • Version control is essential to avoid overwriting stable releases.
  • Delivery options enable broader distribution of themes and extensions.

Source: This article is based on Oracle's official NetSuite documentation.

Frequently Asked Questions (4)

Do I need to manually modify the manifest file when adding new Sass files to a theme or extension?
Yes, when you add new Sass files, you should manually introduce corresponding Sass entry points in the manifest file. Be cautious, as updates made through gulp commands will overwrite changes unless the `--preserve-manifest` flag is used.
What happens if I attempt to deploy a theme or extension with an existing version number?
NetSuite will overwrite any existing files if you deploy a theme or extension with a version number that already exists. This underscores the importance of maintaining accurate version control to prevent unintended overwrites.
Can themes and extensions be distributed to other NetSuite accounts?
Yes, themes and extensions can be bundled as SuiteApps, which allows them to be distributed to other NetSuite accounts, enhancing their reach and usability.
Is manual intervention required for version control when deploying themes and extensions in SuiteCommerce?
When deploying, developers must specify a version number that is stored in the manifest file. This version control process is necessary to avoid overwriting stable releases, ensuring the integrity of the themes and extensions.
Source: Maintaining Themes and Extensions Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Commerce

View all Commerce articles →