![]() LP fixed this issue in a latest Micros release. Using the Micros 3700 system some merchants are not able to sell more than 1 gift card per transaction as they get a “duplicate” transaction message when trying on the second card. We don't believe this is fixable by us especially since Micros requires points entry on a POINTS_REDEMPTION operation, which is how the Redeem Value function) has to be structured) to support cash back rewards issuance. We don’t touch the SIM file upon installation and are not capable of making any changes to it. A merchant advised that he spoke to Micros about this, and Micros said it was something in the SIM file causing this. After research, this observation appears to be a restriction within Micros that cannot be changed. Micros merchants have expressed it would be nice to have this default as well since clerks use this button more frequently then Redeem Gift Only. When clerks use the 'Redeem Value' button however, the Micros “Enter Amount” field is blank and forces the cashier to have to enter the amount of the sale. Merchants think this is nice and the cashier just has to hit enter. When clerks use the 'Gift Redeem Only' button, the Micros “Enter Amount” field defaults to the total of the sale. Enter Amount Default Setting on Redeem Value Button There are a number of ways the tracking can be setup and because these changes require accessing the SQL tables, it is recommended these updates be performed by an experienced Micros technician. While it does not affect the functionality of the system, if these items do not get added to tracking, the Micros sales/revenue reports will not balance properly when gift/reward cards are sold or redeemed. The exact names for each of the items are as follows: A Micros technician familiar with your installation needs to dial in and update the tracking (reporting) to include the "GC Recharge", "Redeem Gift" tender and "Redeem Rwds" tender. rewards transactions inside Micros reports. We have encountered instances where the Redeem Value function that withdraws gift balance first followed by reward balance next does not always classify gift vs. Rewards Redemption Reporting in Micros System For now, we recommend using the Fraud Monitor to flag suspicious clerk activity to get a more focused snapshot of the server's activity on the system. There is no current programmatic solution to prevent this from occurring. However, there is a loophole if the server transfers the check to themselves under a NEW check number, thereby adding more rewards to a different patron's account for what really is the same ticket. Only one (1) patron account should properly earn rewards on a unique ticket. The host is programmed to reject earning rewards for the same ticket on two separate loyalty cards. Server Fraud by Transferring Check under New Check Number.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |