> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/product/revenue/products.md).
# Products
### Guide for admins to list products
1. Navigate to the Revenue section in the [Settings](https://run.rox.com/settings)
2. Scroll down to the Products section and click on **Add Product**
3. Products can be categorised in hierarchies in Rox, in the order of **Family ⇒ Group ⇒ Product**
Multiple products can be a part of a product group, and multiple groups can belong to a product family.
4. Create pricebook entries for each product so that sellers can sell a product at different prices depending on the customer and situation.
5. You can temporarily deactivate pricebook entries to restrict sellers from being able to use that pricebook entry in opportunities.
### Guide for sellers on how to add a product to an Opportunity
1. Go to the **Products** tab in the opportunity view
2. Click on **Assign Products** and select the product and its associated pricebook entry
3. You can change the unit price in this step - allows flexibility in case of discounts or upsell.
---
# 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.rox.com/development/product/revenue/products.md?ask=&goal=
```
`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.