> 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/pokemon-center.md).
# Pokemon Center
Complete guide on our Pokémon Center module
Pokémon Center task creation is relatively straightforward, but the site is **Captcha-heavy** and sensitive to proxy quality. Preparing your tasks, proxies, profiles and Captcha harvesters before a drop is important.
***
## **Video Guide**
This video shows an earlier Stellar interface. Use the written 4.0 instructions and screenshots below for current controls.
{% embed url="" %}
***
## Quick Start: Recommended Setup
This setup uses the Stellar AIO 4.0 interface. Select guest for standard Pokémon Center checkout tasks and follow these steps in order.
### 1. Prepare Your Profiles and Proxies
Before creating tasks:
* Update StellarAIO to the latest version.
* Create valid profiles with correct billing, shipping, payment, and email information.
* Confirm that each profile matches the Pokémon Center region you will run.
* Add multiple groups of clean, high-quality ISP and residential [proxies](/stellar/botting-basics/proxies.md).
* Use multiple proxy providers or proxy pools when possible.
* Enable cook group notifications for confirmed product URLs, PIDs, and drop updates.
A Pokémon Center account or session is not required for Guest mode.
### 2. Prepare Your Captcha Harvesters
Pokémon Center is Captcha-heavy, so prepare your [harvesters](/stellar/navigating-stellaraio/what-is-the-harvesters-tab/how-do-i-set-up-the-captcha-harvester.md) before the drop.
* Create only as many harvesters as your computer or server can comfortably handle.
* Open Harvesters → Captcha Harvesters → Create Harvester(s).
* Enable hCaptcha AI Solver on the harvesters you intend to use.
* Select Test AI, confirm Ready, and check your computer’s performance.
* Open your harvesters before the drop.
* Do not wait until Captchas appear and then open many harvesters simultaneously.
* Remain available in case manual Captcha solving is required.
Guest mode automatically uses Stellar’s in-bot Captcha harvesters. There is no Captcha Provider field in Guest task creation.
### 3. Create Your Guest Tasks
The screenshot shows form defaults. Apply the recommended settings below, including the guide’s delay range.
* **Mode:** Guest
* **Profile:** Valid profile or profile group
* **Checkout Proxy:** High-quality ISP or residential proxies
* **Region:** Region matching the Pokémon Center website and selected profiles
* **Product URL or PID:** Confirmed product information or a temporary placeholder
* **Delay:** Between `5000` and `20000`
* Module Unlock Delay: Set to 0 or leave empty (recommended)
* **Quantity:** `1`
* Min SKUs in Cart: 1
* **Catch All:** Optional
* **Endless Mode:** Off unless you intentionally want the task to continue after checkout
* **Endless Limit:** Set only when using Endless Mode
* **Solve 3DS:** Enable only for the EU/UK region
* Rotate on Decline?: Enable when using a profile group
* **Start Time and End Time:** Optional
* **Task Qty:** Start with approximately `5–20` Guest tasks per profile
Only scale beyond this starting point if your profiles, proxies, Captcha-solving capacity, and computer or server can support the additional tasks.
### 4. Enter Your Products
For fast entry, paste multiple products and their quantities using SKU1:1,SKU2:2,SKU3:1. You can also enter each product in its own Product row.
* **PID** is the product ID, including its dashes.
* **QTY** is the number of units you want.
* Set the quantity in the Qty field beside that product.
**Examples:**
Product: 10-10465-166 | Qty: 1 → 1 unit\
Product: 10-10465-166 | Qty: 2 → 2 units
The Qty field defaults to 1. Check it for every product row.
Multiple products: Select Add item to create another row for each product.
Row 1: PID1 | Qty: 1\
Row 2: PID2 | Qty: 2\
Row 3: PID3 | Qty: 1
Replace the SKU or PID placeholders in these examples with actual product IDs, including their dashes. In the fast-entry format, the number after each colon is that product’s quantity. We recommend a maximum of 3 or 4 products per Guest task to be safe. The absolute limit is 5 products per task.
#### Product Information Not Available Yet?
Use a temporary placeholder such as:
`83195729`
This allows you to create and start tasks so they can enter the queue.
Once your cook group provides the confirmed product information, **mass edit your running tasks while they are still in queue**. Replace the placeholder with the correct **PID** before tasks attempt to add the product to cart.
#### **How to Mass Edit Products While Tasks Are in Queue**
Use this when your Guest tasks are already running with a placeholder and the confirmed product information becomes available. You can save the product changes while tasks remain in queue; you do not need to stop or restart them.
1. Open **Tasks** and select the Pokémon Center task group you want to update.
2. Click **Edit All**. Under **Select Mode**, choose **guest** if it is not already selected. The number beside guest shows how many Guest tasks are in that group. This updates every Guest task in the current group, not just selected rows.
3. Replace the placeholder in **Product** with the confirmed URL or PID, including any dashes. Check the **Qty** beside each product. Remove any leftover placeholder or product rows you do not want.
4. For several products, paste **SKU1:1,SKU2:2,SKU3:1**, replacing SKU1, SKU2 and SKU3 with actual PIDs. Stellar separates them into product rows with quantities 1, 2 and 1. You can also use **Add item** to enter them individually. We recommend 3 or 4 products maximum per Guest task; 5 is the absolute limit.
5. For a product-only update, leave unrelated fields and switches untouched. Review the product list and quantities, then click **Save** before tasks begin adding products to cart.
6. Open an individual Guest task’s edit form to confirm the placeholder was replaced, then close the form without making further changes. Leave the tasks running in queue. Repeat for any other Pokémon Center groups you need to update.
**Example below:** SKU1, SKU2 and SKU3 are labels for illustration only. Replace them with confirmed product IDs before saving. The other fields are left untouched for this product-only update.
### 5. Start Your Tasks Early
The recommended approach is to start Guest tasks before the drop.
Tasks may display:
```
Module Disabled
```
This is normally expected while the Pokémon Center module is disabled. Once Stellar enables the module, correctly configured running tasks can begin entering the queue automatically.
Starting early also gives you time to identify profile, proxy, Captcha, or setup problems before the release.
### 6. Confirm Your Setup Is Ready
Before leaving the setup running, confirm:
* StellarAIO is updated.
* Every selected profile is valid.
* Your proxies have been tested.
* Your Guest tasks are running.
* Your harvesters are already open.
* Test AI completes successfully and the AI status shows Ready.
* Your computer or server is not overloaded.
* The correct region is selected.
* Your tasks use either the confirmed product information or a placeholder.
* You are ready to mass edit the confirmed URL or PID while the tasks are in queue.
### 7. During the Drop
When the confirmed product information becomes available:
1. Copy the trusted product URL or PID.
2. Mass edit the running Guest tasks while they are still in queue.
3. Confirm that the placeholder was replaced correctly.
4. Leave correctly progressing tasks running.
5. Solve Captchas quickly when manual action is required.
6. Follow new instructions from Stellar staff and your cook group.
The Pokémon Center queue is randomized and is not strictly first come, first served. Do not restart tasks unnecessarily unless Stellar staff recommends it.
***
## **Preliminary Checklist**
Before creating Pokémon Center tasks, confirm that you have completed the following:
* [ ] Updated StellarAIO to the latest version
* [ ] Created profiles with valid billing, shipping, payment and email information
* [ ] Added clean, high quality ISP and/or residential proxies. It's best to use multiple proxy providers and/or multiple proxy pools
* [ ] Created and tested your Captcha harvesters
* [ ] Confirmed that the AI solver is ready by using Test AI
* [ ] Enabled cook group notifications for product URLs, PIDs, and drop updates
* [ ] Precreated your tasks before the drop
* [ ] Confirmed that your selected region matches your profiles and the Pokémon Center website
* [ ] Tested your setup before an important release
Pokémon Center can be run on a local computer or server. Both can perform well, provided the system can handle your tasks and Captcha harvesters.
Warning: Do not create more Captcha harvesters than your computer or server can comfortably handle. Excessive harvesters can increase CPU usage and delay Captcha solving.
***
## Accounts & Sessions
A Pokémon Center account or Stellar session is **not required for Guest mode**.
Guest mode checks out using the billing, shipping, payment and email information stored in the selected Stellar profile.
Account Gen is available if you want to create Pokémon Center accounts, but those accounts are not required for Guest checkout tasks.
Newsletter mode is also separate from the Guest checkout flow. It subscribes profile emails to the Pokémon Center newsletter and does not create checkout tasks.
***
## Captcha Preparation
Pokémon Center is Captcha-heavy. Captcha preparation can have a significant effect on your results.
**What is a Captcha Harvester?** A Captcha is a verification challenge a website uses to help distinguish people from automated traffic. A Captcha Harvester is a window inside Stellar where these challenges can be solved. When a Pokémon Center task needs a Captcha, the harvester handles the challenge and provides the result so the task can continue. Guest tasks use Stellar’s in-bot Captcha harvesters automatically.
**What does hCaptcha AI Solver do?** It uses AI to attempt to solve hCaptcha challenges in your harvesters automatically, reducing the number you need to solve by hand. Enable it for each harvester you plan to use. In Stellar 4.0, this is the only AI autosolve option; there is no separate server-side AI option. It may not solve every challenge, so keep an eye on your harvesters and be ready to solve manually when needed.
**Why do I need them?** When Pokémon Center requires a Captcha, the task needs a valid solution before it can continue through that step. If harvesters are closed, not ready, or unable to keep up, tasks can be delayed waiting for solutions. Open and test your harvesters before the drop. Use **Test AI** to confirm the solver is ready and choose a harvester count your computer can handle comfortably. There is no fixed recommended number, and opening more than your computer can support can slow solving down.
### Creating Harvesters
Open Harvesters → Captcha Harvesters and select Create Harvester(s). Enter a name, enable hCaptcha AI Solver, set Qty, and select Create.
Choose Qty based on your computer’s performance when using Test AI.
See the complete [Captcha Harvester Guide](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-captchas-tab/how-do-i-set-up-the-captcha-harvester) for setup instructions.
YouTube or Gmail login is not required for Pokémon Center harvesters.
Unless current staff guidance says otherwise, leave the individual harvester proxy field blank so the flow can use the applicable task proxy.
### Open Harvesters Before the Drop
Open your Captcha harvesters before the expected drop time.
Do not wait until Captchas appear and then burst open a large number of harvesters simultaneously. Opening many windows at once can:
* Increase CPU usage suddenly
* Delay the harvesters becoming ready
* Slow down Captcha solving
* Reduce performance during a time-sensitive drop
Open them in advance and confirm they are ready before starting the drop.
hCaptcha AI Solver
Enable hCaptcha AI Solver for Pokémon Center in Harvesters → Captcha Harvesters.
Stellar 4.0 offers hCaptcha AI Solver as its only AI autosolve option. There is no separate server-side AI option.
Before the drop:
1. Turn on hCaptcha AI Solver for each harvester you intend to use.
2. Select Test AI.
3. Confirm that the AI status shows Ready.
4. Monitor your system’s CPU and memory usage.
5. Reduce the number of harvesters if your system becomes slow.
There is no fixed recommended number of harvesters. Use Test AI to check your setup and choose a count your computer can run comfortably. Reduce the count if solving slows down or your system becomes unresponsive.
Only create and open the number of harvesters your computer or server can operate comfortably.
Manual Captcha Solving
Keep your harvesters open and watch for any challenges that need manual input.
You should still remain available during the drop in case manual interaction is required.
***
## Supported Modes
### **Guest Mode**
Guest mode is the primary Pokémon Center checkout mode.
Guest tasks:
1. Wait for the Pokémon Center module and queue to become available.
2. Enter the queue.
3. Process the product URL or PID assigned to the task.
4. Attempt to add the product to cart.
5. Submit checkout using the selected profile.
Guest mode uses Stellar’s in-bot Captcha harvester system automatically. There is no Captcha Provider field inside Guest task creation.
### **Account Gen**
Account Gen creates Pokémon Center accounts using the email and personal information stored in your Stellar profiles.
Use unique profile emails whenever possible. Catchall emails may be more likely to encounter account-generation issues.
Account Gen is optional and is not required before running Guest tasks.
### **Newsletter Mode**
Newsletter mode subscribes profile emails to the Pokémon Center newsletter.
Newsletter subscriptions may provide site announcements or potential early-access opportunities, but subscribing does not guarantee early access.
Use profiles with unique information and email addresses that have not already been registered for the newsletter.
***
## Guest Mode Breakdown
### Name
An optional name used to organize your tasks.
For example:
```
PKC ETB
```
If you are running multiple products, descriptive task names can make mass editing and troubleshooting easier.
### Mode
Select **Guest** to create Pokémon Center checkout tasks.
Guest mode does not require a Pokémon Center account or session.
### Profile
Select the profile or profile group Stellar should use during checkout.
Your profile should contain:
* A valid email address
* Correct shipping information
* Correct billing information
* A valid payment method
* Information matching the selected region
Incorrect or inconsistent profile information can cause address, payment, or profile declines.
### Checkout Proxy
Select the proxy group the task should use.
High-quality proxies are especially important for Pokémon Center because poor or blocked proxies can cause:
* Incapsula blocks
* Requeues
* Captcha issues
* Homepage loops
* Slower queue progress
* Failed cart or checkout attempts
A practical approach is to:
* Prioritize clean ISP proxies for your main tasks.
* Use high-quality residential proxies for your remaining tasks.
* Test multiple proxy pools and providers instead of relying on one source.
Ask your proxy provider which proxy type currently performs best on Pokémon Center.
### Region
Select the region that matches the Pokémon Center website and the information in your profile.
Choosing the wrong region can prevent checkout.
### Product URLs or PIDs
Enter the product URL or PID that the task should attempt to purchase.
A **PID**, or Product ID, is the identifying portion of a Pokémon Center product URL.
Example URL:
```
https://www.pokemoncenter.com/product/701-03742/dratini-sitting-cuties-plush-4-in
```
Example PID:
```
701-03742
```
Enter the complete PID exactly as it appears, including any required dashes.
For fast entry, use SKU1:1,SKU2:2,SKU3:1 to specify each product and its quantity. Replace the SKU placeholders with actual product IDs, including their dashes. We recommend no more than 3 or 4 products per Guest task to be safe; 5 products is the absolute limit. Alternatively, use Add item to give each product its own row and Qty:
```
Row 1: PID1 | Qty: 1
Row 2: PID2 | Qty: 2
Row 3: PID3 | Qty: 1
```
#### Using a Placeholder
When the correct product information is not available yet, enter a random placeholder so you can save and start your tasks.
Example:
```
83195729
```
The placeholder allows your tasks to enter the queue. Once your cook group provides the confirmed product URL or PID, mass edit the running tasks while they are still in queue.
Replace the placeholder with the correct URL or PID before the task begins its add-to-cart process.
### Coupon
Enter a valid coupon or promotional code if one is available.
Leave this field blank when you are not using a coupon.
### Delay
The delay controls how frequently the task retries applicable steps.
Recommended starting delay:
```
10000
```
Lower delays may allow faster retries but can increase the risk of blocks, errors, and requeues. Higher delays are generally safer but may respond more slowly.
The delay can be live edited, but make any necessary changes before the task enters the add-to-cart process.
### Module Unlock Delay
This optional setting delays the task after Stellar enables the Pokémon Center module.
Recommended setting:
```
0 or leave empty
```
For the recommended setup, use 0 or leave Module Unlock Delay empty so the task can proceed as soon as the module is enabled.
Leave the field blank if you want the task to continue as soon as the module becomes available.
### Quantity
Set Qty beside each Product row to the number of units you want.
Recommended starting quantity:
```
1
```
Higher quantities can increase the risk of Incapsula errors or retailer quantity-limit issues. Confirm product limits with your cook group before increasing this value.
Quantity can be live edited before the task enters the add-to-cart process.
### Min SKUs in Cart
This determines how many **different products or PIDs** must be added before Stellar submits checkout.
Recommended starting value:
```
1
```
This setting counts different products, not the total quantity of one product.
#### Example
If the task contains three different PIDs and Minimum SKUs in Cart is set to `2`:
* Product 1 carts successfully.
* Product 2 carts successfully.
* Product 3 is out of stock.
Stellar can proceed because the required minimum of two different products was reached.
If only one product carts, Stellar will not check out because the minimum requirement was not met.
If you only want one product, set Minimum SKUs in Cart to `1`.
### Catch All
Enable this setting if you want the task to use the catchall email configuration saved in Stellar’s Settings tab.
Leave it disabled if you want to use the email stored directly in the selected profile.
Catchall configuration is optional.
### Endless Mode
Endless Mode controls what happens after a successful checkout.
* **Disabled:** The task stops after one successful order.
* **Enabled:** The task restarts after checkout and continues attempting additional orders.
Only enable Endless Mode if you intentionally want the task to continue after a successful checkout.
### Endless Limit
When Endless Mode is enabled, use Endless Limit to set the maximum number of successful orders the task may place.
For example, an Endless Limit of `3` stops the task after three successful orders.
Leave this blank when Endless Mode is disabled.
### Solve 3DS
Enable **Solve 3DS** only when running the EU/UK region.
Leave it disabled for the United States and Canada.
### Rotate on Decline?
When enabled, Stellar can rotate to another profile after a decline.
This is recommended when using a profile group because it allows the task to try another profile instead of repeatedly using the declined one.
If you selected only one profile, there is no additional profile available to rotate to.
**Important:** During high-traffic Pokémon Center releases, PKC's backend may not properly update the email address when **Rotate Profile on Decline** rotates to a new profile. This is a Pokémon Center website/backend behavior and is not caused by Stellar. If you notice the previous email remaining after a profile rotation, this can occur even when Stellar successfully rotates the profile.
### Start Time and End Time
These optional settings control when a running task may begin processing and when it should stop.
If you use a scheduled start or end time, confirm the correct date, time, and timezone before the drop.
### Task Qty
The Qty field at the bottom of the task-creation window determines how many tasks Stellar creates using this configuration.
This is different from the product Quantity field:
* **Product Quantity:** How many units the task attempts to purchase.
* **Task Qty:** How many separate tasks Stellar creates.
***
## Account Gen Mode Breakdown
### Name
Optional organizational name for the account-generation tasks.
### Mode
Select **Account Gen** to create Pokémon Center accounts.
This mode does not create checkout tasks.
### Profile
Select the profile containing the information and email address that should be used for the account.
Unique emails are recommended. Ensure the profile email can receive messages from Pokémon Center.
### Checkout Proxy
Select a clean, high-quality proxy group for account creation.
Avoid creating a large number of accounts through the same weak or blocked proxy pool.
### Region
Select the region where the Pokémon Center account should be created.
The region should match the information saved in the profile.
### Password
Enter the password Stellar should use for the new Pokémon Center account.
Use a secure password and store it somewhere safe.
### Catch All
Enable this if you want Account Gen to use the catchall configuration saved in Stellar.
Unique individual emails are preferred when possible.
### Email Access
The 4.0 Account Gen task form does not include an IMAP Session selector.
Make sure you can access the email address saved in the selected profile.
### Delay
The delay controls the timing between account-generation requests.
There is no single delay that is ideal for every release. Use the current recommendation published by Stellar staff or your cook group.
### Start Time and End Time
Optional scheduling controls for the account-generation tasks.
### Task Qty
Determines how many Account Gen tasks are created with the selected configuration.
Make sure you have enough eligible profiles and emails for the number of tasks being created.
***
## **Newsletter Mode Breakdown**
### Name
Optional organizational name for the newsletter tasks.
### Mode
Select **Newsletter** to subscribe profile emails to the Pokémon Center newsletter.
Newsletter mode does not create accounts or checkout tasks.
### Profile
Select the profile containing the email and personal information that should be registered.
Use unique information and an email that has not already been subscribed.
### Checkout Proxy
Select a clean, high-quality proxy group.
### Region
Select the region matching the Pokémon Center newsletter and profile information.
### Delay
Recommended starting delay:
```
5000 or higher
```
Adjust this value if newer guidance is posted.
### Captcha Provider
Select the Captcha provider used for Newsletter mode.
Bot is the recommended starting option. Only select a third-party provider if it is configured in Stellar and currently supported for this flow.
The Captcha Provider field belongs to Newsletter mode. Guest mode uses Stellar’s in-bot Captcha harvesters automatically and does not display this field.
### Start Time and End Time
Optional scheduling controls for newsletter tasks.
### Task Qty
Determines how many Newsletter tasks Stellar creates.
Only create as many tasks as you have eligible profiles and unused email addresses.
***
## How Many Tasks Should I Run?
A common starting point is:
```
5–20 Guest tasks per profile
```
Scale based on:
* Number of valid profiles
* Number and quality of your proxies
* Number of proxy providers and pools
* Captcha-solving capacity
* Computer or server performance
* Current task limits announced by Stellar
* Drop-specific instructions
More tasks do not automatically produce better results. Running more tasks than your proxies, profiles, or computer can support may reduce overall performance.
***
## When Do I Start My Tasks?
There are two common approaches.
### Option 1: Start Early — Recommended
Start your Guest tasks before the drop.
The tasks may display:
```
Module Disabled
```
This is normally expected when the Pokémon Center module has not been enabled yet. Once Stellar enables the module, running tasks can automatically begin entering the queue.
This approach gives you time to identify profile, proxy, or setup problems before the drop.
### Option 2: Start When the Queue Goes Live
You can start tasks when the Pokémon Center queue becomes available.
This requires faster reaction time and gives you less time to correct setup problems.
### Recommended Timeline
Before the drop:
1. Update Stellar.
2. Confirm your profiles and proxies.
3. Precreate your Guest tasks with a placeholder PID.
4. Open and test your Captcha harvesters.
5. Use Test AI and confirm the AI solver is ready.
6. Start your tasks early.
7. Monitor Stellar and cook group announcements.
8. Mass edit the confirmed product URL or PID while your tasks are in queue.
The Pokémon Center queue is randomized. It is not strictly first come, first served.
Be patient after entering queue. Avoid stopping tasks unnecessarily unless Stellar staff announces that a restart is required.
***
## Latest Prep Call Recording
Watch the latest Pokémon Center prep call for release-specific explanations and examples:
{% embed url="" %}
Prep-call instructions may apply to a specific release. If a recording conflicts with the current task interface, this written guide, or a newer Stellar announcement, follow the newest information.
***
## Common Errors and Fixes
### Module Disabled
**What it means:** The Pokémon Center module has not been enabled for the current queue or drop.
**What to do:**
* Leave correctly configured tasks running.
* Wait for the module to be enabled.
* Monitor Stellar announcements.
* Restart only if Stellar staff recommends it or the task remains stuck after the module is confirmed active.
### Incapsula Block
**Likely cause:** The task proxy is blocked, low quality, or overused.
**What to do:**
* Live edit the task to a different proxy group.
* Try a different proxy pool or provider.
* Use clean ISP or high-quality residential proxies.
* Avoid sending too many tasks through a small proxy pool.
### Requeued Repeatedly
**Likely cause:** Requeues can be caused by Pokémon Center’s queue system, task traffic, proxy quality, or site protection.
**What to do:**
* Allow the task to continue retrying.
* Test another clean proxy pool if the same tasks repeatedly fail.
* Avoid restarting every task at once.
* Confirm you are using the recommended delay.
### Captchas Are Delayed or Not Solving
**Possible causes:**
* Harvesters were not opened before the drop.
* Too many harvesters were opened simultaneously.
* The hCaptcha AI Solver is not ready.
* Your computer or server is overloaded.
* Too many harvesters are running for the available hardware.
**What to do:**
* Open harvesters before the drop.
* Select Test AI.
* Confirm the hCaptcha AI Solver is enabled and ready.
* Reduce the number of active harvesters.
* Close unnecessary applications.
* Solve manually when required.
### Payment or Profile Decline
**Likely cause:** Pokémon Center rejected information in the profile. This may be a profile-related decline rather than a problem with the card itself.
**What to do:**
* Confirm the billing address matches the payment method.
* Check the shipping address for formatting problems.
* Confirm the selected region is correct.
* Avoid inconsistent or previously rejected profile information.
* Enable Rotate Profiles on Decline when using a profile group.
### Getting Homepage
**Likely cause:** This is commonly caused by a temporary site-flow or proxy issue.
**What to do:**
* Allow the task to retry.
* Restart only the affected task if it remains stuck.
* Try another clean proxy group if the behavior continues.
### Task Does Not Checkout After Carting a Product
Likely cause: Min SKUs in Cart is set higher than the number of different products successfully added.
**What to do:**
* Review the Minimum SKUs in Cart value.
* Set it to `1` when you only require one product.
* Make any changes before the task reaches checkout.
### Product Cannot Be Found
**Possible causes:**
* The placeholder PID was never replaced.
* The URL or PID is incorrect.
* A required dash is missing from the PID.
* The task reached the product stage before it was mass edited.
**What to do:**
* Copy the confirmed URL or PID from a trusted source.
* Enter the PID exactly as supplied.
* Mass edit the tasks while they are still in queue.
* Confirm the correct region is selected.
### Wrong Region or Checkout Failure
**Likely cause:** The selected region does not match the product website or profile.
**What to do:**
* Confirm the Pokémon Center region.
* Confirm the profile’s country and address.
* Recreate or edit the affected task using the correct region.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://guides.stellaraio.com/stellar/retailers/pokemon-center.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
