> For the complete documentation index, see [llms.txt](https://aphrowuu-aco.gitbook.io/aphrowuu-aco-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aphrowuu-aco.gitbook.io/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide.md).

# Retailer Profile Guide

Current retailer-by-retailer profile, payment, Auto Jig, and run-size guidance.

Use this guide before creating, importing, editing, or exporting checkout profiles. Every value you upload must be accurate, valid, and ready to use at checkout.

{% hint style="info" %}
All checkout profiles in this guide are US-based. Use a valid US phone number, state, ZIP code, billing address, and shipping address.
{% endhint %}

{% hint style="warning" %}
Uploading successfully does not prove that a profile will work at checkout. Double-check the card, account login, email, phone number, address, ZIP code, and apartment or unit before every run.
{% endhint %}

## Know which retailers need accounts

The dashboard currently supports these built-in checkout-profile retailers:

| Retailer           | Retailer account needed? | What to know                                                                 |
| ------------------ | ------------------------ | ---------------------------------------------------------------------------- |
| **Walmart**        | Yes                      | The account email must match the checkout profile email.                     |
| **Target**         | Yes                      | Confirm the account can sign in before uploading or exporting profiles.      |
| **Pokemon Center** | No                       | Uses checkout profiles only; a working email is still required for receipts. |
| **Riot Games**     | Yes                      | Confirm the account credentials work before a run.                           |
| **Topps**          | Yes                      | Confirm the account credentials work before a run.                           |
| **Sam's Club**     | Yes                      | Confirm the login and any membership needed for the release.                 |
| **Costco**         | Yes                      | Confirm the login and any membership needed for the release.                 |
| **Supreme**        | No                       | A valid checkout email is still required.                                    |
| **Custom Shopify** | No linked account        | Checkout requirements can vary by Shopify store.                             |
| **Menards**        | No                       | A valid checkout email is still required.                                    |
| **Bandai**         | Yes                      | Confirm the account credentials work before a run.                           |
| **COIN**           | No                       | A valid checkout email is still required.                                    |

{% hint style="info" %}
“No account needed” only means the dashboard does not require a linked retailer login. Every checkout profile still needs a valid email address.
{% endhint %}

Available sites can change. The retailer choices shown in [Checkout Profiles](https://github.com/bigboii-cmd/discord-bot-webapp/tree/main/docs/guides/%7B%7Bsite_url_full%7D%7D/dashboard/profiles?tab=checkout-profiles/README.md) are the current source of truth for your dashboard.

## Keep account-only tools separate

These account types are supported elsewhere in the dashboard but are not built-in checkout-profile retailers:

| Account type          | Checkout profile support | Use                                                         |
| --------------------- | ------------------------ | ----------------------------------------------------------- |
| **Amazon**            | No                       | Retailer-account storage; Amazon accounts require 2FA data. |
| **Microsoft Outlook** | No                       | Email-account and account-request tooling.                  |

Add and test retailer logins from the [Accounts tab](https://github.com/bigboii-cmd/discord-bot-webapp/tree/main/docs/guides/%7B%7Bsite_url_full%7D%7D/dashboard/profiles?tab=accounts/README.md).

## Complete every required profile field

### Profile and retailer

* Give each profile a clear, unique profile name.
* Select the exact retailer. Retailer-specific account and Auto Jig behavior depends on this selection.
* Use a valid email in the form `name@example.com`.
* Make sure the inbox exists, can receive messages, and is not full or locked.
* Keep each profile's valid information unique and internally consistent.

### Card

* Enter the cardholder name exactly as required by the card issuer.
* Select the correct card type.
* Enter the complete card number. The dashboard accepts 13–19 digits, but you must confirm that the number itself is correct.
* Enter the correct 3- or 4-digit CVV.
* Enter a valid expiration month from 01–12 and an expiration year that has not passed.
* Confirm the card is active, unlocked, and available for the intended purchase.

{% hint style="danger" %}
Card numbers are masked after they are saved. Check every digit before saving or importing because you cannot reveal the original full number later.
{% endhint %}

### Billing address

* Enter the billing name exactly as the card issuer expects it.
* Enter a working US phone number.
* Enter the complete US street address, city, state, and ZIP code.
* Make sure the billing address and ZIP code match the card issuer's records.

### Shipping address

* Use a real, deliverable recipient name and address.
* Enter the correct US phone number.
* Include the correct apartment, suite, unit, building, or other required Line 2 information.
* Confirm that the street, city, state, and ZIP code all describe the same US address.
* If shipping and billing are different, complete and verify both address blocks.

{% hint style="warning" %}
Never replace a real apartment, suite, or unit number with a generated value or delivery instruction. A profile can pass format validation and still be undeliverable.
{% endhint %}

## Use valid field formats

| Field                | Accepted format or check                                                 |
| -------------------- | ------------------------------------------------------------------------ |
| **US phone**         | 10 digits after an optional leading `1`                                  |
| **US ZIP**           | 5 digits or ZIP+4                                                        |
| **US state**         | A valid two-letter state code or full state name                         |
| **Card number**      | 13–19 digits; confirm the actual number is correct                       |
| **CVV**              | 3 or 4 digits                                                            |
| **Expiration month** | `01` through `12`                                                        |
| **Expiration year**  | A current or future year                                                 |
| **Email**            | One address with a valid username and domain, such as `name@example.com` |

## Verify accounts before a run

For retailers marked **Yes** in the account table:

1. Add the retailer account in the [Accounts tab](https://github.com/bigboii-cmd/discord-bot-webapp/tree/main/docs/guides/%7B%7Bsite_url_full%7D%7D/dashboard/profiles?tab=accounts/README.md).
2. Use the same email on the retailer account and checkout profile so the dashboard can link them.
3. Sign in directly at the retailer and confirm the password still works.
4. Complete any email, phone, CAPTCHA, two-factor authentication, or membership verification.
5. Confirm the account is not locked, suspended, or waiting for a password reset.
6. Check any retailer-specific requirement, such as Walmart+ or a warehouse-club membership, before the release.

## Double-check before uploading

Before importing a CSV or saving a bulk edit:

1. Confirm every row has the intended retailer and a unique profile name.
2. Confirm every required-account retailer has a working account with the same email.
3. Recheck the card number, CVV, expiration, cardholder name, and billing address against the card.
4. Recheck both phone numbers and confirm they can receive calls or messages when verification is required.
5. Look up the address and verify the US street, city, state, ZIP code, and real unit.
6. Confirm the email inbox works and can receive retailer confirmations.
7. Fix every validation warning shown by the import review or checkout-profile list.
8. Select the correct retailer before using Auto Jig, then preview every generated change.
9. Make sure only the profiles you intend to export are marked active.
10. Spot-check several profiles after import before using a bulk export.

{% hint style="success" %}
A profile is ready only when its card, account, email, phone, billing address, and shipping address have all been checked—not merely when the upload finishes.
{% endhint %}

## Use the current optimized setup

| Retailer           | Payment guidance                                              | Address guidance                                                | Starting amount                             |
| ------------------ | ------------------------------------------------------------- | --------------------------------------------------------------- | ------------------------------------------- |
| **Target**         | Hard cards                                                    | No jigs                                                         | 5–6 per address                             |
| **Walmart**        | Hard cards or VCCs; Amex VCCs are common                      | Save clean profiles; use Line 1 and Line 2 Auto Jig when needed | 1,000 profiles; estimated 3–4 checkouts     |
| **Pokemon Center** | Employee hard cards first; Capital One or Robinhood VCCs next | Intermix light Line 1, Line 2, and both-line variations         | 125 profiles across as many valid addresses |

{% hint style="danger" %}
Do not use Amex VCCs for Pokemon Center under the current guidance.
{% endhint %}

## Before every run

1. Confirm that the profile contains the recipient's real name, deliverable address, and correct apartment or unit number.
2. Confirm that billing information matches the card issuer's requirements.
3. Select the correct retailer so the saved retailer-specific Auto Jig rules load.
4. Preview every bulk change before applying it.
5. Check [Task Limits](https://github.com/bigboii-cmd/discord-bot-webapp/tree/main/docs/guides/%7B%7Bsite_url_full%7D%7D/dashboard/task-limits/README.md) and stay within the current profile and account limits.
6. Stop and investigate repeated declines, cancellations, account locks, or address validation errors.

## Finish with the guide for your retailer

* [Pokemon Center](/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide/pokemon-center.md)
* [Walmart](/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide/walmart.md)
* [Target](/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide/target.md)
* [Sam's Club and Costco](/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide/warehouse-clubs.md)
* [Other supported retailers](/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide/other-retailers.md)
* [Amazon account guidance](/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide/amazon.md)


---

# 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://aphrowuu-aco.gitbook.io/aphrowuu-aco-docs/retailer-guides/retailer-profile-guide.md?ask=<question>&goal=<endgoal>
```

`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.