Claude Prompt Library

Claude Prompts for Logistics and Supply Chain Teams

30 copy-paste prompts

Paste in your shipment, carrier, or inventory data and get a finished tracker, report, or SOP back in one reply. Not "give me some advice".

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Hand-curated and tested by the AI Academy team.

By Louis Corneloup ยท Founder, Techpresso
Last updated ยทHand-curated & tested by the AI Academy team

Shipment Tracking & Exception Reports

5 prompts

Live Shipment Status Tracker

1/30

You are a senior logistics operations analyst. <context> The ops team needs one view of in-transit shipments across carriers instead of checking separate carrier portals. </context> <inputs> - Shipment list (ID, carrier, origin, destination, status, ETA): [PLACEHOLDER] - Number of shipments to simulate if no data is given: [PLACEHOLDER, default 15] </inputs> <task> Build a shipment tracker as a single HTML page with a table, color-coded status badges (On Time, Delayed, Exception, Delivered), and a summary bar showing counts per status. If no data is given, generate 15 realistic sample shipments across 3 carriers (for example FedEx Freight, XPO, Old Dominion) with mixed statuses. </task> <constraints> - Self-contained HTML with inline CSS, no external libraries or images. - Sort shipments by ETA ascending. - Flag any shipment more than 24 hours past its ETA as "Exception" in red. </constraints> <format> A single previewable HTML artifact. </format>

Builds a single-page shipment tracker with color-coded status badges and a summary count bar.

๐Ÿ’ก

Pro tip: Paste in your actual carrier export columns even if the headers are messy, Claude will map them instead of you reformatting first.

Late Delivery Exception Report

2/30

You are a logistics operations manager. <context> The weekly ops review needs a written exception report explaining why shipments missed their SLA. </context> <inputs> - Late shipments with reason codes and delay hours: [PLACEHOLDER] - SLA target in hours: [PLACEHOLDER, default 48] </inputs> <task> Produce a structured exception report grouping late shipments by root cause (carrier delay, customs, weather, warehouse dwell, and similar), with counts, average delay, and one recommended corrective action per cause. If no data is given, invent 10 realistic sample late shipments. </task> <constraints> - Group by root cause, sorted by frequency descending. - Include a one-paragraph executive summary at the top. - Keep language factual, no blame language toward named individuals. </constraints> <format> A structured document with a summary section and a data table. </format>

Groups late shipments by root cause and hands the ops review a summary with a fix per cause.

๐Ÿ’ก

Pro tip: Include the raw reason codes from your TMS even if they look cryptic, Claude will translate them into plain-language causes.

Customs Delay Escalation Email

3/30

You are an international freight coordinator. <context> A shipment is stuck in customs past the promised clearance window and the client is asking for an update. </context> <inputs> - Shipment ID and commodity: [PLACEHOLDER] - Days stuck in customs: [PLACEHOLDER] - Broker or agent contact name: [PLACEHOLDER] </inputs> <task> Draft an escalation email to the customs broker requesting an update and a firm resolution timeline, plus a shorter parallel email to the client managing expectations. Use realistic placeholder shipment details if none are given. </task> <constraints> - Two distinct emails, clearly labeled. - Professional, urgent tone, never accusatory. - Each email under 150 words. </constraints> <format> Two ready-to-send email drafts with subject lines. </format>

Drafts a broker escalation email and a matching client update for a customs delay.

๐Ÿ’ก

Pro tip: Give the exact number of days already promised and missed, Claude uses that gap to set the tone and the urgency of the ask.

Damaged Freight Claim Summary

4/30

You are a claims and loss prevention coordinator. <context> A shipment arrived with visible damage and the company needs to file a carrier claim. </context> <inputs> - Shipment details (carrier, BOL number, commodity, value): [PLACEHOLDER] - Damage description and whether photos were taken: [PLACEHOLDER] </inputs> <task> Produce a completed freight claim summary ready to submit to the carrier, including an itemized list of damaged goods, claimed value, and a supporting documentation checklist. Invent realistic sample shipment and damage details if none are given. </task> <constraints> - Include an itemized damage table with quantity and value per line. - List required supporting documents (BOL, photos, invoice, inspection report). - State the total claim amount clearly at the bottom. </constraints> <format> A structured claim summary document. </format>

Turns a damage report into a submission-ready carrier claim with an itemized loss table.

๐Ÿ’ก

