FLX US & CA

Complete guide on our FLX module

Use the FLX module in Stellar 4.0 for supported US and Canadian FLX raffle workflows. Entry submits a raffle entry, Check Points checks your account’s FLX reward points, Account-Gen creates an account, and Cancel Entry cancels an existing entry. For regular Footsites checkout, use the separate Footsites module.

Quick Start: Recommended Setup

1. Save your FLX account in the Accounts tab and confirm you can sign in to it. Complete any verification requested by the retailer.
2. Prepare a profile with accurate contact, shipping and payment details, plus reliable proxies. Match the account, profile and release region.
3. Create an FLX task group, click Create Task and choose entry. Select the Profile, Checkout Proxy, Site and saved Account.
4. Enter the release SKU and select an eligible size. Start with one task per account and the default 3000 ms delay.
5. Choose whether to add the profile’s address/payment, use Headstarts, or enter for Store Pickup. Only enable options you intend to use.
6. If using Manual Payment SMS Input, install Google Chrome and be ready to enter the code in the harvester window that opens.
7. Run Entry only for a release you intend to enter. After results are available, developers recommend rerunning the same Entry tasks to check wins.

Check Points is optional: it checks FLX reward points. It does not solve security checkpoints and is not a mandatory preparation step before Entry.

Preliminary Checklist

Profiles and accounts

Prepare a profile containing accurate contact, address and payment details. Save your account credentials under Accounts → FLX and confirm the account works on the retailer’s site or app. Start with one task per account rather than running many simultaneous actions on the same login.

Proxies

Use reliable ISP or residential proxies. The existing Stella Proxies resource is available if you need a provider. Test a small setup first; a flagged proxy, account issue or site change can affect results.

Release information

Your cook group can help with the correct SKU, site, region, sizes and entry window. Confirm eligibility and release rules before submitting an entry. An Entry task is a real submission, not a harmless test.

Accounts & Sessions

Accounts stores the login credentials that FLX tasks use. A session is the saved login state created when Stellar logs in. Select the intended saved account in Entry, Check Points and Cancel Entry; do not treat those modes as guest checkout.

Keep the account verified and its details accurate. Developers identified account-verification checks as a cause of repeated Refreshing Session / Submitting Entry loops. If login fails, check the account manually before repeatedly restarting tasks.

Manual SMS Code Entry

Payment SMS Input controls how a requested phone-verification code is supplied. With Manual selected, a captcha harvester window opens when Stellar needs the code. Enter the code in the small text box inside that window. Google Chrome must be installed on your computer.

This window is being used for code entry. The FLX task form does not have a Captcha Provider field, so this is not a separate captcha-solving setup.

Supported Modes

• entry — submits a raffle entry for the chosen Site, SKU and size.
• cancel-entry — cancels an existing entry for the chosen account and product.
• check-points — checks the account’s FLX reward points.
• account-gen — creates an FLX account using the selected profile; its country determines the US or Canadian region.

Entry Mode Breakdown

Select entry in the Mode dropdown. The screenshot shows Store Pickup enabled to reveal its extra fields; enable it only when you want pickup.

Name, Profile and Checkout Proxy

Name is an optional label, such as FLX Entry - Release - Account. Profile supplies the relevant contact, address and payment details. Checkout Proxy selects the proxy group used for the task’s requests.

Site

Choose Champs Sports CA, Champs Sports US, Footlocker CA, Footlocker US or Kids Footlocker. Match the release and your account’s intended site and region.

SKU and Size

SKU is the release’s product code. Get it from the release information or your cook group. Size offers Random and numbered sizes from 03.0 through 16.0 in half-size steps. The current control supports selecting sizes; start with one eligible size. Select Random only if you are willing to accept the size it may choose. The example screenshot’s size is illustrative.

Account

Select the FLX account you saved under Accounts. The old guide called this Session; the current field is Account.

Delay

Delay is the pause between task actions or retries, in milliseconds. The default is 3000 ms. The previous recommendation of 3000–5000 ms is a starting range to test based on proxy performance. Faster requests do not guarantee a successful entry.

Headstarts

Headstarts use the account’s available FLX rewards for the entry. Enter the number you intend to use, such as 1, 3 or 5, when the release allows it. Developers explain that Stellar reports when the account does not have enough available. You can use Check Points beforehand to check the account’s rewards.

Add Address? and Add Payment?

Add Address applies address details from the selected profile to the account. Add Payment applies payment details from the profile. Enable only the changes you want and verify the profile first; leave them off when you intend to keep the existing account details.

Payment SMS Input

The current dropdown offers Manual, Text Verified (US), Hero SMS (US), SMS Pool (US) and SMS Man (US). Manual uses the code-entry window described above. For a third-party service, configure its credentials and available balance in Settings before selecting it. The providers labeled US are US options.

