> 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/amazonv3.md). # AmazonV3
AmazonV3 is an account-based module designed for Amazon restocks, timed releases, invite-only products, household goods, collectibles, electronics, and other products that may appear without warning. Amazon account quality is extremely important. A smaller number of established, properly prepared accounts will generally perform better than a large number of new or poorly maintained accounts. *** ## **Amazon Video Guide** Watch the complete Amazon setup `New video guide coming soon...` *** ## Quick Start: Recommended Setup This is the standard Amazon setup. Use **Special Mode** for most random restocks, long-running coverage and products where you do not have a verified Offer ID. Use **Fast Mode** for timed or low-stock releases when both the SKU and verified Offer ID are available. Fast Mode supports Single Item and Multi Item setups. You may run **Fast and Special at the same time**. Make sure every task is configured correctly for its selected mode and avoid creating unnecessary duplicate coverage. ### 1. Prepare Your Amazon Accounts Account quality is one of the most important parts of an Amazon setup. Before creating tasks: * Use established Amazon accounts when possible. * Confirm each account’s email and password. * Save a valid default shipping address. * Save a valid default payment method. * Remove expired payment methods and outdated addresses. * Enable Amazon two-step verification. * Install a compatible authenticator application. * Obtain the Authenticator Key for each account. * Keep normal purchasing activity on important accounts. * Test each account using an ordinary in-stock product. * Confirm the correct region and account type. * Keep Prime enabled if the account has a Prime membership. A smaller group of established, properly maintained accounts will generally perform better than a large group of new or unstable accounts. ### 2. Add Your Amazon Sessions Open: ``` Identities → Sessions → Amazon ``` Add each account using: * **Region:** Region matching the Amazon account * **Email:** Amazon account email * **Password:** Current account password * **Account Type:** Personal or Business * **Authenticator Key:** Secret key obtained from Amazon’s two-step verification setup * **CVV:** CVV for the default payment method when requested * **Login Method:** Request Login * **Login Proxy:** One clean, stable ISP proxy dedicated to that account **Request Login** is the recommended login method. Use **Browser Login** only when Request Login repeatedly fails or Amazon requires additional browser interaction. After creating the sessions: * Confirm each Authenticator Key is correct. * Confirm each account has the correct region and account type. * Test the sessions before building a large task setup. * Avoid logging into the same account from multiple locations or IP addresses simultaneously. Treat every Authenticator Key like a password and store it securely. ### 3. Prepare Your Proxies ISP proxies are the recommended starting point for Amazon. Create separate proxy groups for: * Session login * Monitoring * Special and Fast checkout tasks Recommended proxy practices: * Assign one stable ISP login proxy to each Amazon account. * Keep an account’s login and checkout locations consistent. * Avoid rotating an account’s login IP. * Avoid sharing one login proxy across many accounts. * Avoid using the same small proxy pool for monitoring and checkout. * Use multiple proxy providers or pools. * Test every important proxy group before a release. Datacenter proxies may also work when they are clean and stable. Residential proxies are generally not recommended for continuous Amazon monitoring because they may rotate IPs and consume significant data. ### 4. Create Your Amazon Tag Group Special Mode uses an Amazon Tag Group to cover one or more products. Open: ``` Tags → Create Tag Group → Manage SKUs ``` Add products using: ``` SKU;Title;MaxPrice ``` Example: ``` B07RQ1HNFQ;Product Name;27.00 ``` The Max Price is the maximum price for one unit before tax. Use a focused list containing only products you actually want to purchase. Every SKU inside the Tag Group should have a corresponding Monitor task. ### 5. Create Your Monitor Tasks Monitor tasks detect Amazon inventory and ping Special tasks. Recommended starting setup: * **Mode:** Monitor * **Monitor Proxy:** Dedicated ISP monitor proxies * **SKU:** Amazon SKU or ASIN * **Offer ID:** Required only when using the Fast Monitoring Method * **Max Price:** Maximum acceptable price for one unit * **ZIP Code:** Blank unless the selected region or flow requires it * **Region:** Region matching the Amazon listing * **Monitoring Method:** Scrape unless a verified Offer ID is available and Fast monitoring is specifically desired * **Captcha Provider:** Configured provider when solving Captchas * **Should Solve Captcha:** On when using a configured provider * **Amazon Warehouse Deals:** Off unless used intentionally * **Amazon Third Party:** Off unless used intentionally * **Task Count:** `1–3` Monitor tasks per SKU #### Choosing a Monitoring Method Use **Scrape** when: * You do not have a verified Offer ID. * You want the Monitor to use Max Price. * You are monitoring ordinary or random restocks. Use **Fast** when: * You have a verified Offer ID. * You want to monitor an exact Amazon offer. * Current drop instructions recommend Fast monitoring. Fast monitoring requires an Offer ID and ignores Max Price when selecting the offer. Use **Business** only with the appropriate Amazon Business account setup. For Monitoring Delay, follow the current Stellar or drop-specific recommendation. Increase the delay if tasks encounter rate limits, antibot responses, or proxy bans. ### 6. Create Your Special Tasks Special Mode is recommended for most Amazon restocks. Use Special Mode for: * Random restocks * Long-running coverage * Multiple products * Prime and non-Prime accounts * Monitor-triggered checkout Recommended starting setup: * **Mode:** Special * **Checkout Proxy:** Clean, stable ISP proxy * **Input List:** Amazon Tag Group * **Delay:** Use the current tested or drop-specific recommendation * **Product Qty:** Follow the product-specific purchase limit * **Session:** Prepared Amazon session * **Captcha Provider:** Configured provider; CapSolver is a recommended starting option * **Cart Attempts:** Leave at the current default unless newer instructions recommend another value * **Checkout Attempts:** Leave at the current default unless newer instructions recommend another value * **Shipping Speed:** Leave blank when the account has Prime * **Check Quantity Limit:** On for a single-SKU setup; off for a multi-product Tag Group * **Should Solve Captcha:** On when using a configured Captcha provider * **Skip 3DS:** Off unless you intentionally accept the additional payment risk * **Endless Mode:** Off * **Task Count:** One well-configured Special task per Amazon account is normally sufficient Special Mode normally does not require an Offer ID because Monitor tasks detect inventory and ping the Special task. ### 7. Configure Fast Mode When Appropriate Fast Mode is intended for timed, low-stock or actively releasing products when the correct SKU and Offer ID are available. Both the **SKU and Offer ID are required** for Fast Mode, regardless of whether you use Single Item or Multi Item. #### Single Item Setup Leave **Multi Item** disabled when running one product. Recommended starting setup: * **Mode:** Fast * **Multi Item:** Off * **Checkout Proxy:** Clean, dedicated ISP proxy * **SKU:** Confirmed Amazon SKU or ASIN * **Offer ID:** Verified Offer ID for the intended offer * **Delay:** `1000` milliseconds or higher * **Product Qty:** Follow the confirmed product limit * **Max Price:** Maximum acceptable price for one unit before tax * **Session:** Prepared Amazon session * **Endless Mode:** Off #### Multi Item Setup Enable **Multi Item** when you want one Fast task to attempt multiple products. Enter each product using this format: `SKU:OID:QTY:MAXPRICE` Example: `B07RQ1HNFQ:OFFERID123:1:27.00` Each entry must contain: * **SKU:** Amazon SKU or ASIN * **OID:** Verified Amazon Offer ID * **QTY:** Desired quantity * **MAXPRICE:** Maximum acceptable price for one unit before tax Both the SKU and Offer ID are required for every item. Amazon must process each product individually, so adding more products makes the task slower. We recommend limiting each Multi Item task to approximately **3–5 products**. Only add products that are actually expected to release. Do not load the task with large lists of unrelated or outdated products. #### Important Fast Mode Notes Fast Mode: * Does not require a Monitor task. * Does not require Captcha solving. * Supports Single Item and Multi Item setups. * Requires a valid SKU and Offer ID for every product. * Currently supports the United States and United Kingdom. * Has a current limit of approximately 20 Fast tasks per Stellar instance. You may run **Fast and Special at the same time**. Avoid creating unnecessary duplicate tasks or excessive Fast coverage. More products and tasks do not automatically create a better setup and may increase rate limits or slow processing. ### 8. Start Your Tasks #### Random Restocks For continuous or random restocks: 1. Confirm that the Amazon sessions are signed in. 2. Start the Monitor tasks. 3. Start the Special tasks. 4. Confirm that every SKU in the Tag Group has an active Monitor. 5. Leave the Special tasks waiting for Monitor pings. 6. Keep the computer or server online. 7. Monitor account, proxy, and Captcha-provider status. #### Known Releases Before a scheduled release: 1. Confirm the SKU, Max Price, region, and product quantity. 2. Confirm any required Offer ID. 3. Test the Amazon sessions. 4. Start Monitor tasks before the release. 5. Start Special tasks and confirm they are waiting for Monitor pings. 6. Start Single Item or Multi Item Fast tasks near the confirmed release time when Fast Mode is being used. Confirm that every Fast item contains the correct SKU, Offer ID, quantity and Max Price. 7. Fast and Special may run at the same time. Confirm both setups are properly configured before the release. 8. Keep tasks running through additional inventory waves unless Stellar staff recommends stopping them. Do not run Fast tasks unnecessarily for long periods. ### 9. Confirm Your Setup Is Ready Before leaving the setup running, confirm: * StellarAIO is updated. * Every Amazon account has a valid default address and payment method. * Every Amazon session is signed in. * Authenticator Keys are correct. * Each account uses a stable login proxy. * Monitor and checkout proxies are separated. * The Amazon Tag Group contains the correct products and Max Prices. * Every Special-mode SKU has an active Monitor. * Fast tasks use a verified Offer ID. * Every Fast item has a confirmed SKU and Offer ID. * Multi Item entries follow `SKU:OID:QTY:MAXPRICE`. * Multi Item tasks contain no more than approximately 3–5 actively releasing products. * Fast and Special tasks do not contain unnecessary duplicate coverage. * Endless Mode is disabled. * Captcha providers are configured where needed. * Accounts, sessions, and proxies have been tested. ### 10. During the Release During an Amazon restock: * Leave correctly progressing Monitor and Special tasks running. * Confirm that Special tasks are receiving Monitor pings. * Watch for Captchas, reauthentication, quantity-limit, and rate-limit messages. * Verify every checkout inside the Amazon account before treating it as confirmed. * Stop monitoring a SKU after the account reaches its purchase limit. * Keep other SKUs in the Tag Group running when they remain eligible. * Follow newer Stellar announcements and drop-specific instructions. If a Fast task becomes rate-limited: 1. Stop the affected task. 2. Confirm only one Fast task was using the account. 3. Confirm the same SKU was not also running in Special. 4. Check the account’s dedicated proxy. 5. Allow the account to rest for at least two hours. 6. Restart using a delay of `1000` milliseconds or higher. Drop-specific announcements always override this general setup. *** ## Preliminary Checklist Before creating Amazon tasks, confirm that you have completed the following: * [ ] Updated StellarAIO to the latest version * [ ] Prepared established Amazon accounts * [ ] Confirmed every account’s email and password * [ ] Saved a valid default shipping address * [ ] Saved a valid default payment method * [ ] Removed outdated addresses and expired payment methods * [ ] Enabled Amazon two-step verification * [ ] Installed an authenticator application * [ ] Copied the Amazon Authenticator Key for each account * [ ] Added each account under **Identities → Sessions** * [ ] Selected **Request Login** * [ ] Assigned a clean, dedicated ISP login proxy to each account * [ ] Added separate ISP proxy groups for monitoring and checkout * [ ] Created an Amazon Tag Group for Special mode * [ ] Obtained the correct SKUs and Offer IDs from a trusted source * [ ] Configured a supported Captcha provider if needed * [ ] Tested each account on an ordinary in-stock product * [ ] Enabled cook group notifications for Amazon restocks and Offer IDs *** ## Amazon Account Preparation ### Account Quality Avoid using a brand-new Amazon account immediately for an important release. A recommended warming process is: 1. Create or obtain the Amazon account. 2. Add valid personal information. 3. Save a default address and payment method. 4. Manually order an ordinary product. 5. Allow the order to ship successfully. 6. Complete a normal test order through Stellar. 7. Allow that order to ship before using the account heavily. Books, household goods, and other ordinary products are useful for testing account health. Do not create an account and leave it unused for an extended period before suddenly using it for automated high-demand orders. ### Maintain Real Account Activity Amazon accounts with normal purchasing history generally perform better than accounts used exclusively for automated releases. Regularly review each account and remove: * Expired cards * Old payment methods * Incorrect addresses * Duplicate addresses * Outdated personal information Keep the preferred address and payment method set as the account defaults. ### Payment Methods Using a different payment method for each account is recommended. You should also retain access to payment statements. Amazon may occasionally request documentation showing a transaction or verifying account ownership. If the name associated with the payment method differs from the Amazon account, correct it when possible. ### Addresses Use accurate, deliverable addresses. Do not make unnecessary alterations to legitimate addresses. Amazon is primarily concerned with account security, payment risk, and suspicious activity. Multiple legitimate accounts may use the same household address, but there is no guaranteed safe account-to-address ratio. Account quality and consistent information remain important. ### Prime Membership Amazon Prime is not required. Free Amazon accounts can use Stellar. Prime membership may affect available shipping-speed options. *** ## Proxies and Servers ### Recommended Proxy Type ISP proxies are recommended for Amazon. Benefits include: * Stable session IPs * Low latency * No rotating residential data usage * Better support for tasks running continuously * Fewer login changes Datacenter proxies may also work when they are clean and stable. Residential proxies are generally not recommended for continuous Amazon monitoring because they can consume significant data and rotate IPs. ### One Stable IP Per Account Assign one clean, dedicated ISP login proxy to each Amazon session. Avoid: * Sharing one login IP across many accounts * Rotating an account’s login IP * Logging into one account from several locations simultaneously * Running the same account through unrelated checkout proxies A stable account and proxy pairing can reduce repeated logins and session challenges. Logging into or checking out with one Amazon account through multiple IPs at the same time can trigger reauthentication or account restrictions. ### Separate Monitor and Checkout Proxies Create separate proxy groups for: * **Monitoring** * **Checkout and Fast tasks** * **Session login** This prevents constant monitoring traffic from affecting your checkout or login proxies. Use multiple proxy providers and pools instead of relying entirely on one provider. ### Running Locally or on a Server Amazon can run locally, but a reliable server is recommended for members who want continuous monitoring and restock coverage. When selecting a server: * Choose a location close to the Amazon region you are targeting. * Aim for latency below `50 ms`. * Lower latency, such as below `20 ms`, is preferable when available. * Use a stable Windows environment. * Test the server, proxies, sessions, and tasks before an important release. Speed matters, but clean accounts and stable proxies remain more important than using an unnecessarily large setup. *** ## Amazon Sessions and Login ### Adding an Amazon Session 1. Open **Identities** in Stellar. 2. Open the **Sessions** section.
3. Select **Add Session**. 4. Choose Amazon. 5. Enter the required account information.
6. Save the session. 7. Test the session before creating a large task setup. Amazon sessions may include: * **Session Name:** Organizational name for the account * **Region:** Amazon region assigned to the account * **Email:** Amazon account email * **Password:** Amazon account password * **Account Type:** Personal or Business * **Authenticator Key:** Secret key used to generate two-step verification codes * **CVV:** CVV for the default payment method * **Login Method:** Request Login or Browser Login * **Login Proxy:** Dedicated proxy used to maintain the account session ### Request Login (Recommended) Request Login uses the saved Amazon credentials and Authenticator Key without requiring a browser window. It is generally the fastest and most stable login method. ### Browser Login Browser Login opens a browser window and allows Stellar to complete the login flow. Use Browser Login when Request Login repeatedly fails or when Amazon requires additional browser interaction. Google Chrome must be installed for applicable browser-login flows. ### Account Type Select **Personal** or **Business** when one login has both account types connected. If the login only has one Amazon account type, the default selection is normally sufficient. This setting determines which linked account Stellar enters during login. It does not change the checkout process. *** ## Setting Up the Authenticator Key Request Login requires the Amazon Authenticator Key. ### Finding the Key 1. Sign into the Amazon account. 2. Open **Account.**
3. Open **Login & Security**.
4. Find **Two-Step Verification Settings**.
4. Select **Edit** or **Get Started**. 5. Choose **Authenticator App**. 6. Select **Can’t scan the barcode?**
7. Copy the displayed string of characters.
8. Save the key securely. 9. Add the account to your authenticator application. 10. Enter the generated code into Amazon to finish setup. 11. Paste the original Authenticator Key into the matching Stellar session.
Treat the Authenticator Key like a password. Anyone with the key may be able to generate valid login codes for the account. Google Authenticator is one supported option, but another compatible authenticator application may also work. *** ## Mass Importing Amazon Sessions Open: ``` Identities → Sessions → Mass Import Sessions ``` Use the following format
Supported region codes should match Stellar’s current Amazon region options. If the region is omitted, Stellar may default to the United States. Always test a small import before adding a large group of accounts. *** ## Offer ID Overview An **Offer ID**, also called an OID, identifies an exact Amazon offer, including the seller and listing configuration. Offer IDs are commonly provided by cook groups for timed or high-demand releases. Verify every Offer ID before running it. An incorrect Offer ID may target the wrong seller, listing, condition, or price. When an Offer ID is used, it takes priority over the Max Price field for selecting the offer. Do not rely on Max Price to protect against an incorrect Offer ID. Use the most recently confirmed Offer ID from a trusted source. ### When Offer IDs Are Required * **Fast mode:** Required * **Fast Monitoring Method:** Required * **Special mode:** Not normally required * **Scrape Monitoring Method:** Not required * **Invite mode:** Not required ### Direct SKU and Offer ID Format For a precise timed Special-mode release, the following format may be used: ``` SKU:OfferID ``` This bypasses the normal monitor-triggered workflow and directly attempts add to cart. Use this only for confirmed timed releases. It is not recommended for random restocks. Do not use `SKU:OfferID` in Monitor tasks. *** ## Creating an Amazon Tag Group Special mode uses the **Input List** field to select an Amazon Tag Group. ### Creating the Group 1. Open the **Tags** tab. 2. Create a new Tag Group. 3. Give it an identifiable name. Example: ``` Amazon ``` 4. Select **Manage SKUs**. 5. Add the products you want Special mode to cover. 6. Save the Tag Group. 7. Select it through Special mode’s Input List field. ### Product Format Use: ``` SKU;Title;MaxPrice ``` Example: ``` B07RQ1HNFQ;Product Name;27.00 ``` The Max Price represents the maximum price for **one unit before tax**, not the total price of the entire order. Use a focused list of products that you actively want to purchase. Every SKU inside the Special-mode list should also have an appropriate Monitor task. *** ## Supported Modes ### Special Mode Special is the recommended checkout mode for most Amazon restocks. Special mode: * Uses an Amazon Tag Group * Waits for Monitor pings * Can cover multiple SKUs * Does not normally require Offer IDs * Supports Prime and non-Prime accounts * Is suitable for long-running restock coverage Watch behavior is handled automatically by the current Special-mode flow.
### Fast Mode Fast Mode aggressively attempts checkout using an exact Amazon SKU and Offer ID. Fast Mode supports both **Single Item** and **Multi Item** setups. Fast Mode: * Requires a valid SKU and Offer ID for every product. * Does not require a Monitor task. * Does not require Captcha solving. * Is best suited for timed drops and low-stock releases. * Supports the United States and United Kingdom. * Has a current limit of approximately 20 Fast tasks per Stellar instance. * Can run at the same time as Special Mode. For Multi Item tasks, enable **Multi Item** and enter each product using: `SKU:OID:QTY:MAXPRICE` Because Amazon processes each item separately, adding more products slows the task. Limit Multi Item setups to approximately **3–5 products** and only include products that are actively releasing. Strictly run only one Fast task per Amazon account.
### Invite Mode Invite mode requests access to eligible Amazon Invite-Only products. Invite mode: * Supports multiple SKUs * Is intended for supported European and UK regions * Does not directly check out the product * May require Captcha handling Receiving an invitation is not guaranteed.
### Monitor Mode Monitor mode watches Amazon inventory and pings Special tasks. Monitor tasks do not place orders. You can create Monitor tasks manually or use **Bulk CSV List** to create many Monitor tasks efficiently.
*** ## Special Mode Breakdown ### Name Optional organizational name. ### Mode Select **Special** for monitor-triggered Amazon checkout tasks. ### Checkout Proxy Select a clean, dedicated ISP checkout proxy. Keep the account’s login and checkout locations consistent whenever possible. ### Input List Select the Amazon Tag Group containing the products you want this task to purchase. One Special task can cover multiple SKUs through the selected Tag Group. ### Delay Recommended starting point: ``` 1000 ``` Increase the delay if the task encounters rate limits or proxy-related errors. ### Product Qty Enter the quantity the task should attempt to purchase. Common Amazon limits are often three or five units, but limits vary by product and account. Confirm the current limit with your cook group. If the configured quantity exceeds the retailer limit, Amazon may reduce the order quantity or reject the attempt. ### Session Select the prepared Amazon account. One well-configured Special task per account is normally enough because its Tag Group can contain multiple products. ### Captcha Provider Select a provider configured in Stellar’s Settings. CapSolver is a recommended starting option. Other supported providers may include 2Captcha and CapMonster. The provider’s API key must be saved in Stellar before it can be selected successfully. ### Cart Attempts Controls how many add-to-cart attempts Stellar makes during the flow. Recommended starting value: ``` 10 ``` ### Checkout Attempts Controls how many checkout attempts Stellar makes after carting. Recommended starting value: ``` 15 ``` ### Shipping Speed Controls the delivery method selected during checkout. * **Blank:** Recommended when the account has Prime * **Fastest:** Prioritizes faster shipping and may incur additional charges * **Cheapest:** Prioritizes lower-cost or free shipping * **Random:** Allows the flow to select from available options Review the expected shipping cost before selecting a paid shipping method. ### Start Time and End Time Optional scheduling controls. The task must still be started for scheduled settings to take effect. ### Check Quantity Limit When enabled, the task stops or changes behavior after Amazon reports that the account has reached the product’s quantity limit. Recommended: * **Single-SKU setup:** On * **Tag Group with multiple products:** Off Disabling it for a Tag Group prevents one product’s limit from stopping coverage for every other product. ### Should Solve Captcha * **On:** Uses the selected Captcha provider when one appears. * **Off:** The task may rotate proxies instead. Enable this when you have a configured provider and want the task to solve detected Captchas. ### Skip 3DS * **On:** Attempts to bypass or avoid the standard 3DS challenge. This may be faster but can increase payment risk or require later payment updates. * **Off:** Uses the normal checkout flow and may require manual approval. Use the current drop-specific recommendation for your region and payment method. ### Use TopCashback Uses the TopCashback integration configured in Stellar. ### Endless Mode Restarts the task after a successful checkout. Recommended: ``` Off ``` Restart successful Amazon tasks manually when you intentionally want another order. ### Endless Limit Sets the maximum number of successful orders when Endless Mode is enabled. Leave it blank when Endless Mode is off. ### Task Qty The Qty field at the bottom determines how many copies of the configured task Stellar creates. This is separate from Product Qty. *** ## Fast Mode Breakdown ### Name Optional organizational name for the task. Use a name that identifies the release, account or product group. ### Mode Select **Fast** for aggressive checkout attempts using exact Offer IDs. ### Multi Item Leave this disabled when running one product. Enable it when you want the task to attempt multiple products. Multi Item entries must use: `SKU:OID:QTY:MAXPRICE` Both SKU and Offer ID are required for every entry. ### Checkout Proxy Use a clean, low-latency ISP proxy. Keep the account’s login and checkout locations as consistent as possible. ### SKU Required for Single Item Fast tasks. Enter the Amazon SKU or ASIN for the product. Example: `B07RQ1HNFQ` ### Offer ID Required for Single Item Fast tasks. Enter the exact Offer ID for the intended seller, listing, condition and price. The SKU and Offer ID must correspond to the same product and region. ### Multi Item Input When Multi Item is enabled, add each product using: `SKU:OID:QTY:MAXPRICE` Example: `B07RQ1HNFQ:OFFERID123:1:27.00` The values represent: * `SKU` — Amazon SKU or ASIN * `OID` — Verified Offer ID * `QTY` — Desired quantity * `MAXPRICE` — Maximum acceptable price for one unit before tax We recommend no more than approximately **3–5 products per Multi Item task**. More products make the task slower because of how Amazon processes each item. Only include products that are expected to release. Do not add hundreds of old or unrelated products. ### Delay Recommended minimum: `1000` Do not run below `1000` milliseconds unless newer drop-specific instructions explicitly recommend it. Lower delays can quickly rate-limit the account. ### Product Qty For Single Item tasks, enter the desired purchase quantity. For Multi Item tasks, quantity is included in each entry as the `QTY` value. Always follow the product’s current purchase limit. ### Max Price For Single Item tasks, enter the maximum acceptable price for one unit before tax. For Multi Item tasks, Max Price is included in each entry as the `MAXPRICE` value. The Offer ID identifies the exact offer, so always verify that the Offer ID belongs to the intended seller, listing, condition and price. ### Session Select the prepared Amazon session assigned to the task. Avoid excessive Fast tasks on the same account. Aggressive or duplicate checkout traffic can cause rate limits. ### Start Time and End Time Optional scheduling controls. A scheduled Start Time does not replace reviewing the task before the release. Confirm all SKUs, Offer IDs, quantities and Max Prices before starting. ### Endless Mode Recommended: **Off** Fast Mode already sends aggressive checkout requests. Endless Mode can significantly increase account risk. ### Endless Limit Only applies when Endless Mode is enabled. ### Task Qty Number of Fast tasks to create. Make sure every task uses an eligible Amazon session and properly tested proxy. There is currently a limit of approximately 20 Fast tasks per Stellar instance. Fast and Special tasks may run at the same time. *** ## Invite Mode Breakdown ### Name Optional organizational name. ### Mode Select **Invite** to request access to supported Amazon Invite-Only products. ### Checkout Proxy Select a clean ISP proxy. ### SKU or SKUs Enter one or more eligible Amazon SKUs. Separate multiple SKUs using the format supported by the current task interface. ### Delay Recommended starting point: ``` 3000 ``` ### Session Select the Amazon account requesting the invitation. ### ZIP Code Optional location information. Use it when required by the Amazon region or product. ZIP Code is more commonly needed in supported UK or European flows. ### Captcha Provider Select a configured provider if the invite request may encounter a Captcha. ### Should Solve Captcha Enable this when using the selected Captcha provider. ### Start Time, End Time and Task Qty Optional scheduling fields and the number of Invite tasks to create. *** ## Monitor Mode Breakdown ### Name Optional organizational name. ### Mode Select **Monitor** to watch Amazon inventory. ### Monitor Proxy Select a dedicated ISP monitor group. Avoid using the same small proxy group for both monitoring and checkout. ### Use Bulk CSV List Enable this option when creating Monitor tasks from a prepared CSV list. This is useful when monitoring many individual SKUs and prevents the need to create every task manually. Use the current Amazon monitor CSV template provided by Stellar. ### SKU Enter the Amazon SKU or ASIN to monitor. ### Offer ID Required for the Fast Monitoring Method. Leave it blank when using Scrape monitoring unless current instructions specifically require it. ### Max Price Enter the maximum acceptable price for one unit. Max Price is used by Scrape monitoring. The Fast method relies on the Offer ID. ### ZIP Code Optional location used when inventory or availability depends on a postal area. Leave it blank when it is not required. ### Monitoring Delay Recommended starting point: ``` 5000 ``` Advanced setups with healthy proxies and low latency may test delays around `3800`, but increase the delay when encountering rate limits, antibot responses, or proxy bans. ### Region Select the Amazon region where the product is listed. ### Monitoring Method #### Scrape * Does not require an Offer ID * Reads Amazon’s frontend product availability * Uses Max Price * May be more vulnerable to soft proxy bans * Recommended when no reliable Offer ID is available #### Fast * Requires an Offer ID * Uses the exact offer * Ignores Max Price for offer selection * Provides faster monitoring * May be less dependent on account cookies #### Business * Intended for Amazon Business accounts * Uses Business-specific availability and pricing * Select only when monitoring through an appropriate Business account setup ### Captcha Provider Select a configured provider if you want monitor tasks to solve Captchas. If left blank, the task may rotate proxies instead. ### Reset Delay Optional delay before the Monitor resets after a trigger. ### Start Time and End Time Optional scheduling controls. ### Should Solve Captcha Enable this when using a configured Captcha provider. ### Amazon Warehouse Deals Enable this only if you intentionally want the Monitor to include Amazon Warehouse offers. Warehouse items may have different conditions from new products. ### Amazon Third Party Enable this only if third-party sellers are acceptable. Third-party offers may have different sellers, conditions, prices, shipping costs, and return policies. Use a verified Offer ID or appropriate price protection. ### Task Qty Number of Monitor tasks to create. A practical starting point is `1–3` Monitor tasks per SKU. Scale based on proxy quality and the importance of the product. *** ## Scaling Your Amazon Setup The recommended starting task counts are listed in **Quick Start: Recommended Setup**. When scaling Amazon, prioritize account quality over account quantity. Before adding more accounts or tasks, confirm that you have: * Established Amazon accounts * Valid default addresses and payment methods * Correct Authenticator Keys * One stable login proxy per account * Separate Monitor and checkout proxy pools * Enough clean ISP proxies * Reliable Captcha-solving capacity * A computer or server capable of running continuously * A tested setup that works on an ordinary product A smaller setup with established accounts, stable proxies, consistent information, and successful order history will generally perform better than a large setup of fresh or unstable accounts. Add Monitor redundancy only when you have enough clean ISP proxies to support the additional traffic. Do not increase your Fast task count by assigning multiple Fast tasks to the same Amazon account. *** ## Quantity and Purchase Limits Amazon purchase limits vary by product, account, and release. Before selecting Product Qty: * Check the product listing. * Confirm the current limit with your cook group. * Review any drop-specific Stellar instructions. * Consider the account’s previous purchases of the same SKU. If the entered quantity exceeds Amazon’s limit, Amazon may reduce the quantity, reject the checkout, or report that the account has reached its maximum quantity. If an account reaches its limit for one SKU: * Stop that SKU’s Monitor for the affected account. * Do not enable Endless Mode. * Continue monitoring other eligible SKUs in the Tag Group. * Use another eligible account only when permitted. Max Price always represents the price of one unit before tax, even when Product Qty is greater than one. *** ## Latest Prep Call Notes ### Current Amazon Guidance - Reviewed July 31, 2026 * Warm new accounts with ordinary purchases before important releases. * Prioritize account quality over account quantity. * Keep default payment and shipping information current. * Use a unique payment method when possible. * Assign one stable ISP login proxy to each account. * Keep monitor and checkout proxy pools separate. * Use Special mode for long-running, multi-product coverage. * Use Fast mode for timed or low-stock releases. * Run only one Fast task per account. * Do not target the same SKU in Fast and Special simultaneously. * Use `1000 ms` as the minimum Fast-mode delay. * Run `1–3` Monitor tasks per SKU. * Use a verified Offer ID for Fast mode. * Keep Endless Mode disabled. * Test questionable accounts with an ordinary product before assuming they are permanently restricted. *** ## Latest Prep Call Recording The latest Amazon prep call: {% embed url="" %} Prep-call recommendations may apply to a specific release. Follow the newest interface, written guide, and Stellar announcements when instructions conflict. *** ## Common Errors and Fixes ### Amazon Antibot — Rotating Proxy **Cause:** Amazon is flagging the account or proxy. **Fix:** * Allow the task to rotate if configured. * Try another clean proxy. * Increase the task delay. * Confirm the account uses a stable login IP. * Reduce unnecessary tasks. ### Captcha Detected — Rotating Proxy **Cause:** Amazon presented a Captcha and no solving flow completed it. **Fix:** * Try another proxy group. * Select a configured Captcha provider. * Enable Should Solve Captcha. * Check whether the account is soft-banned. * Allow a restricted account to rest before retrying. ### Waiting for Monitor **Cause:** The Special task is waiting for a Monitor or supported external stock ping. **Fix:** * Leave the task running. * Confirm a Monitor exists for each SKU in the Special Input List. * Confirm the Monitor and Special tasks use matching SKUs. * Confirm the Monitor has not stopped or become rate-limited. ### Placing Special Order or Waiting for Monitor Loop **Possible cause:** Amazon is requiring the account’s CVV again or the site is not accepting the checkout state. **Fix:** * Sign into the Amazon account manually. * Re-enter the CVV for the default payment method. * Confirm the default address and payment method. * Restart the affected task. ### Fast Mode Rate Limit Possible causes: * Delay below `1000` milliseconds * Too many aggressive requests * Excessive Fast tasks using the same account * Unnecessary duplicate product coverage * Poor, blocked or heavily shared proxy * Account already restricted * An oversized Multi Item list Fix: 1. Stop the affected task. 2. Confirm the delay is `1000` milliseconds or higher. 3. Reduce unnecessary duplicate tasks. 4. If using Multi Item, reduce the list to approximately 3–5 actively releasing products. 5. Confirm every SKU and Offer ID is valid. 6. Use a clean, dedicated ISP proxy. 7. Allow the account to rest before trying again. Fast and Special may run at the same time, but every additional request increases account traffic. Keep the setup focused and avoid unnecessary duplicate coverage. ### Ghost Checkout **What it means:** Stellar records a checkout, but no confirmed order appears in the Amazon account. **Fix:** * Check the account’s Orders section before assuming success. * Reset the account password if the problem repeats. * Remove outdated addresses. * Re-add or verify the default payment method. * Retest the account with an ordinary product. ### 401 Error **Cause:** The Amazon session is no longer authenticated. **Fix:** * Open Identities. * Clear the affected session’s cookies. * Confirm the account password and Authenticator Key. * Log the account in again. * Check the dedicated login proxy. ### CSRF Token Error **Likely cause:** Proxy or monitoring-session problem. **Fix:** * Test the Monitor proxy group. * Replace blocked proxies. * Increase the Monitoring Delay. * Restart only the affected Monitor tasks. ### OOS, Missing Address or Missing Payment in Fast Mode This message may appear when the product goes out of stock during the checkout request. It does not always mean the account is actually missing information. **Fix:** * Confirm the address and payment method once. * If both are present, allow the task to continue. * Check whether the item is still available. ### Getting Rendered Addresses **Possible causes:** Proxy problem or unnecessary ZIP Code setting. **Fix:** * Change the checkout proxy. * Remove ZIP Code when it is not required. * Confirm the account’s default shipping address. * ZIP Code is more commonly required for UK flows than US flows. ### Adding to Cart 302 **Cause:** The product likely went out of stock during checkout. **Fix:** * Allow the task to retry. * Restart the affected task if it remains stuck. * Confirm the Monitor is still reporting valid inventory. ### Failed to Find Offer ID **Possible causes:** * Incorrect or expired Offer ID * Wrong product or region * Offer no longer available * Temporary module issue **Fix:** * Obtain a newly confirmed Offer ID. * Confirm the product region. * Verify the seller and offer. * Use Special mode with Scrape monitoring if an Offer ID is unavailable. ### Fast Multi Item Error Possible causes: * An entry does not follow `SKU:OID:QTY:MAXPRICE`. * A SKU or Offer ID is missing. * The Offer ID does not match the SKU or region. * Quantity or Max Price is missing or incorrectly formatted. * Too many products were added. * One of the offers is no longer available. * The task encountered an unhandled Multi Item edge case. Fix: 1. Confirm every entry contains all four required values. 2. Confirm every SKU and Offer ID is correct. 3. Confirm the quantity and Max Price are valid. 4. Remove unrelated or inactive products. 5. Reduce the task to approximately 3–5 products. 6. Recreate or restart only the affected task. If the format is correct and the error continues, report the task status and error details in the Stellar **Bugs** channel. Multi Item required major changes to the Fast flow, so some edge cases may still need to be reported. ### Monitor Reports In Stock but Checkout Reports Out of Stock Amazon’s frontend and checkout inventory can update at different times. This is normal during fast-moving restocks. Leave the Monitor running and allow later inventory waves to trigger another attempt. ### Maximum Quantity Reached The account has reached Amazon’s purchase limit for that SKU. **Fix:** * Stop that SKU’s Monitor for the affected account. * Do not use Endless Mode. * Use another eligible account if allowed. * Continue monitoring other SKUs in the Tag Group. ### Frequent Re-Login **Possible causes:** * Rotating session proxy * Shared login IP * Multiple tasks using different IPs * Poor-quality proxy * Incorrect Authenticator Key **Fix:** * Assign one clean ISP login proxy to the account. * Stop rotating the session IP. * Confirm the Authenticator Key. * Avoid simultaneous logins from several locations. * Use Request Login after correcting the proxy setup. --- # 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/amazonv3.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.