Skip to content

Reorder warnings with draft purchase orders

Watches stock in a small business ERP and warns early from past usage, before a threshold is crossed. It compares vendors on price, duties, delivery time and reliability, then prepares a purchase request that only becomes a draft order when a person presses the button.

OperationsWorks with Claude Desktop with MCP · n8n+1Community example

What it does

  • Reads stock levels and past usage from the ERP on a schedule
  • Flags items that will run out before the next delivery, not just ones below a threshold
  • Compares candidate vendors on price, taxes and duties, lead time and past reliability
  • Writes a purchase request with the chosen vendor and the reasons the others lost
  • Explains the request in plain words on request, with every number taken from the data, not the model

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Creating the draft purchase order, with the approver recorded
  • Sending anything to a vendor

You decide what happens next.

More about this workflow

This setup is for operators and managers who keep the busywork moving. It takes a repeat chore off your plate and hands back something you can check quickly.

First, it reads stock levels and past usage from the ERP on a schedule. Next, it flags items that will run out before the next delivery, not just ones below a threshold. Then it compares candidate vendors on price, taxes and duties, lead time and past reliability. After that, it writes a purchase request with the chosen vendor and the reasons the others lost. Finally, it explains the request in plain words on request, with every number taken from the data, not the model. It works with your accounting app and chat, each on its own login with limited access.

You get the prep work done and waiting for you. The agent stops and asks for your yes before creating the draft purchase order, with the approver recorded and sending anything to a vendor, and says plainly if a step cannot be undone.

“Nothing is ordered until a person presses Create order”
vivek-vpc vivek-vpc on GitHub · Oct 25, 2026
Before you startAccounting app · Chat accessScoped permissionsClaude Desktop with MCP or n8n
Explore required tools and model recommendations

Tools and access

  • QuickBooks

    Handles the accounting app part of this job. Grant accounting data, no payments.

    API required: Yes. Needs an Intuit developer app with OAuth.

  • Slack

    Handles the chat part of this job. Grant a bot token in the channels it needs.

    API required: Yes. Needs a Slack app created in your workspace. It gets a bot token with the scopes you approve.

Official links only. Not sponsored, no affiliate links.

Model recommendations

Best pick

GPT-6.1 Sol

Cheap cached input suits jobs that rerun the same instructions each week.

$2 per million input tokens, $10 per million output tokens, for prompts up to 272K tokens. Longer prompts cost $4 in and $15 out.

OpenAI docs as of October 11, 2026

Cheaper backup

Gemini 3.5 Flash-Lite

Low cost for simple data pulls and matching.

$0.30 per million input tokens, $2.50 per million output tokens.

Google docs as of October 11, 2026

Our own picks. Not sponsored, no affiliate links.

Build your prompt

Add your details, then copy the prompt into your tool.

1Your details

Fill these in and the prompt updates as you type.

e.g. erpnext

how many weeks of history to use

what matters most, price or lead time

web console, telegram or whatsapp

2Your prompt

4 of 4 still empty
Fill these in before you run it: [ERP SYSTEM: e.g. erpnext] [USAGE LOOKBACK: how many weeks of history to use] [VENDOR SCORING: what matters most, price or lead time] [APPROVAL CHANNEL: web console, telegram or whatsapp] You are the Reorder warnings with draft purchase orders agent. Watches stock in a small business ERP and warns early from past usage, before a threshold is crossed. It compares vendors on price, duties, delivery time and reliability, then prepares a purchase request that only becomes a draft order when a person presses the button. Use only the details filled in above. If any [BRACKETED] item is still blank or unclear, stop and ask for it first. Do not guess. What you do on your own: - Reads stock levels and past usage from the ERP on a schedule - Flags items that will run out before the next delivery, not just ones below a threshold - Compares candidate vendors on price, taxes and duties, lead time and past reliability - Writes a purchase request with the chosen vendor and the reasons the others lost - Explains the request in plain words on request, with every number taken from the data, not the model What you must never do without a yes from a person: - Creating the draft purchase order, with the approver recorded - Sending anything to a vendor Rules: - Before any step on the list above, stop and ask. Say in plain words what you want to do, who it affects, and whether it can be undone. - If something cannot be undone, say so first, in one short line. - Write drafts, not final actions. A person sends, pays, posts, or deletes. - Keep a short log of every action you took and every source you read. - If you are unsure, ask instead of guessing.
View run instructionsPaste into: Claude Desktop with MCP, n8n, LangGraph

Your answers stay in this browser only.

Run your workflow

Connect your tools with only the access this setup needs, then follow these steps.

Steps

Do these in order. Test on old data before it touches live work.

  1. 1Connect QuickBooks with its own login, not yours. Grant accounting data, no payments.
  2. 2Connect Slack with its own login, not yours. Grant a bot token in the channels it needs.
  3. 3Paste the prompt where your harness takes instructions. See the note under the Copy button.
  4. 4Do a dry run on old or test data first. Check every draft and every stop point by hand before you let it near live work.
  5. 5Read its log after the first real run. Only widen access once a week of runs looks clean.

Safeguards and trust score

The score describes this example setup’s access, approval boundaries, ability to undo changes, and scope.

Access18 / 30

Can draft things that send or spend, so it sits close to risky actions.

Human approval30 / 30

Waits for a yes on: creating the draft purchase order, with the approver recorded, sending anything to a vendor.

Undo and logs14 / 20

Proposes changes to live records, so the setup needs a change log and a way back.

Scope18 / 20

Runs on its own login across 2 tools. Fewer connections means a smaller blast radius.

How to raise it

  • Access: Take away its ability to send, post or spend. Let it only write drafts, and have a person press send or pay from their own account +6
  • Undo and logs: Stop it from editing live records. Have it write the change as a proposal you apply, and keep a log of every change with a way to roll it back +3
  • Scope: Run it on one tool only, with its own login that can see just what this job needs +2

Do all of these to reach 91, up from 80.

Want help getting there? Get an AI Trust Audit from Pixeldesigns

Reviewed by Trustcase (example setup). How scoring works

Embed badge

Show this trust score on your site or README. It links back here.

Trustcase trust score badge
Markdown
[![Trustcase trust score for Reorder warnings with draft purchase orders](https://trustcase.dev/badge/reorder-warnings-with-draft-purchase-orders.svg)](https://trustcase.dev/use-cases/reorder-warnings-with-draft-purchase-orders)
HTML
<a href="https://trustcase.dev/use-cases/reorder-warnings-with-draft-purchase-orders"><img src="https://trustcase.dev/badge/reorder-warnings-with-draft-purchase-orders.svg" alt="Trustcase trust score for Reorder warnings with draft purchase orders" height="20"></a>

Other workflows that use the same tools

  • Ticket triage

    Support. Sorts new tickets by topic and urgency so the right person sees them first.

  • Incident timeline

    Engineering. Builds the timeline during an outage so people can focus on the fix.

  • Client site request handler

    Engineering. Turns a client's text message about their website into a proposed code change ready for review. Made for a freelancer who maintains a small site for a client.