Pro tip: Note the BOL number and carrier claim portal name if you have them, Claude will format the summary to match what most carrier forms ask for.

Multi-Carrier Shipment Reconciliation Sheet

5/30

You are a logistics data analyst. <context> The team needs to reconcile shipment counts and costs across multiple carrier invoices against internal shipment records. </context> <inputs> - Internal shipment log (ID, carrier, cost): [PLACEHOLDER] - Carrier invoice totals: [PLACEHOLDER] </inputs> <task> Build a reconciliation table comparing internal records to carrier invoices, flagging mismatches over a chosen tolerance, and a summary of total variance by carrier. Use a realistic sample set of 20 shipments across 3 carriers if no data is supplied. </task> <constraints> - Default flag tolerance is $5 per shipment unless a different tolerance is specified. - Sort flagged mismatches to the top. - Include a total variance row per carrier. </constraints> <format> A data table with a variance summary section. </format>

Reconciles internal shipment records against carrier invoices and flags every mismatch worth chasing.

๐Ÿ’ก

Pro tip: Set your own tolerance in dollars before running this, the default of $5 is a starting point, not a rule for your contracts.

Route & Fleet Planning

5 prompts

Weekly Delivery Route Plan

6/30

You are a fleet dispatch supervisor. <context> Dispatch needs a route plan assigning drivers and stops for the coming week. </context> <inputs> - Driver list and vehicle capacity: [PLACEHOLDER] - Delivery stops with addresses and time windows: [PLACEHOLDER] </inputs> <task> Build a weekly route plan assigning stops to drivers and vehicles by day, respecting time windows and vehicle capacity, and grouping stops geographically to reduce drive distance. Invent a realistic sample of 4 drivers and 24 stops if none are given. </task> <constraints> - Balance stop count evenly across drivers. - Group stops geographically by day. - Flag any stop whose time window looks unreachable given the day's route. </constraints> <format> A day-by-day route table plus a short notes section on flagged issues. </format>

Assigns a week of delivery stops to drivers by day, grouped geographically and flagged for conflicts.

๐Ÿ’ก

Pro tip: Include real time windows, not just addresses, that's what lets Claude catch the stop that can't realistically be reached that day.

Multi-Stop Route Optimization Worksheet

7/30

You are a route planning analyst. <context> A single driver has too many stops in one day and needs an optimized stop order to cut backtracking. </context> <inputs> - Stop addresses or zip codes with delivery windows: [PLACEHOLDER] - Starting depot address: [PLACEHOLDER] </inputs> <task> Produce an optimized stop sequence grouped by proximity, an estimated total mileage range, and a fallback order to use if a stop's window is missed. Invent a realistic sample of 12 stops across 3 zip zones if none are given. </task> <constraints> - Present the sequence as a numbered list. - Include an estimated drive time range between stops. - Note any two stops with conflicting time windows. </constraints> <format> A numbered route sequence with a mileage and time estimate table. </format>

Reorders a driver's stop list by proximity and flags any time-window conflicts before the route runs.

๐Ÿ’ก

Pro tip: Group your own stops by zip code first if you have 20 or more, it keeps the sequence realistic instead of an approximate straight-line guess.

Fleet Fuel Cost Comparison Table

8/30

You are a fleet operations analyst. <context> Ops wants to compare monthly fuel spend across vehicle types to decide on a partial fleet conversion. </context> <inputs> - Vehicle list with type, monthly miles, mpg, and fuel price: [PLACEHOLDER] </inputs> <task> Build a comparison table of monthly fuel cost per vehicle and per vehicle type, plus a projected savings estimate if the least efficient 20 percent of vehicles were replaced with a more efficient model. Use a realistic sample fleet of 15 vehicles across 3 types if none is given. </task> <constraints> - Show cost per mile per vehicle. - Sort by cost per mile descending. - State the assumptions used for the savings projection clearly. </constraints> <format> A data table with a savings summary paragraph. </format>

Ranks fleet vehicles by fuel cost per mile and estimates savings from replacing the worst performers.

๐Ÿ’ก

Pro tip: Use your actual local diesel or gas price from this month, not a national average, the savings number changes a lot with local fuel cost.

Driver Shift and Dispatch Schedule

9/30

