> For the complete documentation index, see [llms.txt](https://help.rbsgo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rbsgo.com/point-of-sale/point-of-sale-module/pos-analysis/cover-analysis-product-group.md).
# Cover Analysis- Product Group
The **Cover Analysis – Product Group Report** provides detailed information about sales covers based on product groups. This report helps users analyze sales performance by grouping products and reviewing the number of covers or packs sold for each product group.
## Steps to Open the Cover Analysis – Product Group Report
Step 1: Navigate to the **Point of Sale** module and click the **Analysis** menu.
1. Select **Cover Analysis – Product Group**
* The **Cover Analysis – Product Group** screen will be displayed.
Step 2: Choose the Required Filters
Step 3: After selecting the required options, click on the **Display** button.
* The report will be generated and displayed on the screen.
If you want to save or download the report in Excel format:
1. Click on the **Excel Export Icon** available on the report screen.
---
# 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://help.rbsgo.com/point-of-sale/point-of-sale-module/pos-analysis/cover-analysis-product-group.md?ask=&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.
