PROMPT BRO
Purchase desk

One purchase request list from every team

Three departments request the same item. Stores has it in the next rack.

Tested Claude Opus 5.5, medium effort · 15 Nov 2026 · on the practice files

By hand1–2 hrs
With AI15 min
Per week · estimate
Easier on your office computer.Send to my computer
I usePick yours. We'll show the right steps.

Make a request sheet

Use request ref, department, SKU, qty, approved need and current stock in same unit. Confirm duplicate refs locally.

First time? Try it on fake data first:

Privacy Remove bank account numbers, PAN, personal phone numbers and emails. Use vendor business names or codes, item codes and approved commercial details.

Fill the orange boxes
You send (the "prompt": the message you paste into your AI tool)
purchase-requests.xlsx

Whenever I send the next details, use this format. Request period: [Request period] Consolidation rule: [Consolidation rule] I'm attaching purchase-requests.xlsx. A. Flag duplicates and unapproved rows; combine valid requests by SKU. B. Compare total requested with available stock once per SKU; calculate proposed shortage, no order. Treat stock in the file as 'as supplied, not verified' unless the file, or a record I supply from an earlier step (for example a dated count sheet or an approval of verified quantities), shows it comes from a physical count or software report with a date; label the shortage provisional until stores confirm. Values in my approved rule or input files (for example safety stock, reorder level or approved buy quantities) are supplied facts, not unverified claims; only on-hand stock needs a count or report. Do not hold a clean line for anything else. Label each stock figure exactly once as supplied (from the file), verified (dated count, software report or an earlier-step record) or provisional (awaiting stores), and keep that label through every total. C. List held requests and questions for department/stores. Use only supplied facts, quotes and approved terms. Flag missing GST, freight, payment days or delivery instead of assuming. Check stock against physical count or software before ordering. A person checks before sending, ordering, paying or posting.

Set it up once. Save the approved format and comparison rules, without vendor records. Pick your tool at the top to see how.

After that, each time: send the new details and confirm the latest approvals and stock.

First time? Try it in a normal chat: paste and send.

Which model? Use your tool's strongest model with thinking turned on.

In your AI tool: attach the files with the + button, paste, send.

What you'll get back (example, from the practice files)
3valid requests
2held rows
8P1 shortage
  • R2Repeated ref. Both occurrences held.
  • P118 requested. 10 available; 8 shortage.
  • P2Covered. 5 requested, 8 available.
Before you trust it

Then send this: Recount duplicate refs, sum valid demand by SKU and subtract stock once.

If it goes wrong
Subtracts stock each row

Reply: "Group SKU first."

Drops duplicate silently

Reply: "Hold both and verify."

Orders automatically

Reply: "Shortage proposal only."

Sir ne bola urgent. Ab bolo: ho gaya.

Did it work?