You are a dispatch coordinator. <context> Dispatch needs a weekly shift schedule covering all delivery routes with backup coverage for callouts. </context> <inputs> - Driver roster with availability: [PLACEHOLDER] - Number of daily routes and shift length rules: [PLACEHOLDER] </inputs> <task> Build a weekly shift schedule assigning drivers to routes and shifts, with one designated backup driver per day. Invent a realistic sample roster of 8 drivers if none is given. </task> <constraints> - Respect any stated maximum consecutive workdays. - Flag any day with no backup coverage. - Keep the format usable as a printable grid. </constraints> <format> A weekly schedule grid with day columns and driver rows. </format>

Builds a weekly driver schedule with backup coverage and flags any day left exposed.

๐Ÿ’ก

Pro tip: List your actual max-consecutive-days rule up front, Claude will enforce it instead of guessing a generic labor rule.

Last-Mile Delivery Zone Coverage Plan

10/30

You are a last-mile operations planner. <context> The company is expanding delivery coverage and needs zones assigned to drivers by volume, not just geography. </context> <inputs> - Service area list (zip codes or neighborhoods) with estimated daily package volume: [PLACEHOLDER] - Number of available drivers: [PLACEHOLDER] </inputs> <task> Divide the service area into balanced delivery zones by estimated volume per driver, and flag any zone likely to be overloaded. Use a realistic sample of 10 zones and 5 drivers if none is given. </task> <constraints> - Aim for roughly even package volume per zone. - Name zones descriptively rather than by number only. - Include a one-line rationale per zone assignment. </constraints> <format> A zone assignment table plus a short rationale section. </format>

Splits a service area into volume-balanced delivery zones and flags any zone at risk of overload.

๐Ÿ’ก

Pro tip: Use your real package volume by zip, not headcount or population, volume is what actually predicts an overloaded zone.

Vendor & Carrier Communications

5 prompts

Carrier Rate Negotiation Email

11/30

You are a procurement and carrier relations manager. <context> An annual rate renewal is coming up and the company wants a lower rate given increased shipment volume. </context> <inputs> - Current carrier name and current rate: [PLACEHOLDER] - Shipment volume change and target rate or discount ask: [PLACEHOLDER] </inputs> <task> Draft a rate negotiation email to the carrier account rep citing volume growth and requesting a specific rate adjustment, plus a short internal talking points list for the follow-up call. Invent realistic sample volume and rate figures if none are given. </task> <constraints> - Keep the email under 200 words. - Lead with the relationship and volume facts before the ask. - Present talking points as a short bullet list. </constraints> <format> One email draft plus a bullet list of call talking points. </format>

Drafts a volume-backed rate negotiation email plus talking points for the follow-up call.

๐Ÿ’ก

Pro tip: Quote your actual shipment volume growth from the last 12 months, a specific percentage lands harder than a general claim of growth.

RFP for a 3PL Warehouse Partner

12/30

You are a supply chain sourcing manager. <context> The company is evaluating third-party logistics providers to outsource warehousing and fulfillment. </context> <inputs> - Current volume (orders per month, SKU count, storage needs): [PLACEHOLDER] - Target region and go-live date: [PLACEHOLDER] </inputs> <task> Produce a request for proposal document covering scope, current volume, required capabilities, evaluation criteria, and a response deadline. Use a realistic sample volume profile if none is given. </task> <constraints> - Include a scoring rubric with at least 5 weighted criteria. - Keep sections clearly numbered. - State a realistic response deadline, 3 to 4 weeks out. </constraints> <format> A structured RFP document. </format>

Builds a complete 3PL RFP with a weighted scoring rubric ready to send to candidate warehouses.

๐Ÿ’ก

Pro tip: Weight the scoring rubric before you send the RFP, not after proposals arrive, it keeps the comparison honest.

Vendor Performance Scorecard

13/30

You are a vendor management analyst. <context> A quarterly review of carrier and 3PL vendors is due, scoring them on reliability and cost. </context> <inputs> - Vendor list with on-time rate, damage rate, cost variance, and responsiveness rating: [PLACEHOLDER] </inputs> <task> Build a scorecard ranking vendors on a weighted composite score, with a one-line recommendation per vendor (renew, renegotiate, or phase out). Invent a realistic sample of 6 vendors if none is given. </task> <constraints> - State the weighting used for each metric. - Sort vendors by composite score descending. - Keep recommendations to one line each. </constraints> <format> A scorecard table with a recommendation column. </format>

Scores and ranks vendors on a weighted composite metric with a clear renew or phase-out call per vendor.

๐Ÿ’ก

Pro tip: Set your own weights for on-time rate versus cost before running this, a cost-driven business and a service-driven one should not use the same split.

