Step-by-step instructions
Managers can assign customers to clear loyalty groups, explain why a customer receives a discount or bonuses, and keep CRM, orders, receipts, and marketing rules consistent.
Use the interactive screenshot walkthrough first. Switch steps with the step dots, then read what to fill and why it matters.
Fields on this screen
Customer groups list
How to fill: Start from the list and search existing groups before adding a new one.
Why: Duplicate groups split customers, reports, and marketing rules.
Add
How to fill: Click Add only when a new loyalty or discount group is needed.
Why: The new draft needs a name, program type, and numeric rules before saving.
Group name
How to fill: Use a short operational label such as Gold VIP, Staff Family, Wholesale, or Birthday Club.
Why: Staff must recognize the group quickly in CRM and orders.
Name translations
How to fill: Expand the name field and fill every active company language.
Why: Multilingual companies need customer groups that match the selected interface language.
Clients can use deposit accounts
How to fill: Keep enabled only when this group is allowed to pay from customer deposit balances.
Why: Deposit rules affect payment options and customer balance explanations.
Bonus program selector
How to fill: Choose Discount system for a direct discount or Bonus system for point accrual and redemption.
Why: Only the fields for the selected program are meaningful.
Discount amount
How to fill: Fill only for Discount system and use a percent number.
Why: Direct discounts reduce order totals immediately.
Bonus amount
How to fill: Fill the earning percent for purchases when Bonus system is selected.
Why: This controls how many points the customer earns from regular purchases.
Welcome bonus amount
How to fill: Fill only when the business wants a registration reward.
Why: A starting bonus balance should be explainable when the customer first appears.
Referral bonus
How to fill: Fill only when referrals or recommendations give a reward.
Why: Referral campaigns need a consistent reward value.
Birthday bonus
How to fill: Fill only when birthdays should credit a bonus.
Why: Birthday marketing and CRM automation depend on this amount.
1 point equals
How to fill: Set the conversion between bonus points and currency value.
Why: Customers and staff need a predictable redemption explanation.
Maximum bonus payment percentage
How to fill: Set the highest part of an order that bonuses can cover.
Why: This keeps loyalty generous without accidentally removing the whole payable amount.
Save and verify
How to fill: Save after every value is checked, then return to the list and verify the row.
Why: Only the saved row can be assigned to customers and used downstream.
Common mistakes
- Creating several groups with similar names instead of editing the existing loyalty group.
- Choosing Bonus system but leaving bonus percentage, coefficient, or redemption limit unclear.
- Using a direct discount when the business actually wants points and balance history.
- Allowing deposit usage for a group that should not spend stored balances.
- Changing group rules without checking how existing customers and reports will be interpreted.
AI Agent Field Reference for implementation
This block is intentionally below the human instructions. It explains storage names and downstream dependencies for automation, support, and future AI agents.
| Field | Stored as | Purpose | Why it matters |
|---|---|---|---|
| Group ID | group_client.id | Unique identifier for the customer group. | CRM, company settings, customer records, orders, reports, and automations need a stable group reference. |
| Company | group_client.Company | Company workspace that owns the group. | Prevents loyalty rules from leaking between companies. |
| Group name | group_client.name | Multilingual group name stored as language/text objects. | Staff, customer screens, CRM filters, marketing rules, and AI explanations need a readable group label. |
| Type discount | group_client.type_discount | Program type selected in the dropdown: D for Discount system or B for Bonus system. | This value decides whether SABSUS uses direct discount fields or bonus accrual and redemption fields. |
| Discount | group_client.discount | Direct percent discount used when Discount system is selected. | Order totals and margin explanations depend on this value for discount-based groups. |
| Use deposit | group_client.use_deposit | Whether clients in the group can use deposit accounts. | Deposit availability affects payment options, customer balance use, and support explanations. |
| Bonus percentage | group_client.bonus_percent | Percent of purchase amount credited as bonuses when Bonus system is selected. | This is the main loyalty earning rule for customer purchases. |
| Birthday bonus | group_client.bonus_bf | Bonus amount credited for birthday scenarios. | Marketing, CRM reminders, and loyalty agents need to know if birthday rewards exist. |
| Registration bonus | group_client.bonus_registration | Welcome bonus credited when a customer registers or joins. | This value explains starting bonus balances and onboarding promotions. |
| Referral bonus | group_client.recomendbonus | Bonus amount connected to referrals or recommendations. | Referral campaigns and customer-bonus support need a clear source value. |
| Coefficient | group_client.coefficient | Value conversion for one point or bonus unit. | Agents need this value to explain how many currency units a customer's points can cover. |
| Maximum bonus payment percentage | GroupClientStruct.maxprocent / UI field | Maximum order percentage that should be payable with bonuses. | This protects margin and prevents bonuses from covering more of an order than the business allows; verify persistence in the current backend action before automating around it. |
| Created at | group_client.created_at | Creation timestamp. | Useful for audit, setup history, and troubleshooting recent loyalty changes. |
| Updated at | group_client.updated_at | Last update timestamp. | Support and AI agents should check freshness before explaining loyalty rules. |
Related guides
Use these guides to connect this section to adjacent SABSUS workflows.