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
Make a request sheet
Use request ref, department, SKU, qty, approved need and current stock in same unit. Confirm duplicate refs locally.
Privacy Remove bank account numbers, PAN, personal phone numbers and emails. Use vendor business names or codes, item codes and approved commercial details.
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.
What is that?
A Project is a folder in ChatGPT that keeps your instructions and files for every chat inside it. It's on the free plan too. Checked 14 Nov 2026.
What is that?
A Project in Claude is a workspace with its own instructions and files that every chat inside it uses. Checked 14 Nov 2026.
What is that?
A Gem is a custom Gemini that loads your instructions before every chat. Free on every plan; you create it on a computer. Checked 14 Nov 2026.
What is that?
Signed in with a work account, Microsoft's Copilot Chat applies enterprise data protection: your prompts aren't used to train its models. Checked 14 Nov 2026.
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.
Keep your actual records in your own workbook; ask AI for the local method using headings and rules only.
Excel A:F request ref, dept, SKU, qty, approval, available stock. Rule [Consolidation rule]. Give COUNTIF duplicate flag for every occurrence, approved valid demand, unique SKU summary with SUMIFS demand, check consistent stock per SKU, subtract stock once and floor shortage at zero. No order. Tell me exactly where to paste formulas or set up the local steps. Use fictional examples only; do not ask for actual customer, employee or vendor records.
Run the method locally; verify every exception against source records and obtain approval before acting.
- R2Repeated ref. Both occurrences held.
- P118 requested. 10 available; 8 shortage.
- P2Covered. 5 requested, 8 available.
Then send this: Recount duplicate refs, sum valid demand by SKU and subtract stock once.
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?
If your whole team does this, we'll set it up for all of them in one session.