Freight Broker Onboarding Checklist

14/30

You are a carrier relations coordinator. <context> A new freight broker is being added to the approved carrier list and needs to be onboarded correctly. </context> <inputs> - Broker company name and MC/DOT number: [PLACEHOLDER] - Insurance status: [PLACEHOLDER] </inputs> <task> Produce an onboarding checklist covering compliance verification, insurance certificate collection, rate agreement signing, and system setup steps, with an owner and due date per step. Invent realistic sample details if none are given. </task> <constraints> - Order steps in the sequence they must happen. - Flag any step that blocks the broker from being dispatched loads. - Keep the checklist to one page. </constraints> <format> A checklist table with columns for step, owner, due date, status. </format>

Lays out every compliance and setup step needed before a new broker can be dispatched a load.

๐Ÿ’ก

Pro tip: Flag the insurance certificate step as blocking, that single missing document is the most common reason a broker onboarding stalls.

Supplier Delay Notification Template

15/30

You are a procurement coordinator. <context> A key supplier has notified the company of a production delay that will push back inbound inventory. </context> <inputs> - Supplier name and affected PO numbers: [PLACEHOLDER] - Original versus new delivery date: [PLACEHOLDER] </inputs> <task> Draft an internal notification to warehouse and sales teams about the delay and its downstream impact, plus a template reply to the supplier requesting a firm revised date and any mitigation options. Invent realistic sample PO and date details if none are given. </task> <constraints> - Keep the internal notice under 150 words. - Clearly state which orders or customers are at risk. - The supplier reply must request a specific commitment date. </constraints> <format> Two templates, internal notice and supplier reply, clearly labeled. </format>

Notifies internal teams of a supplier delay and pushes the supplier for a firm revised date in one pass.

๐Ÿ’ก

Pro tip: List which specific customer orders are tied to the delayed PO, that's what makes the internal notice actionable instead of just informational.

These prompts give you the what. Tutorials give you the why.

Learn when to use extended thinking, how to build Claude Projects, and workflows that compound. 300+ tutorials and growing.

Try AI Academy Free

Standard Operating Procedures

5 prompts

Warehouse Receiving SOP

16/30

You are a warehouse operations manager. <context> New receiving staff need a documented step-by-step procedure for inbound shipments. </context> <inputs> - Warehouse name and receiving dock hours: [PLACEHOLDER] - WMS system name: [PLACEHOLDER] </inputs> <task> Write a numbered standard operating procedure for receiving inbound freight, from dock check-in through putaway, including quality inspection and discrepancy handling steps. Use realistic generic details if specifics are not given. </task> <constraints> - Number every step. - Include a discrepancy escalation sub-section. - Keep steps action-oriented, starting each with a verb. </constraints> <format> A numbered SOP document with a discrepancy handling appendix. </format>

Writes a numbered receiving SOP from dock check-in to putaway with a built-in discrepancy process.

๐Ÿ’ก

Pro tip: Name your actual WMS by system name, Claude will phrase the scanning and confirmation steps to match how that system is used.

Cold Chain Handling SOP

17/30

You are a cold chain compliance officer. <context> The warehouse handles temperature-sensitive goods and needs a documented handling procedure for audits. </context> <inputs> - Product category (frozen, refrigerated, or similar): [PLACEHOLDER] - Required temperature range and monitoring equipment used: [PLACEHOLDER] </inputs> <task> Write an SOP covering receiving, storage, temperature monitoring, and excursion response for temperature-sensitive goods. Invent realistic sample temperature ranges if none are given. </task> <constraints> - State the acceptable temperature range explicitly at the top. - Include a clear excursion response procedure with escalation contacts. - Note that this SOP supports an audit and does not replace regulatory guidance. </constraints> <format> A numbered SOP document. </format>

Documents receiving, storage, and excursion response for temperature-sensitive goods in one SOP.

๐Ÿ’ก

Pro tip: State your real monitoring equipment and alert thresholds, the excursion response section is only useful if it matches what actually triggers your alarms.

Returns Processing SOP

18/30

You are a reverse logistics supervisor. <context> Returned goods are piling up without a consistent process for grading, restocking, or disposal. </context> <inputs> - Return reasons tracked: [PLACEHOLDER] - Restock condition grades and disposal policy used: [PLACEHOLDER] </inputs> <task> Write an SOP for processing returns from receipt through grading, restock, refurbishment, or disposal decision. Use realistic generic grading categories if none are given. </task> <constraints> - Define each grading category clearly. - Include a decision flow for restock versus disposal. - Keep the SOP to numbered steps. </constraints> <format> A numbered SOP document with a grading definitions table. </format>

