> 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/user-access/logic-global-admin/pos-options/pos-options-1/retail-customer-selection-mandatory-in-billing.md).
# Retail Customer Selection Mandatory in Billing
**YouTube:** [How to Globally Make Retail Customer Selection Mandatory in Billing?](https://www.youtube.com/watch?v=dzGgXN_12qs)
## How to Globally Make Retail Customer Selection Mandatory in Billing?
In this tutorial, we’ll explain a feature that **requires selecting a retail customer before saving a sale voucher**, ensuring proper customer details are captured in every transaction.
***
### Access Global Settings in Logic Admin
* Open **Logic Admin**.
* Navigate to **Global Settings**.
* Under **POS Options**, go to the **POS Options 1** section.
* Locate and enable the option labeled as:
> **"Retail Customer Selection Mandatory in Billing"**
Let's proceed with this option turned on to understand its practical implications in Voucher entry.
* Click **Save**, then **restart the software** to activate the setting.
***
**Note**:
* This option is also available in individual **sale bill configurations**, but it needs to be set **manually per billing series**.
* Enabling it in **Global Settings** applies it **across all billing series and branches**.
***
### Implement the Functionality
* Open the **Sale Bill - Touch Screen** window.
* Begin creating a **sale bill**.
* Try to **save the bill without selecting a customer**.
The software will prompt:
> “Retail customer selection is mandatory to proceed.”
* Select an **existing customer** or create a **new one**.
* Now you’ll be able to **save the bill successfully**.
***
**Result**: Ensures better tracking and accountability by mandating customer selection before billing.
---
# 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/user-access/logic-global-admin/pos-options/pos-options-1/retail-customer-selection-mandatory-in-billing.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.