Project inventory and recommend when to reorder each product
Have Claude Code pull inventory and sales data, project the next twelve months of sales and stock by product, and recommend when to reorder each one, using written notes on supplier lead times and holidays.
What the agent did
Source-reported example · as described by Alex Willen (acquires and operates Amazon e-commerce brands; author of The Automated Operator)
The author, who acquires and operates e-commerce brands selling on Amazon, had Claude Code build scripts to pull inventory and sales data for each brand, then talked through each brand's context (acquisition dates, inventory at a 3PL, supplier lead times, supplier locations), which Claude saved in a file per brand.
Asked to review the data first, Claude picked out anomalously low sales months and very-low-stock items with no inbound units, and the author explained them. Claude then produced inventory projections and reorder recommendations for each brand.
After a day of correcting its method, the author set up an /inventory command whose instructions have Claude refresh stale Amazon data, read the brand's context notes, show trailing-twelve-month sales by SKU and month, state its adjustment factors, project next-twelve-month sales and month-end stock using Python, and recommend when to reorder each SKU, factoring in Chinese New Year and other holidays.
Per the post, Claude also asked whether an inbound Amazon shipment had come from the 3PL and whether to adjust the 3PL stock count.
Reported: the author says that since setting up the /inventory command he has "not once used a spreadsheet for this task" and uses it consistently. Reported: initial setup took half a day, and the first projections were "very bad", followed by a day-long cycle of corrections. No figures on time saved, stockouts avoided or forecast accuracy are given.
Limitations
The first projections were wrong: Claude underestimated seasonality, sometimes ignored the CLAUDE.md note, copied last year's sales unchanged, and made math errors that led to wrong reorder recommendations; the author added explicit steps to the command to fix each problem.
Even after it noted feedback, it often repeated the same mistake. It recommends reorder timing only; it does not place orders with suppliers.
The scripts and the full instruction file are not published, and the number of brands and SKUs isn't stated. No accuracy or time-saving figures are given. The results are the author's own description.
Try it in your business
What you'll need
Claude Code; sales and inventory data by SKU (the author pulled it from Amazon with scripts Claude Code wrote); written notes per brand covering supplier lead times, holiday closures, off-platform stock and past stockouts; an instruction file or command listing the projection steps.
Not disclosed: The scripts' code and how the Amazon credentials were connected; the full text of the instruction file and per-brand context files; the number of brands and SKUs; how accurate the projections turned out against actual sales.
Claude Code built custom scripts that pull data from Amazon with the author's credentials, plus a custom /inventory command; that is custom code rather than written instructions alone or an off-the-shelf app connection.
The original is a custom-built system. The prompt below is a simpler starting point and won’t reproduce it.
Author's example instructions
Published by the author as an example; not confirmed as the exact prompt behind the reported result.
1. Check to see if the sales/inventory data we have locally is >5 days old, and if not, pull fresh data from Amazon. 2. Check the context notes for the brand it's working on. 3. Pull inventory and sales data from the local cache. 4. Display the trailing twelve month sales data by SKU and by month. 5. Describe any factors it's going to use to make adjustments to TTM sales data when projecting NTM sales. 6. Review its stated adjustment factors, then project NTM sales by SKU on a monthly basis, and display the amount of stock remaining at the end of each month based on those projections. Use Python for the math here. 7. Recommend when to reorder each SKU, factoring in CNY and other holidays.
Optional starting prompt (ours, untested)
How ours differs from the original setup: Same Claude Code execution agent. Works from an exported sales file and a written notes file instead of custom scripts pulling from Amazon; adds explicit check-ins before projecting and before applying adjustments, and keeps the output as a draft with no orders or supplier contact.
Read the sales and inventory export in [sales file] and my notes in [context file] (supplier lead times, holiday closures, stock held elsewhere, past stockouts). Before projecting anything, show me the trailing twelve months of sales by product and month, flag months that look unusually low or products with very little stock and nothing inbound, and ask me about them. Then list the adjustments you plan to make to last year's monthly sales and wait for my OK. Using Python for the math, project the next twelve months of sales by product and show the stock left at the end of each month. Finally, recommend a reorder date for each product, accounting for lead times and holiday closures, and show the numbers behind each date. Treat this as a draft for my review: don't place, send or change any orders, and don't contact suppliers.
Replace the [bracketed] parts with your own files and tools.
Get examples like this every Tuesday and Friday
Practical ways to put AI agents to work in your business. We check the original sources, explain the setup and point out the limits. Free.
Unsubscribe any time. Privacy policy
Related use cases
Build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive
Have Grok Bot build an estimate and job-cost tracker connected to QuickBooks, email and OneDrive, as the author says he did to replace his construction-management software.
Our suggested starting prompt — not the author's original · untested
You'll need: Grok Bot with access to your QuickBooks, email and OneDrive (the post does not say how it was connected); the estimate and job-cost categories your current software uses, ideally with a sample from one job; your own review of the tracker and of anything the bots prepare.
I want an estimate and job-cost tracker to replace [current software or spreadsheet]. Build it as a workbook saved in [OneDrive folder] with: an estimate sheet per job ([line items and cost codes]), a bills and actual-cost sheet per job, and a summary of budget against actual cost per job. Fill the cost data from QuickBooks ([company file]) and from bill emails in [mailbox or label], read-only: do not change anything in QuickBooks, send any email or delete anything. Match each bill to a job and cost code, and list the ones you cannot match, with the reason. First show me the structure and a sample for [one job] before you fill in the rest. For draws: when I ask, prepare the draw package for [job], draw number [n], using only invoices that were not in earlier draws, and list any issues from the last draw request. Save it as a draft and write a draft email to [bank contact]. Do not send anything to the bank; show me the package and the draft first.
Run a new client's standard audits and draft the kickoff strategy brief
Have Claude Code run a new client's standard first-week audits and draft a strategy brief with recommended priorities for you to review before the kickoff call.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude Code; read access to the client's website and, for the analytics and CRM reviews, the client's Google Analytics/Tag Manager and email/CRM tools; a written audit checklist; a brief template; the owner's review before anything is sent
We're onboarding a new client: [client name], website [URL], industry [industry], main goal [goal] (from their intake form in [file]). Please prepare a first-week audit and a draft strategy brief for me to review. 1) Technical SEO: check the public site for crawlability, page titles and descriptions, broken links, page speed and mobile issues. 2) Analytics: from the export or read-only access I've given you [path/access], note whether Google Analytics and Tag Manager are set up and tracking key actions. 3) Competitors: for these competitors [list], compare the main keywords and topics they appear to target. 4) Email/CRM: from my notes [file], summarize their current setup and gaps. Save each audit as a separate file with findings, evidence and what you couldn't check. Then draft a one-to-two page strategy brief with the top 3–5 recommended priorities, each tied to the audit findings, and list open questions for the kickoff call. Keep everything as drafts in [folder]: don't send anything to the client, don't change any site, analytics or CRM settings, don't buy any tools and don't delete anything. Ask me before using any login or access I haven't listed.
Onboard a new client end to end: draft the contract, set up their Slack channel and podcast feed, and build website mockups for your review
Have Claude run a client-onboarding skill that drafts the client's contract, creates their shared Slack channel, adds them to your client database, and prepares samples, website mockups and a podcast feed for your review, while you send the invites, grant access and write the client messages yourself.
Our suggested starting prompt — not the author's original · untested
You'll need: Claude with skills (or saved instructions) describing your onboarding process; your internal docs, past contracts and the client's correspondence; access to your documents (for example Google Drive and Docs) and, if you let it do setup steps, to your team chat (the author used Slack via Claude's browser use) and client database; your own review of the contract, every account, channel or access change, and every client message. Building the skills was a one-off investment of about a day of the author's time, by his estimate.
Help me onboard a new client for my [type of service] business. Work in stages and stop for my approval at the end of each one. Stage 0 (first time only): Read my internal docs and past client notes in [folder]. Write a short overview of what my business does and how it works, then draft a step-by-step client onboarding checklist. I'll correct it. Once I approve it, save it as reusable instructions I can run for future clients. Stage 1, contract: Using the client emails and call notes I've attached and my past contracts in [folder], draft a service contract for [client] as a document. Look up their public details (legal name, registered address, registration number) and list where you found each one. Highlight anything that differs from my usual contract or that you're unsure about. Don't send it or upload it to a signing service. I'll review it and send it myself. Stage 2, setup: List every channel, record and account this client needs (for example a shared [Slack] channel that follows my naming pattern, or an entry in my client database), and wait for my OK before you create each one. Don't invite the client, grant access, change permissions, or enter any password or payment details. Give me the invite link or the exact page to open, and I'll do those steps. Stage 3, tailoring and samples: Review [the client's website or materials], list the special cases my service needs to handle for them, and propose a rule for each. After I approve the rules, prepare [sample deliverables] for me to check, and flag anything you're unsure about. Stage 4, mockups and delivery setup: Make mockups of [how my deliverable would look on their website], using their public branding, and draft [the feed, page or other delivery setup] privately. Don't publish anything until I approve it. Stage 5, client update: Don't write or send messages to the client. Give me a bullet list of points to cover in my update, then check my draft for clarity and for anything I've missed. Finish with a checklist of what's done, what's waiting for my approval, and what I need to do myself.

