Appearance
Mueller
Click & Collect only. OrbitAIO reserves the item at a Mueller store of your choice and you pay at the counter when you collect it. Nothing is charged online, and no card details are used for this store.
Guest checkout — a Mueller account is not needed.
Run Mueller without a monitor
This is the most important setting on this page, and it is the opposite of the advice for most other stores.
Create a plain task pointed at the product. Do not put a monitor in the group.
A Mueller task is already its own stock detector: it prepares everything once and then retries only the final order step. A monitor cannot be faster than that, and it makes things worse — with a monitor in the group the task waits for the signal before it prepares anything, so all the setup happens after the item is already available.
If you want a monitor purely for Discord stock alerts, that works — just give it its own Store ID and keep it out of the group your checkout tasks run in.
Setup
1. Set your pickup store
Open the profile you want to use, go to Other settings (optional), and fill in Mueller Store ID with the numeric store code, e.g. 3204. You find it on mueller.de in the store's details or in the store page URL.
Do not leave this empty
A task with no Store ID does not start. It refuses immediately with "Missing store: set Store ID in the profile", and it never picks a store for you.
A monitor has no profile, so it takes the store from its own Store ID field — empty there gives "Missing store: set Store ID on the monitor".
2. Profile fields
Mueller receives your first name, last name, e-mail and, if filled in, your phone number.
Your profile address is not used. Delivery and billing address are the pickup store's own address — that is how Click & Collect works. You still need to fill the address fields to save a profile in the app.
3. Create the task
| Field | What to enter |
|---|---|
| Product | Product URL, PPN/IPN code, plain numeric ID, or EAN |
| Quantity | A number, or MAX for the product's maximum allowed quantity |
| Country | Germany (mueller.de, default) or Austria (mueller.at). The Store ID must belong to the market you pick |
| Max Price | Optional ceiling in EUR, compared against the cart total including VAT |
| Delay | Retry interval in ms. Around 3000 works well |
| Profile | The profile carrying your Mueller Store ID |
| Proxy | A residential group with several exits |
You can also start a task with an empty Product field. It waits at "Waiting for product…" and picks the product up the moment you fill it in via task edit.
Product input formats
| Format | Example |
|---|---|
| Full URL | https://www.mueller.de/p/some-product-123456/ |
| PPN / IPN code | PPN123456789 |
| Numeric ID | 123456789 |
| EAN | 4001234567890 |
Variants
A URL without a PPN/IPN code lands on the product's default variant. If the product has variants, paste the URL of the one you actually want.
Start early
Mueller accepts sold-out items into the cart, so a task started while the item is still unavailable prepares the entire checkout in advance and then waits on the last step alone. Start your tasks before the drop.
Because of that, "Waiting for restock…" barely ever appears here. The normal waiting state is the task sitting at step 8/8 with "OOS – Retrying…". That is correct, not stuck.
Store stock is not online stock
What mueller.de shows about online availability says nothing reliable about the shelf in your pickup store — the two disagree constantly, in both directions. Judge by the task, not by the website.
Proxies
Use residential proxies, and keep the group small — two to four exits is ideal.
Mueller's blocking is reputation-based, so the task rotates on its own and a restart or two at the beginning is normal. But every new exit costs the task a short extra setup step of its own, and that work cannot be shared between exits. A large group therefore makes a task slower to get going, not more reliable. Prefer a handful of good residential exits over a big pool.
Quantity
A number, or MAX for the product's maximum. MAX costs one extra session restart while the task reads the limit (Max qty=N, restarting…). If the shop refuses the quantity outright, the task stops with "Quantity not supported".
Common statuses
| Status | Meaning |
|---|---|
Missing store: set Store ID in the profile | The assigned profile has no Store ID. Add one and restart |
Missing store: set Store ID on the monitor | A monitor was created without a Store ID |
Waiting for product... | Empty Product field — fill it in via task edit |
OOS - Retrying... (step 8/8) | Normal waiting state. Leave it running |
Max qty=N, restarting... | MAX resolved the limit and is restarting with it |
Backend error, retrying... | Mueller's backend timed out. Never means the item is gone |
Quantity not supported | The product's per-order limit is below your quantity |
Solving CDN challenge... | Normal setup step on a new exit. Takes about a second; a short browser window may flash up |
CDN challenge failed / CDN challenge rejected | That exit could not be prepared. The task moves to the next proxy on its own |
Blocked, rotating proxy... | The exit was refused; moving to the next proxy |
Success: Checkout! | Reservation placed, order number in the log |
Success always has an order number
A task only goes green with a real order number, which you will find in the task log and in your Discord webhook.