You have the workspace set up. Now it is time to use it. This module walks through five real tasks you can run immediately with your Claude Code setup. Each one demonstrates a distinct type of Level 2 AI work — from file analysis to draft writing to data-driven recommendations.

For each use case, you will see the prompt to use and what to expect as output.

---

Use Case 1: PPC Bulk File Analysis

What it does: Reads your PPC bulk export and flags underperforming keywords so you can make targeted bid adjustments.

What you need first: Export your Sponsored Products bulk file from Amazon Ads and save it to your /reports folder as a CSV.

Prompt to use:

Read the file in reports/[your-filename].csv.
Identify every keyword where ACoS is above [your threshold]%.
For each flagged keyword, list: the keyword, current bid, current ACoS, 7-day spend, and 7-day sales.
Then suggest a new bid based on bringing ACoS to [your target]%.
Save the output to analysis/ppc-flags-[date].md.
        

What you get: A clean, actionable file with every over-threshold keyword, its data, and a specific suggested bid — ready to review and act on.

---

Use Case 2: Supplier Negotiation Email

What it does: Drafts a professional supplier email using notes from your last conversation and your current context from CLAUDE.md.

What you need first: A quick notes file in /emails with key points from your last supplier interaction — even just bullet points.

Prompt to use:

Read emails/supplier-notes-[supplier].md.
Draft a reorder email to my supplier [name from CLAUDE.md].
I want to order [X] units of [product].
My current stock is [X] days and I need delivery in [X] weeks.
Also push back gently on the price — I want to negotiate [X]% off the current unit cost.
Use my brand voice from CLAUDE.md (professional but direct).
Save the draft to emails/reorder-draft-[date].md.
        

What you get: A complete, ready-to-review draft email that matches your voice, references your actual situation, and handles the negotiation ask in the right tone.

---

Use Case 3: Weekly Order Summary With Anomaly Detection

What it does: Reads your sales export and generates a plain-language summary with any anomalies flagged (velocity drops, unexpected returns, SKU-level outliers).

What you need first: Export your order report from Seller Central and save it to /reports as a CSV.

Prompt to use:

Read reports/orders-[date-range].csv.
Give me a summary of the past week:
- Total units sold, total revenue, total returns
- Top 3 SKUs by revenue
- Any SKU where sales dropped more than 30% compared to the prior week
- Any ASIN with a return rate above 5%
Flag anything that seems unusual and explain why.
Save to analysis/weekly-summary-[date].md.
        

What you get: A clean weekly digest that would otherwise take you 20-30 minutes of Excel work — done in under two minutes, saved as a reference file.

---

Use Case 4: Listing Copy From a Product Spec Sheet

What it does: Generates Amazon-ready listing copy (title, bullets, description) from your product spec notes.

What you need first: A Markdown or text file in /products with the key details about your product: dimensions, materials, use cases, differentiators.

Prompt to use:

Read products/[product-name].md.
Write Amazon listing copy for this product:
- A title under 200 characters that leads with the main keyword
- 5 bullet points (each under 200 characters) highlighting key benefits, not just features
- A product description of 300-400 words written for [my brand voice from CLAUDE.md]
Target the keyword "[primary keyword]".
Save the output to listings/[product-name]-v1.md.
        

What you get: A complete first draft of your listing that matches your brand voice, uses your specified keyword, and follows Amazon’s formatting requirements — ready to review, refine, and upload.

---

Use Case 5: Inventory Reorder Planning

What it does: Analyzes your current inventory against your velocity to calculate how many units to reorder and when you need to place the order.

What you need first: Your current inventory export from Seller Central (or FBA inventory report) saved to /reports.

Prompt to use:

Read reports/inventory-[date].csv.
For each active ASIN:
- Calculate daily sales velocity using the past 30 days of sales data (use reports/orders-last30days.csv)
- Calculate days of cover remaining at current velocity
- Flag any ASIN with less than [your reorder threshold] days of cover
- For flagged ASINs, calculate how many units to order based on [your reorder target: e.g. 90 days of cover]
- Factor in a supplier lead time of [X] weeks from my CLAUDE.md
Save the output to analysis/reorder-plan-[date].md.
        

What you get: A specific reorder plan with exact unit quantities per ASIN, based on your real velocity data and lead time — no spreadsheet required.

---