The existing Text Verified (US only) provider link is available if you use that service.

Store Pickup?

Enable Store Pickup only for a pickup entry. Stellar uses the postal code from your profile unless you enter an override in Postal Code (Store Pickup). Radius (Store Pickup) is optional; developers state it defaults to 50 when left empty. Confirm the chosen location is suitable for you. Leave Store Pickup off for the non-pickup entry flow.

Start Time, End Time and Qty

Start Time and End Time optionally schedule the task. Leave them blank for manual control. Bottom Qty is the number of tasks to create, not the number of entries the retailer permits or pairs you can win. Start with one per account, review all fields, and click Create.

Check Points Mode Breakdown

Select check-points to check the saved account’s FLX reward points. This mode does not pass security checkpoints or submit a raffle entry.

• Name: optional task label.
• Profile: select the appropriate profile; the current form requires it.
• Checkout Proxy: proxy group used for the request.
• Site: choose the account’s retailer and region.
• Account: select the saved FLX account to check.
• Delay: Start with the default 3000 ms. If proxy errors or rate limiting occur, try a slower interval within 3000–6000 ms and review current release guidance.
• Start Time and End Time: optional scheduling.
• Bottom Qty: number of tasks to create. Start with one per account.

Account-Gen Mode Breakdown

Select account-gen to create an account. The profile’s country determines the US or Canadian region; there is no separate Site or Region selector in this form.

• Name: optional label for the task.
• Profile: select accurate contact details and the intended US or Canadian country.
• Checkout Proxy: choose reliable proxies for account creation.
• Postal Code: optional override; if empty, Stellar uses the selected profile’s postal code. Make sure it matches the intended region.
• Password: enter the password you want to use, or leave it blank for Stellar to generate one.
• Delay: default 3000 ms. The earlier guide recommends around 5000 ms or more for a more moderate account-creation pace.
• Start Time and End Time: optional scheduling.
• Catch All?: enable only if you have a working catchall email setup you control.
• Bottom Qty: number of tasks to create. Start with one and verify the resulting account before creating more.

If you use a catchall, confirm that you can receive messages for the generated addresses before enabling Catch All.

Cancel Entry Mode Breakdown

Select cancel-entry only when you intend to cancel an existing raffle entry. This is not a status-check mode.

• Name: optional label to make cancellation tasks easy to identify.
• Profile and Checkout Proxy: select the appropriate profile and proxy group.
• Site: select the retailer and region of the original entry.
• SKU: use the exact product code for the entry you want to cancel.
• Account: select the account that submitted the entry.
• Delay: default 3000 ms.
• Start Time and End Time: optional schedule; avoid accidentally scheduling a cancellation.
• Bottom Qty: number of cancellation tasks to create. Review the account and SKU before starting.

FAQ

Must I run Check Points before Entry?

No. Check Points checks FLX reward points and can help when deciding whether to use Headstarts. It is not a security-checkpoint requirement.

How do I check whether I won?

After the raffle results are available, developers recommend running the same Entry tasks again to check wins. Also review the retailer’s notifications and account status.

Can I use a Canadian profile in Account-Gen?

Yes. Account-Gen uses the selected profile’s country for the region. Keep the country and postal code consistent. For Entry, Check Points and Cancel Entry, choose the correct Site as well.

Common Errors & Troubleshooting

Entry Not Possible

First confirm that the release’s entry window is still open for that Site and region. Developers have advised restarting the task when the release is definitely live because this can be a random rate limit. Do not treat this as proof that the raffle is open if the release information says otherwise.

Looping Refreshing Session / Submitting Entry

Update Stellar and check the account manually, including any verification request. Developers identified verification checks in this flow and previously recommended clearing the account’s cookies when troubleshooting a stuck session. Clear Cookies removes the saved login session; the next task must log in again. If the loop continues, send support the exact status and logs.

Login failed or invalid session

Verify the saved credentials, selected Site and account status. If the retailer requires an account recovery or verification step, complete it manually. Check proxy connectivity before retrying.

No SMS code window or missing code

For Manual, confirm Google Chrome is installed and look for the harvester window with the small code-entry box. Use the code sent for the current verification attempt. For a third-party service, confirm the selected US service is configured and can receive the required verification message.

Not enough Headstarts or reward points

Check the account’s points and use only an available number of Headstarts. Do not assume creating more tasks adds points or increases the account’s available Headstarts.

Product not found, invalid SKU or unavailable size

Confirm the SKU, Site, country and release window. Check that the size is offered for this release. Your cook group can help verify the release information.

Rate limited, proxy blocked or repeated entry errors

Reduce simultaneous tasks using the same account or proxy, try a more moderate delay, and check current developer announcements. Start with a small test setup. If failures persist, send support the Site, mode, SKU, exact status, time and logs; avoid repeatedly recreating groups without knowing the cause.

---