Order Change Request Workflow
Build an internal tool that captures order-change requests, checks whether the order is already picked or shipped, routes them to an approver, and writes the change with a full audit trail - so changes stop happening verbally with no control.
A login-protected web tool where your team submits order-change requests, the tool flags anything already picked or shipped, an approver signs off, and the approved change is written to the order with who-did-what-when logged and everyone notified.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account (for notifications)
- An export of your open orders as a CSV or Google Sheet (including a fulfillment status column)
The problem this kills
Right now, order changes probably happen in the hallway. A customer calls, a salesperson grabs whoever's near the warehouse, someone scribbles "make it 12 instead of 10" on a sticky note, and the order gets edited - or doesn't. Nobody checks whether the order was already picked. Nobody approves it. And when the wrong quantity ships, there's no record of who asked for what, or when.
That's the gap this tool closes. Order changes stop being verbal favors and become tracked requests: submitted, checked against fulfillment stage, approved by the right person, written to the order, and logged forever.
What you'll build
A small, login-protected web app for your CSRs, sales reps, and fulfillment team:
- A clean form to request a change to an open order - quantity, line items, or dates - with a required reason.
- An automatic fulfillment-stage check: the tool looks up the order and refuses to let a change through if it's already picked or shipped.
- An approval queue where a designated approver reviews each pending change and signs off (or rejects with a note).
- On approval, the tool writes the updated order, stamps a complete audit trail, and emails the requester and fulfillment.
- A duplicate guard so the same change can't be submitted or processed twice.
What's inside the Implementation Plan
- It starts by interviewing you about your business. Before any code is written, the plan makes the AI agent ask you about your real order process - your systems, your status names, your SKU and order-ID formats, your volumes, who approves what, and your weird exceptions. It reads back a short tailored spec and waits for your thumbs-up. You get a tool shaped to how you actually work, not a generic template.
- A step-by-step build, each step ending in a ready-to-paste prompt for your AI coding agent.
- The data model for orders, change requests, approvals, and the audit log - tuned to your answers.
- The fulfillment-stage lock logic (no changes once picked/shipped).
- Login, row-level security, audit trail, the approval gate, and duplicate guards - built in, not bolted on.
- A "No API yet?" fallback so you can ship this today using a CSV or Google Sheet of open orders and export clean updates back out.
The governance it includes (this is the point)
- Login so only your team can open the tool.
- Row-level security so people only ever see their own organization's orders and requests.
- A complete audit trail - every request, check, approval, rejection, and write is logged with who and when.
- A hard human-in-the-loop approval gate - the tool drafts the change and verifies the order isn't picked/shipped, but a person must approve before anything is written to the order.
- Duplicate guards keyed on order ID + change-request ID, so the same change can't slip through twice.
Who it's for
CSRs and customer service teams fielding "can you change my order?" calls, sales reps who promise changes, and fulfillment staff who need changes to stop arriving as verbal surprises. If you live in spreadsheets and an ERP and you're tired of uncontrolled order edits, this is for you.
You've got this - paste the first prompt and let the agent interview you.