Best AI prompts for Amazon inventory and FBA restock
These are copy-paste AI prompts for Amazon inventory and FBA restock, drawn from 46 of the 53 sourced cases on this site. First are all 6 prompts the original sources published, quoted word for word. Then come 40 starter prompts we wrote, clearly labeled, so you can try the same jobs: forecasting and restock, stock levels and storage fees, inbound shipments, and buy costs. They plan, track or query inventory; none of them place a supplier order or create an FBA shipment on their own.
Replace anything in [brackets]. Don't let a prompt place a supplier order or create an FBA shipment until you've checked the output.
Prompts published by the original sources
These 6 prompts were published by the people or companies in the cases. They are labeled From the source. The wording is unchanged, including any uneven phrasing. Rights stay with the original authors; see the license.
Ask Gemini about sales by ASIN, stock cover, return reasons and fees without exporting CSVs
From the source. Copy this prompt as published; replace anything in [brackets].
Which SKUs have afn-fulfillable-quantity below 30 days of average daily units ordered?
Credit: Windsor.ai, Vendor docs, Oct 16, 2026. Original source · Case on this site.
Tools named in the case: Gemini, Windsor.ai.
Result (per source, vendor claim): Vendor page only, with no reported results. It says data can take about 10 minutes to appear after connecting, and that listing updates are accepted for processing by Amazon, not live immediately.
From the tool's vendor, not independently tested.
Worth knowing: This is the vendor's own product page, not a seller's reported result. Example numbers on the page are illustrations, not results. One source is free; combining sources is $19 or $99/month, and Gemini Enterprise is billed separately by Google.
See units on hand and sell-through across FBA, AWD and a 3PL in one place
From the source. Copy this prompt as published; replace anything in [brackets].
Here's the raw JSON from the FBA /fba/inventory/v1/summaries endpoint (pasted below). Write an ingest script that upserts sellerSku, asin, and the fulfillable/inbound quantities into a fba_inventory table, paginating on nextToken, capped at 20 pages. Never overwrite the cost column on the product table — COGS is entered manually and must survive a refresh.
Credit: John Aspinall (Aspi), Blog post, Jul 2, 2026. Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, agency-reported): Every source ran cleanly but totals were still wrong because SKUs didn't join, until he measured join coverage and built a SKU-to-ASIN crosswalk with normalization and a list of orphans. A 90-minute weekly manual reconciliation became a refresh that completes in a few minutes, and he estimates Claude Code turned a week of work into two evenings plus a few dollars of usage.
Reported by an agency about its own client work, not independently verified.
Worth knowing: An agency build log. No model runs at refresh time: the AI built the pipeline and the pipeline is deterministic, which is what you want for inventory numbers.
See which FBA SKUs will run out before their inbound shipments land
From the source. Copy this prompt as published; replace anything in [brackets].
Which of my FBA SKUs are at risk of stocking out in the US? Use Amazon's planning numbers where you can, rank by days of cover, and check whether my inbound shipments land before each at-risk SKU runs out.
Credit: Kuudo, Vendor docs, Not dated on the page (checked Nov 13, 2026). Original source · Case on this site.
Tools named in the case: Kuudo.
Result (per source, vendor claim): These are vendor docs with no customer results. The output is a days-of-cover table with the data source named for each row. Estimates are labelled as estimates, and 'healthy is an answer' when nothing is at risk.
From the tool's vendor, not independently tested.
Worth knowing: It is read-only: it never changes a price, listing or shipment, and it never suggests price as a lever. Kuudo was in beta access at the time.
Ask profit, margin and ACoS questions and update COGS from ChatGPT or Claude
From the source. Copy this prompt as published; replace anything in [brackets].
What's my profit by SKU this month?
Credit: SellerLegend, Vendor docs, Not dated on the page (checked Nov 13, 2026). Original source · Case on this site.
Tools named in the case: SellerLegend MCP.
Result (per source, vendor claim): This is a vendor feature page with example questions and no customer results.
From the tool's vendor, not independently tested.
Worth knowing: Updating COGS replaces that product's cost periods, so confirm carefully.
Set up Claude Code with your Seller Central data and build five starter tools
From the source. Copy this prompt as published; replace anything in [brackets].
Build me a Python script that connects to Amazon SP-API and pulls: yesterday's ordered revenue and units from the Sales API, any ASINs with fewer than 14 days of inventory from FBA Inventory Planning, and my top 5 campaigns by spend from yesterday using the Amazon Ads API. Output a clean summary to the terminal. Read my credentials from a .env file in the same directory.
Credit: Max Sigurdson-Scott & Rob Cosman (Selling From the Beach), Blog post, April 2026 (month shown on the guide). Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, self-reported): A guide, not a reported result. The authors put setup at about 30 minutes and the five builds at a few hours over the first month. They warn about the common mistakes: not saving the AWS secret key when it's shown, skipping self-authorization (no refresh token), and hitting SP-API rate limits.
Self-reported by the source, not independently verified.
Worth knowing: They note that review and organic rank data may need scraping or a third-party source, and that Claude Code should flag terms-of-service issues.
Plan labels, cartons and a pack list for each FBA inbound before the shipment is created
From the source. Copy this prompt as published; replace anything in [brackets].
Act as my Fulfillment Manager. Use only: - A PO and SKU Sheet - Any existing prep SOP - Restriction notes you paste from an export When to run: On each inbound you plan. Ask me first: - Partnered carrier versus self-ship. Give me: - A pack list and label map for the prep room. My approval is required for: - Creating the inbound shipment. Never: - Create the inbound from the pack list. Start with: Prep one inbound on paper with you, then save the pack.
Credit: Store Workbench, Workflow template, Not dated on the page (checked Oct 29, 2026). Original source · Case on this site.
Tools named in the case: Grok Bot.
Result (per source, template): Setup only, with no reported results. Creating the inbound shipment needs your approval, and the setup says never to create it from the pack list.
A published workflow template, not a reported result.
Worth knowing: This is a published workflow template, not a reported result: nobody in the source says what it did for their sales. Read the template's setup steps and test it on one account before you rely on it. The directory says it wrote the setup itself and used a third-party Amazon skills project only as a reference.
Starter prompts written by AI Agents for Sellers
The source in these cases did not publish its exact prompt. We wrote these starter prompts so you can try the same workflow. Each one is labeled Starter prompt written by AI Agents for Sellers, based on [the case]. Replace anything in [brackets]. These starter prompts are part of our own text and are covered by the CC BY 4.0 license on this page.
Forecasting, restock and reorder
Build a reorder plan from sales and stock, and get alerts before a SKU runs out.
Audit a reorder forecasting spreadsheet and rebuild the reorder logic
Starter prompt written by AI Agents for Sellers, based on Inventory Forecast Spreadsheet Audits with AI.
I'm attaching my inventory forecasting spreadsheet. Read every tab before answering. Report: (1) any formulas producing impossible values (negative or blank forecasts), (2) vendors or SKUs with missing lead times, (3) where the reorder point = buffer + lead-time demand is broken, (4) tabs that look copied forward with inconsistent numbers, (5) where excess inventory is sitting (components vs finished goods). Cite the tab and cell for each finding. Don't change anything.
The case: Nhan Dinh (@NhanTDinh), X post, Oct 14, 2026. Original source · Case on this site.
Tools named in the case: Seller Labs MCP.
Result (per source, vendor-affiliated): He reports the AI found a row forecasting negative one knife for months, most vendors missing lead times (so the reorder trigger was buffer plus nothing), excess inventory sitting in parts rather than finished goods, and two years of tabs copied forward with drift.
From a vendor-affiliated source, not independently verified.
Worth knowing: His takeaway: build the model in a sheet first, then hand it to AI. 'AI can run the model. A person owns the number.' The author works at Seller Labs, which sells an MCP for reorder math.
Build your own inventory planner across Amazon UK, EU and US and your 3PLs instead of buying an ERP
Starter prompt written by AI Agents for Sellers, based on Multichannel Inventory Planning Tool (Amazon, 3PLs, Xero) with Claude Code and Grok Bot.
Help me plan an in-house inventory planning tool before we build anything. Stock locations: [3PLs] plus Amazon FBA in [marketplaces]. Demand sources: [website, Amazon, retail]. 1. List the data feeds we need from each location and how often to pull them. 2. Propose ABC grouping rules and two forecast methods I can switch per product and channel. 3. Define red/amber/green alert rules from days of cover and lead time. 4. Design the reorder suggestion: respect MOQ and pallet quantities, and suggest 3PL-to-Amazon transfers separately from supplier orders. 5. POs are drafts only, for my approval in [accounting system]. Ask me for anything you need before you start.
The case: Damian Soong (CEO, Form) (@damian_soong), X post, Oct 17, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, Grok Bot.
Result (per source, self-reported): He says it suggests supplier orders based on MOQs and pallet quantities, plus 3PL-to-Amazon transfers, and drafts POs straight into Xero for the team to approve. He calls it 'a big project' but 'very doable', and says the biggest win is being able to make small changes so it works the way their planner likes.
Self-reported by the source, not independently verified.
Worth knowing: No time, cost or accuracy figures are given. POs are drafted for approval, not sent.
Coordinate inventory orders, growth plans and account-issue fixes
Starter prompt written by AI Agents for Sellers, based on Restock Plans and Account Fixes with Amazon Seller Assistant's Agent.
(Ask Seller Assistant in Seller Central.) "Draft a restock plan for my top 20 ASINs by sales: for each, show current FBA inventory, inbound, days of cover, and a recommended send-in quantity for the next 60 days. Don't create any shipment. Wait for my approval."
The case: CNBC (Annie Palmer), News article, Sep 17, 2025. Original source · Case on this site.
Tools named in the case: Amazon Seller Assistant.
Result (per source, Amazon's figure): Amazon told CNBC that 1.3 million sellers have used its gen AI listing tools, which can produce about 70% of a product listing, and that it didn't plan to charge for Seller Assistant.
Amazon's own figures as told to a reporter, not independently tested.
Worth knowing: All adoption figures come from Amazon. See the 2026 plugin and workflow cases for later updates.
Check which best-sellers refunds make unprofitable before you reorder
Starter prompt written by AI Agents for Sellers, based on Refund-Aware Restock Decisions with Grok Bot and Sellerboard.
Using my connected Amazon data and Sellerboard, look at the last 6 months for every ASIN. Build a table: units sold, revenue, refund count, refund rate, Amazon fees, COGS (from Sellerboard) and net profit. Flag ASINs with high sales but a high refund rate and little or no profit. Then tell me which flagged ASINs are back in stock or due for a reorder, and for each one whether it looks worth replenishing, showing the numbers. If COGS is missing, write 'unknown' instead of guessing. Don't place or change any orders.
The case: TonyGainzzz, X post, Oct 14, 2026. Original source · Case on this site.
Tools named in the case: Grok Bot, Sellerboard.
Result (per source, self-reported): 5 of those ASINs were back in stock and he was about to replenish all of them. He reports only 1 of the 5 was actually worth replenishing, so he bought 1 instead of 5.
Self-reported by the source, not independently verified.
Worth knowing: In a reply he explains why he used both sources: Amazon's data has refunds and fees but no cost of goods or profit, so Sellerboard's COGS is what makes the profit check work. He shared no refund or profit thresholds, prompt, or dollar savings.
Combine Amazon sales, Amazon stock and 3PL stock into a weekly reorder list, approved before suppliers are emailed
Starter prompt written by AI Agents for Sellers, based on Weekly Reorder Emails to Manufacturers with n8n.
Here are this week's units sold by SKU, Amazon FBA stock, 3PL stock and my reorder sheet (lead time, reorder point, case pack, vendor) [paste]. For each SKU below its reorder point: suggested order quantity rounded to case packs and the vendor. Group by vendor and draft one short purchase-request email per vendor. Don't send anything; I'll approve first.
The case: Abhishek Jain (P26 Consultancy), Blog post, Jul 8, 2026. Original source · Case on this site.
Tools named in the case: n8n.
Result (per source, agency-reported): The write-up describes how the workflow runs but reports no numbers on time saved or stock outcomes.
Reported by an agency about its own client work, not independently verified.
Worth knowing: This is the consultancy's own case study. The workflow itself has no AI step; AI is only mentioned as a possible add-on. The Amazon pull is described as using MWS, which Amazon has replaced with SP-API, so a new build would use SP-API.
Get daily stock alerts and a weekly reorder dashboard without downloading inventory reports
Starter prompt written by AI Agents for Sellers, based on Stock Alerts and Reorder Dashboard Skill with Claude.
Using my connected Amazon data: for every active ASIN, show units available, inbound, 30-day sales velocity, days on hand, and the reorder date and quantity given a [60]-day lead time. Group into overdue, at risk, healthy and overstock. Post a short summary to Slack daily, and the full table every Monday.
The case: Chris Rawlings (Sophie Society) on Orange Klik, YouTube video, Jun 25, 2026. Original source · Case on this site.
Tools named in the case: Claude, Sophie Society MCP.
Result (per source, vendor-affiliated): In the run he shows, it highlighted one critical product already overdue to ship in, listed the overstock items, and showed the best seller's next order was about two months away. He also shows a master listing skill that turns five downloaded reports into a dashboard and a bulk flat file ready to upload. He calls some skills experimental and says they can break on very large catalogs.
From a vendor-affiliated source, not independently verified.
Worth knowing: Sophie Society is Rawlings' own company, which sells the MCP and the skills, and the session promotes his paid challenge. Recorded on Orange Klik's channel.
Get a weekly account summary and a list of ASINs running low in Slack without pulling reports
Starter prompt written by AI Agents for Sellers, based on Weekly Slack Account Report and Restock List with Claude Code and Amazon's Selling Partner Connector.
You are my Amazon account manager. Every Monday at 9:00 a.m., use the Amazon Selling Partner connector to check FBA inventory and last week's sales for all my ASINs. Send me a Slack message with total sales, ad spend and TACoS vs the prior week, then a table of ASINs with under [30] days of cover at the last 30 days' sales rate (ASIN, units on hand, inbound, days of cover, suggested units to send). Read-only: don't create shipments or change anything.
The case: Alvin Santos, YouTube video, Sep 29, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, Amazon Seller Assistant.
Result (per source, agency-reported): Each week the routine sends a Slack report with an overall summary of the account, spend before and after, sales, TACoS and total sales, plus a list of ASINs that need restocking. When a routine misbehaves, he screenshots it, describes the problem in chat and gets back a longer, more detailed instruction.
Reported by an agency about its own client work, not independently verified.
Worth knowing: The connector is in beta. The report's figures are blurred in the video, so no numbers are shown. The video ends with an offer of a free audit from his agency.
Build your own profit, forecast and inventory-health dashboard from the Amazon API and your spreadsheets
Starter prompt written by AI Agents for Sellers, based on Sales, Profit and Inventory Dashboard with Codex.
Help me build a simple dashboard for my Amazon store. Pull orders, fees and FBA inventory from the Selling Partner API (walk me through registering a private developer app) and my COGS from this Google Sheet: [link]. Show profit per SKU per week, a 12-week sales forecast, and days of cover per SKU with a reorder flag. Explain each step as if I've never coded.
The case: u/Agador777, Reddit thread, Jun 20, 2026. Original source · Case on this site.
Tools named in the case: Codex.
Result (per source, self-reported): He says Codex built the core system in a couple of hours, including the developer API registration, and calls it his first vibe-coding project. No profit or time-saved numbers beyond that.
Self-reported by the source, not independently verified.
Worth knowing: One Reddit comment (r/AmazonFBA thread 'How is everyone using AI for their Amazon businesses?', June 20, 2026). Self-reported.
Update FBM listings from a distributor feed and place distributor orders automatically
Starter prompt written by AI Agents for Sellers, based on FBM Price and Quantity Feed and Automatic Distributor Orders with n8n.
Build an n8n workflow that runs at 6:00 every day: 1) download the distributor feed from [URL] (CSV: SKU, cost, quantity); 2) for each SKU in my Amazon FBM catalog, set quantity = distributor quantity minus a buffer of [2], and price = cost x [1.35] rounded to .99, within my min/max in the sheet [name]; 3) send the changes as one SP-API JSON_LISTINGS_FEED and email me the processing report. Skip any SKU missing from the feed and list it in the email.
The case: Gentoo (n8n community), Seller Forums answer, Aug 18, 2025. Original source · Case on this site.
Tools named in the case: n8n.
Result (per source, forum answer): The first replaced the manual morning upload of the listings spreadsheet; the second removed manual order creation. He was still building two more: posting the distributor's tracking numbers back to the Amazon order, and answering 'not delivered' buyer messages by pulling proof of delivery from the courier (Royal Mail, DPD, DHL) and replying with AI or a template.
From an Amazon forum moderator's answer, not an official policy page.
Worth knowing: A first-hand forum reply without numbers. If your stock comes straight from a distributor, the morning feed is the piece that prevents overselling, so build it before the auto-ordering.
Project each brand's cash by month to see how much can be taken out while still funding reorders
Starter prompt written by AI Agents for Sellers, based on A Cashflow and Safe-Distribution Dashboard with Claude.
For brand [X]: starting cash $[ ] plus Amazon's pending balance $[ ]. Using my projected monthly unit sales and reorder dates [paste], unit cost, freight per unit and payment terms ([30]% deposit at order, rest on completion), estimate monthly cash in (after referral, fulfillment, storage and returns) and cash out for the next 12 months. Tell me the most I can distribute today while keeping cash above $[buffer] every month. Show the table and your fee assumptions.
The case: Alex Willen (The Automated Operator) (@Willenation), Blog post, May 14, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): It took about half a day on top of the earlier work on the inventory skill. He says the skill only became reliable with Opus 4.7 at max reasoning (5 of 5 test cases). Along the way he caught Claude reading the wrong cash column, skipping the inventory skill, and double-counting Amazon fees. Once it was right, he paid himself a distribution.
Self-reported by the source, not independently verified.
Worth knowing: Add charts and a 'method used' card so you can check the numbers; that's how he found the errors. He keeps a cash buffer per brand because the fee models are simplified.
Stock levels, stranded inventory and storage fees
See units on hand, catch stranded or expiring stock, and flag storage-fee traps.
See current FBA stock for every SKU without logging into Seller Central
Starter prompt written by AI Agents for Sellers, based on FBA Stock per SKU into Google Sheets with n8n.
Build an n8n workflow that runs every morning at 7:00: 1) gets an SP-API access token from my LWA refresh token; 2) calls the FBA Inventory API (getInventorySummaries, details=true) for marketplace [ATVPDKIKX0DER], following nextToken; 3) writes one row per SKU to the Google Sheet [name], tab 'Stock': date, SKU, ASIN, fulfillable, inbound, reserved, unfulfillable; 4) highlights any SKU whose fulfillable count is under [30].
The case: sandiegocausa, X post, Nov 26, 2025. Original source · Case on this site.
Tools named in the case: n8n.
Result (per source, self-reported): He says it took some time to figure out the API, but now he always knows what's in stock. He gives no figures beyond that.
Self-reported by the source, not independently verified.
Worth knowing: A short first-hand post with a screenshot, not a write-up. If you build one, keep the inbound and reserved columns next to fulfillable stock; a single 'stock' number hides units that can't be sold yet.
Keep one stock count across Amazon and other channels, with alerts
Starter prompt written by AI Agents for Sellers, based on Inventory Sync Across Amazon, Shopify and Flipkart with an n8n Template.
Before I turn on automated inventory sync, check my Inventory Master sheet: [attach]. For every SKU, confirm it has an Amazon SKU, Shopify inventory item ID and Flipkart SKU, and a safety buffer. List missing or duplicate mappings. Then show what the sellable quantity would be per channel after the buffer, and flag any SKU where it would go to zero or below.
The case: Rahul Joshi (n8n template), Workflow template, Oct 19, 2026. Original source · Case on this site.
Tools named in the case: n8n.
Result (per source, template): Template only, with no reported results. The setup says to run it once manually to check SKU mappings before turning on the schedule.
A published workflow template, not a reported result.
Worth knowing: This is a published workflow template, not a reported result: nobody in the source says what it did for their sales. Read the template's setup steps and test it on one account before you rely on it. This one writes stock levels to your live listings, so test with a few SKUs first.
Monitor account health, hijackers, stranded inventory and suppressed listings across brands
Starter prompt written by AI Agents for Sellers, based on Seller Central Monitoring and PPC Rules with Claude.
Every morning at 8am, for each of my brands' Seller Central accounts, check: Account Health rating and any new policy warnings; any new sellers on my brand's ASINs (possible hijackers); stranded inventory; suppressed or inactive listings. Post one Slack message per brand with only what changed since yesterday, marked [urgent] or [FYI], and a link to the Seller Central page for each item.
The case: Keith Richman (@keithrichman), X post, May 8, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): He says the PPC rebuild 'Closed gaps that were bleeding spend' and that the daily monitoring 'now runs itself.' No figures are given.
Self-reported by the source, not independently verified.
Worth knowing: This is a company-wide week-one recap, and the Amazon details are brief.
Get daily lists of stuck and fast-selling ASINs from your repricer
Starter prompt written by AI Agents for Sellers, based on Repricer Watch Lists with Grok Bot and Seller Snap.
Every morning, review my repricer and sales data and send me three lists: 1. Not moving: ASINs with zero sales in the last 14 days, with current price, min/max and Buy Box status. 2. Slowing: ASINs with no sales in the last 7-10 days. 3. Selling fast: ASINs averaging 5+ units a day, with days of stock left and a suggested higher min price. Suggest changes only. Don't change any min/max or repricing rule until I approve it.
The case: TonyGainzzz, X post, Oct 28, 2026. Original source · Case on this site.
Tools named in the case: Grok Bot, Seller Snap.
Result (per source, self-reported): He says it's doing a much better job than he can personally do with 180 active ASINs, and it takes less of his time. He gives no sales or margin figures.
Self-reported by the source, not independently verified.
Worth knowing: He hasn't handed over repricing completely: 'Repricing is hard to delegate and I'm not planning to delegate 100% of it (not yet at least).' The post doesn't say how the bot accesses Seller Snap.
Find which SKUs will hit aged-inventory, peak storage or low-inventory fees, from Seller Central CSVs
Starter prompt written by AI Agents for Sellers, based on Q4 FBA Fee Traps Skill Pack for Claude Code.
Here are my Inventory Ledger, FBA Inventory and Fee Preview exports [attach]. List SKUs with units that will be 181+ days old at the next 15th snapshot, the estimated surcharge, and whether a removal order by the 14th is cheaper. Then list SKUs whose 30- and 90-day days of supply are both under 28 (low-inventory fee risk). Show every calculation.
The case: Wang Xiaohan (maker) (@wang_xiaohan), X post, Oct 18, 2026. Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, vendor claim): Launch post and product page only, with no user results. The maker says it needs no SP-API and no Seller Central login, and that blank rates stay blank so the skills ask you rather than invent numbers.
From the tool's vendor, not independently tested.
Worth knowing: The maker sells it ($29 for four skills; the low-inventory-fee check is free for an email). Re-check fee rates against Amazon's help pages before acting, as the page itself advises.
Catch products nearing expiry across many countries without manual scanning
Starter prompt written by AI Agents for Sellers, based on Expiry Flags with Amazon Seller Assistant.
Here's my FBA inventory with expiration dates by FNSKU and my sales velocity for the last 30 days: [paste]. List every unit that will hit Amazon's expiry cutoff before it sells at the current rate, sorted by value at risk. For each, suggest one action (promotion, removal order, or move to another marketplace) and say why.
The case: About Amazon Team, Amazon announcement, Sep 15, 2026. Original source · Case on this site.
Tools named in the case: Amazon Seller Assistant.
Result (per source, Amazon's figure): Co-founder Alexander Dreischuh says AI in inventory planning 'helped us identify products with nearing expiration dates and increased our customer satisfaction.' No numbers are given.
From Amazon itself, not independently tested.
Worth knowing: Amazon's own story about its own tool, with no measured result.
Check subscription performance and long-term storage fees without digging through reports
Starter prompt written by AI Agents for Sellers, based on Subscription and Storage Checks with Seller Assistant.
Using Seller Assistant on my account, summarize subscription (Subscribe & Save) performance for the last 30 and 90 days vs the prior period: units, revenue and cancel rate by ASIN. List ASINs with long-term storage fees accruing or about to, with units and estimated fee. Rank the top 10 actions by cash freed or revenue protected. Don't change prices or create removal orders until I approve.
The case: Amazon Selling Partners (Vital Pet Life), Amazon announcement, Apr 30, 2026. Original source · Case on this site.
Tools named in the case: Amazon Seller Assistant.
Result (per source, Amazon's figure): Kyle calls Seller Assistant a business partner "who already knows the numbers" and "my first resource for data analysis and knowledge on tools and features available to us," with answers that used to take manual digging now coming in seconds. No ACoS, sales, or fee-dollar figures are shared for the Seller Assistant queries.
From Amazon itself, not independently tested.
Worth knowing: Amazon Selling Partners customer story (April 30, 2026). Seller Assistant is the agentic tool; A+, Opportunity Explorer and listing tools are also Amazon gen AI features on the same page. One source page = one case.
Get FBA, sales-report and velocity answers without digging through Seller Central
Starter prompt written by AI Agents for Sellers, based on Daily Account Ops with Seller Assistant at ASM Games.
Using Seller Assistant, review my last 14 days: sales and sessions by ASIN, FBA sellable and inbound units, and any ASINs where sales velocity dropped more than [20]% vs the prior 14 days. Explain likely causes in one line each and list actions I can approve (restock, price, ads). Don't change anything until I say yes.
The case: Mary Beth Westmoreland (Amazon) quoting Alfred Mai, ASM Games, Amazon announcement, Sep 17, 2025. Original source · Case on this site.
Tools named in the case: Amazon Seller Assistant.
Result (per source, Amazon's figure): Mai says it "provides me with the answers and actions that I need immediately, rather than me needing to dig around and spend time finding what I need," and that it "even understands sales velocity." No dollar or ACoS figures are given.
From Amazon itself, not independently tested.
Worth knowing: Amazon's September 17, 2025 announcement of agentic Seller Assistant. Quote is first-hand from a named seller; the rest of the page is product marketing. Same URL also describes a smart bird-feeder Creative Studio Sponsored Video; that brand's dedicated Amazon Ads case study is covered separately as Bird Buddy.
Inbound shipments, prep and supplier orders
Track what you sent to FBA, prep inbound shipments, and follow purchase orders.
Consolidate FBA ledger, transfer and inbound reports across marketplaces into one per-SKU view
Starter prompt written by AI Agents for Sellers, based on FBA Inventory Ledger and Transfer Dashboard with Claude Code.
From the FBA Inventory Ledger (summary and detailed), FC transfers and inventory reports I attach, build one table per SKU across all my marketplaces: starting balance, receipts, customer shipments, returns, transfers in/out, lost/damaged/found adjustments, ending balance and reserved/inbound quantities. Then flag any SKU where units marked lost or damaged exceed units later found, or where the ending balance doesn't add up from the movements. Show the rows behind each flag.
The case: DataDoe, YouTube video, Jun 8, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, DataDoe.
Result (per source, vendor claim): This is a vendor demo with no measured result. It shows the finished dashboard and says a Claude skill to recreate it is in the video description.
From the tool's vendor, not independently tested.
Worth knowing: Made by DataDoe's own channel. It needs a DataDoe account, and the first data pull takes about 24 hours. The same ledger view is the starting point for finding lost or damaged units to claim.
Enter replen lines, run reconciliation checks and screen sourcing leads
Starter prompt written by AI Agents for Sellers, based on Replen Entries, Reconciliation and Lead Checks with Claude Cowork and ChatGPT.
SOP: Open my Buy Sheet (Google Sheet). For each row added since [date] with status "Purchased", go to InventoryLab → Inventory → Replenish, search the ASIN, and create a replen line with quantity = Qty column and buy cost = Unit Cost column. Mark the row "Entered in IL" in the sheet. If an ASIN isn't found, skip it and add it to a list. Don't submit any shipment. Report every line you created.
The case: Ryan (@CookingCashflow), X post, Feb 2, 2026. Original source · Case on this site.
Tools named in the case: Claude, ChatGPT.
Result (per source, self-reported): He describes InventoryLab entries as 'super slow' but 'flawless' and basically autonomous after setup, and thinks reviews and reconciliation are 'Claude's strong suit' for Amazon. Extracting tracking and order numbers from email was 'slow,' and gift-card balance checks got stalled by captchas.
Self-reported by the source, not independently verified.
Worth knowing: Honest about limits (speed, captchas, imperfect legitimacy calls). Matching on brand, model number, size and count is what keeps an arbitrage buy from turning into a wrong-item return.
Turn a batch of retail arbitrage receipts into listings, a COGS sheet and an FBA shipping plan
Starter prompt written by AI Agents for Sellers, based on Retail Arbitrage Receipts to Listings and Shipping Plans with Claude.
I'm an Amazon FBA seller doing retail arbitrage. The folder [folder] has photos of one receipt batch. 1. Read every receipt. For each item give store, date, item title, quantity and unit cost (include tax if it's on the receipt). Mark any line you can't read clearly instead of guessing. 2. Match each item to an ASIN and show me the match before listing anything. 3. After I approve, create the listings, then reconcile my quantity on hand against the receipt totals and flag any mismatch. 4. Add one row per item to my Google Sheet: date, item title, COGS, quantity, ASIN. 5. Draft the FBA shipping plan for the items I mark as prepped and packed. Don't submit it until I say so.
The case: Britton Jewell (@BuyHoldCollect), X post, Oct 25, 2026. Original source · Case on this site.
Tools named in the case: Claude, Amazon Seller Assistant.
Result (per source, self-reported): He says he barely has to touch Seller Central or his Google Sheet any more, and sees 'no reason for a VA when things get listed with one prompt.'
Self-reported by the source, not independently verified.
Worth knowing: No time or dollar figures are given. Check the COGS Claude reads off receipt photos before you price from it.
Pull supplier messages from four channels daily and track every in-flight order to Amazon
Starter prompt written by AI Agents for Sellers, based on A Supplier Order Tracker from Email, WhatsApp, Alibaba and WeChat with Claude Code.
Here are this week's messages from my suppliers and forwarder [paste], and my open orders list (order, units, product, status, dates) [paste]. Update each order's status and the date it changed. List anything waiting on me, any supplier who hasn't replied in [3] days, and any Amazon shipment ID the forwarder still needs.
The case: Alex Willen (The Automated Operator) (@Willenation), Blog post, May 7, 2026. Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, self-reported): He says that once the scraping worked, the rest went smoothly. He still downloads WeChat and Alibaba attachments himself and archives finished orders. Claude also keeps notes on each supplier, such as who needs chasing and who knows Amazon's requirements.
Self-reported by the source, not independently verified.
Worth knowing: He picked the least detectable method for each app because Alibaba and WeChat terms forbid bots: no clicking on Alibaba, and no memory scraping or database pulls on WeChat. Check each platform's terms before copying this.
Replace InventoryLab and Sellerboard with a custom-built tool
Starter prompt written by AI Agents for Sellers, based on Bookkeeping and FBA Shipment App with Claude.
Help me design (don't code yet) a small bookkeeping app for my Amazon + Walmart + eBay business. It must track: sales by channel, refunds, Amazon reimbursements, expenses, shipping costs, inventory on hand by SKU with COGS, and cash flow. Propose the data model (tables and fields), what each channel's settlement/transaction report maps to, and the 5 screens I need. Ask me about anything you're unsure of.
The case: Parker (@pmcommerce), X post, Oct 12, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): He says the best part is that 'when something breaks, Claude fixes it that day.'
Self-reported by the source, not independently verified.
Worth knowing: You become the maintainer. A Reddit seller made a similar point about building your own versus paying for SaaS.
Build your own dashboards and keep a prep center in sync with Amazon orders
Starter prompt written by AI Agents for Sellers, based on Seller Dashboard and Prep Center Sync Built with Claude Code.
Using my SP-API credentials in .env, build a small local dashboard: 1) account health summary; 2) open FBA inbound shipments with units shipped vs received; 3) best sellers by units for the last 7, 30 and 60 days. Read-only: don't call any endpoint that changes listings, prices or shipments. Show me the endpoints you plan to use before writing code.
The case: FulfilledByBinh, X post, Mar 27, 2026. Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, self-reported): After the upgrade, a daily order scan auto-fixes inventory discrepancies, FBA/FBM detection uses live SP-API data, catalog matching flags uncertain items, and channel sync runs automatically. He calls Claude Code his new favorite thing.
Self-reported by the source, not independently verified.
Worth knowing: Short build-log posts with no numbers. Flagging uncertain catalog matches instead of guessing is the part worth copying; an auto-fix that matches the wrong SKU makes the discrepancy worse.
Buy costs, COGS and purchase tracking
Fill in missing costs, track landed cost per batch, and keep a purchase log.
Find and fill in missing ($0) buy costs in InventoryLab
Starter prompt written by AI Agents for Sellers, based on InventoryLab Buy-Cost Updates with Claude Cowork.
Go to InventoryLab and open my active inventory. Filter to FBM items. For every item with a buy cost of $0, read the cost encoded in the SKU (format: [describe your SKU format]) and update the buy cost to that value. When you can't find more, double-check by searching each retailer name from my SKUs. At the end, give me a list of ASINs still at $0 because the SKU has no cost in it.
The case: Saul (@SaulSellsStuff), X post, Jan 14, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): He reports it navigated the site correctly, learned his SKU structure, updated items systematically, double-checked by searching retailer names, and returned a list of ASINs whose SKU didn't contain a cost. He called it 'a no-brainer' at $100/month.
Self-reported by the source, not independently verified.
Worth knowing: It works in your logged-in browser session, so watch the first runs.
Track ingredient and packaging costs per production batch across 3PL and FBA
Starter prompt written by AI Agents for Sellers, based on True COGS per Batch Tracking with Claude Code.
Build me a simple local web app to track COGS per production batch. Inputs: purchases (date, item, quantity, total cost) for ingredients and packaging; BOMs per SKU; production runs (date, SKU, units made, which purchase lots were consumed). Output: COGS per unit for each batch, plus a current weighted COGS per SKU across inventory at my 3PL and at Amazon FBA. Use SQLite. Ask me questions before you start coding.
The case: haitham (@theonlyhaitham), X post, Feb 2, 2026. Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, self-reported): He says he 'immediately saw my real COGS' and had more margin than he thought, so he could spend more on advertising. He estimates he saves at least $300/month on software.
Self-reported by the source, not independently verified.
Worth knowing: This replaced an Excel workflow that broke down as production runs got closer together.
Replace a paid purchase-tracking sheet for an Amazon resale business with a self-built app
Starter prompt written by AI Agents for Sellers, based on Sourcing Purchase Tracker App with Claude.
Build me a simple purchase tracker for my Amazon resale business. I want to log each sourcing buy with: date, source, item, quantity, cost per unit, shipping and tax, and the ASIN I plan to sell it under. Show running totals per month and a list of items bought but not yet sent to FBA. Keep the data in a file I own and let me export it as CSV. Start with the smallest version and ask me before adding features.
The case: CuriousCrateLab, X post, Oct 23, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): The author calls it a small win that's '$468 a year back.'
Self-reported by the source, not independently verified.
Worth knowing: A short post: it doesn't say which features the app has or how long it took to build.
Hand daily back-office jobs (COGS entry, repricer setup, payouts, account health, reorder math) to bots instead of a VA
Starter prompt written by AI Agents for Sellers, based on COGS, Repricer Setup, Payouts and Reorder Quantities with Grok Bot.
Every morning at 6:00 a.m., check my Amazon FBA inventory. For each SKU, get units sold in the last 30 days, units available and units inbound, and recommend how many to buy to stay in stock for the next 30 days (add a holiday buffer from mid-October through December). Flag SKUs with more than 90 days of cover as liquidation candidates and SKUs whose sales changed more than 10% vs the prior 30 days. Send me a table; don't place any orders.
The case: Ben Spangler, YouTube video, Nov 11, 2026. Original source · Case on this site.
Tools named in the case: Grok Bot.
Result (per source, self-reported): The reorder Bot came back with 332 units for an item he had estimated at 350, which he calls "pretty sick." He says that when a Bot makes a mistake he gives it a new rule and it doesn't repeat it. A customer service Bot he's training is "about 70%" there: it handles A-to-z claims but offers some refunds too early, so he still handles customer service and ungating himself. He's on the $100-a-month plan.
Self-reported by the source, not independently verified.
Worth knowing: He reviews everything before it goes out and keeps the Bots off big business decisions. The video ends with a coaching pitch, and his students get his Bot scripts.
Inventory in reports and store audits
Pull inventory into a weekly review, an account audit, or a self-built workspace.
Turn the weekly review of sales, profit, refunds and inventory risk into a repeatable workflow
Starter prompt written by AI Agents for Sellers, based on Weekly Amazon Business Review with ChatGPT.
Here is this week's data for my Amazon business: [paste per-SKU sales, units, profit, refund rate, FBA stock, days of cover, inbound]. Fill in my weekly review template: 1) top 5 and bottom 5 SKUs by profit change vs last week; 2) SKUs with refund rate above [x]%, with the change; 3) inventory risks: under [30] days of cover or over [120]; 4) three questions the team should answer in this week's meeting. Only use the numbers I gave you.
The case: Winke Chan (@WinkeChan), X post, Jun 17, 2026. Original source · Case on this site.
Tools named in the case: ChatGPT.
Result (per source, self-reported): He says it used to be a long manual process and is now more repeatable. No time saved or other numbers are given.
Self-reported by the source, not independently verified.
Worth knowing: His rule: AI should improve efficiency, not replace the operator's judgment.
Pull any Seller Central report by asking for it in plain English
Starter prompt written by AI Agents for Sellers, based on Seller Central Report Pulls from One Sentence with a Claude Skill.
Pull last month's FBA customer returns report from Seller Central through my SP-API credentials and save it as a CSV in my reports folder. Use Seller Central's definition of "last month" for my marketplace's time zone, and log the timestamp, report type, date range and output file name.
The case: Yuri Jew, Blog post, May 6, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): 'Pull last month's returns' puts a CSV in the reports folder about 30 seconds later, and every pull is logged with timestamp, report type, date range and output file so it can be audited or rerun. His weekly returns brief, restock forecast, settlement reconciliation and Buy Box audit now start from one prompt instead of a Seller Central login.
Self-reported by the source, not independently verified.
Worth knowing: A lead-magnet post (comment to get the skill), with no time-saved figure beyond the 30-second pull. The audit log is the part worth copying: it lets you rerun the exact pull behind any number you report. SP-API setup is a one-time job.
Stop downloading reports and building charts by hand every morning
Starter prompt written by AI Agents for Sellers, based on Morning Report Building Replaced by Amazon Seller Assistant Dashboards.
Each morning, give me one view with: yesterday's units and sales by ASIN vs the same day last week, days of supply for every ASIN under 30 days, inbound shipments and their status, and any ASIN whose conversion dropped more than 20% week over week. End with the three things my inventory team should look at first.
The case: Amazon Selling Partners, Amazon announcement, Sep 23, 2026. Original source · Case on this site.
Tools named in the case: Amazon Seller Assistant.
Result (per source, Amazon's figure): Quirk says: 'I'm getting back almost two hours every morning,' and that her team now comes to her with suggestions. In Brown's demo, the assistant found margin would tighten and stock would run short at peak, recommended pricing changes on two SKUs and drafted the inbound shipment.
From Amazon itself, not independently tested.
Worth knowing: Published by Amazon about its own tools, with seller quotes taken at Amazon's Accelerate conference, and the Brown example is a stage demo. Quirk's time saving is the first-hand part.
Run my own and my clients' Amazon accounts from one self-built workspace
Starter prompt written by AI Agents for Sellers, based on Account Workspace Built with Claude Code.
Help me build a small local web app with Claude Code that shows, for today and the last 30 days: units and ordered sales per ASIN, Amazon fees, ad spend, and profit before and after cost of goods. Read data from my own SP-API and Amazon Ads API credentials (read-only), take COGS from a CSV I keep, and mark any number that is still an estimate. Don't add any feature that changes anything in Amazon.
The case: Jack Leader (Jack2 Media) (@Jack2Media), X post, Nov 3, 2026. Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, vendor-affiliated): He says: 'We run our accounts on it every day. A few bumps, ironed out as we go.' The screenshot shows £1,977 ordered so far that day, with £1,057.45 known before stock costs. He doesn't say the tool raised sales, and the tool's own site says its £1.11m preview figure is not a claim that Cleave caused those sales.
From a vendor-affiliated source, not independently verified.
Worth knowing: A launch post for his own product (waiting list open, pricing not decided), so treat it as vendor-affiliated. It shows a non-engineer can build a working seller workspace with Claude Code; it isn't a measured result.
Connect Claude to my own Seller Central data so I can ask questions in plain words
Starter prompt written by AI Agents for Sellers, based on SP-API MCP Server Built with Claude Code.
I have SP-API developer credentials for my own seller account. Help me build a small read-only MCP server in TypeScript that exposes: sales by ASIN for a date range, FBA inventory, open orders, catalog item details and settlement summaries. Handle token refresh, rate limits, pagination and async report polling. Pin every dependency version, keep credentials in environment variables, and don't add any write endpoints.
The case: Mansour Norouzi, Blog post, Apr 1, 2026. Original source · Case on this site.
Tools named in the case: Claude Code, Claude.
Result (per source, self-reported): He says he has automated 80% of the brand's operations, and that asking Claude 'show me my sales for the last 7 days' now 'just works.' A commenter flagged compromised versions of the axios package; his post says it was already patched.
Self-reported by the source, not independently verified.
Worth knowing: You need your own SP-API developer access. The axios warning is the real lesson: a server holding your refresh token and client secret is a target, so pin and check dependencies. Another commenter notes you can reach SP-API with plain scripts and no MCP server.
Audit fees, returns, variation reviews, landed costs and policy deadlines from my own files
Starter prompt written by AI Agents for Sellers, based on Five Account Audits with NotebookLM.
Using only the uploaded FBA fee reports, inventory health reports and returns reports for the last 6 months: which 10 SKUs paid the most in low-inventory-level and return-related fees, how much each, and which have the highest return rate? Cite the report and row for every number.
The case: Ary Ashoor, Blog post, Mar 2, 2026. Original source · Case on this site.
Tools named in the case: Gemini.
Result (per source, self-reported): A how-to with prompts, not a reported result. He says it takes 10 minutes to set up and that every answer is cited back to the reports, invoices and reviews you uploaded.
Self-reported by the source, not independently verified.
Worth knowing: He claims NotebookLM 'only pulls from YOUR data. No hallucinations.' The citations make answers easy to check, so check them. The full prompt pack is a comment-for-the-link offer.
Catch slow fee and ad-spend creep across months, not just one snapshot
Starter prompt written by AI Agents for Sellers, based on Account P&L Cost-Creep Trends with the Helium 10 MCP.
Using Helium 10 MCP get_account_profit_and_loss_breakdown_series, show each cost category as a percent of revenue month by month for the last [6] months. Flag the three categories with the fastest growth rate, name the month each accelerated, and propose checks (fee tier, storage, ad ACoS) before I change anything.
The case: Lauren Stair (Helium 10), Blog post, Aug 25, 2026. Original source · Case on this site.
Tools named in the case: Helium 10, Claude.
Result (per source, vendor claim): Helium 10 cites 1,300+ sellers activating MCP in the first 10 days after the July 16, 2026 launch and thousands of daily tool calls. Bradley Sutton describes sellers cutting storage fees in half after noticing a four-month climb in the series. No named-account dollar proof is published on the page.
From the tool's vendor, not independently tested.
Worth knowing: Vendor how-to (August 25, 2026). Treat the storage-fee anecdote as an evangelist example, not a measured case study.
Fill a weekly KPI sheet from Amazon data and email the brand manager five action items every Monday
Starter prompt written by AI Agents for Sellers, based on Weekly KPI Sheet and Monday Action Email with Claude.
Every Monday: from my Amazon data for last week and the week before, fill my KPI sheet [link] with sales, ad spend, TACoS and contribution after ads per brand. Then write a short email comparing the two weeks side by side and list five action items. Flag any SKU whose fee per unit changed by more than 20%. Don't change anything in Seller Central.
The case: Dr. Travis Zigler (Profitable Pineapple), YouTube video, Nov 6, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): In the run he shows, it caught that the per-unit fees on his tinted lip balm went from 2.67 before deal week to 5.18 after it (the video title calls it a 94% fee spike), so he planned to open a case with his Amazon manager. It also flagged new ads that weren't serving yet. He disagreed with one suggestion to cut Shopify Meta campaigns at about 1 ROAS because they also push Amazon sales.
Self-reported by the source, not independently verified.
Worth knowing: A short demo on his own brands; the brands also sell on Shopify, so blended figures include it. He doesn't say how the Amazon data reaches Claude in this clip.
Let an agent run the store's recurring audit, listing, review-request and ads work through the official seller APIs
Starter prompt written by AI Agents for Sellers, based on Running an Amazon Store (Audits, Listings, Reviews, Ads) with Claude Code Skills.
Act as my Amazon store operator. Each week: 1. Audit: pull sales, sessions, conversion and ad data per ASIN for the last 7 days vs the 4 weeks before. List the 5 biggest problems with numbers. 2. Fix: for each problem, propose one specific change (listing text, bid, budget, negative keyword). Record today's baseline for the metric it should move. 3. Measure: check last week's changes against their baselines and say which helped, which didn't, and what to roll back. Wait for my approval before making any change.
The case: Ebrahim (@EbrahimElb), X post, Jul 23, 2026. Original source · Case on this site.
Tools named in the case: Claude Code.
Result (per source, self-reported): He reports the store sold $130K in about 6 months (6,454 units, 7.7% conversion rate, about 19% net, $250K of stock at list price) and attached a screenshot of the sales figure. He doesn't say how sales compared with before the agent took over.
Self-reported by the source, not independently verified.
Worth knowing: Self-reported, with a screenshot. He said he was open-sourcing the setup in a thread, but the repo link isn't in the posts we could open. Review requests through Amazon's Request a Review feature are allowed. Asking only happy buyers for reviews is not.
Combine many Seller Central reports into one ranked action plan
Starter prompt written by AI Agents for Sellers, based on Account Audit Dashboard Skill with Claude.
I'm attaching my Seller Central exports: business report by ASIN, FBA inventory, returns, voice of the customer, search query performance and Sponsored Products search terms. Combine them per ASIN and find: stock-out risks, ASINs with poor customer-experience flags, search terms that don't match what the product is, and ASINs where conversion is falling. Give me a ranked action list (P0, P1, P2) with your reasoning and an estimated impact, and say which numbers are estimates.
The case: Prabal Sarkar, Blog post, Apr 23, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): He describes the output, not a result: each step in the action plan carries an estimated £ impact, and the dashboard is a single file that opens in any browser. He gives no example account or numbers.
Self-reported by the source, not independently verified.
Worth knowing: A LinkedIn post that offers the skill to anyone who comments 'Audit', so it's partly a lead magnet. The £ impact figures are the skill's estimates; check them before acting.
Run monthly Amazon performance reports without tying up the team
Starter prompt written by AI Agents for Sellers, based on Monthly Reporting with Seller Assistant.
Build my monthly Amazon performance pack: units and sales by ASIN vs last month, which ASINs gained or lost impressions the most, inventory days of supply under 30, and any open policy or account-health flags. End with five questions I should ask next, and don't change anything.
The case: Amazon Selling Partners, Amazon announcement, Apr 8, 2026. Original source · Case on this site.
Tools named in the case: Amazon Seller Assistant.
Result (per source, Amazon's figure): Ramirez says Seller Assistant saves that front-end legwork and that over time it saves money and helps them reach more customers. No time or sales figures for the AI tools are given.
From Amazon itself, not independently tested.
Worth knowing: Amazon's own story about its own tools. Opportunity Explorer and Creative Studio are mentioned separately from Seller Assistant.
Let an AI read the whole store through your own SP-API keys and catch the process mistakes you've been missing
Starter prompt written by AI Agents for Sellers, based on Store Audit and Daily Ops on SP-API with Claude.
Using my SP-API data (read-only), audit my store: (1) orders 5-30 days old still eligible for Request a Review, (2) listings with empty or thin backend search terms, (3) listings whose bullets don't match the product title or images, with conversion rate vs sibling ASINs, (4) my top-ranking keywords and which ASIN holds the rank, (5) days of inventory cover per ASIN heading into Q4 with estimated storage cost. Rank fixes by money at stake. Change nothing without my approval.
The case: u/Infamous-Ad-8129, Reddit thread, Jul 23, 2026. Original source · Case on this site.
Tools named in the case: Claude.
Result (per source, self-reported): He says it found 437 orders eligible for Request a Review that he'd never sent, empty backend search terms on every listing, one listing whose bullets described a different product (2.7% conversion vs 10-14% on siblings), his best keyword rank stuck on his worst listing, and about 377 days of inventory cover heading into Q4.
Self-reported by the source, not independently verified.
Worth knowing: Self-reported Reddit post (r/AmazonFBA, July 23, 2026). Every change goes through his approval with backups first. He says he open-sourced the setup but doesn't link it in the post.
How we picked these
As of Nov 19, 2026, this site has 374 public, sourced cases. 92 of them include inventory as a topic, and 53 of those have a prompt that plans, tracks, forecasts or queries inventory or stock levels: the cases whose main topic is inventory, plus side-topic cases we checked one by one. The other 39 only mention inventory in passing (ads tools that use stock as an input, reimbursement claims, general store agents, sourcing) and stay on Inventory & Ops cases. 6 of those cases include a prompt published by the original source; 40 include a starter prompt written by us and appear on this page, and 7 are not yet on this page.
Section 1 includes all 6 source prompts, unchanged. Section 2 includes all 40 starter prompts we wrote for the cases on this page, grouped by inventory job. This page covers 46 of the 53 inventory cases. We did not pick prompts to promote a tool. Vendor, vendor-affiliated, agency, Amazon, and template cases are labeled as such.
Every case links to its original public source. Every result and note on this page is quoted from the case. We do not independently verify results. Counts reflect what we found, not market share or how many sellers use each tool. See how we source cases. Related pages: Inventory & Ops cases, Which AI agent for Amazon inventory and operations?, and State of AI Agents for Amazon Sellers.
License and how to cite this page
The counts, groupings, and original text written by AI Agents for Sellers, including starter prompts, are CC BY 4.0: reuse them with credit and a link to this page. Quotes, prompts marked “source”, and linked material belong to their original authors.
How to cite this page: AI Agents for Sellers, “Best AI prompts for Amazon inventory and FBA restock”, as of Nov 19, 2026, https://aiagentsforsellers.com/prompts/amazon-inventory/