Pressing the + icon in one of the layers prompts you to create a discount. Based on your role functionalities you'll then be allowed to either select Creating new discount (from scratch), Create discount from template (a discount with some prefilled and non-editable discount variables), or you'll have both choices available. Editing discounts also flows similarly.
After making a selection (from template or new), tapping next will take you through some steps. For new it'll be five to six steps as follows:
- General information
- Financial information
- Coupons (Trigger type Coupons only)
The two main parts of a discount are conditions and actions. In its very essence a discount works as follows:
If conditions x and y are met, action z will be triggered.
With this in mind, we can elaborate on discount triggers.
There are four trigger types:
- Price rule
- Generated coupons
Trigger type Price rule indicates that the given action will be automatically applied, as soon as all conditions are met.
Trigger type Manual indicates that the given action can be manually applied, as soon as all specified conditions are met.
There are two permissions that impact in-store use of manual discounts. Permissions are managed from the Roles and rights chapter namely, from the functionalities card of a users role.
Show manual discount related functionalites
|Functionality name||Scope when functionality Manage is ticked|
|ApplyManualDiscount||Enables in-store associates to Apply manual discounts on orders|
|CancelManualDiscount||Enables in-store associates to Cancel manual discounts on orders|
Further, the above stated discount permissions can be elevated in combination with the use of the setting
Security:ElevatedFunctionalityProvider and a value of TemporaryElevationCode, or ElevationBarcode.
When setting trigger type to Coupon, conditions are not mandatory. For coupon discounts, the given action will be applied as soon as the coupon code is given. If conditions are specified, these have to be met before the coupon code can be applied. Using this trigger you will subsequently need to create a discount with trigger Price rule and in the Discount actions click on the Generate Coupon tab and choose the discount which you've already created using the Coupon trigger.
This trigger type works exactly the same as the regular coupon trigger type with one difference; coupons for this discount can't be manually specified. They are generated on certain orders, using a discount, crazy right? Using this trigger you will subsequently need to create a discount with trigger Price rule and in the Discount actions click on the Generate Coupon tab and choose the discount which you've already created using the Generate Coupon trigger.
Marketing descriptions and translations
Discounts also contain marketing description fields. These fields are translatable, but not during the discount's creation directly (for now, at least). If you'd like to set translations for this field, simply finish the creation of your field and then open it again to add translations.
Your input under the Marketing description field is what your POS users would see under the side menu item possible discounts in a customer Basket flow. Therefore, it would be nice to be as much elaborative as possible. That way it's easier for a store employee to know what it is that needs to be done in order for the customer to actually obtain the discount.
Here is a simple marketing description example: ***"Get 10% off on order values above €100"***. This makes it clear for a store employee**POS** user that in order for the customer to get a 10% off, the order value needs to be above €100.
Additionally, we can attach the discount to a Campaign
Using this field you can control which organization unit(s) this discount would be tagged to.
Example: Selecting New York store as organization unit implies that the discount could only originate from there.
As the name implies, you can specify the validity of the discount by date and time.
The time zone applied would auto adjust based on the tagged organization unit or organization set chosen for this promotion. In other words, if you've set the start time to 09:00, and you've chosen an organization set which includes stores (organization units) in The Netherlands and in Portugal, where there is usually an hour time difference. The promo engine will automatically set the start time to 09:00 in the respective countries despite that hour time difference.
The second step is specifying financial information. Before we jump into it, note how the side pane shows information on the steps we have already gone through.
Of all financial information, only Currency is mandatory. Additionally, you can set a maximum usage per order, per customer or a maximum usage in overall.
Restitution claim company
The field Restitution claim company, is where you can add a third party to incur some an orders due amount. An example here would be the amount covered by a health insurance company. Keep in mind that a restitution organization unit needs to be created in order to tag it here, and for this to work (the restitution tick in organization type needs to be ticked when creating). The implication of this setup is that the order using this discount would now create two orders in the order overview. The first would include the invoice made for the customer, and accordingly showing the restitution amount as a discount, while the invoice attached to the other order would serve as a request for payment to that tagged restitution organization unit (an invoice with an open amount). The latter invoice can then be sent to the restitution organization unit for reimbursement. Proper financial booking configurations can be made to conclude the financial implications of such a scenario.
Return orders that initially included restitution organization units at time of sale would also create two order flows.
The recurring benefits fields are optional, here you can specify some behavior when it comes to your discounts (recurring) financially impacting aspects.
The following describes what each field implies:
User balance limit
Is where you specify the monetary value of the discounts recurring benefit (example: €50.00).
The field expects a monetary value only, thus when it comes to discount actions Product sets, Get a product, Pick a product, or an action where a percentage is the discounts benefit, would in turn deduct the equivalent monetary amount (of the granted product or the monetary value of the percentage) from the specified user balance limit.
User balance limit custom field
Is where you specify the custom field that would need to apply in order for the user to be able to avail the benefit. Only type 3 (OrderLine) custom fields appear here.
You can either use the User balance limit or the User balance limit custom field, both cannot be used simultaneously.
User reload strategy
Is where you specify the interval after which the discount benefit would be reinstated (example: the €50.00 user balance limit would be reinstated quarterly).
The user reload strategy field (within its context) impacts any discount action. A no input means "No reload". So if you had a Maximum usage per user of "1", and your user reload strategy is left "blank", implies that the respective discount action is not reloaded once the discount recipient has used it once.
The initially selected trigger type determines the discount actions available for selection in the drop-down menu.
Now for the good stuff: Actions! Bear with us, we have a ton of actions, and even more conditions. Actions is the actual benefit a discount gives. Some discount conditions are only available for certain discount actions, some work the other way around, it can get pretty complicated. What you eventually get in return, is an awesome discount engine.
Based on the action(s) selected from the drop-down menu, the rest of the page will populate. Cards will be added for each discount action selected. Below we cover the various actions.
Not applicable if initial trigger type selected was Manual. Here, you can specify a product set to be discounted.
It is not possible to create a product set beforehand and attach it to the discount, the set is created in the actual discount using the filter products.
The filter is used to specify which products form the set. The ones that would accordingly apply to this condition. Once you click the '+' icon you'll be presented with two options.
- Option 1: Add products in bulk, which prompts a notepad like modal where you can specify a Product property and input the corresponding values (use commas to separate between values).
- Option 2: Add product filter, which works the same as described here.
Afterwards, you can click the boxed magnifying glass icon on the filter products card to show all selected products in one view.
Set discount values
The field Discount Type presents you with several options like discount amount, percentage or unit price. The Free product choice implies that if the discount conditions are met the products you now specify here (using filters) will be presented to the user as possible free product(s) to the underlying order.
Not applicable if initial trigger type selected was Manual. These are very straight forward, percentage or fixed amount discounts. Simply, a percentage or an amount that will be deducted from the total due payment amount on an order.
Pick a product
Not applicable if initial trigger type selected was Manual. This action works same as Get a product, except for the fact that you can specify multiple product for the customer to choose from. You can also distribute the options across tiers, so for each tier you can specify a minimum order amount that is required before the customer can pick one of the products from that tier. Further, you can specify a default product selection (optional).
There are two settings that would influence the behavior in scenarios of an out-of-stock default product:
|true||This would imply that the front end user would not get the default product as an option if the product is out-of-stock. If there was a list and all options were out of stock, no options will be returned.|
|true||This would imply that if the default product is out-of-stock, and the next/most expensive in stock product from the specified product list (a default behavior assuming a list exists) is also out-of-stock/cannot be determined, then the initial out-of-stock product would anyway be added to the order and the front end user would be prompted with an out-of-stock notification.|
Not applicable if initial trigger type selected was Manual. A sliding discount is a simple order discount, but the discount amount depends on one of two things:
- total order amount
- quantity of products in the order
For example; you can set the discount to be 10% when there is only one product on the order, and then set it to 20% if there are two products. You can add as many steps as you would like.
This discount action allows you to set a discount on gift wrapping or shipping costs. This discount is a simple percentage or amount.
Get a product
Not applicable if initial trigger type selected was Manual. In this action, you can specify a product to be given to the customer. You can specify a quantity of the product to be given to the customer. Additionally, you can set a unit price that would for example be discounted that the units original price or set to
0.00 to give the product away for free.
Setting the unit price to "0.00" will automatically check the Give away product box, and the Unit price field will disappear since it becomes invalid in such scenario. The Give away product checkbox implies that the product being given as the action for this discount is totally "Free".
Using this discount action, you can set an amount or percentage discount based on the customer's age. You can either let the customer's age be the actual discount amount or percentage, or create age tiers with the amount attached.
Custom field discount
Not applicable if initial trigger type selected was Manual. The custom field action allows you to create a discount based on a custom field. This one is a little complicated and warrants some extra explanation. So make sure to check out how Custom fields are created. Further, select it then specify your discount type (percentage or amount).
Fixed amount (Trigger type manual only)
This action will only be visible if trigger type manual was initially chosen. It can be set to a fixed amount or a maximum amount, where the actual amount has to be specified when applying the discount to an order. This is possible since this will already be a manual process during checkout. Additionally, you can set the discount to apply either on the whole order or on specific order line(s).
Percentage (Trigger type manual only)
This action will only be visible if trigger type manual was initially chosen. The action behaves similar to the fixed amount one, except it uses percentages instead of amounts.
Employee discount (Trigger type manual only)
This action will only be visible if trigger type manual was initially chosen. The action is a simple percentage discount that can be given to employees.
Generate coupon (Trigger type price rule only)
This action requires you to have a DiscountCouponEmail Stencil be set up.
This action will only be visible if trigger type price rule was initially chosen. Further, you'll first need to create a discount with trigger type Generated coupons or Coupon in order for this to work, as it needs to be linked here.
A coupon code is generated and e-mailed to the orders attached customer as a result of this action. The coupon code can then be used on future orders to avail the discount action that was specified in the Target discount ID.
Target discount ID field: This is a dropdown list that displays all discounts with a trigger type Generated coupon or Coupon. You'll need to link the related one here.
Store generated coupon on user checkbox: Ticking the box will bind the generated coupon to the coupons receiving customer only (customer attached to an order at the time coupon was granted). This means that the customer who initially received the coupon, would be the only one who can actually use the coupon on future orders. POS users would also be notified of any bound customer coupons during order checkouts, and can then easily apply it.
Here is how a bound customer coupon would look on POS. You can see a €10 coupon bound to this customer on the right pane. Tapping Apply would simply apply it to the order:
Check the coupon use case sample.
Original order discount (Trigger type generated coupons only)
This action will only be visible if trigger type Generated coupon was initially chosen. Using this action, you can set a discount to be an amount, which will be calculated based on the total amount of the order in which the coupon you're using was generated. Optionally, you can set the amount to only be calculated based on a certain set of products.
This is where you configure certain conditions for your orders, that have to be met before the discount can apply or be applied.
This condition can be used to require an order to be of a certain amount before the discount can be applied. A maximum amount can also be set.
This condition can be used to set some product related rules as to when this discount would trigger. Conditions like exclude products with a sale price, identical products only, or exclude product sets are possibilities on how you can use this condition.
Using the product sets type, you can further configure the discount in a way so that the discount only triggers if "a certain quantity of products are included in a customer order/basket from the specified product set" or if "a certain amount is spent on products from that set".
One product set at a time, so use the '+' to add more sets if needed.
Can be used in the same way as described under product sets action.
The Customer condition can be used to create a discount for a specific customer or set of customers.
- Customers can be specified using Email addresses or Customer IDs.
For example: Your input could look something like "firstname.lastname@example.org, email@example.com, firstname.lastname@example.org" for email addresses, and something like "554785, 784145, 987454" for Customer IDs. This would mean that the discount would only apply to those specified.
- Customer fields can be used to specify a broader group. Compared to Email addresses and Customer IDs, this one is more generic since the possible configurations are somewhat more inclusive of a larger group.
For example: You want to give a discount to all customers who have a certain domain name in their email address. An input of @newblack.io would give all customers with such a domain email address the underlying discount and not just email@example.com, just saying.
- Subscriptions is a dropdown and thus, requires having an existing subscription. Selecting one would imply that only customers who adhere to the requirement of that subscription would be able to avail the discount.
For example: You have a subscription called receive newsletter that prompts on your front ends for customers to tick. If that subscription requirement is met, then the discount would apply to that group of customers only.
Is used to specify an age (Exact or Range) of the customer.
For example: An input of 30 in the Exact age field would imply that the discount would only apply to customers of age "30".
Age is just a number.
It is possible to in- or exclude certain stock labels from being eligible for a discount using the Stock label condition.
User roles can also be included with the discount using the User role condition. This condition can be set on the logged-in user or the customer. When setting it on the customer, user roles can also be excluded.
User custom fields
It is possible to require that at least one or all user custom fields are met in order for a discount action to apply. Any custom user field can be configured via the People module and thus, used here.
User custom field includes both UserType Employee and Customer.
Order custom fields
It is possible to require that at least one or all order custom fields are met in order for a discount action to apply. Any custom order field can be configured via the Orders module and thus, used here.
Orderline custom fields
It is possible to require that at least one or all order line custom fields are met in order for a discount action to apply. At the moment, a front end is under development where a custom field on order line level (type 3) can be created. Till then, if you wish to use this condition, please use the service CreateCustomField and specify your
3. Check Custom field developer documentation if you'd like to find out more about the available services.
To include specific order types only in your discount. Using this condition you can choose to have a discount apply on CarryOut, Delivery or Reservation orders only.
Using this condition, you can set up your discount in a way where it would only kick-in if a certain product custom requirement applies.
Example: You offer your customers a unique personal touch by allowing them to specify custom text to be printed on one of your products. Let's assume they're a pair of jeans where initials can be printed on the back pocket. Such product requirement can then be attached as a discount condition, but only when specific values apply (a value in this context would be the requested custom print). Let's again assume you've specified 'NB' as a value here. With such setup, this means that the discount will only kick-in if the customer requests to have 'NB' as their custom print to this product requirement as time of order placement.
Multiple product requirements can be added, and the same product requirement can be added multiple times.
User type (Trigger type manual only)
This condition will only be visible if trigger type manual was initially chosen. On manual discounts, it is possible to in- or exclude certain user types.
Coupon validity (Trigger type Coupon and Generated coupons only)
This condition will only be visible if trigger type Generated coupon was initially chosen. The condition can be used to crystallize a coupon's validity and consists of two cards (Start date and End date):
As the name already implies, this card impacts the start date a coupon becomes valid/usable.
There are a few options that can be used to determine the start date:
- Requested date on original order: The coupon becomes valid starting from the original order date. In instances where an order includes several order lines and multiple order line dates, you can then specify to Use closest or Use furthest order line date as your start date.
Example: Assume a mixed order that is partially carry out (fulfilled on March 1st), and partially endless aisle (fulfilled 2 days later on March 3rd). Use Closest would imply a coupon validity start date of March 1st, while Use furthest would imply a start date of March 3rd.
- X days after order date: The coupon becomes valid starting X number days after the order date. The same concept of Use closest or Use furthest order line date applies as explained in the above example.
- Coupon creation date: The coupon becomes valid instantly at time of issuance.
- X days after coupon creation date: The coupon becomes valid after X number days from the date of its issuance.
- Specific start date: A specific start date from where the coupon becomes valid (cannot be more straight forward than this).
As the name already implies, this card impacts the end date a coupon becomes invalid (expires).
There are a few options that can be used to determine the end date:
- Same as start date: Basically, this option implies that the coupon will be valid for just a day since it'll expire same day as your chosen start date.
- Specific end date: A hard end date where the coupon would then expire.
- X days after start date: The coupon expires X number of days after your chosen start date.
Originating OU (Trigger type Generated coupons only)
This condition will only be visible if trigger type Generated coupon was initially chosen. Using this condition, you can limit a coupon to only be used in the OU on which it was originally generated.
After configuring your condition(s), we move into discount validation. A user with the functionality
DiscountSelfVerification would need to verify the discount for it to go-live.
At this point, the discount engine will do some complicated magic behind the scenes, like super complex. You're probably wondering what we're talking about - you've never seen the discount engine think. Well, it's extremely fast okay. You won't even notice.
If all rows have a green checkmark, you're good to go, and we are proud of you. Save your discount and go get yourself a brownie. You deserve it.
Using the setting
Discounts:RequireVerification with a value false would skip the verification step i.e. no verification would be required, and vice versa if the value of the setting is true.
Coupons (Trigger type Coupon only)
This additional step would only be available on the right pane after the "Validate discount" card if your trigger type was initially chosen as Coupon. Here is where you can add coupon codes to your discount. There are several ways of doing so:
- The Custom option: Manually add your own (custom) coupon codes.
- The Multi option: EVA randomly generates a bunch of codes. After saving, refresh the page to see your coupon codes. The coupon codes will also be sent to the user that generated them in an e-mail.
- The Handler option: Based on your coupon handler settings
- The Import option: Upload coupon codes using an Excel upload. Currently, this can only be done using the services DownloadCouponExcelTemplate and UploadCouponExcel. Make sure to download a new template every time you make an upload.
The Excel sheet consists of the following columns. Here is a description of each and the respective values expected:
- CouponCode: A required field used to identify the coupon. Excel can only contain unique coupon codes, otherwise the file will be rejected.
- IsActive: An optional boolean field that indicates whether the coupon should be active or not. If no value is given, the coupon will be made active if it’s a new one. If it's an existing one, then it will retain its current value.
- MaximumUsage: An optional integer field that indicates the allowed maximum times a coupon can be used by your customer. If no value is given, the coupon will default to a maximum usage value of 1. If it's an existing one, then it will retain its current value.
- UsageCount: An integer field that indicates the number of times a coupon has been used.
Setting the Maximum Usage to 2 would mean that the Usage Count would never exceed 2. If a maximum usage was not set, the usage count can be used to track how many times a coupon has been used. So basically, if an order uses a discount (order status: completed), a +1 would be added to the usage count of that discount. The maximum usage can then be used to put a ceiling to that value.
Coupon code suffix
Using the setting
Discount:PseudoCouponCodeSuffix you can combine 2 discounts in one. However, one of the 2 must be of trigger type
Coupon. For example, if you have a coupon discount called
coupon10% and the value of the setting
freeshipping, the discount engine will then automatically attach the
freeshipping discount to an order where a coupon discount was triggered. In this example, it would mean that the customer would avail both a 10% discount triggered by the coupon, and a further free shipping discount.