Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Micros 3700 Coupon SIM
- Thread starter Wildbar
- Start date
Well, we've done similar things with food vouchers for employees, I made one from a place where they can print out bar-code coupons at the bottom of their checks, and I've done another that let them scan coupons.
Which kind of coupons exactly are you looking for? Coupons that aren't tracked with one-time use reference codes are considerably easier, but if you are willing to create a custom table to track it, it really isn't all that hard to create a simple SIM for managing it. You don't even need an interface back-end if you are only running them for that one individual site; can do it all with the SysUtils DLL.
Any specifics exactly on how you want the coupons to be displayed and work?
Which kind of coupons exactly are you looking for? Coupons that aren't tracked with one-time use reference codes are considerably easier, but if you are willing to create a custom table to track it, it really isn't all that hard to create a simple SIM for managing it. You don't even need an interface back-end if you are only running them for that one individual site; can do it all with the SysUtils DLL.
Any specifics exactly on how you want the coupons to be displayed and work?
- Thread starter
- #3
Looking for something like a coupon we can give to unhappy guests to encourage them to comeback. We would either print it at the pos as a standalone or add it to the bottom of a copy of there bill. Preferably a prompt for the amount so the manager can give what they think is needed but preset amounts could work to, $10, $20, $30 etc Thinking a 3 month expire date. We do have the Icare module but cant figure out how to program adhoc coupons, nor can our Micros programmers (although the documentation says you can) To make it easy I don't think we would track them We would just redeem them to an open $ discount.
Are you planning to do bar-codes or just a message?
That would be really easy actually. The easiest one of course is the stand-alone because you don't have to figure out how to store any variables for that coupon.
Adding it to the copy of their bill isn't that hard either though; I would probably create a placeholder menu item that isn't linked anywhere and has a non-print print class, and then through an inquiry that checks for their SIM permission level, apply the menu item to the check. Then I would have a custom footer event that scans for the placeholder, if it is on the check, it then produces the coupon at the bottom. Preset amounts are of course easier in this scenario because we can just use a separate placeholder for each amount, but it is possible to do it with an open amount as well. I would go with a placeholder simply because it means a manager could add it to the servers check and then not have to worry about it later; it would just print when the server finishes out their table; otherwise you could also do it as part of the final check print which would be even easier, but would also require the server to get you then, and you might be busy.
Finally.. if you're willing to invest the time to do it.. ESC/POS does support a limited set of borders (I'm willing to give you an example SIM with everything except that part because I've never done that part) so you could even make the coupons prettied up.
That would be really easy actually. The easiest one of course is the stand-alone because you don't have to figure out how to store any variables for that coupon.
Adding it to the copy of their bill isn't that hard either though; I would probably create a placeholder menu item that isn't linked anywhere and has a non-print print class, and then through an inquiry that checks for their SIM permission level, apply the menu item to the check. Then I would have a custom footer event that scans for the placeholder, if it is on the check, it then produces the coupon at the bottom. Preset amounts are of course easier in this scenario because we can just use a separate placeholder for each amount, but it is possible to do it with an open amount as well. I would go with a placeholder simply because it means a manager could add it to the servers check and then not have to worry about it later; it would just print when the server finishes out their table; otherwise you could also do it as part of the final check print which would be even easier, but would also require the server to get you then, and you might be busy.
Finally.. if you're willing to invest the time to do it.. ESC/POS does support a limited set of borders (I'm willing to give you an example SIM with everything except that part because I've never done that part) so you could even make the coupons prettied up.
Also.. the more complicated but in my opinion cleaner route (I'm not the most experienced with Micros given I've only worked on it for about ... 9? months now, so I don't know if this is best practice) but I might also consider going the separate table route rather than adding a placeholder. That way if a server decides to get cute and do repeats on the placeholder and transfer it off or silly things like that.. well, they wouldn't be able to. It would store the check sequence number and only print if it finds a coupon listed for it, which would also make open amounts much easier.
- Status
Similar threads
- Locked
- Question
- Locked
- Question