Promotions allow you to create custom discount strategies over your cart based on a coupon/gift or for a particular user or even a combination. Promotions can further have other properties that allow us to control how they will be used. In this section we shall discuss all the use cases.

The above is a Dashboard of promotions. One can configure this dashboard based on project needs, by default the above view holds.

Setup of a Promotion

Field NameDescription
NameA System wide unique name for the promotion
Display NameA user friendly name that could also be used to be dsiplay on the website (implementation dependent)
TypeThis defines the nature of the promotion. Interpretation of this value is based on the promotion strategy implemented by the developer. The default states supported are : CAMPAIGN, DISCOUNT, PROMOTION, REFUND, PENALTY
Validity Date Rangeif specified, marks the date range the promotion isvalid inclusive of the boundary dates.
ActiveSometimes we may want to keep the promotion in our system, but de-activate it or pause it. A checked sign means its active.
DescriptionAn optional description (may or may not be displayed on the end user site)
EligibilityDefines under what additional conditions is the user eligible to avail the promotion
Eligibility > Max usage CountHow many times the user can use the same code
Eligibility > Min Cart ValuePer usage, what is the minimum value of the cart
Discount AmountWhat amount and unit should the discount finally be offered if the user is eligible. The amount could be a full value or a of the Sub-Total. Note: One can also have more complex scenarios based on the implmenetation of the promotion strategy for the website.

hotmail arrow-hotmail box-hotmail yahoo arrow-yahoo box-yahoo coupn-code arrow-coup-code box-coupn-code

Generating Coupons

One can generate coupons for users based on their userId token (emailid by default or a code or a combination of both). The admin can paste a comma separated list of tokens / addresses (or as a column from Excel also), into the box and then click Generate Coupons For Users. This will auto generate a coupon code for each user. However sometimes we may want to provide a coupon code without knowing which user will use it; in that case one can explicitly provide a coupon code with a  : , infront of it. The following examples of tokens, make it clear:

abc@hotmail.comWill grant a random Coupon code to this user to use. The coupon code can only be used by this user. For this to work, your Coupon section must also support an input to determine the user (if the user is not logged in) grant a HJHWESSU Coupon code to this user to use. The coupon code can only be used by this user.
:P12345Will allow anyone to use the coupon code.

Beyond the basic definition of types of tokens defined above, it is upto the developer to implement this custom to application needs using the promotion strategy.
Note: By default, generating coupons will not send any notification. This is to allow the user to check or verify. To send a notification to users with emails, the Notify All button has to be used.

Deleting Coupons

Follow the same principles for the token definitions while generation. Once pasted in the text box, click the Delete Coupon For Users.
Note: The listing also supports Bulk Actions, so its possible to show a checkbox infront of each coupon in the listing and have a Delete button to delete them. This can be configured via the Backend, even though its not available in the default view. Something similar to how Delete Bulk action works in the catalog. Similary other custom actions can also be configured.

Nofitying users

Notify Users, will send an email (based on template associated), to all emails mentioned in the Users text box. It will further validate if the email is within the list of users who are granted coupons. If not, it will not send to random users.

Promotion Strategy

The admin interface only defines, what control variables to setup to guide the promotion process. However the final nuances on how to deal and calculations are implementation dependent. This implementation is defined by the developer in the Promotion Strategy. For example, one may also have items on SALE in the cart and as part of your promotion polocy you may not want to grant discount on sale times. So you can program the strategy to only consider the cart sub-total minus of any SALE items already in it. Speak to your developer on how you wish to refine the strategy. Another point is, one can add more control variables to the Admin interface, for a more complex custom strategy (should it be needed).

Back to Top