# Tasks and Controllers {% hint style="danger" %} **THIS FEATURE IS FOR PREMIUM MEMBERSHIPS ONLY!** {% endhint %} **Bricker Mode** is all about automating your listings to ensure you always have the best price across multiple platforms. To make this work seamlessly, Bricker Mode uses **Tasks** and **Controllers**. Here’s everything you need to know. ## **What Are Bricker Mode Tasks?** Tasks are the individual automation features that run on each website where you’ve listed your item. Each task ensures your listing has the best price on that specific platform. With tasks, you can: * Set a **minimum payout** to avoid selling at a loss. * Set a **maximum payout** to keep your price realistic and avoid listing at a price that’s too high to sell. * View the **currency** you’re selling in. * Monitor the **delay time** between price updates in real time. ## **What Are Bricker Mode Controllers?** Controllers group together multiple tasks for the same item. They organize your listings by **size** and **quantity**, making it easier to manage multiple platforms at once. For example: * If you’re selling 2 pairs of EU 41 on StockX, 1 pair on Alias, 1 pair on Laced, and 1 pair on Klekt, all these tasks will be grouped into **one controller** for EU 41. (As seen on the picture below) {% hint style="info" %} **StockX exception:** if you are running both **Direct** and **Resale** for the same SKU and size, RestocksAIO can keep them in separate controllers. This is intentional because Direct and Resale use different market pools and should not always share the same pricing logic. {% endhint %} ### Bricker categories Every task belongs to one of three **categories**, which the tool derives automatically from the task configuration: * **Resale** — default category for flat-fee resale listings. * **Direct** — StockX tasks with Buyer-Direct Seller Mode enabled. * **Consign** — Consignment / Flex listings. Categories are independent of each other: the same SKU and size can exist simultaneously as Resale, Direct, and Consign tasks without colliding. Each category is queued and monitored separately, and the category label is surfaced in sale notifications so you know which bucket a sale came from.
## Controller Settings * **Smart Bricker Mode** [**(Click for in-depth guide)**](/features/bricker-mode/smart-bricker-mode.md)**:** Pauses the task if your item is undercut too many times or by too much. * **Parallel Check** [**(Click for in-depth guide)**](/features/bricker-mode/parallel-price-check.md): * *Enabled*: Each task works independently, without comparing prices across platforms. * *Disabled*: The tool compares prices across platforms and adjusts them to avoid selling for a lower payout than the best available price. * **Retrieve Alias Prices from Global Indicator**: Pulls pricing data from Alias’s global market trends. * **Retrieve StockX Prices from Algorithmical Indicators**: Uses StockX’s guidance data (Sell faster / Earn more) for smarter pricing. * **Allow non-Flex indicators for StockX Flex items:** Uses non-Flex price data for Flex-eligible items when running Consign StockX tasks. * **Delete alternate Direct/Resale category on sale (StockX)**: If you keep both StockX Direct and Resale live for the same product, the opposite category can be cleared automatically after one side sells. ## Expanded controller view Click the chevron at the right end of any controller row to expand it and see one row per active task — each marketplace, its product ID, current delay, payout settings, the chosen price, and the resulting payout.

Expanded controller showing per-site task rows. Status dot (yellow=running, blue=monitoring), per-site Lowest Payout / Max Payout filters, currency, current chosen price, and resulting payout.

## Monitor Received: per-task pricing breakdown Hover over **Received N prices** in any controller row to open a tooltip showing the live per-site indicator data the bot used for its pricing decision.

For each indicator (Highest Bid, Lowest Ask, Earn More, Sell Faster, Beat US, plus Flex variants) the tooltip shows the value, projected payout, and the reason it was either chosen (green) or rejected (red).

## Statistics & quick filters Open the statistics popup on the Bricker Mode page to access controller-level insights and one-click filters: * **24h Price Changes**: Total number of price updates made in the last 24 hours. Use the filter button to show only controllers that had price changes. * **Alias Price Increases (24h)**: Controllers where Alias price increases were applied in the last 24h. * **Not Lowest Ask**: Show controllers whose tasks are not at the lowest ask on their marketplaces. * **Session Sales**: Filter controllers that had sales during the current session. * **Has Errors**: Surface controllers with errors that may need attention. These filters add tokens to the Bricker search box, so you can combine them with text filters like name, style code, or site.

The Statistics popup shows live counters: Items in Queue, Lowest Ask Items, Not Lowest Ask Items, Total Sales, Price Changes (24h), Alias Price Increases (24h), Total Errors, plus shortcuts to View Sales during Session and Open Recommendations.

## Mass Editor Use the **Mass Editor** to apply changes (LP, MP, settings, site removal) across many controllers at once.

The Mass Editor lists every active controller and lets you bulk-edit Lowest/Max Payouts, toggle Smart Bricker Mode and indicator behaviors, and trigger batch actions through the Function Menu.

The Function Menu inside the Mass Editor exposes batch operations: Remove Site, Edit LP / MP for a selected site, Increase LP By, and more.

--- # 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/tasks-and-controllers.md?ask= ``` 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.