Welcome to The Ops Digest!

Each week, we drop no-BS insights and one AI prompt to cut wasted costs, tighten workflows, and eliminate manual grunt work.

Today: your reps are spending 20 minutes answering questions that your inventory data could handle in seconds. We're giving you a Claude Skill that turns stock checks, lead time lookups, and substitute recommendations into a 30-second conversation.

Your Rep Just Spent 20 Minutes Answering a Question

It's 2:15 PM on a Tuesday. A customer calls your rep: "Hey, do you have 200 units of the 3/4-inch stainless tee fitting in stock? And if not, what's close?"

The rep puts the customer on hold. Logs into the ERP. Searches for the SKU. Checks the warehouse in Dallas. Checks the warehouse in Houston. Finds 140 in one, 80 in the other. Then the customer asks about the carbon steel version too, so the rep starts over. Now they're looking up lead times because the 316 stainless is on backorder. Then pricing, because this customer has a negotiated discount.

Fifteen, maybe twenty minutes later, the customer has their answer.

This happens dozens of times a day across your sales team. And every one of those lookups pulls a rep away from the calls that actually move deals forward.

Manual order entry is keeping your team buried in busywork

Are they still manually keying in orders?

Your team ought to spend their time on work that actually needs them.

Book a free 20-minute Y Meadows Strategy Session to learn how Y Meadows automates order entry with rules-based validation so nothing slips through.

👉 See it in action

Why The Problem Is Bigger Than It Looks

The availability-check tax doesn't show up on any dashboard. Nobody tracks "minutes spent navigating the ERP." But the aggregate cost is significant.

• According to Salesforce's State of Sales research, reps spend only 28-30% of their week actually selling. The rest goes to admin tasks, data entry, internal meetings, and information lookups. (Salesforce, 2024)

• Forrester's Activity Study found that the average rep loses about 14 hours per week to administrative work. That's nearly two full selling days, gone. (Forrester)

• McKinsey's B2B Pulse found that B2B buyers will actively look for another supplier if they can't get product availability information quickly, listing it alongside real-time customer service as a core loyalty requirement. (McKinsey)

That last one is the kicker. Your customers aren't patient about this anymore. They've been trained by Amazon and by competitors with better portals. When they call your rep and the answer takes 20 minutes, they're not impressed by thoroughness. They're annoyed.

Build It: The Instant Availability Check Skill

This is a Claude Project that acts as a product lookup desk for your reps. They type (or paste) a customer question in plain English, and the skill checks it against your actual inventory data, lead time tables, and substitution maps. The answer comes back in seconds, formatted so the rep can read it to the customer on the phone or paste it into an email.

One AI concept this week: a Claude Project with structured reference data. If you've followed along with earlier issues (the quote verification build, the account handoff engine), this will feel familiar. Same idea, different use case.

Step 1: Create the Project

Go to Claude.ai → Projects → Create New Project. Name it "Product Availability Desk."

Step 2: Paste This Skill Definition Into Your Custom Instructions

You are the Product Availability Desk for [Your Company Name]. You answer product availability questions instantly using the reference documents uploaded to this project.

## HOW REPS WILL USE THIS

Reps will type or paste customer questions like:
- "Do we have 200 of SKU-4412 in stock?"
- "Customer needs 3/4 inch stainless tee fittings, 500 units, by next Friday"
- "What's the lead time on the 2-inch PVC Schedule 80 coupling?"
- "Customer asked for SKU-7790 but we're out. What's the closest substitute?"

## FOR EVERY QUERY, PROVIDE:

1. AVAILABILITY CHECK
   - Search the inventory snapshot for the requested product
   - Show: SKU, description, quantity on hand by warehouse/location
   - If multiple warehouses have stock, show all locations and quantities
   - If total available meets the requested quantity, say so clearly
   - If total available falls short, say by how much

2. LEAD TIME (if product is out of stock or insufficient quantity)
   - Check lead time data for this product or category
   - Show: supplier, expected lead time in business days
   - If a restock date or incoming PO is noted in the data, include it

3. SUBSTITUTES (if product is unavailable or customer asks)
   - Check the substitution map for approved alternatives
   - Show: substitute SKU, description, key differences from the original
   - Check availability of each substitute
   - Only suggest substitutes that are listed in the substitution map. DO NOT invent substitutes.

