runbookify
← All plans
Warehouse & Inventory Management / Receiving & Inbound

Blind Receiving Count Capture

Build an internal tool where receivers key what they physically counted without seeing the expected quantity, then a supervisor reconciles the revealed variance before the receipt is finalized - killing rubber-stamp receiving.

BeginnerAn afternoonBuilds onNext.js (App Router) on VercelSupabase (Postgres, Auth, Storage, RLS)Resend (email notifications)
What you'll build

A login-protected blind-count receiving screen that hides expected quantities from the counter, reveals the variance for supervisor reconciliation, enforces reason codes on big variances, and exports an approved receipt CSV plus a full variance log.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.

Before you start

  • A free Supabase account
  • A free Vercel account
  • A free Resend account (optional, for email alerts)
  • Your expected receipts / POs in a spreadsheet or CSV

The problem this kills

When a receiver can see the expected quantity on the packing slip or PO, the count stops being a count. It becomes a confirmation. People glance at the box, glance at the number, and key the number that's already printed in front of them. Shortages walk straight into your inventory as "received in full." Overages disappear. By the time someone notices the stock is wrong, the truck is long gone and the supplier dispute window has closed.

The fix is old-school warehouse discipline: the blind count. The person counting never sees what they're supposed to find. They count what's actually on the dock and key that. Only afterward does the system reveal the gap - and a supervisor, not the counter, decides what to do about it.

Doing this on paper is slow and easy to game. Doing it in your WMS usually means an expensive module you don't have. This plan lets you build exactly the blind-receiving tool your operation needs, in an afternoon, by describing your process to an AI agent and letting it build the app for you.

What you'll build

A small, login-protected web app for your receiving team:

  • A supervisor loads expected receipts (from a PO/ASN export or a simple sheet) and assigns a blind-count task.
  • The receiver opens the task and keys what they physically counted, per SKU - with the expected quantity completely hidden from their view.
  • On submit, the system reveals the variance (expected vs. counted) and flags anything outside your tolerance.
  • Large variances require a reason code before they can move forward.
  • A supervisor reconciles and approves the receipt - the human gate - and only then is it finalized.
  • The tool exports an approved receipt CSV in the exact columns your system of record expects, plus a complete variance log for trend analysis and supplier disputes.

What's inside the Implementation Plan

  • It starts by interviewing you about your business. Before it writes a single line, the agent asks about your receiving process, your PO/ASN data, your SKU and naming conventions, your typical and peak inbound volumes, your variance tolerances, and your real-world edge cases. It reflects a short tailored spec back to you, gets your thumbs-up, and then builds a tool shaped to how you actually receive - not a generic template you have to bend to fit.
  • A copy-paste prompt for every build step, written for a non-coder.
  • The exact data model for tasks, expected lines, blind counts, and variance reconciliation.
  • The blind-count screen with expected quantities locked out of the counter's view.
  • Reason-code enforcement on large variances and duplicate guards by receipt task id.
  • The supervisor reconciliation and approval gate.
  • A "No API yet?" fallback so you can build the whole thing today from a spreadsheet, even with zero integration to your current system.

The governance it includes (this is the point)

This is not a toy. The plan bakes in the controls a real receiving operation needs:

  • Login so only your team can use it.
  • Row-level security so each organization only ever sees its own receipts and counts.
  • A complete audit trail - who assigned, who counted, who approved, and exactly when.
  • A hard human-in-the-loop approval gate - the receiver counts, the system reveals, but nothing is finalized until a supervisor reviews the variance and approves.
  • Duplicate guards so the same receipt task can't be counted or finalized twice.
  • Reason codes captured on every material variance, so disputes and patterns are documented, not guessed.

Who it's for

  • Receiving associates who need a fast, honest way to key counts on the dock.
  • Inventory control supervisors who are tired of variances that only surface weeks later, and want a documented, approvable reconciliation step.
  • Anyone running a warehouse, stockroom, or fulfillment operation who wants accurate inbound counts without buying a heavyweight WMS module.

You've got this. Open the Implementation Plan, paste the first prompt into your AI agent, and let it interview you - your blind-receiving tool is one afternoon away.

Gated download

Enter your email — the plan downloads instantly and a copy lands in your inbox.

By submitting your email you'll also receive the weekly runbookify newsletter. You can unsubscribe at any time.