Lowes

Complete guide on our Lowes module

Lowes supports Guest and Account checkout, plus Monitor tasks for stock checks. It uses a first-come, first-served checkout flow. Restocks can sell out quickly; a correct setup helps you participate but cannot guarantee an order.

Quick Start — Recommended Setup

1. Create a Lowes task group in Tasks and click Create Task.
2. Choose guest for guest checkout or account to use a saved Lowes account. Select your profile and checkout proxy group.
3. Choose shipping or pickup and enter the Product SKU. For Pickup, use a profile with the correct ZIP code and enter the distance you are willing to travel in Radius.
4. For Account mode, select your saved account or use a profile email that matches a saved account. Configure OTP Input for verification codes.
5. Start with product Qty 1 and the default Delay of 3000 ms. For random restocks, pair the checkout task with a matching Monitor task and enable Watch Task. For timed releases, use checkout tasks with Watch Task off.
6. Set the bottom Qty to the number of task rows, click Create, then review before starting. Guest and Account tasks can place real orders.

Preliminary Checklist

Prepare your profiles with accurate payment, billing and shipping details, including ZIP code.

Use high-quality ISP or residential proxies. Flagged or low-quality proxies can cause Akamai-related errors. Keep more than one suitable proxy pool available.

For proxy options, see Stella Proxies.

The existing Stella Proxies resource is also available.

A cook group can help with SKUs, release timing, availability and product limits.

Check your setup before a major release. If you run a test on an in-stock product, remember that a checkout task can buy it. Use only a small setup and a product you intend to purchase; Monitor mode is for stock checks only.

Accounts & Sessions

Guest mode does not require a saved Lowes account. For Account mode, add your Lowes email and password under Accounts, then select that account in the task. The Account hint confirms that leaving the field empty matches a saved account by the profile email; explicitly selecting the account is clearer for beginners.

Adding credentials saves them but does not log in immediately. The task uses them to log in and save its session when it runs. Keep access to the mailbox that receives verification codes.

Verification Codes — OTP Input

OTP means one-time password: a temporary verification code. Guest and Account forms both show OTP Input. Configure the method you want Stellar to use if a code is requested.

IMAP: connect the receiving mailbox in the IMAP tab. The old Sessions → IMAP wording has been replaced by the IMAP tab and OTP Input selector.

• Manual: enter the code in the prompt when it appears. Google Chrome and the manual-entry harvester setup must be ready.
• AYCD: use your configured AYCD Inbox connection to retrieve the code.

Supported Modes

• guest: attempts checkout without a saved account.
• account: logs in using a saved Lowes account and attempts checkout.
• monitor: checks stock and signals matching Watch Tasks. It does not buy the product.

Guest Mode

Choose guest for guest checkout. This example shows Pickup so you can see the Radius field.

• Name: optional task label.
• Mode: choose guest.
• Profile: the saved checkout details to use. Its ZIP code is also used with Radius for Pickup.
• Checkout Proxy: the proxy group for checkout requests.
• Fulfillment Type: shipping delivers the order; pickup searches for store pickup.
• Product SKU: the product number at the end of the Lowes product URL.
• Radius: for Pickup, the distance in miles you are willing to travel from the profile ZIP code. This field is hidden when Shipping is selected.
• OTP Input: IMAP, Manual or AYCD for verification codes when requested.
• Delay: wait before retrying after an error, in milliseconds. The current default is 3000 ms, or 3 seconds.
• Qty in the main form: units to attempt per order. Start with 1 and follow the product limit.
• Start Time and End Time: optional scheduling controls.
• Watch Task?: waits for a matching Monitor signal when on. With it off, Guest checks the product itself and attempts checkout.
• Qty at the bottom: number of task rows to create, separate from units per order.

Account Mode

Choose account for checkout through a saved Lowes account. This example shows Shipping.

