Lids
On this page
Quick Start — Recommended SetupPreliminary ChecklistAccounts & SessionsSupported ModesCheckout ModeMonitor ModeExample: Monitor + CheckoutFAQWhich delay should I use?Can I buy more than one?Do I need a Monitor task?Common Errors & TroubleshootingAkamai errors or blocked requestsCheckout keeps waitingProduct or size cannot be foundCheckout failsComplete guide on our Lids module
Quick Start — Recommended Setup
- In Tasks, create a Lids task group and click Create Task.
- Choose checkout, select your profile and checkout proxy group, and paste the full product link into Event URL.
- Choose a size the product actually offers. Use Random only if you are happy to buy any available size. Start with product Qty 1.
- For random restocks, create a Monitor task for the same Event URL and enable Watch Task on Checkout. For a timed release or standalone checkout, leave Watch Task off.
- Start with the default 3000 ms delay. Set the bottom Qty to the number of task rows you want, then click Create.
- Review your setup before starting. Checkout tasks can place orders using the selected profile.
Preliminary Checklist
Prepare your profiles with accurate billing, shipping and payment details.
Use high-quality ISP or residential proxies. Datacenter proxies are another option if tested successfully with Lids. Any proxy type can be blocked; flagged proxies can cause Akamai-related errors.
If you need a provider, see Stella Proxies. Keep alternatives available rather than relying on one provider or pool.
A cook group can help you find product links, release timing, size information and restock alerts.
Accounts & Sessions
Lids Checkout uses guest checkout with the selected profile. The current form has no Account field, so there is no saved-account or login-session setup to complete for this module.
Supported Modes
- checkout: attempts to purchase the chosen product. With Watch Task on, it waits for a matching Monitor task; with it off, it checks the product itself.
- monitor: checks availability and signals matching Checkout Watch Tasks. A Monitor task does not place an order.
Checkout Mode
Choose checkout to buy a product using your saved profile.
- Name: optional label to help you identify the task.
- Mode: select checkout.
- Profile: choose the saved billing, shipping and payment information to use.
- Checkout Proxy: choose the proxy group for checkout requests.
- Event URL: paste the full Lids product or event URL. This field expects a link, not just a product number.
- Size: select the size or sizes you are willing to buy. The dropdown includes Random, clothing sizes, numeric sizes and fitted-hat sizes such as 7 1/8. Match the product’s sizing; a menu option does not mean that size is available for every product.
- Qty in the main form: units to attempt per order. Start with 1 and follow any product purchase limit.
- Delay: wait before retrying after an error, in milliseconds. The current default is 3000 ms, or 3 seconds.
- Discount: optional discount code. Leave empty if you do not have one.
- Cheapest Shipping?: enable to choose the cheapest available shipping option.
- Use Rakuten?: optional cashback integration. Configure Rakuten in Settings first; leave off if you are not using it. Cashback eligibility is not guaranteed.
- Watch Task?: enable to wait for a matching Monitor signal. Leave off for a standalone Checkout task.
- Start Time and End Time: optional scheduling controls.
- Qty at the bottom: number of task rows to create. This is separate from units per order.
Monitor Mode
Choose monitor to watch the product and notify matching Checkout Watch Tasks when stock is detected.
- Name: optional task label.
- Mode: select monitor.
- Monitor Proxy: choose the proxy group used for stock checks.
- Event URL: paste the same full product link used by the Checkout tasks you want to trigger.
- Monitoring Delay: interval between stock checks, in milliseconds. The current default is 3000 ms.
- Reset Delay: optional wait before the monitor restarts after detecting stock. The field starts blank.
- Start Time and End Time: optional scheduling controls.
- Qty at the bottom: how many Monitor task rows to create. Start with a small setup.
Example: Monitor + Checkout
- Create a Monitor task for your product’s full Event URL.
- Create a Checkout task with that same Event URL, your profile, desired size and product Qty 1. Enable Watch Task.
- Start both tasks. Monitor checks stock; Checkout waits for its signal before trying to buy.
Watch Task can reduce repeated stock checks by Checkout tasks, but it does not guarantee that proxies will avoid blocks. For a timed release, you can run Checkout independently with Watch Task off.
FAQ
Which delay should I use?
Start with the default 3000 ms in a new task. For a slower setup with fewer requests, try 4000–6000 ms for Checkout and 4500 ms for Monitor. Adjust to current release guidance and proxy performance; lower delays do not guarantee success.
Can I buy more than one?
Use the product’s purchase limit as the maximum. Starting with Qty 1 is recommended, especially for limited releases. Remember that creating several task rows may result in several orders.
Do I need a Monitor task?
Only if you want Checkout to wait for a Monitor signal. With Watch Task off, Checkout checks the product itself and attempts checkout. A Monitor alone will never buy the product.
Common Errors & Troubleshooting
Akamai errors or blocked requests
Check that your proxies are active and correctly entered. Try another suitable proxy pool or provider and a slower delay. A fast proxy test does not prove that Lids will accept the proxy.
Checkout keeps waiting
If Watch Task is on, make sure a matching Monitor task is running with the same Event URL. If you intended a standalone Checkout task, turn Watch Task off.
Product or size cannot be found
Check the full product link, current availability and size selection. Use the size format offered by that product. Only choose Random if you are willing to receive any available size.
Checkout fails
Check the profile, product quantity, shipping details and any discount code. If the problem continues, contact support with the exact task status and mode. Do not send passwords or full payment details.