> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/retailer-admin/floor-prices-tool.md).

# Floor Prices Tool

### Overview

Floor Prices (also known as Minimum Bids) set the lowest eligible bid for an auction scope. 

The Floor Price Viewer brings supported configured floor prices into a centralised space, so that  retailer teams can review category, keyword, and placement floor prices.

The viewer is read-only. It does not change live bid floors. 

The **Inspector** tab can be used to explore a vertical slice precisely. This is useful for troubleshooting, or confirming pricing resolved as expected in a given scenario. 

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FE8jUkwpoaL097xS13W4O%2FFloorPriceInspector.png?alt=media&amp;token=771d00a2-9305-48f5-b43f-0cd6dfa47ce0" alt=""><figcaption></figcaption></figure>

The **Manager** tab is used to view many floors simultaneously. This is more useful for broadly reviewing a pricing strategy or portfolio.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2Fuz4rMFgyZsqiARU8bPlH%2FFloorPriceManager.png?alt=media&amp;token=c9e440b3-2626-43b7-9465-ad1e349dd441" alt=""><figcaption></figcaption></figure>

### Why use the Floor Price Viewer?

* Review configured values across supported scope types.
* Filter and browse a large set of configuration records.
* Identify the scope attached to a floor price before requesting a change.
* Use a shared view when working with Epsilon support teams.

#### How to access the Catalog and Product tools

In a retailer team, navigate to the Tools section in the left navigation bar, then click "Floor Prices". You'll land on the Inspector tab.


---

# 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.citrusad.com/retail-media-interface/retailer-admin/floor-prices-tool.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.