Retail:Promotions Best Deal Case
It provides implementation for "Combo" Discount Rule.
Best Deal Case is an alternative mechanism to apply promotions in WebPOS. When working in this mode the way promotions are applied varies from the standard definition in two manners:
- Each line is limited to be applied just one discount. Even Apply Next is allowed, only one promotions is applied. When working in Best Deal Case mode, all promotions behave as they were No Apply Next.
- Best Deal Case algorithm is executed just before paying the ticket, at this point the best possible combination of discounts is applied to the ticket. The best possible combination is the one that maximizes the discounted amount.
How it works
When working in Best Deal Case mode, discounts are applied while products are added to the ticket in the same manner than when working in Standard mode with the difference that, at most, only one discount is applied per line.
When the Pay button is tapped, Best Deal Case algorithm is executed to try to get the best possible discount. If a better discount than the previously calculated one is found, ticket is modified to apply it.
The algorithm that looks the best case, splits the lines that can have different discounts with more than one unit per product in several lines with one unit each and combines all the possible discounts for each of them to obtain the best one.
Because of this in case the number of possible combinations is big, the algorithm can take its time to perform the computation. The more Discount rules are applicable to a product, the more combinations it needs to check.
Best Deal Case mode is enabled at Store level. From Organization window, for Store organizations, Best Deal Case for Discounts and Promotions field is visible, by selecting it, all terminal defined in that store will work in this mode.
When this field is flagged, a new one is shown: Stop Long Best Deal Case Execution. Due the algorithm needs to evaluate all possible combinations, it can occur it to take long to execute. If this field is flagged, the algorithm stops in case the number of combinations to evaluate is too high. When this happens, the ticket remains as it was without trying to find a better set of discounts.