ProcurementWindows app
PO Status Tracker
Track every PO through five steps (placed / confirmed / received / accepted / paid) on a local ledger.
The problem
PO progress lives across chat, email, and ERP. "Where is that PO?" eats minutes weekly.
The solution approach
A local ledger. One row per PO; five status dots; status change auto-timestamped; overdue flagged.
What you will end up with
- PO list: number, supplier, amount, current step, last update.
- Each row has 5 status dots; click to advance.
- Stagnant POs auto-appear in a top "Needs nudge" card.
- Export weekly PO status as Markdown.
Ready-to-use prompt
You are a senior engineer building local desktop tools. The user is a procurement lead, non-developer.
[Goal]
Put every PO's five-step progress on the table; stop chasing for updates.
[Platform & Stack]
- Windows + macOS; Electron + React + TypeScript; local SQLite
[Core Features]
1. PO list: number, supplier, category, amount, owner, current step, last update, notes.
2. Five dots inline: placed / confirmed / received / accepted / paid; click to mark, auto-timestamp.
3. Top "Needs nudge" card: > 5 days since last step.
4. Search + filter by supplier / step / owner.
5. Excel import; weekly export as Markdown / Excel.
[Visual Style]
- Light background, white cards, radius 16, generous whitespace.
- Primary button muted dark; secondary light gray.
- Follows system dark mode; system fonts.
[Robustness]
- All data stays on the local machine. Offline.
- Autosave; 7-day rolling backups.
- Friendly messages on bad input, never raw stack traces.
[Delivery]
1. Outline project structure + plain-text wireframe first; wait for confirmation.
2. Deliver in modules; run each one for me to see.
3. Package a Windows .exe and macOS .dmg, ship a 500-word plain-language user guide, list known limits.
Start with structure and wireframe.After copying
1
Open Codex Desktop and create a new project
2
Paste the prompt and send
3
Wait for Codex to finish; tweak company names, column names, button text as needed