Exception: Demo shop
The demo shop has its own unique half-day definition based on a four hour or greater rental duration, so the Auto-Sale Rule for contract items associated with the demo shop is different. The half/full day definition is much smaller because there are no “exception” dates based on the time of day that the check-out occurred.
Rule nickname | Rule configuration | Rule description | Rule explanation |
DAYS-DEMO | CONVERTDAY(0-870,>=660,30-240,HALF) CONVERTDAY(0-870,>=660,>240,FULL) | Days – demo shop | If a rental check-out occurred before 2:30 PM and that same rental was not returned by 11:00 AM and the duration of the rental on that same day was between 30 and 240 minutes, sell a half day rental. If a rental check-out occurred before 2:30 PM and that same rental was not returned by 11:00 AM and the duration of the rental on that same day was over 240 minutes, sell a full day rental. |
This Days-Demo Rule would be used in a PREPROCESS command configured for the demo shop just as the DAYS rule above is used in the PREPROCESS command for all of the other rental shops.
Rule nickname | Rule configuration | Rule description | Rule explanation |
PREPR-DEMO | PREPROCESS(SUB(EXHANGE)SUB(DAYS-DEMO)) | PREPROCESS- demo shop | Go through the entire rental period and identify exchanges and day types. |
The alternative PREPR-DEMO rule would then be inserted into the rule attached to demo shop contract item (all other sub rules could be re-used assuming that the auto-sale items, exchange precedence, etc., pieces were consistent between the shops).
Rule nickname | Rule configuration | Rule description | Rule explanation |
CONTRACTDM | SUB(PREPR-DEMO) SUB(DEMOS) SUB(SPORT) SUB(REC) SUB(BOARD) SUB(TELEMARK) SUB(XC) SUB(BIKE) SUB(HELMET) SUB(SNOWSHOES) SUB(GROUPDAYS) | Contract demo Auto-Sale Rule | Preprocess the rental activity associated with the contract to determine what type and level of equipment is counted in exchanges and also determine the various rental day types and number of these day types, within the rental period. Next, auto-sell the appropriate items based on the activity associated with the rental contract after the preprocessing has occurred. Finally, group the same day-type/auto-sold item combinations together on one line item per unique combination and increment the # of rental days on each unique line item as opposed to listing each day’s type and auto-sold item on separate lines. This is necessary to enable Dynamic Pricing capability based on multi-day rentals. |
Note: Rental items that do not have a Rental Auto-Sale Rule assigned may now have a line item quantity greater than one. This allows multiple contracts for a large group to be entered on a single line item. In the past, rental items are restricted to Qty < = 1. Primarily this is because the trans_no is used as the unique Rental form number. In most cases this isn't an issue, because guest information is being added to each rental, along with modifiers, etc.
If however, DeferRentals=TRUE is set at salespoints, this presents a problem. These salespoints are configured to sell rental items without collecting guest information, because the guest info is entered later at a Self-Entry station, (and then matched up with the previous transactions using Sales Host utility).
Typically DeferRentals stations are often used for group rentals that need to sell, for example, 100 Basic Ski Packages. Operators have to enter 100 individual line items instead of setting the quantity of one line item to 100.
This enhancement allows rental items without a Rental Auto-Sale Rule to have a line quantity greater than one.