Footsites

Complete guide on our Footsites module

Use the Footsites module in Stellar 4.0 for regular checkout on Footlocker, Footlocker CA, Champs Sports, Champs Sports CA and Kids Footlocker. For FLX raffle entries, use the separate FLX module. Footsites can use a saved account or guest checkout.

Quick Start: Recommended Setup

1. Prepare a checkout profile with accurate billing, shipping and payment details. The existing recommendation is a card that does not require 3D Secure.
2. Create a Footsites task group, click Create Task and choose normal. Select your Profile and Checkout Proxy group.
3. Choose the correct Site, enter the product SKU, select a size and keep Product Quantity at 1 to start.
4. Choose Credit Card or Gift Cards, and configure the Queue Captcha Provider you select.
5. If you want account checkout, select the saved account explicitly. Leaving Account blank can still use an account when its saved email matches the profile email.
6. For a timed release, Normal can run directly with Watch Task off. For restocks, enable Watch Task and run a matching Monitor for the same Site and SKU.
7. Check your setup with a small number of tasks. A running Normal task can place a real order, so only test with a product you intend to buy.

Preliminary Checklist

Profile and payment

Prepare your profiles before creating tasks. Check the shipping country, billing address and payment details. Keep product quantity within the retailer’s limit.

Proxies

Use reliable ISP or residential proxies and test them beforehand. Proxy quality affects performance, but protection errors can also require a Stellar or server-side update. No proxy provider guarantees a checkout.

The existing Stella Proxies resource is available if you need a provider. Keeping alternative proxy groups can help you compare results.

Product information and a small test

Your cook group can help with SKUs, sizing and release timing. Confirm the site and region match the product. Begin with a small setup before scaling up.

Accounts & Sessions

Save the retailer account under Accounts before selecting it in a task. Stellar uses those saved credentials to log in and save a session. A session is the saved login state; it is not a second account.

If Account is empty, Stellar checks for a saved account whose email matches the selected profile’s email. If it finds one, it uses account checkout. If no matching saved account exists, it uses guest checkout. To avoid ambiguity, select the intended account explicitly when you want account checkout.

Captcha Harvesters & Queue Captcha Setup

Queue Captcha Provider is required in Normal mode. Choose the method you have prepared; selecting a provider alone does not configure it.

Bot: use a Captcha Harvester to solve prompted challenges manually. Google Chrome must be installed. Create and open the harvester before running tasks so you are ready when a challenge arrives.

Aycd: configure the AutoSolve feature from AYCD and keep the required AYCD setup running.

Capmonster: configure your Capmonster key in Settings and check the service has enough balance.

A Kasada or other protection error is not necessarily a queue captcha. Changing Queue Captcha Provider will not fix every protection problem.

Supported Modes

• normal — monitors and attempts checkout directly, or waits for a Monitor signal when Watch Task is enabled.
• monitor — checks product availability and signals matching checkout tasks. It does not place orders.

Normal Mode Breakdown

Select normal in the Mode dropdown. This is the standard checkout form in Stellar 4.0.

Name, Profile and Checkout Proxy

Use Name as an optional label. Select the checkout Profile and the proxy group for checkout requests. Review the profile’s email if you intend to use guest checkout, because it can match a saved account.

Site and SKU

Site offers Footlocker, Footlocker CA, Champs Sports, Champs Sports CA and Kids Footlocker. Eastbay is no longer in the current dropdown. Choose the site that matches the product and region.

Enter the product code, not the full URL. In https://www.footlocker.com/en/product/~/C8013057.html?f=1, the SKU is C8013057. This is an example of the format, not a release recommendation.

Product Quantity and Size

Product Quantity is the number of units to buy per order. Start with 1. Size offers Random and numbered sizes from 03.0 through 16.0 in half-size steps; use a size offered for the actual product. The current control supports selecting sizes. For a simple first setup, choose one specific size; use Random only if you are comfortable with the size it may choose.

