AI Across the Supply Chain

AI in Supply Chain: Real Examples of How Teams Use ChatGPT and Claude

AI in supply chain operations today looks like paperwork, not robot warehouses: teams use tools like ChatGPT and Claude to draft and chase supplier emails, write forecast commentary on their own numbers, notify customers about shipment exceptions, document warehouse SOPs, compare vendor quotes, and turn meeting notes into action items. This page walks through each example with copy-paste prompts.

1-on-1 with Pete Enestrom, on your actual work

Pete Enestrom

Written by Pete Enestrom

Yale & Columbia, ex-Microsoft & Intel — 1-on-1 AI coaching for executives

Pete Enestrom — executive AI coach and Zaigo co-founder

Your coach’s background

YaleCOLUMBIAUNIVERSITYMicrosoft

If you run a distribution business, a 3PL, or the operations side of a manufacturer, here is the honest version of the AI story: the AI in supply chain examples worth your attention right now are not robot warehouses or self-driving trucks. They are text jobs. A supply chain runs on paper-shaped work—purchase orders, supplier email threads, forecast commentary, exception notices, SOPs, rate comparisons—and the current generation of AI tools is very good at exactly that kind of work.

This page covers what operations teams are actually doing with tools like ChatGPT and Claude today. No invented case studies, no company names I can't verify, no percentages lifted from a consulting deck. The examples below are composites from the kind of 20-to-200-person distributors, 3PLs, and manufacturers I coach—businesses where the ops leader still answers carrier emails and the office is three people wearing six hats.

The goal here is fluency, not a project. By the end of this page you will know what these tools can and can't do on the office side of a supply chain, you will have six copy-paste prompts that run this week on a free plan, and you will have a sane way to pick your first task. That is the whole assignment.

How is AI used in supply chain operations today?

AI in supply chain work comes in two very different kinds, and confusing them is where most owners get stuck. The first kind is industrial AI: route-optimization platforms, warehouse robotics, demand-forecasting engines that plug into your ERP. That kind is real, but it requires clean data, integration work, and a real budget, and it is not what this page is about. The second kind is language AI—ChatGPT, Claude, and similar tools—which lives in a browser tab, costs nothing to try, and works on the text your operation already produces every day.

The artificial intelligence in supply chain examples a mid-size operation can run this week all share the same shape. A person pastes in real material—a supplier thread, a rate sheet, this month's numbers, rough notes from the warehouse—and asks for a draft, a summary, or a list of questions. The tool does the typing and the reading. The person keeps the judgment: how hard to push the supplier, which carrier to award the lane, what date to promise the customer. That division of labor runs through every AI in logistics example below.

  • Supplier correspondence: drafting and chasing emails across a 14-message thread
  • Forecast commentary: writing the S&OP narrative around numbers you paste in
  • Shipment exceptions: telling the customer a delivery slipped, plainly and fast
  • Warehouse SOPs: turning a supervisor's know-how into a numbered procedure
  • Vendor comparisons: summarizing competing quotes into one clean table
  • Meeting notes: turning ops-meeting notes into owners, dates, and a recap email

What are supply chain teams doing with ChatGPT and Claude today?

Six examples, one for each paperwork job that fills an ops team's week. Copy the prompts verbatim, replace the [brackets] with your own material, and adjust the last line to taste. The prompt is the easy part—the context you paste in is what makes the output worth reading.

The supplier nudge you keep meaning to sendPrompt

I run operations for a [type of business: regional distributor / 3PL / food manufacturer]. Below is the email thread with my supplier about a late purchase order: [paste the thread]. Do three things: summarize where things actually stand in two sentences, list what is still unresolved, and draft a follow-up email asking for a confirmed ship date and a named contact. Firm but relationship-preserving, under 120 words, no blame language.

The tool does the archaeology on a 14-message thread in seconds. You keep the judgment about how hard to push this particular supplier.

Forecast commentary on your own numbersPrompt

Here are this month's demand numbers by SKU family: [paste your table—actuals vs. forecast, and last year if you have it]. Do not calculate or change any numbers. Write the commentary for our S&OP meeting: the three lines that moved most versus forecast, plausible reasons a person should check (seasonality, a promotion, a lost account), and the questions I should bring to the sales team. Under 200 words.

ChatGPT and Claude reason about numbers you paste in—they do not run your forecast. The arithmetic stays in your spreadsheet; the narrative is what the tool drafts.

The shipment went sideways—telling the customerPrompt

A customer's shipment is delayed. Original delivery date: [date]. New realistic date: [date]. Reason in one line: [carrier delay / port congestion / supplier short-shipped]. Draft a customer email that states the new date in the first sentence, gives the honest reason in one sentence, says what we are doing about it, and sets a specific time for the next update. Under 100 words. Apologize once, plainly—no “we regret any inconvenience.”

Answer first, explain second. Customers forgive a late truck much faster than they forgive a vague email.

Warehouse SOPs out of a supervisor's headPrompt

I want to document how our warehouse handles [process: receiving and putaway / pick-pack for will-call / cycle counts]. Right now the process lives in our lead's head. Here is my rough description from watching it: [paste notes]. Before writing anything, ask me up to six questions about steps I probably skipped—exceptions, damaged goods, partial pallets. Then turn my answers into a numbered SOP a new hire could follow, ending with a short checklist.

