Unique Coupon creation for flows
complete
D
David Suescun
Please allow defining a "template coupon" from our WooCommerce coupons to automatically generate unique coupons fay any given flow.
For example: If customers has spent more than X amount in the last year, send an email with a coupon for Y amount (unique to his profile) - this will discourage sharing the coupon as the customer would lose the benefit.
We currently do this with AutomateWoo and ShopMagic
_________________________
By Ken:
Birthday automations, like send custom coupon on birthday…we are currently doing this with the Groundhogg Birthday automaton/benchmark and API calls to the Smart Coupons API
Log In
Milad
complete
K
Ken Lyle
As of today, this appears to be closed. The team even captured my feature of +N days for expireation as well as user-specific. It appears to be one of those miracles where the 1.0 is perfect. I think that this one can be marked Completed, unless I missed something.
Milad
in progress
J
John SOYOO
For those needing this urgently, it's possible to create unique WooCommerce and Shopify coupon codes in a workflow with Pabbly Connect. Use webhooks to start the Pabbly Connect workflow
K
Ken Lyle
It's the two month anniversary of my last request for update. This is an actual feature that at least David and I are using in our existing platforms and are trying to move to Growmatik. It seems simple enough...adding a field to the coupon generator form, or a checkbox "Only for current user", then adding one parameter to your generate coupon function/call. Other than that, it seems like a standard WooCommerce coupon creation, and the whole task appears to be less than an hour. Can we please have some kind of estimate?
K
Ken Lyle
Is there any date on this? Please see https://woocommerce.com/document/smart-coupons/smart-coupons-rest-api/ , and try to get to at least that level of functionality and levaraging the Woo coupons. We use, like David, email restriction, plus expiration date (today + X days), number of uses, etc. to get a one person, one time coupon with a bit of urgency.
K
Ken Lyle
Here's a bit of detail on how we call this from Groundhogg...essentially, the key:value pairs we find most useful, and would like you to prioritize. It seems like you may not need the send_coupon one, because your coupons are always generated in the context of an email itself, as I see it.
Milad
planned