> 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/shapev2.md). # Shapev2 Complete guide on our Shape module
ShapeV2 generates **ATC cookies** for supported retailers. ATC stands for **Add to Cart**. These cookies are used when checkout tasks attempt to add a product to cart and continue through checkout. ShapeV2 currently supports: * Target * Bandai US Always select the correct retailer using the **Site** field. Cookies generated for one retailer cannot be used for another retailer. ## Shape Task Overview ### Gen Mode
### Gen Experimental Mode
## Retailer Differences #### Target For [Target](/stellar/retailers/targetgo.md), ShapeV2 continuously generates ATC cookies for Shipping and Pickup tasks. Target uses several separate systems: * **Regular** [**Shape**](/stellar/retailers/shape.md) **with the Login endpoint:** Generates Target Login cookies. * **Request Login:** Signs Target sessions in using saved account credentials. * **IMAP:** Retrieves emailed Target verification codes automatically. * **ShapeV2:** Generates Target ATC cookies. * **Target Browser Extension:** Generates additional Target ATC cookies. The regular Shape module should be stopped after Target accounts are successfully signed in. ShapeV2 and the Target Browser Extension should remain running while Target Shipping or Pickup tasks are active. #### Bandai US For Bandai, ShapeV2 generates the ATC cookies used by Normal checkout tasks. Bandai does not use the Target Browser Extension. Create ShapeV2 tasks with **Bandai** selected in the Site field and keep them running while Bandai checkout tasks are active. Bandai accounts share their cart across tasks. Run only: ``` 1 active checkout task per Bandai account ``` Running multiple checkout tasks on the same Bandai account can cause products to interfere with one another. ### Preliminary Checklist Before creating ShapeV2 tasks, confirm that you have: * [ ] Updated StellarAIO to the latest version. * [ ] Added high-quality proxies. * [ ] Prepared multiple proxy providers or proxy pools when possible. * [ ] Confirmed whether you are generating cookies for Target or Bandai. * [ ] Reviewed the applicable retailer guide. * [ ] Prepared multiple supported browsers. * [ ] Created the applicable retailer sessions. * [ ] Created your retailer checkout tasks. * [ ] Confirmed your computer or server can handle the planned number of browser tasks. * [ ] Tested a small number of ShapeV2 tasks before scaling. For Target, also confirm that: * [ ] All Target sessions are successfully signed in. * [ ] The regular Shape Login tasks have been stopped. * [ ] The Stellar AIO Target Browser Extension V3 is installed and running. ### Supported Modes ShapeV2 includes two modes: * `Gen` * `Gen Experimental` #### Gen Gen generates ATC cookies using the selected Site, proxy, and browser. This mode allows you to choose from the supported browsers available in Stellar. #### Gen Experimental Gen Experimental uses an alternate headless browser flow to generate ATC cookies. This mode may be useful when running multiple generators, but you should still begin with a small number of tasks. Do not assume that more Gen Experimental tasks will always improve performance. Test the mode with your device, browsers, and proxies. ### Which Mode Should I Use? #### Target For Target, run a mixture of: * `Gen` * `Gen Experimental` Do not run every generator using the same mode and browser. #### Bandai For Bandai, `Gen Experimental` is the recommended starting mode based on the current setup. Test different supported browsers and follow the latest Bandai announcement if the recommended mode changes. Shape performance can vary based on: * Retailer * Operating system * Device * Browser * Proxy provider * Proxy pool * Network * Number of simultaneous tasks * Current website protection There is no single combination that works best for every user. ### Field Breakdown #### Name This is an optional custom name for the task. Use a name that identifies the retailer, mode, and browser. Examples: ``` Target ShapeV2 Gen Edge ``` ``` Target ShapeV2 Experimental Brave ``` ``` Bandai ShapeV2 Experimental Firefox ``` Clear task names make it easier to compare which combinations successfully generate cookies. #### Mode Select the cookie-generation mode. Available options include: * `Gen` * `Gen Experimental` For Target, use a mixture of both modes. For Bandai, begin with Gen Experimental unless newer Stellar guidance recommends a different setup. #### Checkout Proxy Select the proxy group the ShapeV2 task should use. High-quality ISP and residential proxies are recommended. For Target, test a mixture of: * US ISP proxies * High-quality residential proxies For Bandai, ISP proxies have performed well during testing. You can also mix in high-quality residential proxies for additional variety during drops and restocks. For larger setups: * Use multiple proxy providers or proxy pools. * Avoid placing every ShapeV2 task on the same proxy group. * Test your proxy groups before an important release. * Replace or rotate proxies that repeatedly fail to generate cookies. * Avoid using the same proxy across too many simultaneous generators. Proxy performance can change over time. Continue testing your own providers and pools. #### Site Select the retailer for which you want to generate ATC cookies. Current options include: * `Target` * `Bandai` This field is required. Make sure the Site matches the retailer of your checkout tasks. If you are running Target tasks, select: ``` Target ``` If you are running Bandai US tasks, select: ``` Bandai ``` A Target ShapeV2 task cannot provide cookies to Bandai tasks. A Bandai ShapeV2 task cannot provide cookies to Target tasks. #### Cookie Expiration Cookie Expiration determines how long a generated ATC cookie remains available before expiring. The value is entered in milliseconds. The recommended starting value for Target and Bandai is: ``` 300000 ``` `300000` milliseconds equals five minutes. ATC cookies expire quickly. ShapeV2 should remain running while the applicable checkout tasks are active. #### Cookies Per Task Cookies Per Task controls how many cookies each ShapeV2 task attempts to generate or maintain. For Target, the recommended starting value is: ``` 3 ``` For Bandai, the recommended starting value is: ``` 5 ``` More cookies are not always better. Increasing this value or creating excessive generators can increase browser load and the risk of proxy or device bans. Begin with the recommended value for the selected retailer. Adjust only when checkout tasks are consistently running out of ATC cookies. ### Browser Select the browser the ShapeV2 task should use to generate ATC cookies. The available browser options apply to both ShapeV2 modes: * Gen * Gen Experimental #### Recommended Browsers Start with a mixture of: * Edge * Brave * Firefox * Safari, when available on your device If you need additional browser variety, add: * Aloha #### Chrome Guidance Chrome has produced the lowest pass rate in current Stellar testing and is not recommended for ShapeV2. You do not need to include Chrome in your setup. Only test it if Chrome has already generated successful cookies for your specific device, proxies, and retailer. If Chrome produces a poor pass rate, repeated bans, or unstable generators, stop using it and move those tasks to the recommended browsers. Chromium and Opera may remain available in the browser menu, but they are not part of the current recommended starting setup. #### Recommended Distribution Do not assign every ShapeV2 task to the same browser. A small starting setup could include: ``` Gen using Edge Gen using Firefox Gen Experimental using Brave Gen Experimental using Safari ``` If Safari is unavailable, redistribute that task to Edge, Brave, or Firefox. If you need additional browser variety, add an Aloha task. This is only an example. You do not need one task for every browser, and you should not create more generators simply because more browser options are available. Begin with a small number of generators and compare: * Successful cookie generation * Cookie pass rate * Proxy performance * Browser stability * CPU and memory usage * Shape bans Keep the combinations that perform best for your device, proxies, and selected retailer. #### Invisible Invisible mode attempts to generate cookies without displaying a browser window. This feature may only be available for certain modes and is experimental. Recommended testing process: 1. Keep your existing number of ShapeV2 tasks. 2. Enable Invisible mode on only one supported task. 3. Compare its performance with your visible tasks. 4. Scale only after confirming that it works well on your device. Do not increase your total number of ShapeV2 tasks simply because a task is running invisibly. #### Start Time This is an optional time at which an already-started task may begin operating. Setting a Start Time does not start the task automatically. You must still start the task inside Stellar. #### End Time This is an optional time at which the task should stop operating. ### Recommended Target Setup Use the following as a starting point for Target: * **Site:** `Target` * **Modes:** A mixture of `Gen` and `Gen Experimental` * **Checkout Proxy:** High-quality ISP or residential proxies * **Cookie Expiration:** `300000` * **Cookies Per Task:** `3` * **Browser:** Use a mixture of Edge, Brave, Firefox, and Safari when available. Add Aloha if additional variety is needed. Do not use Chrome unless it has proven successful for your setup. * **Invisible:** Optional and experimental * **Target Browser Extension:** Running at the same time Before starting ShapeV2, make sure all Target sessions are already signed in. Keep ShapeV2 and the Target Browser Extension running while Target Shipping or Pickup tasks are active. ### Recommended Bandai Setup Use the following as a starting point for Bandai US: * **Site:** `Bandai` * **Mode:** `Gen Experimental` * **Checkout Proxy:** High-quality ISP proxy * **Cookie Expiration:** `300000` * **Cookies Per Task:** `5` * **Browser:** Use a mixture of supported browsers * **Target Browser Extension:** Not required High-quality residential proxies can also be mixed into the setup. Keep Bandai ShapeV2 tasks running while Bandai Normal checkout tasks are active. Run only one active Bandai checkout task per account because the account cart is shared. ### How Many ShapeV2 Tasks Should I Run? There is no fixed ratio between ShapeV2 tasks and checkout tasks. Start with fewer generators and increase them only if Stellar is running out of ATC cookies. For example, if you are running 10 Target checkout tasks, you could begin with approximately three Gen Experimental tasks alongside a smaller number of regular Gen tasks and the Target Browser Extension. For Bandai, begin with a small number of Gen Experimental tasks and monitor cookie availability before scaling. Running excessive ShapeV2 tasks may: * Increase CPU and memory usage. * Slow down your computer or server. * Place unnecessary load on browsers. * Burn proxies. * Increase the risk of device-level Shape bans. * Reduce the overall cookie pass rate. The goal is to maintain enough fresh ATC cookies for active checkout tasks, not to generate the highest possible number of cookies. ### When to Start ShapeV2 Start ShapeV2 before starting checkout tasks for the selected retailer. Do not wait until the exact release time to test your cookie generation. #### Target Start Order 1. Confirm all Target sessions are signed in. 2. Stop the regular Shape tasks using the Login endpoint. 3. Open the Target Browser Extension. 4. Enable the extension and its cookie generator. 5. Start a mixture of Target ShapeV2 Gen and Gen Experimental tasks. 6. Confirm that Target ATC cookies are being generated. 7. Start the Target Monitor tasks. 8. Start one Target Shipping or Pickup task per account. 9. Keep ShapeV2 and the Target Browser Extension running throughout the drop. #### Bandai Start Order 1. Confirm all Bandai sessions are added correctly. 2. Start Bandai ShapeV2 tasks. 3. Confirm Bandai ATC cookies are being generated. 4. Start the Bandai Monitor tasks. 5. Start one Bandai Normal task per account. 6. Keep the Bandai ShapeV2 tasks running throughout the drop or restock. ### Target Browser Extension The Target Browser Extension is only used for Target. For Target, ShapeV2 should run alongside the Stellar AIO Target Browser Extension V3. Inside the extension: * Add high-quality proxies if required. * Enable the extension. * Enable the cookie generator. * Set Cookies Per Task to `3`. * Set Cookie Expiry to five minutes. * Keep a supported Target browser page open. * Confirm that the extension is connected to Stellar. * Confirm that the available cookie count is increasing. The extension also contains a **Target Login Token** function. That function is for the backup Token Login method and is separate from ATC-cookie generation. You do not need a Target login token when using the recommended Request Login method. The Target Browser Extension does not generate Bandai cookies. ### Recommended Practices * Always select the correct Site. * Test your setup before an important drop. * Use multiple supported browsers. * Use multiple proxy providers or pools. * Test a mixture of high-quality ISP and residential proxies. * Begin with fewer generators. * Increase generators only when cookies are being consumed faster than they are produced. * Keep ShapeV2 running while checkout tasks are active. * Monitor CPU and memory usage. * Give your device and proxies a break after excessive Shape bans. * Run only as many generators as your computer or server can handle reliably. * Follow the latest Stellar announcement when temporary drop instructions are provided. For Target: * Run Target locally when possible. * Test macOS if available. * Use both Gen and Gen Experimental. * Keep the Target Browser Extension running with ShapeV2. For Bandai: * Begin with Gen Experimental. * Use a mixture of supported browsers. * Start with high-quality ISP proxies. * Mix in residential proxies when additional variety is needed. * Run one active checkout task per Bandai account. ### **Notes from Devs** 1. We highly recommend testing how many Shape Tasks you actually need for your checkout tasks. There isn't a fixed ratio, so start with fewer and only scale up if you're running out of cookies. Running 20 Shape Tasks for just 2 checkout tasks doesn't help - you're much more likely to flag your device or proxies. For example, if you're running 10 checkout tasks, start with 3 experimental Shape Tasks and increase them during the drop only if needed. 2. Current Stellar testing shows that Chrome has the lowest Shape pass rate. Start with Edge, Brave, Firefox, and Safari when available. Add Aloha if more browser variety is needed. Chrome is not required and should only be tested when it has already produced reliable results for your setup. 3. If you're getting excessive Shape bans, give your device a break before trying again. Ideally, don't generate any Shape Tasks over the weekend and start fresh for the next drop. 4. We recommend using a mix of US ISP and Residential proxies instead of only ISPs. Since Target usually drops around similar times, you can prepare your Shape Tasks beforehand and test what works best with your setup. 5. There isn't one setup that works for everyone. Every device, proxy provider, network, and setup behaves differently. Keep testing, monitor your tasks during drops, and make adjustments until you find what works best. We can give general recommendations, but you'll get the best results by experimenting with your own setup. 6. If you have access to a macOS device, it's definitely worth testing on Target. In our testing, macOS has consistently performed better for Shape than Windows. ### Common Errors and Fixes #### Incorrect Site Selected If checkout tasks are waiting for cookies, confirm that the ShapeV2 Site matches the retailer. For Target tasks, select: ``` Target ``` For Bandai tasks, select: ``` Bandai ``` Cookies cannot be shared between retailers. #### Checkout Task Is Waiting for an ATC Cookie This means the task does not currently have a valid ATC cookie for its retailer. Confirm that: * ShapeV2 is running. * The correct Site is selected. * Cookies are being generated. * Cookie Expiration is set correctly. * Cookies Per Task is set correctly. * The selected proxies are working. * The selected browsers are supported. For Target, also confirm that: * The Target Browser Extension is running. * The extension is connected to Stellar. * The extension cookie generator is enabled. If cookies are still unavailable: 1. Test another proxy group. 2. Test a different supported browser. 3. Confirm the correct mode is selected. 4. Restart a small number of failed generators. 5. Increase the number of generators gradually if cookies are being consumed too quickly. #### ShapeV2 Is Not Generating Cookies Possible causes include: * Incorrect Site selection * Poor or blocked proxies * An unsupported or outdated browser * A temporary Shape ban * Too many generators running at once * Excessive CPU or memory usage * An outdated Stellar version * Changes to the retailer’s protection Try the following: 1. Confirm Stellar is updated. 2. Confirm the correct Site is selected. 3. Test another high-quality proxy group. 4. Test another supported browser. 5. Reduce the number of simultaneous generators. 6. Restart only the affected tasks. 7. Give the device and proxies time to rest before testing again. #### Cookies Generate but Expire Before Use Confirm that: * Your checkout tasks are already running. * ShapeV2 remains running continuously. * Cookie Expiration is set to `300000`. * Your generators are producing cookies consistently. * The correct Site is selected. For Target, confirm that the Browser Extension remains enabled. Do not generate a large supply of ATC cookies far in advance. These cookies expire quickly and should be generated while checkout tasks are active. #### Excessive Shape Bans Reduce the number of generators and test different: * Proxy providers * Proxy pools * Supported browsers * Modes * Devices Do not repeatedly restart a large number of banned tasks. Allow the affected device and proxies time to rest. If possible, avoid generating unnecessary cookies between major drops. #### High CPU or Memory Usage Every browser-based generator uses system resources. Try the following: * Reduce the number of simultaneous ShapeV2 tasks. * Close unnecessary applications. * Test additional supported browsers. * Monitor system usage before scaling. * Run only as many generators as the device can handle reliably. ### Final Reminder ShapeV2 supports multiple retailers. Always select the correct Site. For Target: * Regular Shape creates Login cookies. * Request Login signs the account in. * IMAP retrieves emailed login codes. * ShapeV2 creates ATC cookies. * The Target Browser Extension creates additional ATC cookies. For Bandai: * ShapeV2 creates the ATC cookies used by Normal checkout tasks. * The Target Browser Extension is not required. * Run one active checkout task per Bandai account. Keep ShapeV2 running while checkout tasks for the selected retailer are active. --- # 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/shapev2.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.