Before looking at an item’s sales, you need to verify that your consumption data is accurate.

Please see our article on Troubleshooting Consumption for more information.

In a perfect world, your sales and consumption should be equal, but in most cases, your consumption will be higher due to over pouring and spillage.

However, there may be times when your sales value is much greater or less than the consumption value. This could be due to the following reasons:

  • Missing sales data
  • Incorrect / missing recipes
  • A different item sold in the POS vs what was actually poured
  • An archived POS Item
  • Open Liquor / Wine Buttons
  • Inventory Time Frame

Missing Sales Data

When you click into the details of an item on the Variance page, you can see how many sales there were for each POS Item it is an ingredient in. If you see no sales, or the sales are lower than expected, you can try refreshing your sales data.  
To refresh your sales data:

  1. Go to the Sales page on the WISK Web Portal
  2. Click the refresh button that shows when your data was last updated

The Sales page displays the total sales for each item for a defined period of time. You can click into the details to see the timestamps of each sale.

If you have a real-time sales integration, you may notice a large gap of sales in an inventory period. If your sales are being imported by a daily sales email, you may notice a whole day missing.

If the refresh does not restore your sales data, please reach out to support@wisk.ai or use the in-app chat to make sure your sales are uploaded.

Incorrect / Missing Recipes

When reviewing the sales for an item, you want to make sure that you have added recipes to all of your POS Items, and that the recipes are correct.

If you add the wrong amount of an ingredient, it can over or under represent your sales for an item depending on the quantity entered.

Different item sold in the POS

This often contributes to instances where you may see that sales are greater than consumption for a specific item. This could be due to under pouring, but it may also be due to an item being sold in the POS, but something else is actually poured.

For example, a less expensive item is punched, but top shelf ingredients are being used.

Typically you’ll be able to see the excess sales from one item reflected in the consumption of another. For example, if a Smirnoff Vodka martini was entered in the POS, but Grey Goose was used.

Archived POS Items

You may sometimes run into cases where you see consumption on an item, but there are no sales. If this was an item that you stopped carrying at some point, it’s possible you may have archived the POS Item (either intentionally or by mistake).

Just go to the POS Items page and search for the item by name. If it is archived, you’ll see text  saying there are archived results. Click the message to view them.

To restore an archived item, click the checkbox beside it and click Restore. The sales will once again be factored into calculations. 

Keep in mind that if you have new menu items, it is always best to create a new button in your POS. If you recycle buttons from products you no longer sell, the history is tied to the PLU number in your POS. If you recycle a button and change it to a new item, the system will think that you always sold the new item for all past sales.

Open Wine / Liquor Buttons

If you have an open button, you can’t currently add recipes to track everything that was sold.

Your buttons need to be as specific as possible to accurately track what is being used from your inventory every time the item is sold. 

If you have an open button, you will always have a variance.

Inventory Time Frame

When taking your inventory, complete it during a period where there are no sales in your venue. 

If an inventory spans multiple days and there are sales in your venue, this will impact your overall sales count. 

For example, if you start an inventory on Monday, but don’t actually save and submit the inventory until Wednesday, that will affect the sales for the next inventory period.

Did this answer your question?