Watson Commerce Ideas

Order Management, Inventory Visibility, Store Engagement, Watson Order Optimizer, Call Center and CPQ are now a part of Watson Supply Chain. Please bookmark the Watson Supply Chain Idea Portal.

Submit new product ideas for Watson Commerce Offerings including Digital Commerce, Websphere Commerce, Watson Content Hub, Watson Commerce Insights, Dynamic Pricing, Price Optimization, Promotion Optimization, Markdown and Deal Management. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.

Connect with your peers and IBM experts on the Watson Marketing and Commerce Community and the Order Management Interest Group, now a part of Watson Supply Chain.

Submit ideas for other Watson Customer Engagement Products:

  • Watson Marketing
  • Watson Supply Chain

Ability to use WC_PERSISTENT cookie to retrieve cart from different eSite stores

We are using REST APIs to implement persistent cart. We have partial authentication enabled for cart API. Here is the issue we run into for registered users. In our system we have enabled user's registered customer role in multiple esite stores such that when the user log in to one storeA, he does not need to log in again for storeB. The WCToken and WCTrustedToken can work across different esite stores. 
1. Call loginidentity REST API with store A with updateCookies=true&rememberMe=true
2. Retrieve WC_PERSISTENT cookie from the response.
3. call get cart REST API passing WC_PERSISTENT for storeA
4. We can retrieve the cart successfully from storeA
5. call get cart REST API passing WC_PERSISTENT for storeB
6. Even though the user has a pending cart in storeB, we are getting an empty cart. Looks like, unlike WCTokens, the WC_PERSISTENT does not allow access to a different store unless we call loginidentity for storeB beforehand. 

We expect the WC_PERSISTENT works across different stores without having users to log in to each esite stores specifically.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Apr 11 2019
  • Needs review
How will this idea be used?

Customer has many eSite stores. Shopper can register once and be able to access multiple stores after logging into one store. They would like to have persistent carts working across multiple stores. For example, the customer could have shopping cart in each eSite stores. They logon to one store first, and if session expires, they expect the WC_PERSISTENT cookie to let the shopper see the shopping carts in each eSite store without logging into each store specifically.

What is your industry? Education
What is the idea priority? Medium
DeveloperWorks ID
Link to original RFE
  • Attach files