Open PO / Expected Receipts Dashboard: Trust Your Inbound Pipeline Again

The problem this kills

Ask three people when a purchase order is "supposed to arrive" and you'll get three answers. The buyer remembers a phone call. The ERP still shows the original date from six weeks ago. The receiving supervisor is staffing the dock off a gut feel. Meanwhile half the POs are partially received, a few quietly slipped overdue, and nobody can point to one screen that says "here is what's actually coming, and when."

So receiving over-staffs on a slow day and gets buried on a heavy one. Planners promise stock that's three weeks late. Buyers chase the same supplier twice because the last expedite note lived in someone's inbox. The data exists — it's just scattered across the ERP, a buyer's spreadsheet, and a string of emails — and it's stale the moment it's exported.

You don't need a new ERP to fix this, and you don't need to be a developer. You need one trustworthy view of the inbound pipeline, and a rule that nobody changes a promised date without a buyer signing off on it.

What you'll build

A private web dashboard for your team that:

• Imports your open POs and receipts from a CSV or Google Sheet — PO number, line, supplier, SKU, ordered quantity, received-to-date, and expected date.
• Computes the real status of every PO line: open, overdue, due this week, partially received, or over-received — automatically, every time you import.
• Shows the pipeline the way each role needs it: by arrival date (what hits the dock this week), by supplier (who to chase), and by SKU (what the planner is waiting on).
• Puts a buyer in control of the truth: when an expected date changes or a line gets flagged to expedite, the AI drafts the change but a buyer reviews and approves it before it updates the view planners rely on.
• Exports a clean expected-receipts CSV in the exact columns your planning system or spreadsheet expects — so the dashboard plugs straight into how you already work.

What's inside the Implementation Plan

• It interviews you first. Before it builds anything, the plan has the AI agent interview you about your business — how you receive today, what your PO and SKU numbers actually look like, your typical and peak inbound volumes, how you decide a PO is "stale," and your messiest edge cases (drop-ships, blanket POs, over-receipts). Then it tailors the data model and rules to your answers. This is not a generic template — it becomes your tool.
• A step-by-step build, each step ending in a copy-paste prompt you hand to your AI agent.
• The exact status logic for open / overdue / due-this-week / partial / over-received.
• Partial-receipt and over-receipt handling, plus a stale-PO flag for orders past due with no movement.
• A duplicate guard keyed on PO + line so the same line can't be imported twice.
• The buyer approval workflow for date changes and expedite flags.
• A "No API yet?" fallback so you can build the whole thing today from a sheet, with a clean CSV export back out.

The governance it includes (this is the point)

This isn't a spreadsheet with a fresh coat of paint. The plan builds in the controls that make a tool safe to actually run a business on:

• Login so only your team can open it.
• Row-level security so each organization only ever sees its own POs and suppliers.
• A full audit trail — who changed which expected date, who approved it, and when.
• A human-in-the-loop approval gate: the AI drafts expected-date changes and expedite flags, but nothing reaches the planners' view until a buyer reviews and approves it.
• Duplicate guards on PO + line so re-importing a file never double-counts a receipt.

Who it's for

Purchasing teams, receiving supervisors, and inventory planners who live and die by the inbound schedule — and who are tired of three versions of "when is it coming?" If you currently run your receiving plan off a spreadsheet that's stale by lunchtime, this is for you.

You've got this — paste the first prompt and let the agent interview you.