Cashbacks
Running Cashbacks Based On Sale History
Contrary to discounts that are setup according to users' purchases, cashbacks are setup according to merchants' sales.
You can setup your offer such that if you (the merchant) are not able to sell a certain amount or number of items before a certain date, users that paid that item can qualify for a cashback to get their money back.
You can also setup an offer that give users a 10% cashback on their purchases if you are able to sell a certain number of a specific item before a specific data.
Here are some use cases:
Case 1: An offer to purchase a course that refunds customers' 10% of their money if more than 1000 subscriptions to the course are sold before a certain date
Case 2: An offer to purchase a course that refunds customers' 10% of their money if more than 1000 subscriptions worth more than 10000 tokens in total to the course are sold before a certain date
Case 3: An offer to purchase tickets to a party that refunds customers' 100% of their money if less than 100 tickets to the party are sold before a specific date
Case 1:
Here is a step by step guide to setup an offer to purchase a course that refunds customers' 10% of their money if more than 1000 subscriptions to the course are sold before a certain date
Go to the product page of the item for which you want to create a cashbacks by finding the item on your channel's main page and clicking on it
On the product page, click on the Adjust settings button
In the menu that shows, click on Update Discounts & Cashbacks and select the Cashbacks tab
Let's put our cashback status to Open
For the second parameter, let's start our reward from today: October 19th, 2023. This means users that qualify for our cashback will be able to claim it from today
The third parameter is a bit tricky since it is a comma separated list of multiple parameters (the start of the time range, the end of the time range, the cashback percentage, the lower threshold, the upper threshold, and the limit). Let's pick a time range between October 1st, 2023 at midnight and October 10th, 2023 at midnight to account for the sales made by the channel.
To do so, we will need to convert the dates into Unix Timestamps. Head over to this page. Input the date October 1st, 2023 at midnight and click on the button Human date to Timestamp to convert into Epoch timestamp (1696118400).
Repeating the same for the second date (October 10th, 2023 at midnight) gets us 1696896000.
Our next parameter is the cashback percentage which we will set at 10%.
The next parameter sets a lower bound on the number of items the channel should have sold between the 2 dates above for the cashback to be applied, that number is 1000 items
The parameter after that sets an upper bound on that number. Let's make it a big number to not prevent users from getting a cashback just because we sold too many items (10,000).
The last parameter in the comma separated list sets a limit on the number of times a user can claim this specific cashback. Let's set it at 1.
To sum up, our input for third field will be: 1696118400, 1696896000, 10, 1000, 10000, 1
This will reward each user that has bought our item with a 10% cashback in case we are able to sell more than 1000 items. The cashback is disabled if we sell less than a 1000 items or more than 10,000 items
Since in this case we are only rewarding users based of the number of items purchased, we will leave the fourth field empty.
There is no Check Identity parameter here. That value is also used for cashbacks but has to be set with the discount function. In case you need to change this parameter but don't want to create a discount, you can still use the discount form but leave the discount Status parameter's value to pending.
The Rewards In parameter sets whether you want users to be withdrawing the cashback in tokens (cash) or in credits (discount on the current product)
The last parameter if set to Yes, will only check count the number of sales of the current item (uber) and if set to No, will count the sales of all items available on the current channel
Case 2:
For this case we are adding to the previous criteria a new one based on the total cost of subscriptions sold; we not only want there to be at least 1000 subscriptions sold but we the total price of the subscriptions sold to be at least 10,000 tokens
Repeat the exact steps above
The fourth field in this case will not be left empty, this field enables you to qualify based on the total cost of items sold instead of the total number of items sold.
For instance, inputting this (1696118400, 1696896000, 10, 10000, 1000000, 1) in the fourth field will reward each user that has bought our item with a 10% cashback in case we are able to sell more than 1000 items worth at least 10,000 tokens. The cashback is disabled if we sell less than a 1000 items or items worth less 10,000 tokens. It will also not apply if we sell more than 10000 items or items worth more than 1000,000 tokens
Case 3:
Here is the setup for an offer to purchase tickets to a party that refunds customers' 100% of their money if less than 100 tickets to the party are sold before a specific date
The entry for the third field will be: 1696118400, 1696896000, 100, 100, 1000000, 1
And there's no entry for the fourth field and the other fields can be filled the same as for the previous cases.
This will give users 100% refund on their purchases of tickets to the party if we did not manage to sell at least 100 tickets or we sold 1000,0000 (the upper bound always has to be set even if it doesn't make like in this scenario, so be sure to pick a very big number to be safe).
Last updated