“Ask me questions first” is the highest-leverage sentence on this page. The tool is genuinely good at finding the gaps in what you thought you wrote down.

Comparing vendor quotes without the spreadsheet fogPrompt

I am comparing [three] [carriers / suppliers] for [lane or category]. Below are the quotes or rate sheets: [paste them, or paste your notes on each]. Build a comparison table of the terms that matter—price, lead time, minimums, payment terms, anything unusual. Then write a three-sentence summary I could put in front of our owner, ending with what should be clarified before deciding. Do not fill in numbers I did not give you.

“Do not fill in numbers I did not give you” keeps the tool honest. The comparison structure is standard; the numbers are yours.

Ops meeting notes into action itemsPrompt

Here are my raw notes from today's operations meeting: [paste]. Turn them into three lists: decisions we made and who owns each one, issues we raised but did not resolve, and commitments with dates. Then draft a five-line recap email to the team. Bullet points, no filler, no commentary.

Run it the same afternoon, while you can still correct it. By Friday the notes are an archive; today they are a management tool.

What do these AI in supply chain examples have in common?

None of the examples above touches a truck, a forklift, or a conveyor. Every example lives on the office side of the operation, and every example follows the same pattern: a person pastes material the business already has, the tool returns a draft or a list of questions, and a person checks the result before anything leaves the building. The judgment in each example—the pressure on the supplier, the carrier award, the promised date—stays with the person who owns it. That is not a limitation of the technology; it is the correct way to use the technology.

Notice also what these AI use cases in supply chain work do not require: no integration with your TMS or WMS, no software purchase, no IT project. Every prompt on this page runs on the free plans at chatgpt.com or claude.ai, from the browser already on the office computer. The barrier is not budget or infrastructure. The barrier is that somebody has to sit down for twenty minutes with a real supplier thread and try—which is exactly what the checklist below is for.

Where does AI in logistics fall short?

Accuracy first. ChatGPT and Claude write with the same calm fluency when they are wrong as when they are right, and in a supply chain context the wrongness has teeth: an invented lead time, a plausible-sounding Incoterm, a customs rule that doesn't exist. The habit that keeps an operation safe is already built into the prompts above—paste the source document and say “based only on this.” Never let the tool supply a number, a date, or a regulation from memory, and verify anything you plan to repeat to a customer or a carrier.

Confidentiality second. Treat anything you paste as shared with an outside vendor. Customer contract pricing, supplier terms, anything under NDA, and personal information about employees are all out—unless your company has a written policy and a business plan that explicitly allow it. Many operations I talk to have no written rule at all, and that gap is worth closing before the habit spreads on its own; this site publishes a plain-English AI usage policy template you can adapt in an afternoon. When in doubt, strip the names and figures and ask the structural question instead.

Finally, the tool has never seen your operation. ChatGPT knows the generic version of a rate negotiation, a cycle-count procedure, an exception email—the tool does not know your lanes, your customers' receiving windows, or which of your carriers actually answers the phone. That gap is permanent, and it is the reason every example above ends with a person checking the work.

What makes a good first AI task for an operations team?

Pick the first task the way you'd pick a first job for a new office hire. Six tests—if a task passes all six, the task is a good candidate for this week.

  • It happens every week—supplier chases, exception emails, meeting recaps—not once a quarter
  • The input is text you already have: an email thread, a rate sheet, rough notes, pasted numbers
  • You can check the output in under two minutes because you know the right answer
  • A wrong draft costs nothing, because a person reads everything before it leaves
  • The material contains no contract pricing, NDA-covered terms, or personal information
  • One specific person owns trying it—“the company should look into AI” is how nothing happens

What changes when someone teaches you?

Everything on this page is yours to run this week, alone, at no cost—and for a lot of owners, self-teaching is the right plan for a while. The pattern I see in coaching is consistent: month one is delight, month two is a plateau. The generic prompts work, and the open questions become specific to your operation—which workflows to rebuild first, how to get the purchasing desk and the warehouse leads using the tools under the same written rules, and how to capture a twenty-year supervisor's know-how while he is still answering questions.

That is the point where a human teacher—not an AI coach bot, not another webinar—earns the fee. In a 1-on-1 session we open your actual supplier threads, rate sheets, and meeting notes, find the hours these tools can genuinely hand back to your people, and build the prompts and habits around your operation, your customers, and your risk tolerance. This page is the map. Coaching is walking it together on your floor.

1-on-1 coaching

Bring these to your team.

Examples show what's possible. A working session makes them yours—on your operations, with your people.

Format1-on-1Sessions
LocationNYCor Remote
Duration2-4 hrsFocused
ResultClarityWalk away ready
Pete Enestrom in a 1-on-1 coaching session

Your coach

Coached by Pete Enestrom

Yale and Columbia grad, former Microsoft and Intel, and a venture-backed exited founder. Pete has spent the last four and a half years going deep on every major AI tool, and he teaches the way operators learn: on your real work, at your pace, with nothing assumed.

YaleCOLUMBIAUNIVERSITYMicrosoft
Pete Enestrom's signature

Common questions

Straight answers, the way I'd give them across a table.

Keep reading

Beyond coaching

When the workflow needs to be encoded, not just learned — that's what our team at Zaigo builds.