FLX US & CA

Complete guide on our FLX module

Our FLX module is built for Foot Locker FLX (US + Canada) and focuses on account-based entry workflows, including passing checkpoint steps and submitting entries for specific products/sizes. Because FLX flow is typically first-come, first-processed and can involve checkpoint validation, Stellar splits the process into dedicated task modes (Entry, Check-Points, and Account-Gen) to keep your setup clean, fast, and repeatable. This module is best suited for users running multiple accounts to maximize entry success for hyped footwear releases.


(For members who want a fast setup without reading everything)

  • Add FLX accounts under Identities → Sessions (or Accounts) → FLX

  • Use high-quality ISP or Residential proxies (avoid flagged pools)

  • Run Check-Points tasks first (to get accounts checkpoint-ready)

  • Run Entry tasks for the same SKU + size using those sessions

  • Keep delays moderate (start around 3000–5000ms) and adjust based on proxy quality

  • Before a real release, run a test Entry (or a safe test flow if available) to confirm sessions + proxies work


Preliminary Checklist

Profiles

Create and save your checkout profiles under the Profiles tab in Stellar. These contain your:

  • Billing information

  • Shipping information

  • Payment information (if applicable)

Tip: Even if FLX entry isn’t a traditional “checkout,” profiles are still used for identity/address fields when required.


Proxies

High-quality proxies are strongly recommended for FLX.

Recommended types

  • ISP Proxies: best balance of speed + trust (recommended default)

  • Residential Proxies: great for trust/rotation if you hit blocks more often

Avoid

  • Low-quality datacenter proxies (more likely to trigger checkpoint-related issues)

If you need proxies, Stella Proxies offers both ISP and Residential options.


Sessions (Accounts)

FLX is account-based. You’ll need FLX accounts added in Stellar before running Entry or Check-Points tasks.

Recommended

  • 1 task per account (don’t reuse a single account across too many tasks at once)

  • Keep account email/password correct and consistent


Your cook group helps with:

  • SKU / product codes

  • Sizing guidance (which sizes are realistic)

  • Drop timing + region notes (US vs CA differences)


Test Task

Before a major release:

  • Run a small set of tasks (2–5 accounts)

  • Confirm proxies aren’t blocked

  • Confirm sessions load correctly

  • Confirm your mode flow works (Check-Points → Entry)


Task Modes Overview

FLX includes these task modes:

1) Entry

Used to submit an entry for a specific product using:

  • SKU

  • Size

  • Session (account)

  • Profile

  • Proxies

2) Check-Points

Used to prepare accounts for entry by completing checkpoint-related steps. Recommended to run before Entry tasks, especially close to release windows.

3) Account-Gen

Used to create new FLX accounts (US/CA) directly inside Stellar. Includes support for:

  • Postal code

  • Password

  • Catchall (optional)


Creating Tasks (Step-by-Step)

Entry Mode (New Task → Mode: entry)

Use this mode to submit an entry for a specific release.

Required fields (from the task window)

  1. Name: Give it a clear name (example: FLX Entry - SKU - Size - Group1)

  2. Mode: entry

  3. Profile: Select your profile

  4. Checkout Proxy: Select your proxy group (ISP or Resi recommended)

  5. SKU: Enter the product SKU/code

  6. Size: Choose your size (or the required selection)

  7. Session: Select the FLX account session you want to use

  8. Delay: Start around 3000–5000 and adjust as needed

  9. Qty: Keep at 1 unless the module explicitly supports other values

Optional toggles

  • Add Address?: Adds address info from your profile to your account

  • Add Payment?: Adds payment info from your profile to your account

  • Start Time: Schedule tasks to start automatically

Recommended workflow

  • Run Check-Points first

  • Then run Entry tasks (one per account)


Check-Points Mode (New Task → Mode: check-points)

Use this mode to pass checkpoint steps and reduce friction when running Entry.

Fields

  1. Name: Example FLX Checkpoints - Group1

  2. Mode: check-points

  3. Profile: Select profile (recommended)

  4. Checkout Proxy: Select proxy group

  5. Session: Select FLX session

  6. Delay: Start around 3000–6000

  7. Start Time: Optional scheduling

  8. Qty: Keep at 1

