Custom GPT: Build a Supply Chain Report Writing Assistant

What This Builds

You'll create a Custom GPT — a specialized version of ChatGPT — that produces supply chain reports, executive summaries, and supplier communications that match your organization's exact format, language, and style. Unlike custom instructions (which apply globally), this GPT is specifically tuned for supply chain writing, includes example templates, and can produce consistently formatted outputs every time. It becomes a team-shareable tool: any analyst on your team can use it.

Prerequisites

• ChatGPT Plus subscription ($20/month — required for Custom GPT builder)
• Comfortable using ChatGPT for SC writing tasks (Level 3)
• Sample reports you've written previously (used to train the style)
• Cost: $20/month (ChatGPT Plus)

The Concept

A Custom GPT is like building a specialized coworker who exists only to write supply chain reports in your organization's style. You define the persona, the knowledge base, the output formats, and the writing rules once — and then anyone who opens the GPT gets a pre-configured assistant that already knows what a "weekly inventory status report" at your company looks like, what metrics you track, and how your leadership wants information presented.

Build It Step by Step

Part 1: Gather your materials

Before building, collect:

1. 2–3 examples of your best past reports — weekly inventory status, monthly KPI report, or S&OP summary (sanitized of confidential data if needed)
2. Your key metrics and their targets — OTIF target, inventory turns target, forward cover target, etc.
3. Your audience descriptions — who reads each report and what they care about

Part 2: Open the Custom GPT Builder

1. Log into ChatGPT Plus at chatgpt.com
2. Click the profile icon → My GPTs → Create a GPT
3. You'll see the GPT editor with a Configure tab and Preview tab

Part 3: Configure the GPT

Name: "SC Report Writer — [Your Company]"

Description: "Writes professional supply chain reports, executive summaries, and supplier communications in our standard format and style."

Instructions field — paste this (customize the bracketed sections):

You are a Supply Chain Report Writing Assistant for a [company type — CPG / retailer / manufacturer] supply chain analyst team.

YOUR PURPOSE:
Write professional supply chain reports, executive summaries, supplier emails, and analytical narratives that match our standard format and language style.

OUR SUPPLY CHAIN CONTEXT:
- Industry: [your industry]
- Key metrics tracked: [OTIF, inventory turns, forward cover, MAPE, fill rate, days of supply — add your targets]
- ERP system: [SAP / Oracle / NetSuite]
- Reporting audience: [describe your stakeholders]

REPORT FORMATS YOU KNOW:

WEEKLY INVENTORY STATUS REPORT (150-200 words):
- Open: Overall portfolio health in 1 sentence
- Section 2: "At-Risk Items" — bulleted list of SKUs with <[X] days of supply, cause, mitigation status
- Section 3: "Overstock Positions" — bulleted list with excess inventory quantified in days/$
- Close: "Watch for Next Week" — 1-2 bullets of items to monitor

S&OP EXECUTIVE SUMMARY (200-250 words):
- Opening: 3-sentence situation summary (demand context, supply context, current inventory position)
- Key Tensions: 2-3 bullets of the critical trade-offs for leadership to understand
- Decisions Needed: numbered list of specific decisions required, with options and implications
- Close: Forward look

SUPPLIER ESCALATION EMAIL:
- Subject: "[ESCALATION] PO #[number] — [Supplier Name]"
- Para 1: What the issue is (specific, factual)
- Para 2: Business impact of delay (days of supply, revenue at risk, customer impact)
- Para 3: Specific action required and deadline
- Sign-off: Professional close

ROOT CAUSE ANALYSIS:
- Header: Event summary (what, when, financial impact)
- Section 1: What Happened (timeline, chronological)
- Section 2: Root Causes (2-4 causes with evidence, organized by contributing factor)
- Section 3: Corrective Actions (owner, action, target date)

WRITING RULES:
- Lead with the so-what, not the methodology
- Use quantified language wherever possible (X%, $X, X days)
- For executive audiences: no supply chain jargon without definition
- For SC audiences: use standard SC terminology freely
- Be direct. No filler phrases. No unnecessary hedging.
- Never say "it is important to note that" or "it should be noted"

WHEN GIVEN RAW DATA OR BULLET POINTS:
1. Identify the appropriate report format
2. Ask for clarification only if critical numbers are missing
3. Produce the formatted output immediately
4. Offer: "Would you like me to adjust the tone, length, or focus?"

Part 4: Add Knowledge files (optional but powerful)

In the Knowledge section, click Upload files and upload:

• A sanitized example of your best weekly inventory report
• A sanitized example of your S&OP summary
• A one-page document with your key metrics and targets

The GPT will use these as style references, producing output that matches your organization's actual format.

Part 5: Set conversation starters

Add these as conversation starters users will see when opening the GPT:

• "Write this week's inventory status report"
• "Write S&OP executive summary"
• "Write a supplier escalation email"
• "Write a stockout root cause analysis"

Part 6: Save and share

Click Save. On the privacy setting: choose Only me if the content is company-specific. If you want to share with your team, choose Anyone with a link and share the link with colleagues.

Real Example: Team-Wide Deployment

Scenario: You've set up the SC Report Writer GPT and shared it with your 5-person SC analyst team. Each analyst uses it for their assigned categories.

Before: Each analyst spent 90+ minutes writing their portion of the weekly report in slightly different formats. The roll-up always needed editing.

After: Each analyst pastes their bullet-point findings into the GPT, gets a properly formatted section in 2 minutes, and the consolidated report is consistent in format and language across all sections. Total team time on report writing: 30 minutes instead of 7.5 hours.

Unexpected benefit: New analysts onboard faster because the GPT embeds the "house style" — they produce professional-grade reports from week 1 instead of week 6.

What to Do When It Breaks

• Output doesn't match your format → Paste an example of the format you want and say "Match this format exactly for all future outputs." If needed, update the Instructions field with the example.

• GPT ignores specific metrics or targets → Make sure your targets are explicitly in the Instructions field (e.g., "OTIF target is 97%, not 95%"). Knowledge files are good for style; specific numbers belong in Instructions.

• Team members get different output quality → Share the exact conversation starters with the team so they phrase inputs consistently. The quality of the output depends heavily on the quality and completeness of the input.

Variations

• Simpler version: Use Level 3 custom instructions in ChatGPT — same concept but without the Custom GPT builder, and not shareable with a team.
• Extended version: Add a prompt chain: users paste bullet points → GPT writes the narrative → GPT then writes a 3-sentence email to send the report with key highlights to the distribution list.

What to Do Next

• This week: Build and test the GPT with your actual report formats. Compare the output to what you normally write.
• This month: Share with your team and run it for 4 consecutive weekly reports. Track actual time saved.
• Advanced: Connect the GPT to Power Automate (Level 4 automation guide) so data flows in automatically and reports are distributed without any manual steps.

Advanced guide for supply chain analysts. Custom GPT creation requires ChatGPT Plus ($20/month). Keep proprietary data out of public or team-shared GPTs — share via link only within your organization.