Store
Store items
Store items are one of the ways for the users to redeem their accumulated Gamification points.
The items in the Store can be Bonuses of all kinds depending on the operator integration and software limits;
Match Bonuses (Percentage on deposits)
Free Bonuses (with playthrough) + Cash Bonuses (without playthrough)
Free Spins
Tangible items can be anything from Amazon items to โvirtualโ goods such as iPhone. You can create a Campaign for special items such as the ones above that will notify your support team via Email or Slack once the item was purchased, i.e. Start campaign on Store item purchased event โ where the item is iPhone โ send email โPlayers XYZ just purchased iPhoneโ
Items can be categorized, so you can put Free Spins bonuses under a category called โFree Spinsโ. The categories can have priorities, the lowest one will show on the left side. An empty category will not appear in the Store.
To create new categories move to the Gamification tab -> Settings: Store Categories -> Create
Items may also have โrelated itemsโ, chosen by the operator, and if empty, similar items from the same category will be shown.
Multi-currency amount
Multi-currency amount provides possibility to tune store item name or description according to the user currency. As soon as values are defined you can use them in the store item name and description with placeholder tag {{amount}}.
Example of usage: '{{amount}} {{state.core_wallet_currency}}' cash bonus For such store items, users of EUR currency will see the amount and currency name matching to EUR configuration and users of USD own value.
Terms & Conditions
You can also add Terms & Conditions to the items in the Store. For example, if you offer some kind of a bonus in the store, you have the ability to add extra information or conditions. It is optional so if you donโt add any text from the BO, the T&C hint will not be displayed inside the store item.
Pricing
Please take your time and invest a good amount of thinking of the pricing process, and make sure you are not allowing point leaders to buy many cheap items in the Store, or the opposite, give the option for starter players to use the Store and allow them the possibility to buy an item such as Free Spins.
Items can be capped per purchase, limited for specific periods of time, e.g 1 item per day, 10 items per week, etc.
When giving the price to an item such as 20 Free Spins, make sure it isnโt cheaper than buying 10 Free Spins.
Make sure the points price make sense - 20 Free Spins on XYZ Slot will cost the operator $5 (Depending on the coin value inside the game), and 20 Free Spins on ABC Slot will cost the operator $8, so ABC Slot item should cost more points.
There are 2 segments in the Store that can be used to optimize the Store items:
Who can see an item, segment E.g. Cheap item (300 points) for starter players โ Show only to a Segment of Low point amount (players with 0-1000 points) VIP players that already have a lot of points available will not see this item, they will see more expensive items appropriate for their level, as they make points quicker than others.
Who can purchase an item, segment E.g. Allow purchase of Free Bonuses only for a Segment of players with less than $1 in their balance, or Allow purchase of item B only if the player ever bought item A.
You can play with these 2 segments to show items for some users or hide from others.
A Store item that failed to be purchased due to a non-allowed segment, will not deduct points from the player, while a Store item that failed to be purchased due to the operator casino software rejection will deduct points from the player's balance and the item that was purchased will appear in the โPending Bonusesโ area of the Gamification widget for future redemption when the conditions for accepting it will be met.
In some cases where regulation prohibits this, the points can be reinstated to the player and the bonus purchased will not be available. In such cases please contact your account manager to set up this mode.
The Bonus items in the Store are based on Bonus Templates which are created separately in the Bonus Templates interface (see Bonus templates)
Choose the actual template that you want to relate to the specific Store item (in the example below 100 Cash Spins on the game I, Zombie, where the value is $25). You need to decide:
A bonus amount will be given to the player in the specific Bonus Template. In this case, it should be 0 as this is a Free Spins bonus.
UI Amount is a string that they will see in the Bonus section under the image of the item that was purchased.
Bonus API integration
Bonus API integration is custom development for the specific platform provider (PAM) of the client. In some cases, issuing a bonus will require only user ID and amount to trigger a bonus template on the platform side, and in other cases more complex configuration is handled by Smartico to compensate lack of flexibility on the platform bonus system, see below:
Purchase History in Store
The purchase history can be found in the Store section in the Gamification Widget. Players can view all items they've purchased, including details such as cost, availability for repurchase, stock status (if managed by the operator), purchase date, and a "Buy Again" button.
If a player doesn't have enough points to repurchase an item or if the item is out of stock, the "Buy Again" button will be inactive. This ensures players have clear information about their purchasing options and history.
Enhanced limitations for store items
You can control how purchase restrictions are applied. When setting a 'Max number of items a user can buy', you can choose how the restriction period is calculated - but only if the โDaysโ option is selected. You have three options to define how the limitation period resets:
1. Time from Last Purchase โ The restriction period starts from the moment the player makes a purchase and lasts exactly that many days. For example, if the limit is 1 item per day, and the player buys an item at 3:00 PM, they wonโt be able to buy another until 3:00 PM the next day.
2. Calendar Days, user time zone โ The restriction resets at midnight in the player's local time zone. If the limit is 1 item per day, the player can buy an item at any time during the day and they wonโt be able to buy another until midnight in their own time zone.
3. Calendar Days โ you can select the time zone when the limit will reset. The restriction resets at midnight in the specified time zone. If the limit is 1 item per day, players can buy an item anytime during the day, but the restriction will reset at midnight in the chosen time zone, regardless of their own location.
Gray Out Unavailable Store Items
In Label Settings โ Widget / Real Users and Widget / Test Users, there is an option called 'Gray out unavailable for purchase items' (disabled by default).
When this option is enabled:
Store items that players cannot purchase due to insufficient balance or because they are outside the 'Who can buy this item' segment are automatically displayed as greyed out in the UI.
If a player does not have enough points, gems, or diamonds to purchase an item, a message is displayed indicating how many more are required. This calculation is based on the itemโs cost and the playerโs current balance.
The message is fully translation-based, which means it can be customized. If you do not want to display the exact number of missing points, you can simply edit the translation and remove the
{points_missing}{gems_missing}{diamonds_missing}tags.
Restrict Store Item Purchase by Schedule
You can restrict the purchase of a store item based on a defined schedule. When a schedule is set, the item remains visible in the store, but cannot be purchased during the restricted period. If a player attempts to buy the item while the restriction is active, they will see an error message, which can be customized in the Store Item Template.
Active Hours in Store items
You can set โActive hoursโ for Store items and when a time range is configured, the item will only be visible during those hours. Outside that window, it will remain hidden. The option is disabled by default, meaning the item will be visible all day.
'Active Hours' can work independently or in combination with 'Availability Period' and 'Restrict Purchase by Time', depending on your configuration.
Active Hours + Availability Period
When configuring a Store Item, two time-based settings determine when it becomes visible:
1. Availability Period - Defines the date range during which the item can appear. Example: 1 Dec 11:00 โ 31 Dec 22:00 UTC The item will never show outside these dates.
2. Active Hours - Defines the hours of the day when the item is visible. Example: Daily from 10:00 โ 20:00 UTC
How They Work Together
A Store Item is visible only when both conditions are true:
The current date is inside the Availability Period
The current time falls within the Active Hours
Example Behavior
Availability: 1 Dec 11:00 โ 31 Dec 22:00 Active Hours: Daily 10:00โ20:00 UTC
Date
Visibility
1 Dec
11:00โ20:00 (starts later because Availability begins at 11:00)
2โ30 Dec
10:00โ20:00 daily
31 Dec
10:00โ20:00 (last day the item appears)
After 20:00 on 31 Dec, the item disappears permanently
Summary
First appears: 1 Dec at 11:00 UTC
Visible daily: 10:00โ20:00 UTC
Last appears: 31 Dec until 20:00 UTC
After that: No longer visible
Active Hours + Restrict Purchase by Time
When configuring a Store Item, these two settings control visibility and purchase behavior:
Active Hours - Defines the daily hours when the item is visible in the store. Example: 10:00 โ 20:00 UTC daily
Restrict Purchase by Time - Limits the time range when players are allowed to buy the item. Example: 1 Dec 11:00 โ 31 Dec 22:00 UTC
Important: Purchase restrictions do not hide the item - they only block the purchase action.
How They Work Together
The item is visible only during Active Hours
Players can purchase it only within the Restrict Purchase by Time window
If the item is visible but purchase is restricted, the โBuyโ action shows an error
Example Behavior
Active Hours: 10:00โ20:00 UTC Purchase Window: 1 Dec 11:00 โ 31 Dec 22:00 UTC
Date
UI Visibility
Purchase Availability
1โ31 Dec
10:00โ20:00 daily
10:00โ11:00: purchasable (before restriction starts)
After 11:00: purchase blocked (error shown)
1 Jan onward
10:00โ20:00 daily
Purchasable at all times during visibility (no restrictions apply anymore)
Summary
The item stays visible only during Active Hours
Purchase restrictions do not hide the itemโthey only block buying
Outside Active Hours, the item disappears from the UI
Active Hours + Restrict Purchase by Time + Availability Period
When all three settings are used together, they control when the store item is visible and when players can purchase it.
Availability Period - Defines the full date range during which the item is allowed to appear. Example: 1 Dec 11:00 โ 31 Dec 22:00 UTC
Active Hours - Defines the hours during each day when the item is visible. Example: Daily 10:00 โ 20:00 UTC
Restrict Purchase by Time - Limits when players are allowed to buy the item but does not affect visibility. Example: 5 Dec 15:00 โ 15 Dec 18:00 UTC
How They Work Together
The item is visible only when both:
The current date is within the Availability Period
The current time falls inside the Active Hours
Purchase is allowed only inside the Restrict Purchase by Time window (if set). If visible but purchase-restricted, clicking Buy shows an error.
Example Behavior
Active Hours: 10:00โ20:00 UTC Availability Period: 1 Dec 11:00 โ 31 Dec 22:00 Restrict Purchase by Time: 5 Dec 15:00 โ 15 Dec 18:00
Date Range
UI Visibility
Purchase Availability
Notes
1 Dec
11:00 โ 20:00
Purchasable (no restrictions)
First appearance
2โ5 Dec
10:00 โ 20:00
Purchasable (no restrictions)
5โ15 Dec
10:00 โ 20:00
Not purchasable from 15:00โ18:00
Purchase restriction applies
15โ31 Dec
10:00 โ 20:00
Purchasable (no restrictions)
Item disappears after 31 Dec 20:00
1 Jan onward
Not visible
Not purchasable
Availability Period ended
Summary
Item appears only during Active Hours and inside the Availability Period
Purchase restrictions limit buying but do not affect visibility
After 31 Dec 20:00, the item will never appear again
Last updated
Was this helpful?