> For the complete documentation index, see [llms.txt](https://docs.payfacto.com/payfacto-knowledge/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/system-configuration/tools/sales-deletion.md).

# Sales Deletion

#### Sales Deletion <a href="#sales_deletion" id="sales_deletion"></a>

The Sales Deletion option from the Tools menu allows to permanently remove all existing sales reports and guest checks from the Back-Office and all punches in the Time and Attendance module This option does not erase the programmed revenue centers, employees, or configuration functions. Only Maitre'D Technical Support should use this option. Select the Sales Deletion option. The following warning message displays.

After you have read the warning message, press Enter or click on OK.

{% hint style="warning" %}
IMPORTANT: This operation is PERMANENT and IRREVERSIBLE.
{% endhint %}

**->DELETE<-**

Type the word DELETE in uppercase to confirm that you really want to perform a sales deletion, then click OK to proceed.

The system will prompt to enter a new System Starting Date.

**Starting Date:**

Enter the date your system will start save sales historical information from. This option should be set to your first day of live operation with the Maitre'D POS System.


---

# 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://docs.payfacto.com/payfacto-knowledge/maitred-pos/maitred/maitred-online-help-contents-by-module/system-configuration/tools/sales-deletion.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.