Categories: NSB Guides

Walmart – NSB Guide

NSB supports the following regions for Walmart: WalmartUS and WalmartCA.

Accounts Setup

You need to add your accounts to run Walmart.

Go to NSB Accounts tab.
Create a new group (from top left corner).
Select Walmart as group type.
Once the group is created, you may add your accounts by inserting emails and passwords.
IMAP is required so NSB can automatically fetch and enter the login verification code.
After adding your accounts, make sure you login to your accounts by clicking the “Green Start Icon” in the top right corner. Note: Walmart Account registration is not supported in NSB.

Task Creation

Input:

Add the item ID as task input.

For example, if the item URL is: https://www.walmart.com/ip/GOTRAX-G3-Plus-Adult-Electric-Scooter-300W-10-Tires-Max-18-mile-Foldable-Escooter-for-Adult-Gray/501533764

The item ID will be: 501533764
Accounts:

Select your accounts by selecting one of the Walmart account groups you’ve already created in the Accounts tab.
Size:

Not required for almost all items.
Offer ID:

If you have the offer id, you can use it. Otherwise, NSB will pick the cheapest offer.
Proxies:
- You can notice that Walmart has 2 dropdowns to pick proxies. This is mainly used when running on “Queue” drops.
- You can specify a list of proxies to checkout (the first proxy list) and choose a different proxy list to enter and pass Queue (the second proxy list).
Quantity:

You may specify the quantity by clicking the Advanced field when creating your task and entering the desired quantity.
Starting Your Tasks:

You should start your tasks with random input (if you are not sure about the dropping item SKU) easily 30 minutes before the drop time in order to prepare it for queue.
Once the real SKU drops, simply use Control (or Command if on mac) + I in order to inject the desired SKU. Tasks won’t restart, they will continue checking the queue for the new SKU.

Walmart Modes

1. Normal Mode (Required for Queue drops): Use this mode if you are testing on an available item, running for initial drop (with Queue), or if you want each task to monitor an item restock on its own (each task will keep checking if the item you want got restocked).

Monitor and Watch Modes: These two modes are closely related and work together:

Running Monitor tasks without corresponding Watch tasks is ineffective.
Watch tasks require active Monitor tasks; otherwise, they will show no Monitor task available for the given item code.

2. Monitor Mode:

Purpose: Continuously checks the availability of specified Item Code(s).
Restock Detection: When a restock is detected, a monitor task will notify all associated Watch tasks, allowing them to complete the checkout.
Proxy Use: A proxy list with high-quality proxies is recommended for running Monitor tasks.
Multiple Item Codes:
- You can add Multi Codes using the + button.
- The task monitors all the SKUs at once, depending on the number of proxies in the assigned proxy list.
- The number of proxies should match or exceed the number of SKUs being monitored.
- Watch tasks will be waiting for monitor tasks. Once notified, Watch tasks will start working instantly.

This is an example of a monitor task monitoring 1 item. You may add as many items per task as you want.

3. Watch Mode:

Purpose: Waits for a matching Monitor task to detect a restock of a specific item.
Triggering:
- Once a restock is detected, the Watch task proceeds to checkout.
- You can add multiple SKUs to a Watch task (same as the Monitor task above).
Persistence:
- Watch tasks run continuously until manually stopped.
- After checkout, the task automatically restarts to maximize the chances of securing multiple restock checkouts.
Auto-Restart:
- If the task fails to checkout within 2 minutes, it auto-restarts to attempt checkout again.

Recommended Proxy Type

ISPs are usually used to to pass Queue and Resis for checkout. So, a recommended setup for Queue Drops will be as follows:

Pick Residential proxies in the first proxy dropdown list, which is used for checkout and flow.
Pick ISPs in the second proxy dropdown list, which is used to pass Queue.
(It is better to run some tasks with ISPs for queue and some with Resis for queue.)

Site Security

NSB will solve site security on its own. If it failed to, usually it means the proxy you are using is bad and you need to change it.
456 is a common error on Walmart, it’s usually a proxy or flow (bot) issue. We try our best to keep the module up to date by improving the flow/module, so as long as we mention that the module is working with no issues then your proxies are causing the 456 error.