What is Valor AIO? Valor AIO is a paid all-in-one checkout bot for Windows and macOS, now on version 3.0. It runs tasks across several retail platforms (Footsites, Best Buy, Target, New Balance, Funko and more), each grouped by site. Proxies are optional in the software, but Valor's own docs call them highly recommended and nearly required on many sites.
A clean Valor AIO proxy setup is the difference between tasks that reach checkout and tasks that loop on errors until the drop is over. Valor gives you proxy groups, per-account proxies, a site connection test and separate proxy fields for captcha harvesters and browser windows. Each of those pieces behaves a little differently, and most failed runs trace back to one of them being set up wrong.
This guide is based on the current Valor 3.0 documentation and the official Valor site. It covers which sites Valor supports today, exactly how proxies are added, the line format Valor expects, which proxy type suits which task, how many IPs you need per task, and what to check when tasks start failing. If you learned Valor from older tutorials, note that the 2020 launch version supported only a few sneaker sites. Valor 3.0 is a much broader retail bot, and pre-3.0 menu names may not match what you see now.
What sites does Valor AIO support right now?
The Valor 3.0 docs have module guides for Footsites (Foot Locker and Champs, US and CA), Best Buy, Target, New Balance, Funko, Shopify, Nike FLOW, Nike DRAW, Walmart and Pokémon Center. The official site claims coverage of 500+ retailers. Each module needs its own task group.
That last point matters for proxies. Valor ties every task group to one site, so if you run Target and New Balance on the same night you will build at least two task groups, and each one can point at a different proxy group. Plan your proxy groups around sites from the start rather than dumping everything into one list.
Valor is not an impulse buy. The official site lists a license at $1,999.99 with renewals at $49.99 a month, and copies are released in waves through a waitlist and Discord announcements.
How do you add proxies in Valor AIO?
Open the Proxies page from the top navigation bar, click the blue Add icon in the top left to create a named proxy group, paste your proxies into the text area one per line, then click Save List. The proxies appear in the table on the right, and any task group can then select that group.
Step 1. Create one group per site or purpose
Valor's docs suggest separate groups for different sites or tasks. A practical split is one checkout group per site you run, plus a separate monitor group for sites that offer a monitor proxy field (Target does). Keeping them apart stops a heavy monitor from burning the IPs your checkout tasks rely on.
Step 2. Paste and save the list
Select the group, paste your lines into the text area and click Save List. To move lists between machines, use Import and Export under Proxy Groups for many groups, or the buttons beside the selected group name for one group. Valor warns that mixing them up can import data incorrectly.
Step 3. Attach the group to your tasks
When you create tasks inside a task group, pick your list in the Proxy Group dropdown. It is marked optional on every module, but the module guides for Footsites, Best Buy, New Balance, Funko and Target all say proxies are highly recommended. Quick Tasks launched from Valor's monitor have their own Proxy Group fields, so set those too if you use them.
Step 4. Decide whether accounts get a fixed proxy
On the Accounts page you can add a proxy to the end of an account line. Valor's docs say an account with a proxy attached will always use that proxy during checkout. That is useful on login-based sites where you want one account to keep appearing from the same IP.
Step 5. Check the captcha and window proxy fields
Captcha harvesters have an optional proxy field. Valor's docs say most modules use the task's own proxy for captcha solving by default, and recommend leaving the harvester proxy blank if you only use that harvester for such a module. Settings also has a Domain Change Window Proxy (used for certain Shopify releases) and a 3DS Window Proxy for 3D Secure windows. Both are only needed if you know your home IP is banned on the site.
Which proxy format does Valor accept?
Valor's proxy page uses the standard ip:port:user:pass layout, one proxy per line. Account lines use email:password, with an optional proxy added at the end. Paste proxies exactly as your provider delivers them, with no spaces, no protocol prefix and no trailing commas.
The example in the docs looks like this:
45.67.120.34:8000:user1:pass1
52.14.88.201:9000:user2:pass2Loopway delivers proxies in the dashboard as host:port:user:pass lines, which is the same order, so a Loopway list can be pasted straight into a Valor proxy group. For account lines, Valor's example shows a proxy as ip:port after the password (example2@gmail.com:password123:192.168.1.25:8000). The docs do not show a full user:pass proxy inside an account line, so test one account before you bulk import.
Which proxies are best for Valor AIO?
For checkout tasks on login-based sites such as Target and Best Buy, static ISP proxies are the strongest default: one fixed, clean IP per account that stays the same for the whole drop. Rotating residential proxies suit monitor groups and high task counts where each request can come from a new IP.
Valor's module guides give a useful hint here. Its Best Buy, New Balance and Funko pages all say those sites mainly judge proxy reputation, meaning how suspicious an IP looks based on data collected across the internet, and that some proxies are already flagged before you use them. That puts IP quality ahead of raw speed. Here is how that maps to task types:
- Account-based checkout (Target, Best Buy). These tasks log in, save a session and come back to it. Valor says password-login sessions on Target tend to last longer, while OTP login sessions last around four hours. A static ISP IP keeps each account on one stable address while the session is alive.
- Account creation tasks. Valor's Best Buy module has a Create Account mode. If you will use those accounts later, create each one on the same static IP you plan to check out with.
- Guest checkout (Footsites, New Balance). No saved session to protect, so either static ISP or residential works. Valor's New Balance guide is explicit that you should not run more than one task per proxy.
- Monitoring. A separate monitor group on rotating residential keeps repeated stock checks off your checkout IPs. Valor's New Balance guide also advises against heavy monitoring on non-drop days.
Static ISP proxies built for this job are on the Loopway Retail ISP page: dedicated IPs, 0 fraud score, unmetered bandwidth, sold from $1.08 for a single day. For monitors, rotating residential proxies are billed per GB instead. If you are unsure which family fits your setup, the ISP vs residential guide walks through the trade-offs.
How many proxies do you need per Valor task?
Plan on one proxy per task. Valor's New Balance guide says not to run more than one task per proxy, and its Target guide says the best way to see fewer rate limits is to run unsaturated proxy pools. For account-based sites, that also means one proxy per account.
So 40 Target tasks on 40 accounts means 40 checkout IPs, plus your monitor group. With only 20 clean IPs, run 20 tasks rather than doubling up, since two tasks on one IP double its request load.
For big Target runs, Valor's guide suggests stagger-starting roughly 50 to 200 tasks per minute, 30 to 60 minutes before release, which is easier on your proxies than firing everything at once.
Testing your Valor proxies before a drop
Valor's proxy table has a site dropdown, a Test All button and per-row action buttons. Choose the site you are about to run and test the group. Remove anything that fails to connect.
Valor's docs say plainly that this test only shows whether a proxy can connect to the selected site, not whether it is good for checkout. The docs recommend a real task as the true test.
A sensible pre-drop routine:
- Run Valor's Test All against the target site and drop dead proxies.
- Check a few IPs in the Loopway proxy tester for latency and location, or confirm the exit IP with the IP checker.
- Run a small batch of real tasks on a low-stakes restock or with a placeholder product to watch task statuses.
- Keep the full group quiet until release day so it is not worn out by monitoring.
Troubleshooting common Valor proxy problems
Valor's docs flag several statuses as normal, so check these before you replace a whole list.
Tasks loop on Out of Stock or Product Not Live
On Footsites this is expected before and just after release. Valor says tasks keep trying to cart until the site lets them through, and there is no clear release-starting status.
Target shows Rate Limited
Valor describes this as normal, a kind of queue Target uses to let tasks through slowly. Most tasks will see it. To see less of it, spread tasks across more IPs rather than stacking several tasks on each one.
Tasks are blocked across the board
Valor's New Balance guide recommends trying a different proxy provider for the next release when tasks are blocked often. Its Footsites guide adds that the device itself can count against you: servers and machines without a GPU look less human. If you run Valor on a VPS, test a few tasks on your own PC to see whether the proxies or the machine are the issue.
Captcha harvesters behave oddly
If a harvester has its own proxy set while the module already solves captchas on the task proxy, you can end up with two IPs on one checkout. Clear the harvester proxy field for modules that use the task proxy.
Nothing runs at all
Open Settings and check Task Engine Status. If it does not say Ready, Valor's docs say to restart and contact support. That is a bot issue, not a proxy one.
For more on proxy choice for these sites, see our guides on ISP proxies for Target and daily ISP proxies, which suit one-night Valor runs.
Key Takeaways
- Valor 3.0 supports Footsites, Best Buy, Target, New Balance, Funko and other modules, with one site per task group.
- Add proxies on the Proxies page with the blue Add icon, paste
ip:port:user:passlines and click Save List. - Run one task per proxy, and on login sites keep one account on one static IP.
- Valor's Test All only checks connectivity, so confirm proxies with a small real run before the drop.
- Keep monitor traffic in a separate group so it does not wear out your checkout IPs.
FAQ
Can Valor AIO run without proxies?
Yes, the proxy group field is optional on every module. Valor's own docs still call proxies highly recommended and nearly required on many sites, and running several tasks from one home IP is the fastest way to get blocked.
Does Valor support IP-whitelisted proxies?
The Valor 3.0 docs only show the user:pass format. If your provider offers both, use user:pass so the list works on any machine you run Valor from.
Where do I add a proxy for a single account?
Add it to the end of the account line on the Accounts page. Valor says that account will then always use that proxy during checkout.
Should my captcha harvester use a proxy?
For most modules, no. Valor uses the task's proxy for captcha solving by default and recommends leaving the harvester proxy blank when the harvester is only used for those modules. Check each module guide to confirm.
Are static ISP or residential proxies better for Valor?
Static ISP proxies are the safer default for checkout and account tasks because each IP stays fixed. Rotating residential proxies are a good fit for monitor groups and large guest-checkout runs.
Why do my proxies pass Valor's test but still fail at checkout?
The built-in test only confirms the proxy can connect to the site. Valor's docs note that some sites judge IP reputation and that some proxies are flagged before you ever use them, which a connection test cannot show.
Get your Valor AIO proxy setup right once, with groups per site, one IP per task and a real test run before release, and every drop after that gets easier. If you need clean, dedicated static IPs for your next run, Loopway sells Retail ISP proxies by the day, so you only pay for the nights you actually run.