Commerce Platform

This topic applies to

Applies to

SuiteCommerce Web Stores

Commerce Platform includes platform capabilities that you can use to build and deploy a more interactive and engaging shopping experience for customers. NetSuite 2018.2 includes the following enhancements:

Availability of Subscription Email in Multiple Languages

The Subscription Email feature enables you to send email to customers inviting them to subscribe to marketing email or confirm their existing subscription preferences. Prior to 2018.2, you could customize the email text in only one language. To better serve the needs of an international audience, you can now customize subscription email templates in all languages supported by NetSuite. You can customize the email subject and all other email text apart from the footer (which is identical for all bulk email sent by NetSuite).

Support for multiple languages is provided using System Email Templates. Standard System Email Templates are available in all supported languages for both the opt-in invitation message and the opt-in confirmation email message. Therefore, by default, customers receive the email in their preferred language. If you want to customize the email, you can modify the text of the standard email template or you can create your own custom templates. You can create custom templates in all languages supported by NetSuite. You can also insert NetSuite record fields into the template, including fieids from the Subsidiary record, such as subsidiary name and address. You need the System Email Template permission (available on the Permissions > Lists subtab) to create and edit system email templates.

All default and custom templates for subscription email are available in the new Marketing Subscriptions category of System Email Templates.

For information on how to create and modify subscription email templates, see:

Note

If you use customized text in subscription email messages at the moment, your existing customized email text will be converted to custom system templates automatically and the converted templates are selected by default on the Marketing Preferences page. However, you should review the converted templates for accuracy and verify that they are working as expected. In addition, you should ensure that the template has text available in your company default language.


System Email Templates for Web Store Email Messages

Prior to 2018.2, email messages related to web store transactions could be customized using either Web Store Email Templates or the Customize Text Groups feature. From 2018.2, you can also create and modify web store email messages using System Email Templates, which is the same method used for other types of system-automated email. System Email Templates are highly customizable and give you greater control over the appearance and content of email sent from your web store. For example, you can customize how ordered items are displayed and you can add product pictures.

System Email Templates are also ideal for an international audience because, if you have the Multi-Language feature enabled, you can set up multiple language versions of the same email template. Web store users receive the email message in their preferred language.

Mobile-friendly, default email templates are available for all web store email messages. You can customize these templates or create new ones.

For more information, see System Email Templates for Web Stores.

System Email Templates are available for the following web store email types:

  • Website Order Notifications

    • Order Received

    • Order Canceled

    • Order Approved

    • Order Fulfilled

  • Website Digital Delivery Notifications

    • Gift Certificate

    • Gift Certificate Confirmation

    • Download Available

    • License Code

  • Website Other Notifications

    • Checkout Errors

    • Password Recovery

    • Registration Confirmation (the existing System Email Template for this email type has been updated)

Suppose you currently have Web Store Email Templates or Customized Text Groups selected on the Website Setup record for any of the above email. With 2018.2, custom System Email Templates are created for you using your existing selections. You can also manually convert Web Store Email Templates or Customized Text Groups to System Email Templates. For more information, see Create System Email Templates from Web Store Email Templates and Create System Email Templates from Customized Text Groups.

After you verify that the converted templates are working as expected, you can select them on the Email subtab of the Website Setup page to activate them for use in your web store. For more information, see Select Email Templates for your Web Site. Web Store Email Templates and Customized Text Groups also continue to be available for use.

Note

Web Store Email Templates support only one language. If you choose to use a System Email Template that has been converted from a Web Store Email Template, you ensure that at a minimum, the template has text available in your company default language.


SuiteScript 2.0 for SSP Aplications

As of 2018.2, you can use SuiteScript 2.0 scripts within SSP applications and leverage the many advantages of SuiteScript 2.0. For more information about SuiteScript 2.0, see the help topic SuiteScript 2.0 Advantages.

To activate SuiteScript 2.0 for SSP applications, go to Setup > Company > Enable Features and select the new SuiteScript 2 Server Pages feature on the SuiteCloud tab. After the feature is enabled, you can use SuiteScript 2.0 in your SSP applications. You can also continue to use SSP applications that use SuiteScript 1.0. However, you cannot use a combination of SuiteScript 1.0 and SuiteScript 2.0 in the same SSP application.

The major differences between SuiteScript 1.0 and SuiteScript 2.0 SSP applications are:

  • Different syntax is used in SuiteScript 2.0 and SuiteScript 1.0 scripts – SuiteScript 2.0 scripts used in SSP applications must begin with a declaration that they are written in SuiteScript 2.0. This declaration is not required in Suitescript 1.0. For more information and examples, see Sample SSP Application Code (SuiteScript 2.0).

  • Explicit deployment required for SuiteScript 2.0 SSP applications – to be accessible on a website or domain, an SSP application must be explicitly deployed to that domain or site. Deployment to a website means that it is accessible from all domains associated with the website.

  • Single SuiteScript 2.0 SSP application permitted per path – you cannot deploy more than one SSP application to a single URL root.

  • Touch points are not supported for SuiteScript 2.0 SSP applications – Instead of touch points, SuiteScript 2.0 SSP applications use a default SSP file to store the logic of which script should be triggered when the user accesses different parts of the website. At present there are no NetSuite SSP applications that contain a default application file, however, you can develop and use your own.

    The ability to select a default application file for a domain or website will be available in a future release. In 2018.2, SSP applications that use SuiteScript 2.0 can be used for:

    • Backend processing, for example, logging.

    • Services on the website, accessible using a direct link to the URL root at which it is deployed.

For detailed information on creating, installing, and deploying SuiteScript 2.0 SSP applications, see SuiteScript 2.0 SSP Applications.

Automatic Cache Invalidation Improvements

The 2018.2 release introduces performance improvements for the Automatic Cache Invalidation feature.

Beginning in 2018.2, group invalidation requests are used to reduce the number of individual requests during bulk upload. When applicable, multiple path invalidation requests are replaced with a single wildcard invalidation request. In addition, frequently modified content is not cached on CDN to enhance processing performance.

For more information, see Automatic Cache Invalidation.

Search Engine Access to Shopping Carts

Prior to 2018.2, search engine spiders (also known as bots or crawlers) were restricted from following the add item to cart links on SuiteCommerce websites. This restriction has been removed in 2018.2.

To prevent bots from following links to items on your website, which results in the items being added to the shopping cart, use the industry-standard file robots.txt. This file is used to inform bots which areas of the website should not be processed or scanned.

For more information, see How to Create the Robots.txt File.

Secure Hosted Web Pages

The Hosted Web Page domain type can now be created as a secure domain. See Set Up a Web Store Domain for more information.