4. PRICING (if pricing data is uploaded)
   - Show list price for the requested product
   - If the rep mentions a customer name and customer-specific pricing exists, show that instead
   - Flag if the quantity qualifies for a volume tier break

5. RESPONSE SUMMARY
   - Write a 2-3 sentence plain-English summary the rep can read directly to the customer or paste into an email
   - Tone: helpful and specific, not salesy

## RULES
- ONLY use data from the uploaded reference documents
- If a product is not found in the uploaded data, say: "[PRODUCT NOT FOUND] - This SKU/description does not appear in the current inventory data. Check the ERP directly or ask ops."
- NEVER invent stock levels, lead times, or prices
- If data is stale (check the date on the inventory file), flag it: "Note: Inventory data is from [date]. Stock levels may have changed."
- Round response time: aim for the shortest accurate answer possible

Step 3: Upload Your Reference Data

This is where the value lives. The skill is only as good as the data you give it. You'll want four files (use whatever you have, skip what you don't):

• Inventory snapshot (CSV or Excel) with SKU, description, quantity on hand, and warehouse location. This is the core file. Everything else is a bonus.

• Lead time table with SKU or product category, supplier name, and quoted lead time in days. If you have actual vs. quoted lead times (from our vendor lead time issue), even better.

• Substitution map listing which products can replace which. This is the file most companies don't have in a clean format, and it's the one that saves the most time on the phone. Even a partial list helps.

• Price book (optional) with SKU, list price, and any volume tier breaks. If you built the grounded quoting project from our AI hallucination issue two weeks ago, you already have this file ready.

Where to Find Your Data (by ERP System)

The inventory snapshot is the must-have. Here's where to pull it:

• SAP: Transaction MB52 (Warehouse Stocks) or MMBE (Stock Overview). Export to spreadsheet.

• NetSuite: Reports → Inventory → Inventory Valuation or Quantity Available. Use the CSV export.

• Epicor (Kinetic): Inventory → Stock Status Report or Part Tracker. Export to Excel.

• Sage: Inventory → Reports → Stock Status Report. Some versions require the Crystal Reports viewer for export.

• Microsoft Dynamics 365: Inventory Management → Inquiries → On-hand Inventory, or run the "Inventory On-hand" report under IM reports.

Important: these files go into the Claude Project, not into the rep's hands. You (or your ops person or admin) upload the inventory snapshot, lead time table, substitution map, and price book directly into the project's knowledge base. The reps never touch these files. They just open the project and start asking questions. All the reference data is already there waiting for them.

The freshness question; an inventory snapshot is stale the moment you export it. For most distributors, a Monday morning manual refresh works fine as a starting point. But if your stock moves fast, you can do better.

Most ERPs can schedule a report to run automatically and export to a file, either to a shared drive or to email. Set your inventory snapshot to run every hour during business hours. Then use a simple automation (a scheduled script, a Power Automate flow, or even a Zapier trigger on the email attachment) to upload that file to your Claude Project, replacing the old one. Now your reps are working with data that's at most an hour old instead of a week old, and nobody has to remember to do the export manually.

Either way, build this into the rep's workflow: the skill gives the fast first answer, the ERP confirms before the order goes in.

The File Nobody Has (But Everyone Needs)

Most companies can export inventory and pricing. The substitution map is the one that usually doesn't exist in a clean format.

Right now, substitution knowledge lives in the heads of your most experienced reps and warehouse staff. When SKU-4412 is out of stock, veteran rep Sarah knows that SKU-4418 is the same fitting in 304 stainless instead of 316, and that 80% of customers won't care about the difference for non-corrosive applications. The new rep doesn't know that. They tell the customer it's out of stock and suggest calling back next week.

Building the substitution map takes some effort upfront. A simple spreadsheet with four columns works: Original SKU, Substitute SKU, Key Differences, and Notes (any caveats, like "not rated for high-temp applications"). Start with your top 100 SKUs by volume. You don't need the full catalog on day one.

And here's the bonus: once that map exists inside a Claude Project, every rep on your team has access to Sarah's 15 years of product knowledge. That institutional memory stops being a single point of failure.

What This Looks Like in Practice

Rep types into the Claude Project while the customer is still on the phone:

Manual order entry is relentless.

It just keeps piling up, stealing time from the work only your team can do.

Book a free 20-minute Y Meadows Strategy Session to see how Y Meadows automates order entry with rules-based validation built in, so your team can focus on the work that needs them.

👉 Book a 20-min walkthrough →