We're an enterprise customer with locations across multiple time zones. If I create a time-based menu or a time-based price, whatever I use for the times are applicable in that form across all time zones. Example, an item's price shifts between 3p and 6p to a dollar less. That 3p to 6p is 3-6 ET & 3-6 CT & 3-6 MT, etc. Which is what I would expect.
However, when we create a discount that is available to all locations but only during a specific time, again 3-6p, the times shift across zones. Example, If i'm logged into a location in ET and set the discount to 3-6p, that's what I get in ET. BUT, the discount is now available 2p-5p CT and 1p-4p MT!
What I've been forced to do is create a restaurant group for each time zone, add the correct locations to the appropriate time zone groups, then create versions of the same discount with each of them relevant to their own time zone.
C'mon man! Can someone tell me if I'm missing anything? If not, can someone please submit this to Product as a flaw? We're expanding to the west coast soon and having to create four groups and four versions of a discount is a LONG way to go as a workaround to functionality that already exists in other avenues (menus/menu items).
