Skip to content

Weekly purchasing review with late delivery chasers

Once a week it works through purchase orders in a database you own: approvals waiting with their delivery deadlines, items late after partial receipts, invoice prices that differ from the order, and suppliers overdue a review. It drafts supplier chasers and leaves approvals and payments to you.

OperationsWorks with Claude Code · Cursor+1Community example

What it does

  • Lists draft orders waiting for approval with delivery deadlines and remaining budget by currency
  • Flags items late after partial receipts and orders quiet for fourteen days
  • Compares invoice unit prices and quantities against the order and goods received
  • Drafts a delivery chaser to a supplier from the order history
  • Renders a weekly snapshot for the Monday purchasing meeting

Your approval boundaries

Approval required

These actions always wait for your yes:

  • Approving or cancelling any order
  • Sending a chaser to a supplier
  • Paying anything

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 lists draft orders waiting for approval with delivery deadlines and remaining budget by currency. Next, it flags items late after partial receipts and orders quiet for fourteen days. Then it compares invoice unit prices and quantities against the order and goods received. After that, it drafts a delivery chaser to a supplier from the order history. Finally, it renders a weekly snapshot for the Monday purchasing meeting. It works with your database, accounting app and email, 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 approving or cancelling any order, sending a chaser to a supplier and paying anything, and says plainly if a step cannot be undone.

“Files stay on your machine; nothing sends or pays.”
Enterprise DNA Enterprise-DNA-OS on GitHub · Oct 7, 2026
Before you startDatabase · Accounting app accessScoped permissionsClaude Code or Cursor
Explore required tools and model recommendations

Tools and access

  • Supabase

    Handles the database part of this job. Grant a role limited to one table.

    API required: Yes. Needs a Supabase project and an API key. Give the agent a role limited to one table.

  • QuickBooks

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

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

  • Gmail

    Handles the email part of this job. Grant read-only plus compose (drafts) scopes.

    API required: Yes. Needs a Google Cloud project with an OAuth app and the Gmail API turned on. The agent signs in through OAuth with only the scopes you pick.

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.

2Your prompt

4 of 4 still empty
Fill these in before you run it: [PURCHASE ORDER EXPORT OR DATABASE] [BUDGETS BY CURRENCY] [APPROVAL RULES] [SUPPLIER REVIEW CADENCE] You are the Weekly purchasing review with late delivery chasers agent. Once a week it works through purchase orders in a database you own: approvals waiting with their delivery deadlines, items late after partial receipts, invoice prices that differ from the order, and suppliers overdue a review. It drafts supplier chasers and leaves approvals and payments to you. 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: - Lists draft orders waiting for approval with delivery deadlines and remaining budget by currency - Flags items late after partial receipts and orders quiet for fourteen days - Compares invoice unit prices and quantities against the order and goods received - Drafts a delivery chaser to a supplier from the order history - Renders a weekly snapshot for the Monday purchasing meeting What you must never do without a yes from a person: - Approving or cancelling any order - Sending a chaser to a supplier - Paying anything 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 Code, Cursor, Claude Desktop with MCP

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 Supabase with its own login, not yours. Grant a role limited to one table.
  2. 2Connect QuickBooks with its own login, not yours. Grant accounting data, no payments.
  3. 3Connect Gmail with its own login, not yours. Grant read-only plus compose (drafts) scopes.
  4. 4Paste the prompt where your harness takes instructions. See the note under the Copy button.
  5. 5Do 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.
  6. 6Read 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: approving or cancelling any order, sending a chaser to a supplier, paying anything.

Undo and logs14 / 20

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

Scope16 / 20

Runs on its own login across 3 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: Cut it down from 3 connected tools to the 2 it needs most, each with its own limited login instead of your full account +2

Do all of these to reach 89, up from 78.

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 Weekly purchasing review with late delivery chasers](https://trustcase.dev/badge/weekly-purchasing-review-with-late-delivery-chasers.svg)](https://trustcase.dev/use-cases/weekly-purchasing-review-with-late-delivery-chasers)
HTML
<a href="https://trustcase.dev/use-cases/weekly-purchasing-review-with-late-delivery-chasers"><img src="https://trustcase.dev/badge/weekly-purchasing-review-with-late-delivery-chasers.svg" alt="Trustcase trust score for Weekly purchasing review with late delivery chasers" height="20"></a>
  • New hire access plan from a role matrix with two approvals

    When a hire webhook arrives, code builds a least privilege access plan from a role matrix and the model only fills in words. People Ops approves the plan, and IT must also approve any admin or production access. Accounts are created without duplicates and rehires are reactivated rather than recreated.

  • Duplicate vendor payment check with a payment hold on approval

    Answers back office questions like whether a vendor was paid twice. A code based tool finds the duplicates, high dollar exposure pauses the run for a person, and only an approved result places a payment hold. Every step lands in an audit trail.

  • Farm advisory drafts with cited sources and officer sign off

    For an agricultural extension office, it reads the week's rainfall forecast, pest alerts and market prices against each household's crop stage and drafts a plain advisory. Every recommendation cites its bulletin, and the officer signs off before anything goes to a farmer.

  • Purchase request review packs with role based sign offs

    Takes an internal purchase request, classifies it, pulls supplier evidence and policy snippets, and prepares a review pack and draft documents. Logistics, finance, legal and the department head each make their own decision, and the agent cannot approve or pick a supplier.

Other workflows that use the same tools

  • Weekly CRM health report

    Sales. Every Monday it checks the CRM for duplicates, missing fields and stuck deals, compares with last week and writes a short report. Numbers come from queries, not the model.

  • Closet inventory from purchase and sale emails

    Ecommerce and resale. A weekly run reads your inbox for purchase confirmations and resale item sold notices and drops them in a review tray. Nothing enters or leaves your closet inventory until you confirm it.

  • Daily media briefing with cited sources

    Marketing. Reads about a thousand news items a day for a communications team and drafts a briefing where every claim links to its source. A named analyst approves it before anyone senior sees it, and high risk stories trigger an alert within 15 minutes.