coupon with maximum uses per customers, also for guest checkout (use email)

[apiuser]

Feature request from seansan, posted on GitHub Dec 01, 2014

When a coupon is made with maximum uses per customers. Then one would expect it to check the database for an order from that customer (and we have the email). Or at least an option: if not logged in, check email too.

So the option use coupon once only counts logged in customers

When there should also be a check for (unique) email counts per order for guest checkouts

This would be great to add. We have a customer who has ordered every month the last year with a coupon code that can only be used once per customer. It is not closed loop solution: but checking for an already existing order from the email you would solve 99%

http://magento.stackexchange.com/questions/4785/magento-coupon-codes-only-one-coupon-guest-customer

[apiuser]

Comment from rex-z, posted on GitHub Jun 21, 2016

@Hi there, It has been more than a year. Was there any update? Will this feature exist on Magento 2.0?

@sonalagr , for now you will have to set the promo code to be valid for logged in customers only (remove NOT LOGGED IN option). Another option is to use auto generation code so every code is unique, and make it one time use storewide.

[apiuser]

Comment from tkacheva, posted on GitHub Jun 21, 2016

@rex-z coupon enhancements is a part of promotion scope. Follow the roadmap updates

[apiuser]

Comment from seansan, posted on GitHub Jun 21, 2016

@tkacheva : "Follow the roadmap updates"

Where can these be found? (did not know this either)

[apiuser]

Comment from tkacheva, posted on GitHub Jun 22, 2016

@seansan they are given at magento live and imagine conference

[apiuser]

Comment from seansan, posted on GitHub Jun 22, 2016

OK. THX

FYI Would be really good to have this online somewhere.

On Wed, Jun 22, 2016 at 11:49 AM, Olena Tkacheva notifications@github.com wrote:

@seansan https://github.com/seansan they are given at magento live and imagine conference

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/magento/magento2/issues/776#issuecomment-227695902, or mute the thread https://github.com/notifications/unsubscribe/AAn0a9dy9poI98HqJzhKeqWlDIM1jQgtks5qOQUggaJpZM4DCmmn .