Batch/Wave Pick Builder
Group open orders into smart pick waves by ship-by time, zone, and carrier cutoff, then generate batch pick lists so pickers grab common SKUs in one trip - with a supervisor approval gate before anything hits the floor.
A team tool that loads open orders, proposes pick waves by your real rules, lets a supervisor approve or tweak them, then releases batch and zone pick lists as clean CSV/PDF for your WMS or printer.
Before you start
- A free Supabase account
- A free Vercel account
- A free Resend account
- A CSV or Google Sheet export of your open orders with their line items
The problem this kills
Your pickers are walking miles for nothing. The same SKU sits in the same bin, but five different orders each send someone to grab one unit, one trip at a time. Meanwhile the carrier cutoff is creeping up, the rush orders are buried in the queue, and your supervisor is squinting at a spreadsheet trying to decide what to release next - by hand, every single shift.
Wave and batch picking fixes this on paper: group orders that share SKUs and zones, pick them together, and hit your carrier cutoffs in priority order. But building the waves manually is slow and error-prone, and the same order can accidentally land in two waves and get double-picked. Most warehouses either pay for a heavy WMS module they don't fully use, or they just live with the wasted steps.
What you'll build
A simple internal web app where your team logs in, loads the open orders, and gets a proposed set of pick waves built by your rules - ship-by time, carrier cutoff, zone, and order similarity (so common SKUs are batched). A supervisor reviews the proposed waves on screen, tweaks them if needed, and approves. Only then does the tool release the batch and zone pick lists - exported as clean CSV (and printable PDF) in the exact shape your WMS or label printer expects.
It is fully buildable today even if you have no WMS API: drop in a CSV or Google Sheet of open orders, and the tool produces release-ready pick lists on the other end.
What's inside the Implementation Plan
- It interviews you first. Before writing a line of code, the plan has the AI agent interview you about your real picking process - your zones, your carrier cutoffs, how you name SKUs and orders, your typical and peak order volumes, and your messy exceptions. The tool is then tailored to your warehouse, not a generic template.
- A step-by-step build you paste into Claude Code, one prompt at a time.
- A wave-building engine that respects carrier cutoff priority, separates single-line from multi-line orders, and batches shared SKUs.
- A supervisor review-and-approve screen (the human gate).
- Duplicate guards so the same order can never sit in two waves, and the same wave can't be released twice.
- CSV/PDF pick-list export in your exact columns, plus the no-API Google Sheet fallback.
The governance it includes (this is the point)
This isn't a loose script - it's a controlled tool, by design:
- Login so only your team can use it.
- Row-level security so each warehouse or org only ever sees its own orders.
- A full audit trail - who built a wave, who approved it, who released it, and exactly when.
- A hard human-in-the-loop approval gate - the tool drafts the waves, a supervisor reviews and approves, and only then are pick lists released to the floor.
- Duplicate guards - an order can't appear in two waves, and a wave can't be released twice.
Who it's for
Pick/pack supervisors and fulfillment leads who run a real warehouse floor, want shorter pick paths and reliable carrier cutoffs, and are tired of building waves by hand in a spreadsheet - without buying or fighting a giant WMS module.
You've got this. Paste the first prompt and let the interview tailor it to your warehouse.