VIP and Happy Hour Discounts without Triggers. Happy Hour Discount overrides VIP Discount…
- 1 less State (VR)
- 5 less Rules that previously handled VR and updates to PriceList
- 1 less Action (Execute Automation Command wasn’t necessary)
- number of Actions being fired inside various Rules reduced substantially
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
Order States (named DiscountType
) used:
<>
: (blank) when an Order is first added; to be updated toND
,HH
, orVIP
ND
: No Discount (same as blank, but easier to identify and work with)VIP
: VIP Discount as defined byD1/D2/D3
Product TagsHH
: Happy Hour Discount as defined byHH
Product Tag; overridesVIP
HP
: Happy Hour Pending (temporary holding State while we chech the Item Order Time against the HH Window) to be updated toHH
orND
.
DB Tools Import Files:
Automation: Discount_VIP_HH_Automation.zip (2.1 KB)
VIP Order Tags: VIP_OrderTags.zip (588 Bytes)
HH Order Tag: HH_OrderTags.zip (563 Bytes)
Customer Entity Type VIP Level
field:
Happy Hour Order Tag:
VIP Discount Order Tags:
Product Tags:
Edit Discount Amounts in the Product Tag Editor:
Set your Happy Hour Days and Times via Rules:
Printer Template:
[<J00>Total FREE:|{ORDER STATE TOTAL:Gift}]
[<J00>Discounts:|[=F(TN('{ORDER TAG TOTAL:Discount}')+TN('{ORDER TAG TOTAL:VIP Discount}')+TN('{ORDER TAG TOTAL:HH Discount}'))]]
[<J00>TOTAL SAVINGS:|[=F(-1*(TN('{ORDER TAG TOTAL:Discount}')+TN('{ORDER TAG TOTAL:VIP Discount}')+TN('{ORDER TAG TOTAL:HH Discount}')+TN('{ORDER STATE TOTAL:Gift}')))]]