@Jesse is this what you meant from the other post where you said we could (for retail) not have any menu shown we could instead add automation commands to products to have the “menu area” set up like a retail system so all the buttons such as price change, discount, payment etc are in the “menu area” instead. I have created a dummy product called price change and assigned the price change automation command to it but it doesnt work, is this what you meant?
My thoughts were that as i have added the price change automation command to this dummy price change product that when i press the price change “product” on pos screen it would actually activate the price change automation instead of trying to add a “price change” product. So i could scan an item onto the ticket, press to select it and then press the price change button (from the menu area) to change the price
ideally if we can do a set up like this it would be great for retail, setting up dummy products to assign automation commands to so that they appear on the menu area instead of having any menu/categories showing as these are not needed for retail when we will just scan a barcode. this way we could create a “retail” screen where the menu and categories are with all the pos functions such as price change, discounts, payments etc etc or am i using the automation command column in the product editor incorrectly? or is just not designed to work like that?
Am I missing something. Isn’t that column category?
Edit! OK got it, it is fast menu. It doesn’t work because that price change is product itself (I think it change itself price, not Boys Moses Basket). I saw you have price change on automation button (left column). It will work there.
You can’t do order line automation with products. Create a order tag group with all order line automations map it to all products and turn auto select off. Use products for ticket automation like open drawer.
Use Order Tagged event to build your automation for order line commands.
The effect will be when order selected your POS menu on right changes to Order Line commands. Price Change, Void, No Tax, etc. Ticket based commands or system commands can be the actual menu and products/quick menu. You could even use Suffice/Prefix for reasons etc.
Cheers @Jesse ill have a play with this tonight i thought itd be an order line vs ticket issue but wasnt quite sure i was doing it right
@sukasem ive got retail and bar setup in one database at the min so with the retail setup i wont have any of the order line buttons on left hand side and no menu/categories on the right. Instead ill have my ticket auto commands on the right hand side (where the categories and products are now) and orderline auto command setup as @Jesse suggested above
@Jesse i take it then i will still need two screens? The main screen with all the ticket auto commands on and the order tag screen that appears after selecting a product from ticket to open the order line auto commands?
BTW @rickh you can automate database swaps… if you wanted to make command buttons for switching shops one press would swap databases so you wouldnt have to run on same database.
For that example yes. It makes sense and would be smoother operation with less chance of mistakes on operator side. I mean no accidentally pressing ticket based command while order selected. No accidentally pressing order based commands on entire ticket when no order selected. And the change is seamless simply select the order or deselect the order.
Yea thats something i still have to setup but wanted to do all the main setup specific to both then separate so that i dont need to copy things across or build them twice, just thought itd be easier to complete main setup first then copy database, rename for my retail setup and delete the bar department
BTW if you wouldn’t mind sending me a copy of your database I had some ideas I wanted to try using some of your setups. I accidentally erased the last copy you sent me.
also having some probs with the auto commands, none of my ticket ones seem to work, open drawer, abort (cancel transaction) when pressed nothing happens
i realised that i hadnt added portions for the “products” as auto commands, so that now works however as they are setup as products the auto command runs but adds the “product” to the ticket. is there anyway to stop it being added to the ticket?
it would be a good addition from a retail setup that if a product has an auto command assigned to it, it doesnt then add that product to the ticket it just runs the auto command instead, i dont know if thats doable or if it will affect other setups?
Try adding cancel order action into same automation command put it at top of list of actions in the rule. This is unconventional so would probably need to do a few tricks
Use Order Tagged event for the function you want. Are you using it to launch another automation command? If so there is no need instead run your actions and constrain it to the tag name.
thats one kink in the process sorted 
