> 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/analytics/audit-trail-report.md).

# Audit Trail Report

The Audit Trail Report provides a comprehensive log of all order items that have been deleted from orders after the initial transaction was processed.

It displays information such as:

* **Deleted At (UTC) —** The date and time the item was deleted, displayed in UTC.
* **Deleted By** — The user who deleted the item.
* **Product Name —** The specific item that was deleted.
* **Parent Name** — The parent product the item belongs to (if applicable).
* **Order #** — The order number associated with the deleted item.
* **Quantity** — The number of units deleted.
* **Order Source** — The platform the order originated from (e.g., POS, Kiosk, Online).
* **Order Created At** — The original date and time the order was created.

[Adding or Removing Products](/pos/order-modification/changes-to-an-order/adding-or-removing-products.md)

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FhjemhQhCZ7IVwdFF1Dp8%2Fimage.png?alt=media&amp;token=64bd20a9-7b2e-468d-9033-328586161798" 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 by asking a question.

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

```
GET https://docs.bossithq.com/analytics/audit-trail-report.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.