Price Of Single Item Different During Certain Hours

[Hasa]

Okay,

So im trying that now,

I created a new rule
Event Name: Order Added To Ticket
Custom Contstrain: Menu Item Name Equals Breakfast Special
Action: Change Order Price

Now What Haha?

Sorry im still learning.

[Jesse]

@Hasa

Sorry im still learning

Dont worry we all are what I meant was we can probably define some custom tags for those products… in your case that single product. When it is added to the ticket we can read it via Order Added Rule and we can make it check some constraints for the Custom Tag and for Time etc to determine which price it should be.

[Hasa]

Oh okay,

Well I have tryed everything I could think of with no luck, so any help would be greatly appreciated.

Thanks

[Jesse]

I will build a crude quick example that I think might work for you. Give me a few minutes

[Hasa]

Thanks Bud. Take your time.

[Jesse]

Notice I ended up not using the Custom Tags as I mentioned because you wanted just a single item. If you were doing multiple items or wanted variable items per hour you could use custom tags and read that tag instead of the actual Menu Item Name.

This is a great way to do Happy Hour… and BTW @Gerlandog Using this method along with Custom Tags might solve your issue you had long time ago with a trigger initiated Happy Hour… If you were in middle of an order that started before happy hour but it crossed into happy hour before the order was finished… you could simply cancel the order and re-add it and it would have correct price keeping the current ticket and all other items in tact so you would have no need to close the ticket to load a price list.

PS In fact I think this would be the best approach for Happy Hour.

[emre]

BS? What kind of a price tag is it?

[Jesse]

HAHAHA you caught me… play on words… it was Breakfast Special but you can interpret it how you like hahaha

[emre]

Great sample. I’m sure @gerlandog will love this idea as it allows to implement happy hour without using triggers and it immediately stop applying price tags if happy hour period ends in the middle of order adding process.

@Jesse

it was Breakfast Special

lol… I should think that at first place

[Hasa]

Wow thanks @Jesse Im trying it now.

[Hasa]

Okay, I just did it and even when I put time time contraint at after 01:00 and before 02:00 it still gives the discounted price.

Is another Action needed to revert it back to the normal price?

[Jesse]

Make sure you have matches all set

[Hasa]

Ahh Sorry. I did not. @kendash

It works.

Wow, I just tested it and it changes the prices on the fly without having to log out and clear the cache. This is awsome. Thanks @kendash @emre

[Jesse]

@emre the only way I could see to improve this is to add a Tag that could read the current Day. Maybe improve {DATE:X} so you can use it similar to {DATE:X}EqualsSaturday as a custom constraint? Or is this already available and I just have not figured it out yet?

[emre]

@Jesse

{DATE:X} Equals Saturday as a custom constraint?

Yes it is possible… @QMcKay knows how to do it

[Jesse]

Haha ok ok. I think I know what your referring too. I was hoping for a more simplified way.

[emre]

OK. I found it

[New 4.1.43] New Printer Template Tags

{DATE:X} This tag formats date as defined with X part. Here is a sample template. <L00>Year:{DATE:yy}-{DATE:yyyy} <L00>Month:{DATE:MM}-{DATE:MMM}-{DATE:MMMM} <L00>Day:{DATE:dd}-{DATE:ddd}-{DATE:dddd} <L00>Hour:{DATE:hh}-{DATE:HH} <L00>Minute:{DATE:mm} <L00>Second:{DATE:ss} <L00>Milisecond:{DATE:fff} <L00>AM/PM:{DATE:tt} <L00>Custom:{DATE:MMM/dd/yy hh:mm:ss tt} This template generates that output. [image] {TAX AMOUNT:X} This printer tag prints tax amount for a specific tax template. X part …

Not tested but {DATE:ddd} should return three letter day code. (eg sat,sun). I’ve referred @QMcKay because he tested it before

[Jesse]

Ok I was wrong lol that worked… Great thank you @emre.

So basically add {DATE:ddd} Equals Sat to make it run ONLY on Saturday. So in summary this method allows specific days and times of day to run a happy hour and it will react instantly in middle of an order… This is exactly what @gerlandog was wanting few months back I hope he sees this.

This would be a great way to run promotions too. I think I am going to really play with it some more. I could even use this.

[emre]

Also we can add a regex match like…

{DATE:ddd} Matches Sat|Sun

So it will work for Saturday or Sunday.

More details…

Automatic discount based on customer discount-level with set amounts per product

Yes it is what I’m thinking. We should change execution rule to Matches All and also decrease weekday check to a single constraint as {DATE:ddd} Matches Mon|Tue. This is not a general recommendation for everyone but as you’ve already have a product based discount implementation you don’t need price definitions for hh implementation. PS: I think something conflicts with :X so {DATE X} search returns better results. PS2: We might not need TN function for {DATE:HHmm} as greater/less comparisons…

[Jesse]

My goodness I have been not paying attention lately. I see that @QMcKay basically did this same thing in a more robust way already in a previous post. Well @Hasa you have several methods to think about hahaha.

The post I was referring too is here:

Automatic discount based on customer discount-level with set amounts per product

So it got me wondering, after looking at the gigantic Rule-set: Is it worth it? It looks overly-complex to me at first glance. Happy Hour in itself is fairly simple. As is VIP discounts. But put them together and it looks scary. I can’t help but think there must be some opportunity for optimization in there somewhere… Ticket States (named VIP) used: Active: customer has a VIP Level (1,2,3) InActive: customer does not have a VIP Level, or there is no customer assigned to the Ticket O…