Best practice

  • Run Check-Points tasks ahead of time (or before you start Entry tasks)

  • If you have many accounts, stagger start times or delays to reduce proxy pressure


Account-Gen Mode (New Task → Mode: account-gen)

Use this mode to generate new accounts directly in Stellar.

Fields

  1. Name: Example FLX AccountGen - Batch1

  2. Mode: account-gen

  3. Profile: Select a profile (recommended—especially if email is pulled from profile)

  4. Checkout Proxy: Use high-quality proxies (Resi often best here)

  5. Postal Code: Enter a valid US/CA postal/zip code for the account region

  6. Password: Enter a password (or follow your team’s standard format)

  7. Delay: Start around 5000 for stability

  8. Catch All?: Enable only if you’re using a catchall email setup

  9. Start Time: Optional scheduling

  10. Qty: Keep at 1

Important

  • FLX module supports US + Canada only — ensure your postal code matches the region you intend to use.


Fields & Options

Name

A label for your task. Use a consistent naming pattern:

  • FLX Entry - SKU - Size - AccountBatch

  • FLX Checkpoints - Batch1

  • FLX AccountGen - Batch2

Mode

Select what the task does:

  • entry = submit entry

  • check-points = checkpoint preparation

  • account-gen = generate accounts

Profile (Required)

The identity info used in the task flow (address/payment when needed).

Checkout Proxy

The proxy group used for the task’s requests.

Recommended

  • ISP for general stability

  • Resi if you see frequent blocks or checkpoint issues

SKU (Entry only)

Product identifier. Usually provided by cook groups or found in product metadata.

Size (Entry only)

Select the size(s) you want to enter for.

Session

Your FLX account selection. Typically:

  • 1 session = 1 account

  • Recommended: 1 Entry task per account

Delay

How often the task retries actions (milliseconds).

Starting recommendations

  • Check-Points: 3000–6000

  • Entry: 3000–5000

  • Account-Gen: 5000+ for stability

Add Address?

When enabled, Stellar will apply address details from your profile to your account.

Add Payment?

When enabled, Stellar will apply payment details from your profile to your account.

Start Time

Schedules tasks to begin automatically at a set time.

Qty

Default 1. Most entry flows don’t need higher quantities.

Postal Code (Account-Gen only)

Enter new zip code or the bot will use zip code from your selected profile.

Password (Account-Gen only)

Enter your prefered password or the bot will automatically create one.

Catch All? (Account-Gen only)

Use only if you have a proper catchall email setup.


Standard Release Setup (Most Common)

  • 1x Check-Points task per account

  • 1x Entry task per account (per SKU + size)

  • ISP proxies preferred; use Resi if you encounter issues

“Safety” Setup (If You See More Blocks)

  • Run Check-Points earlier (more time buffer)

  • Use Residential proxies for Check-Points + Entry

  • Increase delays slightly (ex: 5000–7000)


Common Status Messages & Fixes

Status / Error Message
Likely Cause
Fix / Recommendation

Waiting for Start Time

Task is scheduled

Confirm start time or remove it

Logging In / Authenticating Session

Normal login step

Ensure session credentials are correct; try a different proxy

Session Invalid / Login Failed

Wrong password, locked account, or blocked IP

Verify creds, reset account manually if needed, switch to cleaner proxies

Checkpoint Required

Account needs checkpoint flow

Run Check-Points mode first, then retry Entry

Failed to Pass Checkpoint

Proxy flagged or checkpoint challenge failed

Swap proxy pool (Resi recommended), raise delay slightly

Proxy Banned / Blocked

Proxy flagged/low quality

Use higher quality ISP/Resi; avoid reusing burned proxies

Product Not Found / Invalid SKU

Wrong SKU or region mismatch

Confirm SKU, confirm US/CA region, verify source with cook group

Size Unavailable

Size not selectable or out of entry range

Try a different size or confirm size formatting

Entry Failed / Submit Error

Site response error, proxy issue, or session issue

Restart task, change proxy, confirm session is healthy

Rate Limited / Too Many Requests

Too many tasks on same proxy pool

Reduce task count per proxy, increase delay, use larger proxy pool

Unknown Error

Temporary site change or backend issue

Recreate task group, restart bot, retry with different proxies

Last updated

Was this helpful?