Legacy platform

Customer profile

A store associate can find the information of a customer in the customer's profile:

  • Customer's basic details: A store associate can view the basic details such as the customer's name, phone number, address, email-address, birthday and membership type.
    The icons that represent the membership types are controlled by a predefined CSS class. The class name is in the following format:
    app-icon-member_<member_type_common_code_value in lowercase>_40
    Therefore, to add font icons for custom membership types, you must implement a CSS class with a name in the same format. For example, app-icon-member_silver_40. For more information, see Working with font-icons.
    Customer’s email address and phone number are displayed from the customer's contact and not from customer's address. Customer's addresses are displayed with the following precedence:
    1. Default Bill To address
    2. Default Ship To address
    3. If no address is marked as default, the first address created for the customer would be considered.
  • Recommendations: Product recommendations based on customer's order history.

    The generic service YCD_StoreGetRecommendedItemList internally invokes an external service configured in the "Service to be executed for fetching recommended products" rule, to fetch the product recommendations. The output of the service is then passed to the getCompleteItemList API, which is called to display the recommended products on the UI. The number of products displayed in the Recommendations tab depends on the value configured for the "Number of recommended products to be shown in UI" rule. By default, three products are displayed.

  • Recently Viewed: Products that the customer recently viewed on an online shopping interface.

    The generic service YCD_StoreGetLastViewedItemList internally invokes an external service configured in the "Service to be executed for fetching last viewed products" rule to fetch the recently viewed products. The output of the service is then passed to the getCompleteItemList API, which is called to display the recently viewed products on the UI. The number of products displayed in the Recently Viewed tab depends on the value configured for the "Number of last viewed products to be shown in UI" rule. By default, three products are displayed.
    • Product Search Keywords: Keywords used by the customer to search products on an online shopping interface.

      Product keywords that are searched by a customer on an online channel are displayed in the Recently Viewed tab of the Customer Profile screen. Most recent keywords are displayed first. The keywords are retrieved based on the customer details such as CustomerID and CustomerKey.

      A generic service YCD_StoreGetItemSearchKeywordList internally invokes an external service configured in the Service to be executed for fetching products of keyword search rule, which provides the implementation to retrieve product search keywords for the customer from an external system. The value configured for the Number of products from keyword search to be shown in UI rule controls the number of keywords displayed on the UI. By default, three keywords are displayed.

      When a store associate clicks product keywords, the products matching the keywords are displayed. The searchCatalogIndex API is called to search for products in the catalog index based on product keywords. Basic product details such as the product image, description, SKU and price information are displayed.

  • Wish list: Products that the customers have saved on an online shopping interface, with an intention to purchase later.

    The generic service YCD_StoreGetWishList internally invokes an external service configured in the "Service to be executed for fetching customer's wish list” to fetch the products in the wish list from an external store front. The output of the service is then passed to the getCompleteItemList API, which is called to display the products in the Wish List tab of the Customer Profile screen. The number of products displayed in the Wish List tab depends on the value configured for the "Number of wish list products to be shown in UI” rule. By default, three products are displayed.

  • A mini cart is displayed on the Customer Profile screen. When the store associate clicks the cart icon, a pop-over displays the customer's products and their details. The latest draft order created for the customer in the current store is used to display the mini cart. The getCompleteOrderLineList API is called to get the list of products in the cart. A Remove button is displayed next to each product, which a store associate can click to delete the product. When the store associate clicks the Remove button, the modifyFulfillmentOptions API is called with the Action attribute set to "REMOVE" to delete the product. Once a product is deleted, the mini cart is refreshed.
    Note: If you want to implement a different logic other than using latest draft order to display the mini cart, you can do it by customization.
  • Open Carts: Customer's open carts from an online channel.

    The Open Carts tab displays the products from the customer's open carts on an online channel. The generic service YCD_StoreGetOnlineCartList internally calls the external service configured in the Service to be executed to display online cart products in store rule to call the second service, which has the implementation to connect to the external system and fetch the open carts for the customer. Once the carts are retrieved, the getCompleteItemList API is called to get the UI ready item list details.

    The store associate can click a product to view the product details. The getItemAvailabilityForStore API is called to retrieve the availability of the product for all delivery methods.

    The store associate can either add all products or a single product from the Open Carts tab to the store cart. When the store associate clicks the Add All To Store Cart button, it adds the products to an existing draft order. If there is no draft order for customer, then it creates a draft order and adds the products to it. Alternatively, the store associate can select a product from the Open Carts tab and click Add to Cart from the Product Details pop-up window.

    If the cart lines do not have a delivery method, it is defaulted to CARRY. If a cart line has PICK as the delivery method and does not have an associated store, then the delivery method will be CARRY.

    The Mini Cart is updated when the products from the Open Carts tab are added to the store cart. The store associate can click the Mini Cart icon and then click Checkout to continue creating the order. When the View Cart screen loads, the getOrderFulfillmentDetails API is called to get the availability of the order lines.

    The notifyCartStatus service is called every time an item is added from an online cart to a store cart. The service reads the Service to be executed to notify the online channel about products added to store cart rule to call the external service that has the implementation to notify the online channel.