> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/retailers/bandai.md). # Bandai
StellarAIO’s Bandai US module supports account-based checkout and product monitoring. Bandai uses Shape protection, so checkout tasks must be supported by ShapeV2 cookie-generation tasks. *** ### Video Guide Watch the complete Bandai setup `Video guide coming soon...` *** ### Preliminary Checklist Before creating Bandai tasks, confirm the following: * [ ] StellarAIO is updated to the latest version. * [ ] You have one Bandai account for each Normal task. * [ ] Bandai sessions have been added under **Identities → Sessions → Bandai**. * [ ] Profiles contain valid billing, shipping, payment, and email information. * [ ] Each task is associated with the correct Bandai account. * [ ] High-quality ISP and residential proxies are available. * [ ] You have the correct Bandai SKU for each product. * [ ] Monitor tasks have been created for the desired SKUs. * [ ] ShapeV2 cookie generators have been created for Bandai. * [ ] ShapeV2 tasks use a mix of supported browsers. * [ ] You have tested your setup before an important release. * [ ] Your cook group and Stellar announcements are enabled. *** ## Quick Start For the recommended Bandai setup: 1. Add your Bandai accounts under **Identities → Sessions → Bandai**. 2. Create one valid profile for each account. 3. Create one Normal task per account. 4. Enter the correct SKU. 5. Set the product quantity to `1`. 6. Start with a delay of `3333`. 7. Enable **Watch Task**. 8. Create a Monitor task for the same SKU. 9. Set the Monitor delay to `3333`. 10. Use high-quality ISP proxies as your starting setup. 11. Create ShapeV2 tasks using **Gen-Experimental**. 12. Select **Bandai** as the ShapeV2 site. 13. Set Cookie Expiration to `300000`. 14. Set Cookies Per Task to `5`. 15. Use a mix of browsers across your ShapeV2 tasks. 16. Start ShapeV2, Monitor, and Normal tasks before the release. *** ## Accounts and Sessions ### Bandai Accounts Are Required Bandai is an account-based module. Every Normal task must use its own Bandai account because Bandai shares the cart across all activity on that account. Do not use one Bandai account for: * Several Normal tasks * Several different SKUs at the same time * Duplicate tasks for the same product * Multiple simultaneous checkout attempts The recommended rule is: ``` 1 Bandai account = 1 Normal task ``` If you want to run additional Normal tasks, add additional Bandai accounts and create corresponding profiles. *** ### Adding a Bandai Session 1. Open the **Identities** tab. 2. Select **Bandai**. 3. Create or select a session group. 4. Click **Add Session**.
5. Complete the account information. 6. Click **Save**. 7. Confirm the correct account is used by its Normal task. ### Session Fields #### Session Name Enter an organizational name for the session. Using the account email or another recognizable label will make it easier to match accounts to tasks. #### Account Email Enter the email associated with the Bandai account. Make sure the address is entered correctly. #### Account Password Enter the current Bandai account password. If you change the password on Bandai’s website, update the saved session before running the account again. *** ## Supported Modes The Bandai module currently contains two primary modes: ### **Normal Mode**
### **Monitor Mode**
The module also requires the separate [**ShapeV2**](/stellar/retailers/shapev2.md) module to generate the cookies used by Bandai tasks. *** ## Normal Mode Normal Mode handles the account-based cart and checkout process. Create only one Normal task for each Bandai account. ### Normal Mode Fields #### Name Optional. Enter a recognizable task name to organize your setup. A useful name may include the product, account number, or release. #### Mode Select: ``` Normal ``` #### Profile Select the profile containing the billing, shipping, payment, and email information that should be used at checkout. Keep profiles organized so each Normal task can be matched to the correct Bandai account. #### Checkout Proxy Select the proxy group that the task should use during the cart and checkout process. ISP proxies performed well during initial testing. However, performance can change during larger releases. A balanced setup may include: * ISP proxies for most tasks * Residential proxies for additional diversity * More than one proxy provider * More than one proxy pool Always test your own providers before an important release. #### SKU Enter the Bandai product SKU. The SKU identifies the exact product the task should attempt to purchase. Obtain current product information from your cook group or another trusted source. Double-check the SKU before starting. #### Session Select the Bandai account associated with the task when manually assigning a session. The field may be left unselected in certain automatically matched setups, but the task must still use a unique Bandai account. Keep the profile and session information organized so the same account is never assigned to multiple Normal tasks. #### Qty Enter the number of units the task should attempt to purchase. The recommended starting value is: ``` 1 ``` Do not exceed the product’s purchase limit. #### Delay Controls the time between task requests. The recommended starting value is: ``` 3333 ``` This value is entered in milliseconds. Adjust the delay only when updated instructions or your testing indicate that a change is needed. #### Watch Task Recommended: **Enabled** When Watch Task is enabled, the Normal task waits for a Monitor task with the same SKU to detect inventory. The flow is: 1. The Normal task waits. 2. The Monitor task checks the product. 3. The Monitor detects stock. 4. The Monitor alerts the matching Normal task. 5. The Normal task begins the cart and checkout process. This reduces unnecessary requests from every checkout task. #### Start Time and End Time Optional scheduling controls. You must still manually start the task. Setting a Start Time does not start a stopped task automatically. #### Task Quantity The **Qty** field at the bottom of the creation window controls how many copies of the configured task are created. This is different from the product **Qty** field inside Normal Mode. Because Bandai requires one task per account, creating Normal tasks individually is recommended. This helps prevent accidental account reuse. *** ## Monitor Mode Monitor Mode checks the selected SKU for availability and alerts matching Normal tasks when inventory is detected. Monitor tasks do not require Bandai accounts. ### Monitor Mode Fields #### Name Optional. Enter a recognizable name for the monitor. #### Mode Select: ``` Monitor ``` #### Monitor Proxy Select the proxy group used to monitor Bandai. ISP proxies are the recommended starting point based on initial testing. If you encounter blocks or inconsistent monitoring: * Test another ISP pool * Test another proxy provider * Increase the delay if instructed * Mix in residential proxies when appropriate #### SKU Enter the same SKU used by the corresponding Normal tasks. Watch Task will only work correctly when the monitor and checkout task use matching product information. #### Delay The recommended starting value is: ``` 3333 ``` Lower delays make requests more frequently but may increase the chance of proxy or site-related blocks. Higher delays reduce request frequency but may detect stock more slowly. #### Start Time and End Time Optional scheduling controls. The task must still be manually started. #### Task Quantity Controls how many copies of the Monitor task Stellar creates. Begin with one Monitor task per SKU unless current drop instructions recommend additional monitors. *** ## ShapeV2 Setup Bandai uses Shape protection. Normal tasks require a supply of valid Bandai cookies generated through ShapeV2. ShapeV2 tasks should be started before the expected release and kept running while the Bandai Normal tasks are active. ### Recommended ShapeV2 Settings #### Mode Select: ``` Gen-Experimental ``` #### Checkout Proxy Select a high-quality proxy group. ISP proxies performed well during initial testing. You may also test residential proxies for additional diversity during larger drops. #### Site Select: ``` Bandai ``` Make sure Bandai is selected. Cookies generated for another site cannot be used by Bandai tasks. #### Cookie Expiration Enter: ``` 300000 ``` This equals five minutes. The generator must continue producing new cookies because older cookies will expire. #### Cookies Per Task Enter: ``` 5 ``` This controls the number of cookies maintained by each ShapeV2 task. #### Browser Select a supported browser. Do not configure every ShapeV2 task with the same browser. Use a mix of available browsers across the setup. For example, if your available options include different Chrome-based or supported browser profiles, distribute the ShapeV2 tasks between them instead of using one browser for every generator. #### Start Time and End Time Optional scheduling controls. The generator must still be manually started. *** ## Why a Browser Mix Is Recommended Different browser selections can produce different browser environments for ShapeV2 cookie generation. Using a browser mix helps avoid relying on one configuration across your entire setup. For example: ``` ShapeV2 Task 1 → Browser A ShapeV2 Task 2 → Browser B ShapeV2 Task 3 → Browser A ShapeV2 Task 4 → Browser B ``` Use only browser options that are available inside your current Stellar version. Do not create more ShapeV2 generators than your computer or server can operate reliably. *** ## Recommended Setup ### Small Setup For a small Bandai setup: * One Bandai account * One corresponding profile * One Normal task * Product Qty: `1` * Normal delay: `3333` * Watch Task enabled * One Monitor task for the SKU * Monitor delay: `3333` * ShapeV2 Gen-Experimental running * Bandai selected as the ShapeV2 site * Cookie Expiration: `300000` * Cookies Per Task: `5` * High-quality ISP proxies ### Larger Setup For multiple checkout tasks: * One unique Bandai account per Normal task * One organized profile per account * No account reused across tasks * One Monitor task per SKU as a starting point * Enough ShapeV2 cookie generation to support the active setup * A mix of browsers across ShapeV2 generators * Multiple high-quality proxy pools * More than one proxy provider when possible Scale gradually and monitor the system’s CPU, memory, proxy performance, cookie supply, and task statuses. *** ## Proxy Recommendations Initial Bandai testing performed well with ISP proxies. A recommended starting strategy is: * **Normal tasks:** High-quality ISP proxies * **Monitor tasks:** ISP proxies * **ShapeV2 tasks:** High-quality ISP proxies * **Additional diversity:** Mix in residential proxies for some tasks when desired Proxy performance may change during heavily trafficked drops. For a more resilient setup: * Use multiple proxy providers * Use multiple proxy pools * Avoid placing every task on one provider * Test proxies before the release * Replace consistently blocked proxies * Avoid repeatedly restarting tasks on the same failing proxy *** ## Task and Account Limits ### Normal Tasks Run: ``` 1 Normal task per Bandai account ``` This is required because the cart is shared across the account. Reusing the same account across multiple tasks may cause: * Products interfering with one another * Incorrect cart contents * Checkout conflicts * Quantity problems * Failed orders * Account or session instability ### Monitor Tasks Start with: ``` 1 Monitor task per SKU ``` Additional monitors may be used if current instructions recommend redundancy, but avoid unnecessary duplication. ### ShapeV2 Tasks Create enough ShapeV2 tasks to maintain cookies for your setup without overloading your computer, server, or proxies. There is no universal number that fits every setup. Scale according to: * Number of Normal tasks * Cookie availability * Proxy quality * Browser distribution * Available CPU and memory * Live performance *** ## When to Start Tasks ### Before the Release 1. Update StellarAIO. 2. Confirm every Bandai account can log in. 3. Verify each Normal task uses a unique account. 4. Confirm profiles and payment information. 5. Verify all SKUs. 6. Test proxy groups. 7. Start the ShapeV2 generators. 8. Confirm Bandai cookies are being generated. 9. Start the Monitor tasks. 10. Start the Normal tasks with Watch Task enabled. 11. Confirm the Normal tasks are waiting for their Monitor ping. Do not wait until the exact release time to discover an account, profile, proxy, or ShapeV2 problem. ### During the Release * Keep ShapeV2 running. * Keep Monitor tasks running. * Allow Normal tasks time to process. * Watch available cookie counts. * Do not reuse an account in another task. * Do not immediately mass-restart tasks because of a temporary status. * Follow live Stellar announcements if settings or restarts are required. * Replace blocked proxies when necessary. ### After the Release * Confirm successful orders through Bandai. * Stop tasks you no longer need. * Review unsuccessful task statuses. * Record any setup changes that performed better. * Keep accounts and sessions organized for future releases. *** ## Common Errors and Fixes ### Waiting for Monitor Ping This is not an error when **Watch Task** is enabled. The Normal task is waiting for a matching Monitor task to detect inventory. Confirm that: * A Monitor task is running. * The Monitor and Normal tasks use the same SKU. * The Monitor proxy is working. * The Monitor task has not stopped. * The product has not changed to a different SKU. *** ### No Bandai Cookies Available **Possible Causes** * ShapeV2 is not running. * The wrong site is selected. * Cookies have expired. * The ShapeV2 proxy is blocked. * The browser configuration is failing. * Too few cookies are being generated for the active setup. **Fix** * Start the ShapeV2 tasks. * Confirm **Site** is set to **Bandai**. * Confirm Cookie Expiration is `300000`. * Confirm Cookies Per Task is `5`. * Test another proxy pool. * Use a mix of browsers. * Reduce the number of active Normal tasks if cookie supply cannot keep up. *** ### ShapeV2 Is Running but Cookies Are Not Increasing **Possible Causes** * Poor proxy quality * Browser-specific failure * Incorrect site selection * Too many generators for the machine * Temporary Bandai or Shape protection issues **Fix** * Confirm Bandai is selected. * Test a different browser. * Test another ISP or residential proxy pool. * Reduce the number of simultaneous generators. * Restart only the affected generator. * Check Stellar announcements for a current issue. *** ### Account or Session Login Failure **Possible Causes** * Incorrect account email * Incorrect password * The wrong session is associated with the task * The same account is being reused * Bandai is requiring manual account verification **Fix** * Verify the account credentials. * Confirm the correct session is selected. * Confirm the profile belongs to the intended account. * Stop any other task using the same account. * Log into the Bandai account manually if verification is required. * Update the saved session after changing a password. *** ### Shared Cart or Incorrect Product in Cart **Cause** The same Bandai account is being used across more than one Normal task. Because the cart is shared, each task can affect the other task’s cart. **Fix** * Stop every task using that account. * Use only one Normal task for the account. * Assign other Normal tasks to different Bandai accounts. * Confirm the cart is clean before trying again. *** ### Product Does Not Add to Cart **Possible Causes** * Product is out of stock * Incorrect SKU * Shape cookies are unavailable * Proxy is blocked * Purchase limit has already been reached * The account is already being used by another task **Fix** * Verify the SKU. * Confirm the Monitor is detecting stock. * Confirm ShapeV2 cookies are available. * Test a different proxy. * Confirm only one task is using the account. * Check the account’s existing orders and purchase limits. *** ### Proxy or Site Block **Possible Causes** * The selected proxy has been blocked. * Too many requests are being sent through the proxy. * The proxy pool is performing poorly during the release. * Bandai’s protection has changed. **Fix** * Test a different proxy. * Switch to another provider or pool. * Increase the delay if current instructions recommend it. * Mix ISP and residential proxies. * Avoid repeatedly restarting on the same blocked proxy. *** ### Normal Task Does Not Start After Stock Is Detected Confirm that: * Watch Task is enabled. * The Normal and Monitor tasks use the same SKU. * The Normal task is still running. * The task has a valid profile and account. * ShapeV2 cookies are available. * The checkout proxy is working. * The account is not being used by another task. *** ### Task Is Running but No Checkout Occurs A running task does not guarantee an order. Possible reasons include: * Inventory sold out * Account purchase limits * Insufficient ShapeV2 cookies * Proxy failure * Payment decline * Incorrect profile information * Product quantity restrictions * Another task interfering with the shared account cart Check the task status, Bandai account, profile, proxy, and available cookies before restarting. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://guides.stellaraio.com/stellar/retailers/bandai.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.