> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/retailers/queuefair.md).
# QueueFair
Complete guide on our QueueFair module
### **Preliminary Checklist**
Before setting up tasks on QueueFair, make sure you have everything below prepared:
* [ ] **Profiles**
> Create and save your checkout [profiles](broken://pages/Jan7omhGk4GyKDyxn4Rt) under the **Profiles tab** in Stellar. These contain your billing, shipping and payment info.
* [ ] **Proxies**
> - **ISP proxies** – Recommended for some of your tasks
> - **Residential proxies** – Recommended for majority of your tasks
> * Save both proxy groups under the **Proxies tab** in Stellar.
> * If you're looking for proxies, check out [Stella Proxies](https://guides.stellaraio.com/stellar/getting-started-with-stellaraio/stella-proxies) for high quality ISP and Residential proxies. As always, it's recommended to have multiple proxy providers, don't just rely on one.
* **Cook Group Access**
> Optional but recommended. Your [cook group](https://guides.stellaraio.com/stellar/getting-started-with-stellaraio/cook-groups) can help you find product URLs, SKUs and early restock alerts.
### QueueFair Task Overview
### **Queue Mode**
* Which **Mode** do I use?
* **Queue Mode** will allow you to wait in queue with multiple tasks at a time
* What does **Profile** mean?
* Select a **Profile** you want to use and that profile information will be used when checking out items
* Which **Proxies** should I use?
* ISPs and Resis are both OK
* How do I find the **Queue** **URL**?
* **Queue URL** is the entire URL of the product queue
* For example
* What **Delays** should I use?
* Delays around 4000 are OK
---
# 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://guides.stellaraio.com/stellar/retailers/queuefair.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.