• Name: optional label.
• Mode: choose account.
• Profile: the billing, shipping and payment details to use; its ZIP code is used for Pickup.
• Checkout Proxy: select your checkout proxy group.
• Fulfillment Type: shipping or pickup.
• Product SKU: the product number from the product link.
• Account: select a saved Lowes account. If empty, Stellar matches a saved account to the profile email.
• OTP Input: choose IMAP, Manual or AYCD for verification codes.
• Radius: shown for Pickup; distance in miles you are willing to travel from the profile ZIP code.
• Delay: retry delay in milliseconds; default 3000 ms.
• Qty in the main form: units per order.
• Start Time and End Time: optional scheduling controls.
• Watch Task?: waits for a matching Monitor signal when enabled. Leave off to run Account independently.
• Qty at the bottom: number of task rows to create.

Monitor Mode

Choose monitor to check stock for the product and fulfillment type your checkout tasks use.

• Name: optional task label.
• Mode: choose monitor.
• Profile: required in the current Monitor form. Its ZIP code supplies the location unless ZIP Code overrides it.
• Monitor Proxy: the proxy group used for stock checks.
• Fulfillment Type: shipping or pickup. Match your checkout tasks.
• Product SKU: the same product number used by your checkout tasks.
• ZIP Code: optional location override. If entered, it replaces the selected profile’s ZIP code for this task.
• Radius: distance in miles for Pickup monitoring. Match the area you are willing to collect from.
• Monitor Delay: interval between stock checks. The default is 3000 ms, or 3 seconds.
• Reset Delay: wait before monitoring restarts after detecting stock. The default is 30000 ms, or 30 seconds.
• Start Time and End Time: optional scheduling controls.
• Qty at the bottom: number of Monitor rows to create.

Example: Monitor + Pickup Checkout

1. Create a Guest or Account task with Fulfillment Type set to pickup, your product SKU, the correct profile ZIP and a realistic Radius. Enable Watch Task.
2. Create a Monitor task for that SKU and pickup. Use a profile with the same ZIP and the same Radius; if you use its ZIP Code override, make sure it matches your intended pickup area.
3. Start both. Monitor checks availability and signals the waiting checkout task when stock is detected.

For Shipping, choose shipping on both tasks. With Watch Task off, Guest or Account can run without a separate Monitor. Watch Task reduces repeated checkout-side monitoring, but does not guarantee that proxies will avoid blocks.

FAQ

Where do I find the SKU?

For example, https://www.lowes.com/pd/Tide-Refreshing-Breeze-HE-Laundry-Detergent-46-fl-oz/5015041951 has Product SKU 5015041951. Enter that number rather than the entire link.

What quantity should I use?

Start with 1, then follow the retailer’s limit or your cookgroup release guidance. Several task rows can produce several orders.

What delay should I use?

The current default is 3000 ms. The old guide suggested around 2000 ms; treat that as a faster option to test carefully, not a requirement. More frequent requests can increase proxy blocks. Adjust to proxy quality, the release and current staff guidance.

Why is there no ZIP field in my checkout task?

Guest and Account use the selected profile’s ZIP with Radius for Pickup. Monitor has a separate ZIP Code field that overrides its profile ZIP. Check both sides of a Monitor + Watch Task setup so they target the same area.

Common Errors & Troubleshooting

Akamai errors or blocked requests

Check proxy credentials and expiry, try another suitable pool or provider, and reduce request frequency if needed. Site protection can change; check current announcements when several otherwise-correct setups fail. An old incident is not proof that a proxy region remains blocked today.

Waiting for stock or a Monitor signal

Check the SKU, fulfillment type and pickup area. If Watch Task is on, a matching Monitor must be running. A Monitor task alone does not attempt checkout.

No pickup stock found

Verify the profile ZIP, any Monitor ZIP override, Radius and pickup availability on the retailer’s website. Shipping availability does not necessarily mean a nearby store has pickup stock.

Login fails or a code never arrives

Confirm the saved account, profile-email match and selected OTP Input method. Check the receiving mailbox, IMAP or AYCD connection, or the Manual entry window. If errors persist, share the exact task status and mode with support without exposing passwords or payment details.

---