Testing and Deploying Themes in SuiteCommerce
Testing themes locally enables effective verification before deployment in SuiteCommerce. This guide walks through the essential steps.
TL;DR
Testing themes on a local server in SuiteCommerce allows developers to verify customizations before deploying them to NetSuite. This article covers the necessary steps for both testing and deployment, ensuring a smooth transition from development to live environments.
How to Test a Theme on a Local Server
Before deploying your theme to NetSuite, it's crucial to test it locally. This process lets you preview frontend changes without affecting the live site. Here's how to effectively do it:
- Set up your environment: On your local machine, open a command line interface and navigate to your top-level development directory.
- Run the testing command:
Warning: This command also updates thegulp theme:local
manifest.jsonfile. If you have made manual changes that you want to preserve, use the following command instead:gulp theme:local --preserve-manifest - View your theme: To see your changes, navigate to the local version of your application using one of these URLs:
http://<DOMAIN_NAME>/c.<ACCOUNT_ID>/<SSP_APPLICATION>/shopping-local.ssphttp://<DOMAIN_NAME>/c.<ACCOUNT_ID>/<SSP_APPLICATION>/my_account-local.ssphttp://<DOMAIN_NAME>/c.<ACCOUNT_ID>/<SSP_APPLICATION>/checkout-local.ssp- Note: Replace
<DOMAIN_NAME>and<ACCOUNT_ID>with your specific configurations.
How to Deploy a Theme to NetSuite
After thoroughly testing your theme, the next step is deployment. This will enable it for use on your website domain. Follow these steps:
- Access your environment: Open your command line or terminal and navigate to the top-level development directory.
- Deploy your theme with the command:
For accounts that require specific domains, append your account number to the command.gulp theme:deploy
- Enter deployment information: Depending on your setup, you may need to provide the following details during the first deployment:
- Authentication ID: This is the ID that represents your NetSuite account and role. If you've created one previously, it will be reused for future operations.
Warning: Similar to testing, the gulp theme:deploy command updates the manifest.json file, potentially overwriting manual changes made to it. To avoid this, use:
gulp theme:deploy --preserve-manifestConclusion
Properly testing and deploying your themes in SuiteCommerce requires careful execution of commands and understanding of your specific environment settings. Following the outlined steps will ensure that your changes are effectively reflected in your live web application.
Source: This article is based on Oracle's official NetSuite documentation.
Key Takeaways
- Local testing is essential for verifying theme customizations.
- Use
gulp theme:localfor testing andgulp theme:deployfor deployment. - Preserve your changes in
manifest.jsonby using the appropriate flags during commands.
Frequently Asked Questions (4)
Do I need to run any specific command to test SuiteCommerce themes locally?
How can I prevent the 'manifest.json' file from being overwritten during local testing?
What information is required during the first deployment of a theme to NetSuite?
How can I ensure my manual changes to 'manifest.json' are not lost during deployment?
Was this article helpful?
More in Commerce
- Available Items Only Feature in NetSuite 2026.1
Available items only filtering boosts sales efficiency in NetSuite 2026.1 with Intelligent Item Recommendations.
- Commerce Extensions in NetSuite 2026.1
Commerce Extensions in NetSuite 2026.1 enhance performance and user experience in eCommerce.
- Convert Multiple Transaction Line Items into Configured Items in
Enhance transaction processing in NetSuite by converting multiple line items into configured items with improved session handling.
- New SuiteCommerce Features in NetSuite 2026.1
New SuiteCommerce features in NetSuite 2026.1 enhance user experience and improve eCommerce efficiency.
