Map the workflow first
Pokemon Center restocks workflows usually include login prep, queue continuity, cart sessions, checkout backup, and release-window monitoring. Treat those as separate jobs instead of pushing every task through one generic proxy list.
- Use one labeled list for monitoring and another for checkout.
- Keep the highest-value checkout sessions sticky.
- Avoid burning your clean checkout list during broad pre-drop checks.
Split monitoring from checkout
The practical split is simple: rotating or lighter residential sessions for broad availability checks, sticky residential sessions for anything that needs continuity through account, cart, queue, or checkout steps.
- Monitoring list: broader, easier to rotate, and easier to replace.
- Checkout list: sticky, labeled, and saved for the real window.
- Backup list: reserved for alternate profiles or retailer-specific retries.
Size data with buffer
A realistic GB estimate should include setup checks, monitoring time, failed requests, and backup sessions. Buying only for one task run can leave you short when the release stretches.
- Use Drop Day for one focused release.
- Use Restock Pack for multiple alerts or backup sessions.
- Use Collector for repeat monitoring across the month.
Test without over-burning
Test format compatibility before the window, then keep the real checkout list clean. A small local test is enough to catch bad formatting without wasting meaningful data.
- Prepare host:port:user:pass lists before release time.
- Test lightly with the same target family you plan to run.
- Keep credentials, target URLs, and exported files under your control.