Answer general questions related to product recommendations, specifically in the context of Point of Sale CMS and its integration with Salesforce Einstein.
For instructions on how to configure Salesforce Einstein in the CMS, refer to this article. POS Access List–URLs and IP Address
Prerequisites:
Refer to POS Access List–URLs and IP Address for a list of permitted URLs and IP addresses. This is to turn on the necessary communication.
If a customer integrates Einstein via Salesforce, how can they pull recommendations into the Point of Sale (POS) app?
For instructions on how to configure Salesforce Einstein in the CMS, see Configure Product Recommendations for Point of Sale.
Specifically, which APIs are being called, and what permissions are required if there are OCAPI calls used?
- Einstein-based Product Recommendations were built with Demandware—OCAPI
- OCAPI Used—
Are there specific configurations that are required?
For instructions on how to configure Salesforce Einstein in the CMS, see Configure Product Recommendations for Point of Sale.
Is it assumed that all products that are in retail are also on SFCC? If not, how do you reconcile differences between the two systems for making requests and receiving recommendations?
There are products in the store that aren’t in Einstein and vice versa.
What additional data streams are required to fill out the product data that aren’t in the data that comes from Einstein?
Point of Sale makes a call for recommendations only on PDP. We pass the product ID to the API and receive product IDs in response. We show only those that are available in our system as users can go to those products on the POS.
Are the recommendation calls made from the Cloud instance or directly from devices?
The calls are made from Point of Sale.