Hotcakes Wish List Module


You've likely seen wish list functionality on any number of sites out there.  In fact, sometimes, the "wish list" is named something else entirely.  Example of this include lightbox, closet, rack, bookshelf, and other terms depending on the store and its branding.

A wish list allows a customer to save a product they want for purchase later.  This is often useful so they don't have to look for it again, especially in stores with larger product catalogs.  Sometimes, several product may look the same.  So, as a store owner, allowing a customer to have a way to prevent them from accidentally purchasing the wrong product or to remember a product they wanted, only helps to increase your chances of converting that customer later.


The following prerequisites will be necessary to accomplish the goals of this article:

  • Have access to your Hotcakes store administration
  • Configure your store using the getting started wizard or do it manually
  • Have one or more products added to your store catalog

Getting Started

The information provided here is based upon the default configuration of Hotcakes and the default viewset. Your views may have more or less functionality, depending on how it was implemented by your technical team.

Wish List Module

If you used the getting started wizard to setup your store, this module will already be available for you in the Hotcakes Store menu, on the Wish List page.  Depending on how your store has been configured since, you might find it somewhere else in your site.

When a customer first views the module, they won't see any products listed.  They'll need to add at least one product to the wish list before this changes.

Customers can add products to their wish list at any time by clicking the "Add to Wishlist" button on the product details page/view.  This is normally located somewhere nearby the "Add to Cart" button.

Once there's at least one product in the wish list, you'll see the products begin to be listed as shown below.  You'll see the primary image of the product, the title, description, and it's price.  You'll also have the ability to immediately add the product to the cart for purchase, or remove it from the wish list.

If you have more than 50 products in your wish list, only the first 50 will be shown.  In a future update, when you have more than 50, they'll be displayed in a paged format.  Each page will have up to 50 products in it.

Module Settings

This module doesn't have any module settings specific to the store wish list functionality.

Viewset View Location

You'll find the views for this module in the following location in your viewset:


Module Placement

If you used the getting started wizard, this module will initially be placed on the Wish List page, under the Hotcakes Store navigation menu.  In your own store, you'll likely want to move it to be somewhere else on your site.  You may even find yourself renaming the module and/or page to more closely match the branding of your company (at least from your customer's perspective).

In general, there's nothing to keep you from moving and renaming the module in nearly any way.  However, in most stores, the customer will expect to find the wish list in their user account/profile area and/or in the top-level navigation.  You should keep this in mind if you choose to move this module or page.


This module only works as expected when the customer is logged in.  At this time, there's no benefit or functionality change when making the module publicly available to all visitors.  Until the customer is logged in, the module won't have any idea how to look up the wish list items to display.  As such, you should ensure that this module is only ever on a page that is available to customer security roles that you know are logged in.  For example, in the image below the page is visible only to "Registered Users" which is a built-in security role that requires the customer to be logged in to be a part of.

You can also make the page more public if you have the need to.  In this case, you'd simply want to make sure the module itself has view permissions to only show itself to security roles that require a logged in user account.  In the example below, it was first necessary to uncheck the "Inherit View Permissions from Page" checkbox.  Only then could we override when this module is shown to the customer.

Have more questions? Submit a request

Need More Help?

Do you need more assistance with this article? Please review your support options.