> For the complete documentation index, see [llms.txt](https://docs.lidiacommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lidiacommerce.com/components/lidia-merchant-console/merchant-console-user-guide/reports.md).

# Reports

The Reports section is a centralized reporting area where sellers can monitor, analyze, and evaluate all their operations on the platform in a data-driven manner. This section consists of different report types, including Sales Reports, Cancellation/Return Reports, Product Reports, and Withholding Tax Reports, providing sellers with a comprehensive view of both their operational and financial processes.

Reporting enables sellers to regularly track sales performance, identify product-level successes and areas for improvement, and analyze cancellation and return rates to take operational actions. At the same time, financial reports allow sellers to review their revenues, deductions, and legal obligations in a transparent and detailed way.

The reports provided in this section support sellers in making strategic decisions, increasing operational efficiency, and sustainably managing their performance on the platform.


---

# 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.lidiacommerce.com/components/lidia-merchant-console/merchant-console-user-guide/reports.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.
