In addition, SCS is unique from SCA in the following ways: SCS offers no direct customization of source code. SCS only supports a single site/domain. SCS is only customizable via themes and extensions. SCS offers no customization of the checkout flow. SCS is not susceptible to “version lock” due to core customization.
Tag: scs
Transferring Information From Netsuite Back End to Site Front End Using a Suitelet
It’s possible to make a call from an SCS website frontend to the backend via a suitelet. There may be security implications to calling a suitelet from the frontend. Please consult your Team Lead before attempting this, This gives you the ability to get information from the backend, load, edit and create records, call other… Continue reading Transferring Information From Netsuite Back End to Site Front End Using a Suitelet
Resolve Items Could Not Be Added to the Cart in SCA/SCS
Scenario At times, adding items would not be possible on the webstore when the item record has been misconfigured. This solution would help you resolve a specific scenario where items could not be added to the cart with the Browser Developer console showing the following errors: “/app/site/hosting/scriptlet.nl?script=customscript_scs_loggerendpoint&deploy=customdeploy_scs_loggerendpoint“ The following error is returned because there seems… Continue reading Resolve Items Could Not Be Added to the Cart in SCA/SCS
SuiteCommerce Standard (SCS) vs SuiteCommerce Advanced (SCA)
SuiteCommerce Standard (SCS) SuiteCommerce Advanced (SCA) Provides an optimzed web store frontend that delivers shopping, checkout and account management capabilities supporting B2B and B2C Provides an optimzed web store frontend that delivers shopping, checkout and account management capabilities supporting B2B and B2C Provides support for Netsuite Extensibility API, Theme, and extensions to be installed that… Continue reading SuiteCommerce Standard (SCS) vs SuiteCommerce Advanced (SCA)
Test a Theme on a Local Server
In your local developer environment, open a command line or terminal and access the top-level development directory. Run the following command:gulp theme:localWarningPotential data loss. Besides compiling and deploying your theme to a local server, the gulp theme:local command updates the manifest.json file for the theme. This action overwrites any manual changes you made to this file. To… Continue reading Test a Theme on a Local Server
Issues associated with the feature “payment instrument”
While enabling the feature ‘payment instrument’, There are some issues with the ‘edit’ option. The standard fields are non-editable If the user tries to ‘edit’ the existing card after enabling the feature ‘payment instrument’, The expiration month will set default to ‘1’. Since the fields are not-editable, after clicking the ‘Update card’ or ‘cancel’ option… Continue reading Issues associated with the feature “payment instrument”