Hi Milos,
I am user of your module to generate coupon for next customer purchase. We made some test with a customer in a debug group (not the standard Customer Group).
The module is configured to generate voucher each time the customer made 2 orders (for this we select the option Reward counters based on Generated Coupons) and the orders are SHIPPED (in Italian language the shipped status is CONSEGNATO)… but voucher are never generated.
The best is if you can check the configuration of the module.
Note, the shop is a LIVE multi shop, in the back office you have to work in the "Shop 1" store. At this moment I have suspended the module, you have to enable it before to try it.
Voucher code for next order
hello,
let me explain two available workflows in the module
- Reward counter based on VALID ORDERS This option will count all orders of user, even old ones.
If you will define range: (for example) to generate reward for 0-5 orders - module will generate it only one time if number of placed orders is between 0 and 5 - Reward counter based on GENERATED COUPONS This option will count rewards that customer received, it will not count old orders.
If you will define range: (for example) to generate new reward for 0-5 orders - module will generate it each time the counter will fit to defined range
Now I can focus on the settings you use
- you created rule:
- please focus on "coupons from 2 to 2"
- this will be second reward that customer will receive (coupons from 2 to 2)
- so module will generate this reward if customer previously received 1 coupon. Simply saying - customer firstly must receive 1 coupon to get this reward. - Cron Job
you enabled feature to generate and send coupons with cron job
- module will send coupons only if you will run this url manually or with task defined in cron job
I created "first reward":
Then i created test account in your shop
- placed first order - i received "first coupon" reward
- placed second order - i received "manes" reward
(to receive rewards i had to run cron job - see explanation above)
screenshot:
0 comments:
Post a Comment