Manage > Products > Menu List > [Menu] > [Category] > Edit Product Properties
Use the Order Tag section as a comma-separated list of the Tags that are generally on a Pizza, such as:
Pizza Base
Pizza Sauce
Cheese
The Tags are case-sensitive, and there should be no spaces before or after a comma!
Then if there are other Tags for a certain type of Pizza, for example, Hawaiian, continue with the applicable Tags, like Ham and Pineapple. So your Order Tag list might look like this for the Hawaiian (again, note no spaces around the commas):
!Meat > Negating Match > Not tagged as `Meat`
*Meat > Ending Match > Ends with `Meat`
* Meat > " " > Ends with ` Meat` (word)
?\bMeat^ > Regex Match > Ends with or equals Meat
@Flight52 last two answers to your question are different approaches to your issue. Q’s suggestion works great as it lists all optional (removable) indigents on kitchen print even they are default so kitchen staff does not need to remember if selected product does have mushroom by default or not. So I strongly suggest you to implement @QMcKay’s suggestion.
Thank you for the help, I’ve been without internet for 2 days, so a late reply.
I like this way.
If I understand it correctly ! -Mushroom will add mushroom to the inventory. So if a pizza has mushroom in the recipe, the recipe will consume 1 mushroom and the order tag will add 1, ending up with 0 consumption. correct?
So I create 1 Inventory Item called Mushroom, 1 Product that consumes 1 Mushroom, 1 Recipe for the Mushroom Product and 2 Order Tags. 1 called +Mushroom to add extra Mushroom to a pizza and 1 called ! -Mushroom to not use Mushroom on a pizza, both linked to the Product, Recipe, Inventory Item called Mushroom.
I then run a sale through, selling 1 P2 pizza (that normally consumes: 1 Pizza Base, 100 Marinara Sauce, 140 Mozzarella Cheese, 10 French Salami, 1 Mushroom and 1 Green Pepper), using the Order Tag ! -Mushroom.
Thank you for the information on how to Edit product properties, it is something I’ll definitely keep in mind, and I haven’t seen it anywhere else in the forums. In fact it could easily be part of the original tutorial.
For me unfortunately it won’t work.
My serving staff, speak English, my customers speak English, my kitchen staff neither speaks, reads or writes no English, only Thai. So in the kitchen we have a recipe for each pizza in Thai (and English for me) and codes for the pizza (P1, P2 etc). At the moment when we receive a modified order the serving staff will write on the orderpad:
P2
-เห็ด (Mushroom)
so that the kitchen staff can read it.
If they received an order for a P2 with only 4 ingredients listed instead of 5, they would have to exit the kitchen and ask which one it was. And even worse, if they received an order for a P2 with 5 ingredients listed (1 added, 1 removed) they would just assume it was a regular pizza and make that.
And unfortunately my printer cannot print Thai, only Chinese and English, that’s what I get for buying a cheep printer
This is the only product I need. For indigents like mushroom, cheese we don’t need products or recipes.
I created 3 order tags for Pizza. I only set prices and mapping. We’ll solve product mapping in recipe. Mapping an order tag to a product here useful for menu setups like mapping tags to menu products like Coke, Fanta, etc… So product Mapping should remain blank.
Now this is the important part. When I click on No Cheese order tag I want it not to decrease cheese. I don’t want it to add something back to inventory. I just won’t decrease cheese. Let’s update the recipe.
So I should create an original pizza recipe, that contains every Pizza Inventory Item. Then clone it for all the different pizza, and order tag ! for all standard ingredients and “More” for the rest?
I even got it to work with Order Tag Prefix, Except, when I add a Prefix, it ignores cost. Is there a way around this?
Think I sorted it. I add a new Order Tag: + Green Pepper with a price of 10. It doesn’t show up on the order screen (I guess because it has the Prefix written in the name?), But it modifies consumption and price!!!
Which gives me an idea.
Would it be possible to create a list of Order Tags, 2 for each Inventory Item, a NO and an ADD, add the Prefixes NO and ADD. And then the Order Tag would only appear on the order screen if the Prefix was selected?
Try setting up filter for order tags as * so they’ll appear only when a prefix button is selected.
Additionally you can set filter to ! to make an order tag appear when no prefix is selected or just write a prefix name to make it appear when that prefix is selected.
The problem now is, that when an Order Tag is selected, it adds the prefix before the Order Tags name which includes the Prefix already. (+ +Cheese instead of +Cheese) and it doesn’t use the price from the Order Tag either.
Did you follow the tutorial or did you just follow the picture?[quote=“QMcKay, post:2, topic:8148”]
Your Consumption will be reported by Transaction Unit if you do not leave it blank. So if it is defined as Case with a Multiplier of 12, when you sell 1 Can, your consumption will report 1 of 12 = 0.833 of a Case Consumed, with Instock level reported as 0.916 of a Case left. This is not useful in scenarios such as this.
If you leave Transaction Unit blank, your Consumption will be reported by the Base Unit. Most of the time Base Unit Consumption makes more sense. So when you buy 1 Case (of 12), and sell 1 Can, you will see Consumption reported as 1 Can, and your InStock level will be reported as 11 Cans left.
[/quote]
The checkbox beside Additional Units makes it your default Transaction Unit for Purchasing. However, the Consumption will still be reported by the Base Unit unless you have the Transaction Unit defined.
Consumption is never reported by Additional Units, no matter if the box is checked or not. You must define the Transaction Unit.
To define the Transaction Unit as “Case” when you already have an Additional unit defined with the same name, you need to change the name of the Additional unit first (ie. rename it to “CaseA”), then save the Inventory Item, then re-open it, define the Transaction unit as “Case” with a non-zero multiplier, then save it again. Then you can go in one more time and delete the Additional Unit if you want.
The Tags are case-sensitive, and there should be no spaces before or after a comma!
I’m preparing some screenshots for you.
