This notice applies to customers who are using a Web Store Developer Kit (WSDK) solution with different domains. With this setup, WSDK does not work properly on Chrome browsers. You must make changes to ensure that your domains will work on all browsers.
What Is Changing?
Last year Google introduced changes for Chrome that limit sending cookies when doing cross-site requests. When your external catalog site for WSDK (e.g. www.example.com) is using a different domain than your NetSuite shopping page (e.g. 123456.shop.netsuite.com or cart.netsuite.com), Chrome browsers do not pass cookies correctly. This means that a customer can add an item to the external cart, but when they visit the NetSuite-hosted shopping cart (or checkout page) several minutes later, the cart is empty.
Since Google made this change, the best way to use WSDK on Chrome is to use the same domain for your external catalog, shopping, and checkout pages. For example:
- For external shopping catalog: www.example.com
- For NetSuite shopping: cart.example.com
- (Optional) For NetSuite checkout: checkout.example.com
For more information on the changes to Chrome and SameSite cookies, see https://www.chromestatus.com/feature/5088147346030592 and https://web.dev/samesite-cookies-explained/.
Required Actions
Recommended Action
You should move your NetSuite shopping page to the same domain as your external catalog site and update all links to the new shopping URL. To do this:
- Set up a Web Store Only domain in NetSuite. Ensure that this domain is a subdomain of your external catalog domain. For example, if your external catalog domain is www.example.com, you could set up the following Web Store Only domain: cart.example.com.
- For more information, see the help topic Set Up a Domain, SuiteAnswers ID 78143.
- Secure your new Web Store Only domain with an SSL certificate.
- For more information, see Secure Your Domain in the help topic Set Up a Domain, SuiteAnswers ID 78143.
- Deploy your new shopping domain.
- For more information, see Deploy Your Domain in the help topic Set Up a Domain, SuiteAnswers ID 78143.
- Mark your new shopping domain as the Primary Website URL on the Website Setup record.
- Ensure that all links on your external shopping site point to your new domain.
- (Optional) Set up a new Checkout Only domain using the same domain as the external shopping catalog and NetSuite shopping sites. This is not mandatory but is recommended to keep the domain names consistent. Repeat steps 1-3 for this new checkout domain.
Workaround
The following option is not recommended and is not a permanent solution. If you do temporarily use this method, you should still follow the Recommended Action listed above as soon as possible.
As a workaround, you can continue using a cross-site setup, but you must change the type of communication to WSDK by editing your website HTML. Modify the Add Item To Cart HTML so that the method is changed from POST to GET. Use the example below, and for more information, see Integrating your WSDK HTML (bullet point 7) in the help topic Setting Up an External Catalog Site, SuiteAnswers ID 27647.
Example for "Add to cart" links on your external shopping page:
To use this method, you must be aware of Chrome’s SameSite cookies policy, as future updates may make this workaround obsolete. To ensure that your site meets these qualifications, you should move your NetSuite shopping (and checkout) page to the same domain as your external shopping site, as outlined in the Recommended Action section above.
For more information on WSDK, see the help topic Best Practice for Creating an External Catalog Site (WSDK), SuiteAnswers ID 63973.
If you have any questions, please contact NetSuite Customer Support.