Update Order Price with Portion and Price Tag

What your trying to do is not possible the way your trying to do it. I think we can figure out something for you though. The action is working as intended its not an issue with the action.

PM me a copy and i can work through it with you.

We can probably get something to work but Why do you want to consider it that same price tag when you changed the price… that logic doesnt sound right. Is it because your using those price tags for reporting?

Ok I have my answer.

During Live testing I was asked to Change a Price on the fly as often they would nominate a SPECIAL for the next hour/day on a Priced Item. The Thing is the Price could be Normal or it could be from a PRICE TAG.

Therefore through automation I was trying to allow a Price Change to write back to the DBO to change either a Normal Price “Regular” or a Price Tag “Happy Hour” , or “Trade”.

OK so its like I thought… your using it for reporting… may not be sambapos reports per say but your categorizing it with the Price Tag.

Really sounds like to me you should be using a Switch Menu system for Trade, and Regular pricing instead of Price Tags… keep Price Tags for your specials.

Well I guess if the UPDATE ORDER Action support a “Price Tag” variable I thought including that with “Price” it should work?

I wish to maintain the “Price Indicator” {PRICE TAG} on the final price as we can see where the original price before changed originated from.

I can send a backup do you wish for me to remove the extended parameters @Jesse?

Price Tag is there so you can change an order to a Price Tag price. Its not there just to label it.

Sure send me it we can play around see what we can figure out.

It not just a label it was also to change it to a new price as well. As Emre said his code was not designed to do that.

Compiling backup.

Order itself also have a Tag field that added to store some custom data related with order. I’m not %100 sure but Update Order action should have a parameter for that. This is not a feature used a lot so there might not be printing tag for that but if you find such additional area useful I can check that.

I’m leaving for now… (it is 6AM here) I’ll keep following that.

1 Like

That can work as can I store the Previous Tag in USE before I call the Update Order Action? I would be happy to use the following sequence:

  1. Save {PRICE TAG} name
  2. Change Price
  3. Change Price in DBO for saved TAG
  4. Call update Orders again with previous Tag.

Will just need to know how to read/write the custom tag…

You have the backup kendash for testing.

The other way of course would be to use {SETTING:x} to store the old {PRICE TAG}. Now I have confirmation on how it should work I would be happy to move down that route.

NOTE: Have changed topic to Question.

To be honest I think that would be the simpler approach. I am playing around with it.

Yes I agree.

The Yellow button is the new Price Change Button.
You can change Price Levels (PRICE TAGS) Ticket or Order Line.

Cascade “Hotties” has most Price Tags.

Excuse the pop-ups.

Ok its not changing price because of your portion price. Remove portion from it and it will change price but keep portion set. That is one small thing… still working though.

Ok I think you should rethink this business flow. I dont think it will work how your wanting it too. If you want the ability to define a set of prices but also alllow manual changes within that definition I dont think Price Tags is the way to go

Do yo mean in the RULE “ZRGE_Price Order Change” leave Portion parameter Blank? Did that but the price did not change?

Let me explain how that action works.

Price Tag will update an item to that Tags Price… Portion will update item to that portion price… You can not change those manually it reads them and updates order accordingly. So obviously if you try to set a portion thats priced as well as a price definition thats priced… itsnot going to work. So the only thing you can do with your specific setup is leave out portion and price tag and just change price of item…

1 Like

Ok - what I might do is restrict the ability to change a non-regular price. As you said it does not make good practise to have a 2nd,3rd… etc. price level to change the regular price BUT then want to change the price again.

Thank you for your explanation above. I am glad we explored these options.

1 Like

Reallly I dont see anything wrong with wanting to change price again… but it should be understood that once changed its no longer defined as the price tag anymore.

You CAN change price and keep portion name. I can show you how to do that.

Yes if you can please just to ensure I am doing it correctly.
Also can you think of a way I could disable or hide Price Change button if a non-regular price has been selected?

I know you going to say “States” but any other ways…

That is the only way to hide or enable buttons. Why look for other ways?

You simply make an invisible state called PriceTag and just feed it the actual name of the tag used.

Setup your action like this to enable changing price but keeping portion name.