Turns returns handling into a numbered SOP with clear grading definitions and a restock-or-disposal decision flow.

๐Ÿ’ก

Pro tip: Give your real grading labels if you already use them, even informal ones, consistency in naming matters more than which words you pick.

Forklift and Dock Safety Checklist

19/30

You are a warehouse safety coordinator. <context> The site needs a daily pre-shift safety checklist for forklift operators and dock staff. </context> <inputs> - Forklift fleet size and shift schedule: [PLACEHOLDER] - Applicable safety standard reference, if any: [PLACEHOLDER] </inputs> <task> Build a daily pre-shift safety checklist covering equipment inspection, dock area hazards, and required PPE, with sign-off fields. Use realistic generic checklist items if none are given. </task> <constraints> - Group items by equipment inspection, dock hazards, and PPE. - Include a sign-off line with name, date, and shift. - Note that this checklist supports, but does not replace, formal safety training or a compliance review. </constraints> <format> A printable checklist document. </format>

Builds a daily pre-shift safety checklist covering equipment, dock hazards, and PPE with sign-off fields.

๐Ÿ’ก

Pro tip: List any near-miss incidents from the last few months, Claude will add a specific checklist item aimed at the exact hazard that caused it.

New Driver Onboarding SOP

20/30

You are a fleet training coordinator. <context> New delivery drivers need a consistent first-week onboarding procedure. </context> <inputs> - Vehicle types driven and delivery app or system used: [PLACEHOLDER] - Training duration: [PLACEHOLDER] </inputs> <task> Write a first-week onboarding SOP covering orientation, ride-alongs, system training, and a final competency check-off. Invent realistic sample details if none are given. </task> <constraints> - Structure the SOP by day, Day 1 through Day 5. - Include a final sign-off checklist. - Keep the tone practical and specific, not generic HR language. </constraints> <format> A day-by-day onboarding SOP document. </format>

Lays out a day-by-day first week for new drivers ending in a manager competency sign-off.

๐Ÿ’ก

Pro tip: Name the delivery app your drivers actually use day to day, the system training block is far more useful when it's app-specific.

KPI Dashboards & Performance Reports

5 prompts

On-Time Delivery KPI Dashboard

21/30

You are a logistics performance analyst. <context> Leadership wants a monthly view of on-time delivery performance by carrier and region. </context> <inputs> - Shipment records with carrier, region, and on-time status: [PLACEHOLDER] </inputs> <task> Build an HTML dashboard showing on-time delivery rate overall, by carrier, and by region, with color-coded performance bands (green, yellow, red). Invent a realistic sample of 200 shipments summarized into aggregate stats if no raw data is given. </task> <constraints> - Self-contained HTML with inline CSS, no external libraries. - Define the performance bands explicitly, for example above 95 percent is green. - Include a one-line trend note per carrier. </constraints> <format> A single previewable HTML dashboard artifact. </format>

Renders an on-time delivery dashboard broken out by carrier and region with color-coded performance bands.

๐Ÿ’ก

Pro tip: State your real SLA target before running this, the color bands mean nothing if they are not anchored to the number leadership actually cares about.

Monthly Logistics Cost Report

22/30

You are a logistics finance analyst. <context> Finance needs a monthly breakdown of logistics spend by category for the ops review. </context> <inputs> - Cost categories (freight, warehousing, fuel, labor) with monthly totals and prior month for comparison: [PLACEHOLDER] </inputs> <task> Produce a cost report showing spend by category, month-over-month change, and the top 2 cost drivers with a one-line explanation each. Invent a realistic sample cost breakdown if none is given. </task> <constraints> - Show percentage change alongside dollar change. - Sort categories by spend descending. - Keep each driver explanation to one sentence. </constraints> <format> A cost report with a summary table and a short narrative section. </format>

Breaks down monthly logistics spend by category and names the top 2 cost drivers in plain language.

๐Ÿ’ก

Pro tip: Pull last month's actuals alongside this month's, the whole report is more useful as a trend than a single snapshot.

Warehouse Productivity Scorecard

23/30

