> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-in-action-a-feature-overview/retail/loyalty-and-coupon-management/inbuilt-loyalty-system-for-points-accrual-and-redemption-with-customizable-configuration.md).

# Inbuilt Loyalty System for Points Accrual and Redemption with customizable configuration

YouTube: [Inbuilt Loyalty Point System](https://youtu.be/Kmaef_22JG4?si=685YdxZNegNAt87i)

### 🎁 **Utilizing the Loyalty Points System in Logic ERP**

#### 🛒 *Logic ERP Loyalty & Redemption System Guide*

In this tutorial, we’ll walk you through Logic ERP’s **inbuilt loyalty system**, which allows businesses to reward customers with 🎉 **points** and 💳 **redemption options**.\
It’s fully customizable and perfect for retail operations! 🛍️

***

#### 🔐 **Access Loyalty Points Setup**

1. First expand the options by clicking on **Setup** 🛠️
2. Go to **Setup Accounts** 🧾
3. Open **Setup Customer Database** 👤
4. Lastly select the **Set Customer Points Configuration** option. 🎯

***

#### 🧮 **Defining Setup for Point Earning**

* 🪙 **Define the Conversion Rate**\
  ➡️ Set how many rupees will be equivalent to **1 loyalty point.**\
  (e.g., ₹100 = 1 point)
* 📉 **Set Minimum Redemption Criteria**\
  ➡️ Specify the minimum number of points required for redemption.
* For example, in this case, a customer must have **at least 50 points** before they can redeem them.

***

#### 💸 **Defining Setup for Point Redemption**

* 💰 **Assign Value to Each Point**\
  ➡️ Set how much 1 point is worth (e.g., 1 point = ₹1)
* 💾 **Save Configuration**\
  ➡️ Don’t forget to **save** the settings to activate the loyalty system! 🔒

***

#### 🧾 **Applying Loyalty Points in a Sale Bill**

**🛍️ Processing the First Sale**

1. Add items to the bill 🛒
2. Enter customer’s 📱 contact number & 👤 name
3. Is it a New customer? Their details are saved when you save the customer details 🆕
4. Complete the sale and **save the bill** 💾

***

**🔁 Redeeming Points in a Future Sale**

1. Create a new sale bill 🧾 same customer.
2. Enter the **customer’s name or contact number** 📱to automatically fetch their details.\
   ➡️ Their loyalty points will auto-load!
3. When saving, a **message prompt** will show the customer's points and their value and ask whether to redeem them.
   * Click **Yes** ✅ to proceed.
4. In the **Implement Customer Points** window:\
   ➡️ Enter the number of points to use 🎯\
   ➡️ The bill amount will decrease automatically 💸

🧮 *Example: If the customer redeems 70 points = ₹70 off the bill!* 🤑

***

#### 🌟 **Benefits of Using Loyalty Points**

✅ Boost customer engagement\
🔁 Encourage repeat shopping\
🤝 Build long-term brand loyalty\
🎯 Reward your best customers!


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://kb.logicerp.com/logic-erp-in-action-a-feature-overview/retail/loyalty-and-coupon-management/inbuilt-loyalty-system-for-points-accrual-and-redemption-with-customizable-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
