Pack Station Order Verification

The problem this kills

Wrong-item and short-pack shipments are the quiet killers of a fulfillment operation. A packer grabs the look-alike SKU, drops one unit on a quantity-of-three line, or seals a box before the last item goes in - and now you're paying for a return, a re-ship, a refund, and a customer who trusts you less. The packing slip "looked right." Nobody caught it because nothing forced a real check.

Most teams try to fix this with a louder reminder taped to the bench. It doesn't work, because the verification step is optional. The packer can always skip it when it's busy - and busy is exactly when mistakes happen.

This plan kills the problem by making verification the only way to finish. The box cannot be marked packed until every single line has been scanned or keyed and matched against the order. No match, no pack-complete.

What you'll build

A simple pack-station screen your packers open at the bench. They pull up an order, then scan (or type) each item as it goes in the box. The screen tracks progress line by line: green when a line is fully matched, red when something is wrong - a SKU that isn't on the order, too many of one item, or a line still short.

When everything matches, the packer hits an explicit "verified & approved to ship" confirmation and the order is marked packed. If something can't be matched - a damaged barcode, a substitution, a known data glitch - the packer can't just power through. The mismatch has to be resolved, or a supervisor has to enter an override with a recorded reason. Either way, a person made the call and you have the record.

It handles the real-world messiness too: multi-box orders, serialized items that need each serial captured, and a duplicate guard so the same order-and-pack-session can never be confirmed twice.

What's inside the Implementation Plan

The plan is a single file you paste into an AI coding agent (Claude Code). It walks the agent through building the whole tool, step by step, with a ready-to-copy prompt at the end of each step.

Crucially, it opens by interviewing you about your business - your current packing process, the systems and spreadsheets you use, how your SKUs and barcodes are actually named, your typical and peak order volumes, your approval and override rules, and your messy edge cases. It reflects a short tailored spec back to you and waits for your thumbs-up before building anything. You get a tool shaped to how you pack, not a generic template you have to bend to fit.

Inside you'll find:

• The discovery interview and how the agent turns your answers into the data model
• The order + line + pack-session data design, with SKU/barcode matching
• The scan-to-match screen with live per-line status
• Multi-box and serialized-item handling
• The mismatch resolution and supervisor-override flow with recorded reasons
• The "verified & approved to ship" human gate and pack-complete posting
• The pack-confirm CSV export in the exact columns your system expects
• A "No API yet?" path: load orders from a Google Sheet / CSV and export packed-confirm CSV - so it's fully buildable today

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real fulfillment operation needs:

• Login so only your team can use the tool.
• Row-level security so each user only ever sees their own organization's orders.
• A complete audit trail - who scanned, who resolved, who overrode, and exactly when.
• A hard human-in-the-loop gate - the tool drafts the verification result, but a person must explicitly approve "verified & approved to ship," and mismatches must be resolved or supervisor-overridden, before pack-complete is posted.
• Duplicate guards so the same order + pack session can never be confirmed twice.

Who it's for

Packers, pack QC, and fulfillment supervisors who are tired of chasing wrong-item and short-pack errors after the box has already left the building. If you run a warehouse or a 3PL bench and you want the packing step to verify itself, this is for you. You don't need to be a developer - you need an afternoon to a weekend and the willingness to answer a few questions about how you pack.

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