> 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/walmart-go-us.md). # Walmart GO (US)
### Module Summary StellarAIO’s Walmart GO module supports account-based checkout for Walmart US. It is designed for both standard restocks and high-demand releases that use Walmart’s queue system. Walmart can experience heavy traffic, queue delays, rate limits, proxy blocks, and rapid stock changes. Preparing accounts and starting tasks early is important. Always check the latest Stellar announcements before a major release. Drop-specific instructions may temporarily override the general recommendations in this guide. *** ### Video Guide Watch the complete Walmart setup {% embed url="" %} *** ## Quick Start: Recommended Setup This is the standard Walmart GO setup. Follow these steps in order. ### 1. Prepare Your Walmart Accounts and Profiles Before creating tasks: * Update StellarAIO to the latest version. * Add the Walmart accounts you intend to run. * Create one matching Stellar profile for each account. * Make sure the profile email exactly matches the corresponding Walmart account email. * Confirm that every profile contains valid billing, shipping, payment, phone, and email information. * Use unique profiles for your Walmart accounts. * Test important accounts and profiles on an in-stock product before a major release. Walmart supports SMS-verified and non-SMS-verified accounts. If you are running non-SMS-verified accounts, update Stellar to the latest version and prepare either Manual or [Wealth SMS](https://discord.gg/4Sdckp8Tcb) verification. ### 2. Add Your Walmart Sessions Open: ``` Identities → Sessions → Walmart ``` Add each Walmart account using its email and password. You may organize accounts into separate session groups to make larger setups easier to manage. After adding the sessions: * Confirm the saved account credentials are correct. * Confirm each account email matches its assigned Stellar profile email. * Test the accounts before an important release. * Update the saved password if an account password changes. When creating Checkout tasks, leaving the **Session** field blank allows Stellar to automatically match a Walmart session to the selected profile using the corresponding email. This is the recommended starting setup. Select a specific Session only when you intentionally want to assign a particular Walmart account. ### 3. Prepare Email and Phone Verification #### Email OTP Verification [IMAP](/stellar/navigating-stellaraio/what-is-the-identities-tab/imap-overview.md) is optional but recommended when managing many Walmart accounts. If using IMAP: * Create and test your IMAP session. * Select the IMAP session in your Checkout tasks. * Set **OTP Input** to **IMAP**. If you are not using IMAP: * Set **OTP Input** to **Bot**. * Be prepared to enter Walmart email verification codes manually through Stellar. #### Checkout SMS Verification This setting only matters when Walmart asks a non-SMS-verified account to verify a phone number at checkout. Choose one of the following: * **Manual:** Enter a valid 10-digit US phone number and its verification code through Stellar’s verification windows. * **Wealth SMS:** Allow Stellar to complete verification automatically after adding your Wealth SMS API key in Settings. Leaving **Checkout SMS Verification** unselected defaults to Manual. No special phone-verification setup is required when every account is already SMS verified. ### 4. Create Your Monitor Tasks Walmart Monitor tasks are required for the recommended setup. Create Monitor tasks using: * **Mode:** Monitor * **Monitor Proxy:** High-quality ISP proxies * **SKU:** The confirmed Walmart SKU, or leave it blank and live edit it when announced * **Monitoring Delay:** `3000–5000` * **Max Price:** Recommended, especially when allowing third-party offers * **Allow 3rd Party:** Off unless you intentionally want marketplace offers * **Reset Delay:** Blank unless current instructions recommend a value * **Task Count:** Start with `1` Monitor per SKU and scale up to `5` when additional redundancy is needed If ISP monitors struggle during a high-traffic release, high-quality residential proxies may be used as backup. ### 5. Create Your Checkout Tasks Create Checkout tasks using: * **Mode:** Checkout * **Profile:** Profile matching the Walmart account * **Checkout Proxy:** High-quality residential proxies * **Queue Proxy:** High-quality residential proxies, or leave blank to reuse the Checkout Proxy * **SKU:** Confirmed product SKU, or leave blank and live edit it when announced * **Offer ID:** Blank unless current drop instructions specifically recommend one * **Delay:** `3000–5000` * **Qty:** Follow the product limit provided by your cook group or displayed by Walmart * **Session:** Blank for automatic profile-to-session matching * **IMAP Session:** Optional * **OTP Input:** IMAP when using IMAP; otherwise Bot * **Checkout SMS Verification:** Manual by default, or Wealth SMS when configured * **Reset Invalid Password:** Off unless account recovery is intentionally needed * **Task Count:** One Checkout task per Walmart account and SKU Each Checkout task supports only one SKU. You may run different SKUs using the same Walmart account, but do not create duplicate Checkout tasks for the same account and SKU. ### 6. Start Your Tasks Early For a scheduled release: 1. Start your Checkout tasks more than one hour before the expected release when possible. 2. Starting approximately three hours early can provide additional time for accounts to log in and establish their sessions. 3. Confirm that your accounts and sessions are ready. 4. Start the Monitor tasks before the expected restock. 5. Confirm that each Monitor uses the same SKU as its corresponding Checkout tasks. You must manually start tasks even when a Start Time is configured. A scheduled Start Time does not start a stopped task. Do not wait until queue opening to test accounts, profiles, proxies, or verification methods. ### 7. Confirm Your Setup Is Ready Before leaving the setup running, confirm: * StellarAIO is updated. * Every Walmart account has a matching profile. * Account and profile emails match exactly. * Checkout tasks have successfully established their sessions. * Every SKU has at least one running Monitor. * Monitor and Checkout tasks use the same SKU. * Checkout and queue proxies have been tested. * IMAP is ready, or you are prepared to enter email codes manually. * Non-SMS-verified accounts have a verification method prepared. * Wealth SMS users have added a valid API key. * No duplicate Checkout tasks are using the same account and SKU. * You can receive Stellar webhook notifications. ### 8. During the Release When a SKU becomes available: 1. Copy the confirmed SKU from a trusted source. 2. Live edit any Monitor and Checkout tasks that were created without a SKU. 3. Confirm that the Monitor and Checkout tasks use the same SKU. 4. Leave correctly progressing tasks running through temporary queue-entry failures, 456 responses, and high-traffic errors. 5. Avoid restarting the complete setup unless Stellar staff instructs you to restart. 6. Watch for email OTP, phone-verification, and checkout webhooks. 7. Live edit quantities or proxies only when necessary. Walmart may struggle when a queue first opens. Tasks can temporarily fail to enter the queue and continue retrying. A displayed queue estimate of approximately 28–31 minutes may indicate that the task is far behind in line. Allow it to continue unless newer instructions say otherwise. Always follow the latest instructions posted by Stellar staff. Drop-specific announcements override this general setup. *** ### Preliminary Checklist Before creating Walmart tasks, confirm the following: * [ ] StellarAIO is updated to the latest version. * [ ] Walmart accounts have been added under **Identities → Sessions → Walmart**. * [ ] If you are running non-SMS-verified accounts, confirm StellarAIO is updated to the latest version that supports checkout SMS verification. * [ ] Decide whether non-SMS verification will use **Manual** input or **Wealth SMS**. * [ ] If using [Wealth SMS](https://discord.gg/4Sdckp8Tcb), add your Wealth SMS API key in Stellar’s Settings before creating tasks. * [ ] Have access to enough unique US phone numbers for the non-SMS verified accounts you are running. * [ ] Each checkout profile has valid billing, shipping, and payment information. * [ ] Each profile email matches its corresponding Walmart account email. * [ ] Profiles are unique and do not reuse the same card and customer information across accounts. * [ ] High-quality residential proxies are available for checkout and queue entry. * [ ] ISP proxies are available for monitoring. * [ ] You have proxies from more than one provider or pool. * [ ] IMAP is configured if you want automatic email-code retrieval. * [ ] You have the correct SKU or can obtain it when the product is announced. * [ ] At least one Monitor task will be running for each SKU. * [ ] Your accounts, profiles, proxies, and delays have been tested on an in-stock product. * [ ] Cook group notifications are enabled for product and drop information. *** ## Computer or Server Walmart can be run on either a personal computer or a server. ### Personal Computer A personal computer is completely acceptable. Your internet connection may affect how quickly tasks communicate with Walmart and enter the queue. ### Server A server is also acceptable and may offer better internet connectivity, but it is not automatically better than a properly configured personal computer. Choose the environment that gives you: * Reliable internet * Stable system performance * Enough resources for your task count * Convenient access during verification prompts *** ## Walmart Accounts and Sessions ### Accounts Are Required Walmart Checkout Mode requires Walmart accounts. Walmart accounts may be SMS verified or non-SMS verified. SMS-verified accounts require no additional phone-verification setup. Non-SMS verified accounts can run, but Walmart may require phone verification when an account reaches checkout. Stellar supports two ways to complete this: * **Manual:** Enter a US phone number and its verification code through Stellars harvester windows. * [**Wealth SMS**](https://discord.gg/4Sdckp8Tcb)**:** Allow Stellar to complete the verification automatically using Wealth SMS. Verification is requested only when Walmart requires it during a potential checkout. After an account is successfully verified, it should not require verification again while that phone number remains attached to the account. You must use the latest StellarAIO version when running non-SMS-verified accounts. For larger releases, experienced users may run many accounts. Some high-scale setups use 100 or more accounts, but this is not required for beginners. Only run the number of accounts, profiles, proxies, and verification requests you can manage correctly. *** ### Adding a Walmart Session 1. Open the **Identities** tab. 2. Select **Sessions**. 3. Select **Walmart**. 4. Create or select a session group. 5. Click **Add Session**.
6. Enter the account information. 7. Save the session. 8. Run a test task on an in-stock product. ### Session Fields #### Session Name Enter an optional organizational name. Using the account email or a numbered naming system can make a large setup easier to manage. #### Email Enter the Walmart account email. This email should match the corresponding profile email. #### Password Enter the current Walmart account password. If the password changes, update the saved session before running the account again. #### Account Proxy Optional. Assigns a proxy to the account’s session activity. A stable account proxy may be useful during high-demand releases. Test account proxies before the drop and avoid assigning the same proxy to an excessive number of accounts. *** ### Mass Importing Walmart Accounts If you have many accounts: 1. Open **Identities → Sessions → Walmart**. 2. Select the desired session group. 3. Click **Mass Import Sessions**.
4. Enter one account per line using the format displayed in Stellar. 5. Save the sessions. 6. Verify that the accounts were imported correctly. Do not expose your complete account list when requesting support. *** ## Profiles Every Checkout task requires a profile containing: * Email * Shipping address * Billing address * Payment information * Phone number The profile email must match the corresponding Walmart account email so Stellar can associate the correct account with the task. Profiles should be unique. Do not reuse the same card and customer information across multiple Walmart accounts. Stellar does not provide instructions for creating or disguising unique customer information. Consult your cook group for legitimate account-management guidance. *** ## IMAP and OTP Verification IMAP is optional, but it is helpful when managing many Walmart accounts. A working IMAP session allows Stellar to retrieve Walmart email verification codes automatically. See the [IMAP Overview Guide](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-identities-tab/imap-overview) for setup instructions. A common preference order is: 1. Gmail 2. iCloud 3. Outlook 4. Other supported providers You may also forward verification emails from multiple account inboxes to one supported master IMAP inbox. *** ## Supported Modes ### Checkout Mode Checkout Mode is used for: * Standard restocks * Queue releases * Account login * Queue entry * Adding the selected SKU to cart * Completing checkout Only one SKU can be entered in each Checkout task. You may run different SKUs on the same Walmart account, but do not run duplicate Checkout tasks for the same account and SKU. Recommended limit: ``` 1 Checkout task per Walmart account and SKU ```
### Monitor Mode Monitor Mode checks a SKU for inventory. Monitor tasks are required for the recommended Walmart setup. Use: ``` 1–5 Monitor tasks per SKU ``` Start with one Monitor and add redundancy only when your proxy supply and setup can support it.
*** ## Checkout Mode Field Breakdown ### Name Optional. Enter a name that identifies the product or setup. If left blank, Stellar displays available product information such as the SKU. ### Profile Required. Select the profile associated with the Walmart account. If no profiles are available, create them before continuing. ### Checkout Proxy Required. This proxy is used during the checkout process. High-quality residential proxies are recommended. Use multiple proxy providers and pools rather than relying on one source. ### Queue Proxy Optional. This proxy is used when entering Walmart’s queue. High-quality residential proxies are recommended as the general starting point. If left blank, the task uses the selected Checkout Proxy for queue entry. ### SKU The Walmart product identifier. For example, in this URL: ``` https://www.walmart.com/ip/Example-Product/580726295 ``` The SKU is: ``` 580726295 ``` SKUs may not be available before certain releases. You can create tasks without a SKU and live edit the correct SKU after it is announced. Product information should come from your cook group or another trusted source. Stellar does not provide drop SKUs. ### Offer ID Optional. An Offer ID identifies a specific Walmart offer or seller listing. Leave this field blank for the standard setup. When an Offer ID is entered, Stellar can repeatedly attempt to add that exact offer to cart even when it appears out of stock. Only use an Offer ID when it is provided by a trusted source or recommended for a specific release. Stellar does not provide Offer IDs. ### Delay Required. Controls the time between task requests. Recommended starting range: ``` 3000–5000 ms ``` Lower delays make requests more frequently but increase the chance of `456` responses and proxy rate limits. Higher delays are safer but may move more slowly. Adjust delays based on: * Proxy quality * Walmart traffic * Number of tasks * How long tasks have been running * Current drop instructions ### Qty Required. Enter the number of units the task should attempt to purchase. Product limits vary. Check with your cook group or review the Walmart listing before selecting a quantity. Stellar does not automatically lower the quantity when your entered value exceeds Walmart’s limit. ### Session Select a specific Walmart session when you want to manually assign an account. You may also leave this field blank. When blank, Stellar automatically matches a session to the selected profile using the corresponding email. This is the recommended option for most setups. ### IMAP Session Optional. Select the IMAP inbox used to retrieve login codes automatically. ### OTP Input Required. Determines how Walmart verification codes are entered. * **IMAP:** Select when a working IMAP session will retrieve and enter the code. * **Bot:** Select when you want to enter the code manually through Stellar. ### Checkout SMS Verification Controls how Stellar handles Walmart phone verification when a non-SMS-verified account reaches checkout.
Available options: * **Manual:** Stellar opens harvester windows that ask for a 10-digit US phone number and the verification code sent to that number. * [**Wealth SMS**](https://discord.gg/4Sdckp8Tcb)**:** Stellar uses your configured Wealth SMS account to complete phone verification automatically. If the field is left unselected, Stellar defaults to **Manual**. Wealth SMS is currently the only directly supported third-party provider for automatic Walmart verification. Manual verification may use your personal number or a number obtained from any third-party SMS service you choose. This setting only affects accounts that Walmart asks to verify. Accounts that are already SMS verified proceed through the normal checkout flow. ### Reset Invalid Password Enable this only if you want Stellar to attempt account recovery when Walmart reports that the saved password is invalid. Make sure the account’s email is accessible before enabling this option. ### Start Time and End Time Optional scheduling controls. You must still manually start the task. A Start Time does not start a stopped task by itself. ### Task Quantity The **Qty** control at the bottom of the creation window determines how many copies of the configured task Stellar creates. This is different from the product Qty inside Checkout Mode. When creating multiple tasks, confirm that profiles and accounts are assigned as intended. *** ## Monitor Mode Field Breakdown ### Name Optional. Enter a recognizable name for the product or monitor group. ### Monitor Proxy Required. Select the proxy group used to monitor Walmart. ISP proxies generally work well. If ISP monitors begin struggling near a high-demand release, residential monitors may be used as backup. ### SKU Enter the SKU that the task should monitor. You may create the Monitor task before an unreleased SKU is announced and live edit the SKU later. Only one SKU can be monitored per task. ### Monitoring Delay Required. Controls how frequently the task checks Walmart. Recommended starting range: ``` 3000–5000 ms ``` Adjust this based on proxy quality and current site conditions. ### Max Price Optional. Enter the maximum item price you are willing to accept. This limit should be based on the price of one unit, even when the checkout task requests multiple units. Remember that the final order total may also include: * Tax * Shipping * Other Walmart charges A Max Price is strongly recommended when **Allow 3rd Party** is enabled. ### Allow 3rd Party Optional. Enables monitoring of marketplace offers from third-party sellers in addition to Walmart’s standard retail offers. Third-party offers may cost substantially more than retail. If enabled, set a Max Price to prevent an unexpectedly expensive offer from triggering your setup. ### Reset Delay Optional. Controls when the monitor resets after detecting stock. There is no universal recommended value. Leave this blank unless current instructions or your own testing call for a specific delay. ### Start Time and End Time Optional scheduling controls. You must still manually start the Monitor task. ### Task Quantity Controls how many copies of the configured Monitor task Stellar creates. *** ## Scaling Your Walmart Setup The recommended starting task counts are listed in **Quick Start: Recommended Setup**. When increasing the size of your setup, consider: * Number of valid Walmart accounts * Number of matching profiles * Checkout and queue proxy quality * Number of proxy providers and pools * IMAP or manual OTP capacity * Phone-verification capacity * Computer or server performance * Current Stellar task limits * Drop-specific instructions Avoid creating more tasks than your accounts, proxies, and verification methods can support. Duplicate Checkout tasks using the same account and SKU can contribute to login instability, session conflicts, duplicate cart activity, account locks, and checkout failures. Start with a manageable setup, test it on an in-stock product, and scale only after confirming that it works reliably. *** ## Long-Running Monitors and Unknown Restocks For scheduled releases, follow the timing instructions in **Quick Start: Recommended Setup**. When a restock time is unknown, Monitor tasks may be left running for longer periods. For long-running monitors: * Use reliable monitor proxies. * Use delays appropriate for extended monitoring. * Watch for repeated rate limits or proxy failures. * Rotate to another tested proxy pool when necessary. * Confirm that the SKU remains correct. * Keep Stellar updated. * Monitor your cook group and Stellar announcements for new information. Do not use unnecessarily aggressive delays for monitors that may run for several hours. *** ## Queue Behavior Walmart queues are not always entered immediately. The site may slow down or temporarily fail when a large number of users enter at once. If tasks do not enter the queue immediately: * Let them continue retrying. * Avoid immediately restarting the entire setup. * Confirm the proxies are working. * Watch Stellar announcements for specific instructions. A displayed queue time of approximately `28–31 minutes` can act as a placeholder indicating that the task is far behind in line. Allow the task to continue. Queue placement does not guarantee that a task will reach checkout before inventory sells out. *** ## Non-SMS Verified Accounts Walmart may require a non-SMS-verified account to complete phone verification when it reaches checkout. This does not mean every account will be verified when tasks start. Verification is requested only if the account reaches the point where Walmart requires it during a potential checkout. You must update StellarAIO to the latest version before running non-SMS-verified accounts. If all your accounts are already SMS verified, this feature is not required. Updating is still recommended because the release may include other Walmart flow improvements. ### Choosing a Verification Method The **Checkout SMS Verification** field provides two options: * **Manual** * [**Wealth SMS**](https://discord.gg/4Sdckp8Tcb) Leaving the field unselected defaults to **Manual**. ### Manual Verification Use Manual when you want to provide the phone number and verification code yourself.
When Walmart requests verification: 1. Stellar pauses the affected Checkout task. 2. Stellar sends a webhook stating that manual SMS verification is required. 3. The webhook includes the affected account details and a checkout link. 4. A phone-verification harvester window opens. 5. Enter a valid 10-digit US phone number. 6. Enter only the numbers. Do not use spaces, dashes, parentheses, or other symbols. 7. Select **Send Code**. 8. Walmart sends a verification code to the submitted phone number. 9. A second harvester prompt asks for that code. 10. Enter the received code. 11. After successful verification, the task resumes checkout.
You may use: * Your own US phone number * A number from any third-party SMS provider or service Walmart generally allows each phone number to be attached to only one account at a time. If you submit a number that is already attached to another Walmart account, Walmart may remove it from the previous account and attach it to the account currently being verified. After successful verification, the account should not require verification again while the phone number remains attached to it. ### Wealth SMS Automatic Verification [Wealth SMS](https://discord.gg/4Sdckp8Tcb) is currently the only third-party provider directly supported for automatic Walmart checkout verification. To use it: 1. Obtain your Wealth SMS API key. 2. Open Stellar’s **Settings**. 3. Add the Wealth SMS API key. 4. Create or edit your Walmart Checkout tasks. 5. Select **Wealth SMS** under **Checkout SMS Verification**. 6. Start your tasks normally. If Walmart requires phone verification at checkout, Stellar uses Wealth SMS to complete the verification process automatically. This setting has no effect on an account that is already SMS verified. ### Verification Webhook and Manual Checkout When a non-SMS-verified account encounters phone verification, Stellar sends a webhook containing: * The affected account information * Product information * A checkout link The checkout link provides a backup option. If you do not want to complete verification through Stellar, or the automated process cannot be completed, you may log into the account manually and attempt to finish the order in your browser. ### Restarting Manual Phone Verification During manual verification, a keyboard icon appears beside the task’s waiting status.
Clicking the keyboard icon restarts phone verification from the beginning. Use it only when: * The entered number is incorrect * The number cannot receive verification codes * The number is unavailable * You want to submit a different phone number After clicking the icon, Stellar asks for a new phone number and sends a new code to that number. Do not click the keyboard icon while waiting for a valid code unless you intentionally want to abandon the current attempt and restart verification. *** ## Live Editing Walmart tasks currently support live editing during the task flow. You can live edit: * Product quantity * Checkout or queue proxies * SKU when product information becomes available Use live editing carefully and confirm that the correct tasks are selected before applying mass changes. *** ## Latest Walmart Prep Call {% embed url="" %} The latest prep call or announcement may override the general proxy, delay, timing, or Offer ID recommendations in this guide. *** ## Common Errors and Fixes ### Error 456 **Meaning** Walmart is rate limiting requests, experiencing heavy traffic, or blocking the proxy. **What to Do** * Allow the task to retry. * Avoid rapidly restarting the entire setup. * Test another proxy pool if the error continues. * Use several reputable proxy providers. * Adjust delays when necessary. A `456` response is common during heavily trafficked releases. *** ### PX Block or Rotating Proxy **Cause** Walmart’s PX protection detected or blocked the proxy. **Fix** * Allow the task to retry briefly. * Test a different proxy. * Switch proxy type, pool, or provider. * Use high-quality residential proxies for checkout. *** ### Generating Cookie **Meaning** The task is attempting to pass Walmart’s PX protection. **What to Do** * Allow approximately 30 seconds for the process to complete. * Confirm that the checkout proxy is working. * Test a high-quality residential proxy if it remains stuck. * Restart only the affected task when necessary. *** ### Unknown Error Generating PX **Likely Cause** Proxy failure or proxy-authentication problems. **Fix** * Verify the proxy format and credentials. * Test another residential proxy. * Try a different pool or provider. * Restart the affected task after changing the proxy. *** ### Unknown Error Creating Cart **Likely Cause** A proxy or proxy-authentication problem. **Fix** * Test another high-quality residential proxy. * Confirm the proxy credentials. * Restart the affected task after changing the proxy. *** ### Failed to Fetch Availability **Cause** The Monitor task could not retrieve product information. **Fix** * Confirm the SKU is correct. * Remove spaces or unwanted characters. * Test another monitor proxy. * Restart the affected Monitor task. * Confirm the product page still exists. *** ### Cannot Read Properties of Undefined **Possible Cause** A task-group or backend-state conflict. **Fix** 1. Delete the affected task group. 2. Close Stellar. 3. Reopen Stellar. 4. Recreate the task group. 5. Contact support with logs if it continues. *** ### Address-Related Error **Likely Cause** Walmart rejected or could not process the address in the selected profile. **Fix** * Review the shipping and billing address. * Correct spelling and formatting problems. * Confirm required address fields are complete. * Test the profile manually on Walmart. * Try the task again after correcting the profile. *** ### Payment-Related Error **Likely Cause** Walmart rejected or could not update the payment information. **Fix** * Review the card details. * Confirm the billing address matches. * Confirm the card is valid and has sufficient funds. * Test the payment method on Walmart. * Retry after correcting the profile. *** ### Task Did Not Enter the Queue Immediately **Cause** Walmart may slow down or temporarily fail when queue traffic begins. **Fix** Let the task continue retrying. Avoid mass restarting unless Stellar announces that a restart is required. *** ### Task Never Passed the Queue **Possible Causes** * The queue position was too far behind. * The task entered the queue late. * The queue proxy was slow or blocked. * Inventory sold out before the task reached checkout. **Fix** * Start tasks earlier. * Use better queue proxies. * Diversify proxy providers. * Test connection quality before the next release. *** ### Long Queue Time A displayed estimate around `28–31 minutes` may indicate that the task is far behind in the queue. Leave the task running. The displayed time does not always behave like a precise countdown. *** ### Session or Login Failure **Possible Causes** * Incorrect account email or password * Profile email does not match the account * Account requires verification * Account or login proxy is blocked **Fix** * Verify the credentials. * Confirm the profile and account emails match. * Complete requested verification. * Test another proxy. * Run a test task on an in-stock item. *** ### Waiting for OTP **What to Check** * Confirm the selected OTP Input method. * If using IMAP, confirm the IMAP session shows Ready. * Confirm the Walmart email reached the connected inbox. * If using Bot input, watch Stellar for the manual code prompt. * Check forwarding rules if several account emails use one master inbox. *** ### Non-SMS Account Waiting for Verification Walmart requires phone verification before the account can continue checkout. **If Using Manual Verification** * Check for the verification webhook. * Locate the opened phone-verification harvester. * Enter a valid 10-digit US phone number without spaces, dashes or symbols. * Enter the verification code when prompted. * If the number cannot receive the code, click the keyboard icon to restart with another number. **If Using Wealth SMS** * Confirm your Wealth SMS API key is saved in Stellar’s Settings. * Confirm **Wealth SMS** is selected under **Checkout SMS Verification**. * Confirm the Wealth SMS service has available numbers. * Use the checkout link from the webhook if you need to complete the order manually. **If No Method Was Selected** Stellar defaults to Manual verification. Watch for the webhook and phone-verification harvester. **Alternative** Use the checkout link in the webhook to sign into the Walmart account and attempt to complete the order manually. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.stellaraio.com/stellar/retailers/walmart-go-us.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.