Kanban / Two-Bin Replenishment Trigger

The problem this kills

Your two-bin / kanban system works great on the whiteboard and falls apart on the floor. Someone empties a bin, grabs the paper kanban card, and... the card ends up in a pocket, under a pallet, or in the laundry. The buyer never sees it. Three weeks later you're out of a part and the line stops.

Even when the cards do make it back, your buyer is hand-keying them one at a time, can't tell which ones are already on order, and re-orders the same item twice because two cards came in for the same bin.

The fix isn't a bigger ERP project. It's a tiny tool: staff scan or tap the card on their phone when a bin goes empty, the request lands instantly, the system refuses to raise a second request for a card that already has one open, and the buyer sees a clean batched list to approve.

What you'll build

A mobile-friendly web app where:

• Each kanban card has a QR code. A worker scans it (or taps the card from a list) the moment a bin is empty.
• That scan creates a replenishment request for the card's fixed reorder quantity - no typing, no math.
• The same card can't raise a second request while one is still open (no double-buying).
• Requests are batched by supplier so the buyer sees one tidy list per vendor.
• The buyer reviews and approves - then, and only then, requisitions / POs are created.
• The status flips to "Ordered" and shows back on the floor, so everyone can see what's coming.
• Every card shows open vs received at a glance, and you can export everything to CSV.

What's inside the Implementation Plan

• It starts by interviewing you about your business. Before a single line is built, the plan has the AI agent ask you how your two-bin/kanban system actually runs today - your card numbering, your SKU and supplier naming, your reorder quantities, who scans and who buys, your peak volumes, and your messy exceptions. It reflects a short spec back to you for a thumbs-up, so the tool is tailored to you, not a generic template.
• A clean data model for your kanban card master and the scan signals.
• The QR / scan-or-tap flow built for phones.
• The duplicate guard (one in-flight request per card) built in from the start.
• Supplier batching, the buyer approval gate, and the "Ordered" status loop.
• A "No API yet?" path: load your card master from a Google Sheet / CSV and export approved orders as CSV in the exact columns your purchasing system expects.
• Copy-paste prompts for every step.

The governance it includes (this is the point)

• Login so only your team can scan and approve.
• Row-level security so each organization only ever sees its own cards and requests.
• A full audit trail - who scanned, who approved, and when.
• A hard human-in-the-loop gate - a scan raises a request; it never auto-buys. The buyer approves before any PO or requisition is created.
• Duplicate guards - a card already has an open request? A second scan won't create a second order.

Who it's for

Stockroom and production-support staff who run replenishment off paper kanban / two-bin cards that keep getting lost - and the buyers who have to chase those cards down and key them into purchasing by hand.

If that's you, you can build this yourself in an afternoon. You've got this - paste the first prompt and let the agent interview you.