You are a warehouse operations analyst. <context> The warehouse manager wants to track picker and packer productivity against targets. </context> <inputs> - Worker or shift data with units picked or packed per hour, error rate, and target rate: [PLACEHOLDER] </inputs> <task> Build a productivity scorecard comparing actual rate to target rate per worker or shift, flagging underperformance and highlighting top performers. Invent a realistic sample of 10 workers if none is given. </task> <constraints> - Sort by variance to target descending. - Flag any error rate above 2 percent. - Use generic labels such as "Picker 1" if real names are not supplied. </constraints> <format> A scorecard table with a flagged-issues summary. </format>

Compares actual versus target productivity per worker and flags underperformance alongside top performers.

๐Ÿ’ก

Pro tip: Use shift-level data instead of names if this is going anywhere near a broader audience, the scorecard works the same either way.

Freight Spend Variance Report

24/30

You are a logistics cost analyst. <context> Freight costs came in over budget this quarter and finance wants to know why. </context> <inputs> - Budgeted versus actual freight spend by lane or carrier: [PLACEHOLDER] </inputs> <task> Produce a variance report showing budget versus actual by lane or carrier, ranking the largest overages, and a likely cause per overage (fuel surcharge, volume increase, rate hike, or accessorial fees). Invent a realistic sample of 8 lanes if none is given. </task> <constraints> - Show variance in both dollars and percent. - Sort by dollar overage descending. - Keep cause attribution to one short phrase each. </constraints> <format> A variance table with a top-3 overage summary. </format>

Ranks freight budget overages by lane or carrier and attaches a likely cause to each one.

๐Ÿ’ก

Pro tip: Include accessorial fees as a separate line if your invoices break them out, they are one of the most common hidden causes of variance.

Quarterly Supply Chain Business Review Deck

25/30

You are a supply chain director. <context> Leadership needs a quarterly business review summarizing supply chain performance for executives. </context> <inputs> - Key metrics (on-time rate, cost per shipment, inventory turns) for the quarter and prior quarter: [PLACEHOLDER] </inputs> <task> Build a slide-by-slide outline for a quarterly business review covering performance summary, key wins, key issues, and next-quarter priorities. Invent realistic sample metrics if none are given. </task> <constraints> - Limit the deck to 8 slides. - Each slide is a title plus 3 to 4 bullet points. - Include one slide dedicated to a corrective action plan for any metric that declined. </constraints> <format> A slide-by-slide deck outline in text form. </format>

Outlines an 8-slide quarterly supply chain review with a dedicated corrective-action slide for anything that slipped.

๐Ÿ’ก

Pro tip: Bring the prior quarter's numbers even if they were bad, the review reads as more credible with a real trend line than a single quarter in isolation.

Most people use 10% of Claude. Tutorials unlock the rest.

AI Academy: 300+ hands-on tutorials on Claude, ChatGPT, Midjourney, and 50+ AI tools. New tutorials added every week.

Start Your Free Trial

Inventory & Warehouse Management

5 prompts

Inventory Reorder Point Calculator

26/30

You are an inventory planning analyst. <context> The team wants clear reorder points to avoid stockouts without over-ordering. </context> <inputs> - SKU list with average daily usage and lead time in days: [PLACEHOLDER] - Safety stock policy: [PLACEHOLDER] </inputs> <task> Calculate a reorder point and suggested order quantity per SKU, and flag any SKU currently below its calculated reorder point. Invent a realistic sample of 12 SKUs if none is given. </task> <constraints> - Show the reorder point formula used. - Flag below-threshold SKUs clearly. - Round order quantities to sensible case-pack sizes if none are specified. </constraints> <format> A data table with a flagged reorder alert section. </format>

Calculates a reorder point per SKU and flags every one already below its threshold.

๐Ÿ’ก

Pro tip: Give your real lead time per SKU if it varies by supplier, a single blanket lead time understates risk on your slowest suppliers.

Warehouse Slotting Plan

27/30

You are a warehouse layout planner. <context> Pick times are too slow because fast-moving SKUs are stored far from the packing area. </context> <inputs> - SKU list with pick frequency and current location zone: [PLACEHOLDER] </inputs> <task> Propose a re-slotting plan moving high-frequency SKUs to prime pick locations, with an estimated reduction in average pick travel. Invent a realistic sample of 15 SKUs across 3 zones if none is given. </task> <constraints> - Rank SKUs by pick frequency. - State the current versus proposed zone per SKU. - Include a brief rationale for the top 3 moves. </constraints> <format> A re-slotting table with a summary paragraph. </format>

