> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/pos/customer-management/blocking-customers.md).

# Blocking Customers

1. In the POS, go to **Customers** tab.
2. Locate the **customer** and open the **details**.
3. Click **Block user.**

{% hint style="info" %}
Block status remains in place until manually removed. To unblock a customer, click **Unblock user** in the customer details.
{% endhint %}

## Blocked Users

When searching for a customer during order creation, blocked users will be marked in **red text** and labelled **"Blocked"**. 

{% hint style="danger" %}
**Blocking a customer does not technically prevent an order from being created or processed.**

Staff **can still proceed** with taking and completing an order for a blocked customer if the venue chooses to allow it. The block is **purely a visual indicator** intended to inform staff of the customer’s status so they can decide how to proceed based on venue policy.

If you want to block a customer from placing an online order through the website or the app, please reach out to support.
{% endhint %}

<figure><img src="/files/IzGVSBrOgQ3m7lPhQJHn" alt=""><figcaption></figcaption></figure>


---

# 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://docs.bossithq.com/pos/customer-management/blocking-customers.md?ask=<question>&goal=<endgoal>
```

`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.