Payment Method

Credit Card uses the payment details in your selected profile. Gift Cards reveals a Gift Cards selector for your saved tag group.

Gift Cards

1. Open Tags and create a group for your Footsites gift cards.
2. Add one card per line using NUMBER:PIN.
3. Return to the task, choose Gift Cards as Payment Method, then select that group in Gift Cards.

NUMBER:PIN
1234567890:9876

The numbers above are placeholders. Use your own valid cards and keep their numbers and PINs private.

Account

Select the saved account you want, or leave it blank for automatic email matching. A matching saved account is used; otherwise Stellar uses guest checkout. See Accounts & Sessions above before assuming that a blank field means guest.

Queue Captcha Provider

The current choices are Bot, Capmonster and Aycd. Select the method you configured in the captcha setup above.

Delay

Delay controls the pause between attempts in milliseconds. Start with the default 3000 ms. If requests are blocked or proxy errors repeat, try a slower 4000 ms interval and check your proxy pool. Lower delays increase request volume and do not guarantee faster checkout.

Watch Task?

Enable Watch Task to wait for a matching Monitor signal, which reduces repeated checkout requests while waiting. Run a Monitor for the same Site and SKU. Leave it off to let Normal attempt directly, such as for a timed release. Watch Task does not guarantee protection from bans.

Start Time, End Time and bottom Qty

Start Time and End Time are optional scheduling controls. Leave them empty for manual control. The bottom Qty creates that many tasks; Product Quantity controls units per order. Start with one task, review the settings, then click Create.

Monitor Mode Breakdown

Select monitor in the Mode dropdown. This form does not require a Profile or Account.

• Name: optional label.
• Monitor Proxy: proxy group used for stock checks.
• Site: match the retailer and region used by your Normal tasks.
• SKU: match the product code used by the checkout tasks.
• Size: optional size selection; use the relevant product sizing.
• Monitor Delay: Milliseconds between stock checks. Start with a slower 5000–9000 ms interval for ongoing monitoring; the app default is 3000 ms. Adjust based on proxy performance and current release guidance.
• Reset Delay: Start with the default 30000 ms. This controls the wait before monitoring resumes after a stock signal. Change it only for a tested setup or current release guidance.
• Start Time and End Time: optional schedule.
• Bottom Qty: number of Monitor tasks to create, not product quantity.

FAQ

Footsites or FLX?

Use Footsites for regular checkout. Use FLX for raffle entries, checking reward points, and the other FLX-specific account workflows.

Does a blank Account mean guest checkout?

Only when Stellar cannot find a saved account matching the profile email. If a matching saved account exists, it uses that account.

How many tasks can I run?

Start with a small task group and increase gradually only when the setup works reliably.

Common Errors & Troubleshooting

Kasada, Ksd Proxy Ban, Akamai or queue errors

Install available updates and check developer announcements first. Developers have identified Footsites protection changes that required server-side fixes, so these messages do not always mean your proxies alone are bad. Occasional Kasada errors and add-to-cart rate limits can occur during drops; developers have advised allowing tasks to continue rather than restarting at every temporary error. Persistent failures on the current version need a proper report with Site, mode, SKU, exact status, time and logs.

Task stays waiting

Check Watch Task and any Start Time. With Watch Task enabled, run the matching Monitor. Verify both tasks use the same Site and SKU and that the selected size applies to the product.

Invalid product or unavailable size

Check the SKU against the correct retailer’s product page or your cook group’s release information. A code for another site or region may not work. Check the product’s offered sizes before changing the size selection.

Login or checkout failure

Confirm which account or guest path the task is using. Check saved credentials manually if account login fails, and review the profile’s address, payment method, product limit and gift-card details. Do not repeatedly retry an uncertain checkout until you have checked for an existing order.

Checkout log looks delayed

Developers have noted that the Discord checkout log can lag. Use your own task result, order confirmation and retailer order history to verify the purchase instead of relying on the public log alone.

---