> 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-learning-hub-tutorials-and-best-practices/order-processing/sale-order/so-configuration/retail-customer-selection-mandatory.md).
# Retail Customer Selection Mandatory
**YouTube:** [How to Make Retail Customer Selection Mandatory in Sales Orders?](https://www.youtube.com/watch?v=VDOeXvvp-ms)
## How to Make Retail Customer Selection Mandatory in Sales Orders?
In this tutorial, we will learn how to make **Retail Customer Selection** mandatory while generating a Sales Order in Logic ERP. This feature ensures that a Sales Order cannot be created unless a Retail Customer is selected, helping maintain complete customer information and improving order accuracy.
***
### Objective of This Feature
* Make Retail Customer selection mandatory.
* Prevent Sales Orders from being created without customer details.
* Improve order accuracy and traceability.
* Ensure complete customer information for retail transactions.
* Maintain consistent sales records.
***
### Access to Sales Order Configuration
* Go to the **Sales Order Module**.
* Click on **Configuration**.
* Select the required **Sales Order Configuration**.
* Locate the option labeled as:
> **"Retail Customer Selection Mandatory".**
* By default, this feature is disabled.
***
### Observe the Default Behavior
* Initiate a new Sales Order.
* Skip the **Retail Customer** field.
* Continue with the Sales Order entry.
**Since the feature is disabled:**
* The system allows the Sales Order to be created without selecting a Retail Customer.
* No validation message is displayed.
***
### Enable the Feature
* Return to the **Sales Order Configuration** window.
* Enable the option: **"Retail Customer Selection Mandatory"**
* Save the configuration.
***
### Create a New Sales Order
* Click **New Order** to refresh the screen.
* Initiate a new Sales Order.
* Once again, skip the **Retail Customer** field.
* Proceed directly to the **Item Details** section.
**Result**
* The system restricts the action and displays an error message indicating that **Retail Customer Selection is Mandatory**.
* Click **OK** to acknowledge the message.
* The system automatically redirects you to the **Order Details 2** tab, where you must select a Retail Customer before continuing.
#### **Select the Retail Customer**
* Select the required Retail Customer.
* Continue with the Sales Order entry.
**After selecting the Retail Customer:**
* The system allows you to proceed with the Sales Order.
* The Sales Order is created successfully.
***
### Key Benefits
* Ensures complete customer information for every Sales Order.
* Prevents incomplete retail transactions.
* Improves customer tracking and reporting.
* Enhances order accuracy.
* Supports better sales record management.
***
### Best Practice Tips
* Enable this feature for businesses where every retail sale must be linked to a customer.
* Ensure Retail Customer records are created and maintained before order entry.
* Verify customer details before proceeding with the transaction.
* Periodically review customer master data to keep records accurate and up to date.
***
### Final Outcome
When the **Retail Customer Selection Mandatory** feature is enabled, Logic ERP requires users to select a Retail Customer before creating a Sales Order. If no Retail Customer is selected, the system prevents further processing, displays a validation message, and redirects the user to the appropriate section to complete the required information, ensuring accurate and complete sales transactions.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/order-processing/sale-order/so-configuration/retail-customer-selection-mandatory.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.