There is a status field in the coupon value (nms) table. This field has an enumeration of Available or Consumed.
We are using an individual coupon and then calling the coupon code from the coupon table (nms) in a delivery template to add it into the template.
When this happens - it is an out of the box function. But it doesn't update the status of the coupon from available to consumed. This is completely different than redeemed and nothing we do flips the coupon to consumed.
What good is a status of the coupon value being assigned if it doesn't get updated. It doesn't get updated when the coupon is redeemed either. It always says "Available." How can we get this status to flip to "Consumed" when they are assigned? It should do it automatically if we use the delivery template coupon assignment in the advanced tab on the delivery template.
Hi @hetfidd ,
Have you written code to change status of coupon when attached in delivery?
If it's out of the box, you need to trace and find where exactly is the fault. You can check which function is called when coupon is added and does that function performs status update? If yes, then is the status correctly updated.
We had the same issue and the only solution could come up with was to create a different scheduled workflow to update the status.
The status is stored in "nms:couponValue" schema. All the used coupons are linked to a broadlog record.
If the status is Available and message-id>0, then you can set the status to "Consumed" or you can extend the "nms:couponValue" and set to different enum value according to you requirement.
I have come to believe the status "Available" means coupon not yet used because either it was not assigned to anyone or not redeemed by the recipient.
Can someone confirm this?
But rest assured if your coupon cant be re-assigned, it wont be if its linked to a delivery.
No, we haven't been able to crack this. It seems like a bug in the module that it wouldn't look at the start and stop dates entered. The individual coupons are picked automatically (only the available ones) because the coupon campaign has been selected in the advanced tab of the delivery template. However, it ignores the dates for start and stop if we use this method. Not sure why - but it causes us issues. We have to delete all unassigned coupons if we have a new batch with new start/stop dates.