Skip to main content
All CollectionsWISK Inventory - FAQPOS (Point of Sale)
What is the importance of mapping POS items?
What is the importance of mapping POS items?

Determine the cost of your drinks / dishes and how much inventory is used each time an item is sold in your POS

Nick Neale avatar
Written by Nick Neale
Updated over 2 years ago

Article Contents

Introduction

The purpose of mapping your POS Items is to create a definitive link between the dishes/drinks you sell and WISK inventory products.

When you sell a drink or dish, WISK knows the cost and how much of each ingredient is used based on the mapping.

This is essential for identifying variances. Your variance compares a product's consumption to a product's sales.

In other words, it compares how much you actually used to how much you theoretically used based on your recipes and the number of items sold.

Consumption

Consumption is the difference in stock counts from one inventory to the next while taking invoices, returns, and depletions into consideration. It doesn't consider sales at all.

In other words, it's how much you used of an item in an inventory period. If measured in $, this is known as the cost of goods sold.

Sales

For products that find themselves in multiple POS Items—lets say a liquor sold by the shot, single, full unit, or in several cocktails—it's necessary to have POS Item Mapping in place to link each POS Item's PLU with the associated WISK product.

Let's take the following Belvedere sales for example:

Belvedere Shot (1 oz) x 10 = 10oz

Belvedere Single (1.5 oz) x 5 = 7.5oz

Vodka Cocktail A (2 oz) x 6 = 12oz

Vodka Cocktail B (0.5 oz) x 2 = 1oz

If all these items contain Belvedere, then properly mapping these POS Items will tell us that you sold a total of 30.5 oz of this product. We can then compare this value to the actual consumption to see if there had been any overpouring or theft.

If any items are not properly mapped, we would be comparing the consumption to wrong sales total and so that variance would not be reliable.

Did this answer your question?