Rewards Points - Configuring Earning Rules
Overview
Earning Rules define ways by which customers earn points. These can be managed by the Marketplace Owners. To create a new Earning Rule, navigate to the Marketing > Promotions > Reward Points > Earning Rules and press the button Add New.
Here, the page will open up with a set of fields that need to be initially set, before continuing.
Editing the page of an earning rule is very complex and differs, depending on the type of rule, so each type has its subsection here.
General Information (common fields)
The following options below are common to all types of earning rules.
Field | Notes |
Rule Name | This is the name of the rule. It is used for internal purposes only. |
Display Name | This is the rule name that will be displayed in your customer's account, thus bringing out your customer's valuable information on the rule (way) to earn points from your store. |
Type | This means the type of rule. Below are the different types of rules: Behaviour Rule - These are points earned subject to a customer's action or actions. Cart Rule -These are points earned subject to the total amount in the Customer's cart or the contents thereof. Read further below to see how to configure these items.  Once you set this and save it, you cannot change this, and you will need to create a new rule if needed. |
Is Active | Set to Yes if you would like to activate this rule. |
Active From, Active To | Sets the period of rule activity. |
| Websites | Choose which marketplace this rule will apply to. |
Customer Groups | Choose which Customer Groups the rules can be applied to. |
| Stop further rules from processing | If enabled, no other rule will be applied if this applies. This will be based on priority. |
Priority | The order, which will be used in sorting out a variety of rules before they can be applied. Arranged in the ascending order. 0 is the highest. |
Important: It is a common case when different policies are applied to most similar conditions (or the same event), but with some differences - which require applying only one Rule per Order. Then Priority and Stop further rules processing options can be used in organizing their execution order.
For example, a regular customer will receive 10 points, but a VIP shall receive 100.
Let's have two rules, for instance - "Regular" and "VIP". In this case, the VIP rule has a higher priority and has an option for Stop further rules processing enabled. If a VIP customer buys a product, the VIP rule will apply, but for that of a Regular customer, he will not, (since the option for Stop processing... is set). When a Regular Customer buys a product, the VIP rule will be skipped, and the Regular Rule will apply automatically.
Each rule has four possible global modes of applying its conditions in respective Conditions tab, shown on a special header If *[apply mode]* of these conditions are *[validation mode]*:
Applying modes define, when rule can be triggered:
ALL - implies, that rule will be executed only when strictly all the conditions were met;
ANY - implies, that rule will be executed when one or more (but not all) of these conditions are met;
Validation modes defines the result which each condition can produce as "met":
TRUE - implies that the conditions are valid.
FALSE - implies that the conditions are invalid.
These modes create flexible conditions set to satisfy policy of any complexity.
In order for you to continue to populate the rest of the fields, you will need to Save and Continue Edit. Based on the setting you input for Type, this will then determine which conditions and which options you will have available.
Behaviour Rules
These rules only trigger certain Customer' actions, such as writing a review or placing an order.
Conditions
This section allows picking up Event, which corresponds with a Customer's action, and binds it to its a current rule.
Field | Notes |
Customer signs up in store | Customer signing into the marketplace. Useful for awarding points that should be used in the very first Order |
Customer places order | Triggered when the Customer places an order, and it is completed (eg invoiced and shipped). |
Customer refer a friend | The Customer sends an invite to a friend. |
Customer writes a product review | The Customer adds a review, and it is approved by staff. |
Customer has a birthday | This rule is executed by an automated cron job, which starts at 00:00 each day for every Customer. If the Customer has a birthday to mark, the rule will be executed at that time. This is usually used only if the Customer has input their Date of Birth. |
Customer is not active for a long time | This should be set in days. This rule also is executed at 00:00 by an automated cron job. |
Customer creates RMA | Customer creates an RMA through the front end of the platform. |
Newsletter sign up | Customer opts to receive a Newsletter. This requires using the default Newsletter opt-in feature, and does not work with external 3rd party systems out of the box. |
Facebook Like | Customer likes product page on Facebook. Requires social sharing enabled. |
Twitter Tweet | Customer tweets product page on Twitter. Requires social sharing enabled. |
Pinterest Pin | Customer places a pin of a product on Pinterest. Requires social sharing enabled. |
Customer joins the affiliate program | Customer joins with an affiliate program. Requires the Affiliate feature (not included out of the box). |
Customer tier up | Customer tier lever advances. |
Customer tier down | Customer tier lever is lowered. |
Push Notifications sign up | Customer opt in to receive push notifications. |
Referred customer signs up in the store | Referred customer (referee) signs up to the store. Requires Referral Program. |
Order from a referred customer | The referred Customer had placed an order, and it is complete. Requires Referral Program. |
Custom events | List of custom events created using this Custom Behavior Events from the configuration. |
Note: For the events "Customer has a birthday" & "Customer is not active for a long time" (executed by an automated cron job) you can use only the "Give X points to customer" style
Actions
There's also a subsection Apply the Rule only if the following conditions are met, where additional conditions can be set. Here is the list of currently supported properties.
Customer
Option | Notes |
Is a Referral | Checks whether the Customer has invited customers to a store, and if they have become registered customers. This is extremely useful for building a Referral Program for the Customer. |
Is a Referee | Checks whether a customer is a referee (i.e., whether someone invited them). |
Email | Checks the email of a particular Customer. |
Group | Checks the group a particular Customer belongs to. |
Lifetime sales | Calculates the total amount purchased by the current Customer, and compares it with the value supplied. |
Lifetime spent points | Calculates the total points used by the current Customer, and compares it with the value supplied. |
Number of Orders | Calculates the total number of orders, placed by the current Customer, and compares it to the value supplied. |
Is subscriber of Newsletter | Checks whether the Customer has subscribed for a Newsletter. |
Number of Reviews | Calculates the total number of approved reviews made by the current Customer, and compares it to the value supplied. |
Number of referred friends signups | Calculates how many invited customers became registered customers (e. g. became referees). |
Number of referred friends orders | The whole number of orders placed by the referees invited by the current Customer. |
Sum of referred friends orders | The total sum of money for all orders placed by all referees, invited by the current Customer. |
Number of referred friends that ordered at least once | Number of referees invited by the current Customer, which placed at least one Order. |
Order
Option | Notes |
Subtotal | Subtotal of cart, including shipping and handling fees. |
Notification
Field | Notes |
Message in the rewards history | The Message that will be added as a description to the rewards earned from previous transactions, created under this rule. |
Message for customer notification email | The Message sent to the Customer by mail. This Message shall only contain important messages, not the whole template. This Message will be inserted to the Balance update Email template, which can be set in Settings. |
For example, you can create the following behaviour rules in your marketplace:
- Write a review and get 10 points
- Refer a friend and get 10 points when your referee makes their first Order
Tiers
Field | Notes |
Customer Earning Style | Set the strategy, which is used in calculating points.
|
Number of points (X) | Number of points that a customer receives if the rule applies. |
Maximum number of earned points for one Customer per day | Sets a limit to the number of points earned by a customer per day. Set at 0 or leave empty to disable the limit. |
Assign Customer to Group | Allows a Customer to move to his or her desired group, if the rule is triggered. This is extremely useful when maintaining the customers' ranks program, for example, or building a referral program. |
Cart Rule
Award points consist of the total amount of actual money spent in the Cart. This type of rule is recommended when using tier or special prices (with taxes, dependent on the shipping country, for example), which can dynamically alter the actual cost price of a product.
Conditions
Cart Rules have more complex condition subsystems, though you may recognise this system from the Cart Price Rules.
Option | Notes |
Product attribute combination | This allows you to set the product attribute combination. Attributes list is the same, as in Product Rule. It has the following scheme: If an item is tagged [validation mode] in the Cart with [applying mode], and any of these conditions are true:. Validation mode can be either FOUND or NOT FOUND, which defines, whether a checked product exist in the Cart or not; Applying mode can be either ALL or ANY, their meanings are the same as in the previous type of rule: whether all the conditions in this container apply or one or more of them does not. Additional to product properties set, this mode provides three additional properties regarding Cart content:
|
Product subselection | This allows you to check the cart item attributes. It also has a container and has the following scheme: If [selection mode] for a subselection of items in the cart matches [applying mode] of these conditions. Selection mode defines, which primary parameter is checked - product quantity (total quantity) or its row total ((total amount)). It shall be supplied with a numeric value. Applying mode can be either ALL or ANY, their meaning is the same as the previous type of rule: whether all conditions in this container apply or one or more of them does, Container can have the same conditions as the above model. |
Conditions combination | This allows you to break rule into logical parts, each of which can be validated separately. It is extremely useful when ANY applying mode is used for a full rule and the complex conditions required. It creates just a nested block of If *[apply mode]* of these conditions are *[validation mode]* type, as described in General section. |
Cart attribute | This allows you to set reward points earning based on the following cart attributes: Additional Payment Method - Apply condition with an additional payment method. Subtotal - Subtotal of cart, including shipping and handling fees. It can also contain a discount, if Stores > Settings > Configuration > Sales > Tax > Calculation Settings > Apply Customer Tax is set to before discount. Total Items Quantity - The total quantity of items in the current Cart. Total Weight - The total amount that all the products in the Cart weights. Payment Method - Payment method. If the payment method is not selected - this condition will return false. Therefore, this condition forces earnings only on checkouts, or when payment selection is available directly from Cart. Shipping Method - Shipping method. The note above also applies here. Shipping Postcode - Postal code, where the products will be sent. The note above also applies here. Shipping Region - Shipping region. The note above also applies here. Shipping State/Province - The state, or province, where the product will be delivered. The note above also applies here. Shipping Country - The Country, where the product will be delivered. The note above also applies here. Is Rewards Points used - Apply condition when Reward Points is used. Coupon Used - apply condition when coupon is used. Coupon Code - the identification code of the used coupon. |
Customer | This allows you to set rewards point based on the customers’ status, account statistics and other information: Is Referee - The customer is the referee. Is Referral - The customer is the referral. Email - Email of the customer. Group - User group the customer belongs to. Lifetime Sales - Customer's total sales. Lifetime Spent Points - Customer's total spent points. Number of Orders - Customer's total number of orders. Is subscriber of newsletter - The customer is subscribed to newsletter. Number of reviews - Customer's total number of reviews. Number of referred friends signups - Customer's total number of signed up referrals. Number of referred friends orders - Total number of orders made by the customer's referrals. Sum of referred friends order - Total sum of orders made by the customer's referrals. Number of referrals who ordered at least once - Total number of customer’s referrals who ordered at least once. |
Actions
Apply the rule only to cart items matching the following conditions:
Options | Notes |
Cart Item Attribute | The product attribute in the customer’s cart. Price in cart - Price of the items in cart. Quantity in cart - The quantity of items in cart. Row in total - Row total = (ordered item price x ordered item quantity) + Tax) - Discount |
Notifications
Field | Notes |
Message | Shows a notification on the product pages if the rule is applied to the current product. |
Tiers
Field | Notes |
Customer Earning Style | Set the strategy, which is used in calculating points.
|
Number of Points (X) | The number of points awarded at each step. It also regulates the minimal number of points that can be awarded. |
Step (Y) Used only when Give X points for every spent Y Customer Earning Style is selected | Defines the size of one chunk, into which subtotal should be divided. It also serves as a regulator to the minimal amount of currency, which can be awarded by points. |
Quantity Step (Z) Used if Give X points for every Z quantity Customer Earning Style is selected | If it's not empty, items quantity will be divided into chunks of this size, and points will be calculated accordingly. |
Earn Maximum | The maximum number of points earned from the current rule. |
Example: You can create the following cart rules in your store.
- Buy 3 products with one Order and get 100 points.
- For every $1 spent, you will receive 1 point.
- For every product ordered, you will receive 100 points.
This section also contains a special subsection Applying this Rule only to items on the Cart matching the following conditions. It is a shortcut for a condition of Product attribute combination** mode (see above).
Saving and editing the rule
Once you have completed configuring the rule, you can select from the top of the page to Save or Save and Continue Edit if you would like to make further changes.
To edit an existing rule from the Earning Rules grid, simply click on an existing rule from the table. This will open the Rule Edit page.
You may also select to do bulk options by using the checkbox on the left of the table, and selecting the rules you would like to modify and then from the top left Actions dropdown, you can choose to Delete, or Enable/Disable the rule.
Related Articles
Rewards Points - Configuring Spending Rules
Overview Spending Rules are much simpler than earning them since they only define the rate, at which points can be converted to discounts. This can only be managed by the Marketplace Owner. NOTE: Points can be spent when a customer uses a special ...Rewards Points - General Configuration
Rewards Points allows customers to earn points for different actions, and earn additional points from the so-called thresholds (on reaching some tier of sales amount, for example), and even earn from sharing links on most popular social media ...Rewards Points - Additional Configurations and Options
Overview The main configuration/feature of the rewards points module is to allow customers to earn and spend any points they obtain - however there are additional tabs in which you can access a few additional options or reports. You can access these ...Rewards Points - Modifying a Customer's Rewards Points Balance
Marketplace Owners have the ability to modify a customer's rewards points balance from the backend of the platform. First, once signed in to the platform as a Marketplace Owner/Administrator, navigate to Customers > All Customers. Here, you will be ...Integrating your Broker Escrow account with your Omnyfy Marketplace (as a Marketplace Owner)
Configuring your API Key Obtaining the Key from your Escrow Account Before starting, ensure that you are using the correct environment to configure your API keys. https://www.escrow.com/ - Escrow Live Accounts https://www.escrow-sandbox.com/ - Escrow ...