MyVenue
Creating & removing products
How to create a new mvManager product, make it available at the right locations, and remove a product from sale without disrupting historic reporting.
In this article
Create the product
Open mvManager and go to Products > Products.
Select the + button to add a product.
Check the Code. mvManager normally fills the next available code, but it can be changed if your site has a required numbering structure.
Enter the product Name. This is the longer reporting name.
Check the POS Name. This is the name shown on POS keys, kiosks, mvMobile and customer ordering screens, so keep it short and clear.
Select the correct Product Type. Use None for a basic sellable item, Recipe for a sellable item made from ingredients, and Supplied for stock or packaged items purchased from suppliers.
If the product will be sold, tick Sellable and enter the required selling prices on the Pricing tab.
Complete the product setup
On the Settings tab, assign the Category and any required GL Codes.
Add an image if the product will be visible on POS keys or customer ordering screens.
Assign POS or patron modifiers if the product needs choices such as sauces, cooking options, or add-ons.
Assign POS Groups if the product needs to print or display with other similar items, such as bar or kitchen items.
On the Families tab, select the families for the locations where the product should be available.
Save the product before adding barcodes, recipe ingredients, suppliers, or product matrix settings.
Remove a product from use
If the product should no longer be sold, remove it from the relevant menus and families rather than deleting it immediately.
If the product appears in a family because a whole group or category is included, edit the family source in Products > Families instead of trying to remove the inherited product on the product record.
If the item is part of a recipe, open the recipe and remove the ingredient from the Recipe tab where appropriate.
Review any reporting, stock, recipe, barcode, supplier, or menu dependencies before permanently deleting or reusing a product code.
Checks before saving
- Confirm the product is in the correct family for every location that should sell or count it.
- Confirm the POS Name is readable on a POS key.
- Confirm each active price level has the correct price.