Moves your highest-frequency SKUs to prime pick locations and estimates the travel time saved.

๐Ÿ’ก

Pro tip: Pull pick frequency from the last full quarter, not just last month, seasonal SKUs will otherwise get slotted for the wrong season.

Cycle Count Schedule and Log

28/30

You are an inventory control coordinator. <context> The warehouse needs a rolling cycle count schedule to keep inventory accuracy high without a full annual shutdown count. </context> <inputs> - Total SKU count and ABC classification, if available: [PLACEHOLDER] - Count frequency target: [PLACEHOLDER] </inputs> <task> Build a cycle count schedule assigning SKUs to count dates by ABC class, with A items counted most often, plus a blank count log template. Invent a realistic sample ABC breakdown if none is given. </task> <constraints> - A-class counted monthly, B-class quarterly, C-class semi-annually, unless a different frequency is stated. - Keep the log template reusable with columns for expected quantity, counted quantity, and variance. - Present the schedule and the log template as two clearly separate sections. </constraints> <format> A schedule table plus a blank count log template. </format>

Builds an ABC-weighted cycle count schedule plus a reusable count log template.

๐Ÿ’ก

Pro tip: Run your own ABC classification first if you have not already, the schedule is only as good as knowing which SKUs actually deserve monthly counts.

SKU Rationalization Report

29/30

You are an inventory strategy analyst. <context> The catalog has grown cluttered with slow-moving SKUs tying up warehouse space and capital. </context> <inputs> - SKU list with units sold in the last 12 months and current on-hand quantity: [PLACEHOLDER] </inputs> <task> Identify candidate SKUs for discontinuation or clearance based on low turnover relative to on-hand quantity, and estimate the warehouse space or capital that would be freed. Invent a realistic sample of 20 SKUs if none is given. </task> <constraints> - Rank candidates by months of supply on hand descending. - Separate "discontinue" recommendations from "clearance first" recommendations. - State the turnover threshold used. </constraints> <format> A ranked candidate table with a summary recommendation section. </format>

Flags slow-moving SKUs for discontinuation or clearance and estimates the space and capital freed.

๐Ÿ’ก

Pro tip: Use a full 12 months of sales, not a recent quarter, one slow season can otherwise wrongly flag a perfectly healthy seasonal SKU.

Seasonal Demand Forecast Worksheet

30/30

You are a demand planning analyst. <context> The team needs a rough seasonal demand forecast to plan inventory and staffing ahead of a peak period. </context> <inputs> - Last year's monthly sales or shipment volume: [PLACEHOLDER] - Expected growth rate and any known promotions or events: [PLACEHOLDER] </inputs> <task> Build a month-by-month demand forecast applying the growth rate and any noted seasonal spikes, with a called-out peak month and a recommended inventory buildup lead time. Invent a realistic sample of 12 months of prior data if none is given. </task> <constraints> - Show the calculation logic used per month. - Flag the top 2 peak months. - State all assumptions clearly at the top. </constraints> <format> A month-by-month forecast table with an assumptions note. </format>

Projects month-by-month demand from last year's volume and flags the peak months to build inventory ahead of.

๐Ÿ’ก

Pro tip: List any known promotion dates for the upcoming year even if tentative, the forecast is far more useful when spikes are tied to real events, not just a flat growth curve.

Frequently Asked Questions

Copy a prompt, replace the bracketed placeholders with your real shipment, carrier, or inventory data, and paste it into Claude. If you leave a placeholder blank, Claude fills it with a realistic sample so you can see the format before you plug in your own numbers.
No. Every prompt works with sample data if you leave the inputs blank, so you can test the output format before connecting it to your own systems.
Yes. Everything Claude returns, whether it's a table, an SOP, or an HTML dashboard, is plain text or code you can copy into your own tools, spreadsheet, or intranet page and edit freely.
Any Claude plan that lets you paste a few paragraphs of instructions works, including the free tier for shorter reports. Longer dashboards or multi-shipment reconciliations run more reliably on a paid plan with a larger context window.
No. They are written to work with any carrier, 3PL, or warehouse system. Swap in your own carrier names, SKU codes, or platform details in the input fields and Claude adapts the output accordingly.

Prompts are the starting line. Tutorials are the finish.

A growing library of 300+ hands-on tutorials on ChatGPT, Claude, Midjourney, and 50+ AI tools. New tutorials added every week.

7-day free trial. Cancel anytime.