Body: <p>I know you can limit how many times in total a discount code can be used, but how do you limit how many times a single person can use it? We want to offer our members a discount on 3 of our one kind of training. There are many of these each year, so they would pick which ones. We don't want them to be able to just keep using the code beyond 3 and we don't want to have to create a unique code for every single person. Is there a way to limit that so they can only use it 3 times?</p>
  
  <p>Also, is there any way to also limit to by a membership?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-03T00:24:08.847Z
Comments.Text: Do you have a budget? For the first requirement perhaps extending https://github.com/civicrm/org.civicrm.module.cividiscount would be a valuable cause?
Comments.UserDisplayName: Zachary
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-03T05:50:58.403Z
Comments.Text: No, other than maybe a small amount, no real budget (it would be me paying for it out of my own pay). What will happen is they'll just create (and later delete once used) a custom code for every single person when they get/renew their membership. I've seen a number of people on here request this same thing, but they never got any answers to their posts. This is a basic on every other discount module I use across CRMs, CMSs, store software, etc. I'm surprised such a basic is missing here.
Comments.UserDisplayName: Jenni Simonis
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-03T18:34:58.403Z
Comments.Text: That was going to be my suggestion, one code per person. The tables for civicrm_discount are not difficult to work with, might be a way to bulk create them
Comments.UserDisplayName: Zachary
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-03T23:32:37.400Z
Comments.Text: Would credit work as a workaround - instead of a percentage - a set amount?
  Also - I don't see any issues in the issue queue related to this - would be worth while opening an issue - developers might not know this is something worth doing.
Comments.UserDisplayName: themak
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-04T04:39:46.580Z
Comments.Text: They'll be creating them as people buy/renew memberships. There's no way they would be able to deal with any kind of auto-creation. This is only for like 10% of our 10,000+ database, so we definitely don't want to be creating them for everyone in the db.
Comments.UserDisplayName: Jenni Simonis
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-03-04T04:40:13.977Z
Comments.Text: Credit? What do you mean? Maybe I've missed that.
Comments.UserDisplayName: Jenni Simonis
Tags: <cividiscount><discounts>
Title: Limit discount usage per person
ThreadText: # Limit discount usage per person
  
  (Asked by: username_0 on 2020-02-28)
  
  I know you can limit how many times in total a discount code can be used, but how do you limit how many times a single person can use it? We want to offer our members a discount on 3 of our one kind of training. There are many of these each year, so they would pick which ones. We don't want them to be able to just keep using the code beyond 3 and we don't want to have to create a unique code for every single person. Is there a way to limit that so they can only use it 3 times?
  
  Also, is there any way to also limit to by a membership?
  
  **Tags:** cividiscount, discounts
  
  > **Comments:**
  > **username_1**: Do you have a budget? For the first requirement perhaps extending https://github.com/civicrm/org.civicrm.module.cividiscount would be a valuable cause?  
  > **username_0**: No, other than maybe a small amount, no real budget (it would be me paying for it out of my own pay). What will happen is they'll just create (and later delete once used) a custom code for every single person when they get/renew their membership. I've seen a number of people on here request this same thing, but they never got any answers to their posts. This is a basic on every other discount module I use across CRMs, CMSs, store software, etc. I'm surprised such a basic is missing here.  
  > **username_1**: That was going to be my suggestion, one code per person. The tables for civicrm_discount are not difficult to work with, might be a way to bulk create them  
  > **username_2**: Would credit work as a workaround - instead of a percentage - a set amount? Also - I don't see any issues in the issue queue related to this - would be worth while opening an issue - developers might not know this is something worth doing.  
  > **username_0**: They'll be creating them as people buy/renew memberships. There's no way they would be able to deal with any kind of auto-creation. This is only for like 10% of our 10,000+ database, so we definitely don't want to be creating them for everyone in the db.  
  > **username_0**: Credit? What do you mean? Maybe I've missed that.  
  
  ---
  
  ## 0 answers
  
  