Aloha Price Changes & Events 1

[ccTexas]

Hello - we have 4 levels of prices and I accomplish this using System Events and Price Changes under Menus. This weekend one of the events did not activate. Has anyone had this occur and why do you think it happened. I've been told to reenter the event, but I won't know it works until next weekend so I'm looking for other ideas to make sure it works.

Thanks -

 

[RokStar]

The two most common causes are:
1) that your D.O.B. (Date of Business) doesn't match your system's date.
2) You have an event that is overriding a previous event.

You can turn on event debugging in the Aloha system settings, then view the debout.txt file from the TMP folder off of terminal 1. The first thing aloha does after starting should be to fire the events.
It will tell you which events are firing, and in what order.

To test events, I usually fire a series of "One-time" events several hours before the business opens. One that would fire a price change, then later to change it back. Then you can test them and make sure they are firing before the weekend. (And i would just check the debouts to see if they are working.)

 

[DTSMAN]

If one is overriding another this is the heiarchy of the events.
Special overrides monthly.
Monthly overrides weekly.
Weekly overrides dailly.

Bo

Kentucky phone support-
"Mash the Kentrol key and hit scape."

 

[ccTexas]

I did not have any overlap, but I did have the switchover time at the same moment. Here's the info from the Debout that showed it fired.

Aug 23,
23
05
00
[4294898757]
firing 23:05:00 DISABLE PRICE CHANGE 400 0

Aug 23,
23
05
00
[4294898757]
firing 23:05:00 DISABLE PRICE CHANGE 300 0

Aug 23,
23
05
00
[4294898757]
firing 23:05:00 SET PRICE CHANGE 301 0

Aug 23,
23
05
00
[4294898757]
firing 23:05:00 SET PRICE CHANGE 500 0

 

[RokStar]

So, the events fired. Good, that eliminates some t-shooting.
It tells us your events are not corrupted, and do not need to be reentered. Also, your dates match and your events are firing as normal.

Price Change 500 is the last one to fire, so it is the price change that is active.

If 500 is not the change that you want to be active, then there is a heirarchy problem.

The question is, why do you have two price changes firing on the 23rd? Which one is a daily event, which one is a weekly, etc...

You need to figure out why 500 is overriding 301.

The quick and dirty way to do it, is to have price change 301 fire at 23:06.
That would ensure that it would be the active prices, but it won't help you understand how the events are currently working. Your choice.

Also, I am assuming that you are NOT using corporate, or store level events, right? (Do the files 'events-c.cfg' or 'events-s.cfg' exist in your data folder). Or CDM???
If you are, then there are a lot more places to look for the problem.

 

[ccTexas]

I have a "D" bar price just for liquor and a "D" food price for everything else. So I disabled both the "C" Bar and the "C" Food, and enabled "D" Bar and "D" Food. They both cover different items so there is no overlap of items. They are both "weekly" and we have been doing this this way for YEARS. I am not on the CDM system, although I am familiar with it and we hope to use it someday as we have 4 different stores with HUGE menus that change alot. I changed the disables to 23:04 pm and the enables at 23:05 pm for this weekend to see if that helps. The only thing different between last weekend (which didn't fire the D prices) and the weekend before was that I changed the price changes for the D level from the C level to the D level. Before we would continue to charge the C prices at the D price level.

There isn't any sort of limit on the number of price changes in a day? I would assume not.

Carolyn

 

[RokStar]

This is confusing (to me):
I changed the price changes for the D level from the C level to the D level. Before we would continue to charge the C prices at the D price level.

But it must be related to the problem somehow.

Start at the basics.
Find out what exactly failed.
The debouts you presented say that the events did NOT fail.
If the event fires, the price change goes into effect, then there is still incorrect pricing, then it must be the price change.
Look at the debouts closely. Those are your best clues.

But your original complaint, about the events not activating, is no longer valid (If the debouts say so). It is something else. Are you sure that 301 & 500 are the right Pricing? Did the numbers get mixed up?
Keep looking in to it, you'll find it.

(And no, no limitation on Price changes per day)

 

[ccTexas]

Thanks - I'll look at it again and see if I see anything that may be causing it.

Thanks again.
Carolyn