# Bricker Recommendations

<figure><img src="/files/FhhSZqWnLNi6KTcz3Q2T" alt=""><figcaption><p>Bricker Recommendations shows controller-level LP/MP suggestions with expandable per-site and per-indicator detail rows.</p></figcaption></figure>

The **Bricker Recommendations** window gives controller-level and per-site suggestions so you can tighten LP/MP filters quickly, based on live task payouts plus monitor indicators.

## Where to open it

Open **Bricker Recommendations** from the Bricker Mode view. It lists your active controllers and lets you apply changes in bulk or per-site without leaving the window.

## What you see in the window

### Toolbar filters and actions

* **Site Filter**: Limit the grid to a single marketplace.
* **Only Above Market**: Show controllers priced above market.
* **Hide Increase Recommendations**: Hide rows where the suggestion is to raise prices.
* **Show analyzed only**: After running indicator analysis, hide sites without indicator data.
* **Analyze Indicators**: Pulls per-site indicators and fills the nested “Indicators” table.
* **Refresh**: Reloads recommendations with the latest data.

### Controller rows (top grid)

* **Image / Product / SKU / Size**
* **Consign / Resale badge**
* **Sites**: Count of active marketplaces for the controller.
* **Current LP / MP**: Current filters (blended across sites).
* **Market Payout**: Blended market payout estimate.
* **Suggested LP / MP**: Rounded suggestions based on market data.
* **Difference %**: Suggested change vs current LP.
* **Actions**: `Apply All` (applies to all active sites on that controller) and `Focus` (jumps to the controller in Bricker Mode).

### Per-site rows (nested list)

* **Market Payout / Current LP / Current MP / Suggested LP / Suggested MP / Difference %**
* **Reasoning**: Site-specific explanation.
* **Action**: `Apply` (switches to `Accepted` after success).

### Indicator rows (shown after **Analyze Indicators**)

* Sales count, Sales %, Ask %, Avg Payout, Avg Price
* Suggested LP / MP per indicator
* Quick apply button per indicator

## How recommendations are calculated (short version)

* Uses recent task payouts plus monitor indicators; old or noisy points are down-weighted or ignored.
* Per-site market payout is blended, then controller-level values average the per-site results.
* Suggestions focus on meaningful changes and avoid tiny tweaks; “Hide Increase Recommendations” can suppress price-raise suggestions.

## Applying recommendations

**Apply All** updates every active site for that controller. Use the per-site **Apply** buttons when you only want to change a specific marketplace. After applying, the button switches to **Accepted** and values refresh.

Use **Focus** to jump back to Bricker Mode with the controller highlighted if you need a deeper review.

## Filtering and sorting tips

* Click column headers to sort.
* Combine **Site Filter** with **Only Above Market** to find overpriced controllers fast.
* Use **Hide Increase Recommendations** to focus on reductions.
* Run **Analyze Indicators**, then toggle **Show analyzed only** to inspect sites with indicator data.

## Troubleshooting

* **Empty table**: Make sure you have active controllers and recent monitor/task data.
* **Indicator rows hidden**: Run **Analyze Indicators**, then toggle **Show analyzed only** off/on.
* **Apply disabled**: The row will show `Accepted` after a successful apply; refresh to recalc if needed.
* **Recommendations look off**: Check the reasoning text; if data looks inconsistent, refresh or verify monitor feeds.


---

# Agent Instructions: 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:

```
GET https://docs.restock.gg/features/bricker-mode/bricker-recommendations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
