New Asset Receiving & Intake: Nothing Gets Used Before It's On the Books
Scan or key in equipment the moment it arrives, match it to its open PO line, capture serial/model/cost/location, auto-assign a tag — then an asset manager approves before it lands in the official register and a tag is issued.
An internal web tool where receiving staff scan or enter an arriving item, the tool matches it to its open PO line and flags over/under/unexpected receipts, captures serial + model + location + cost, dedupes on serial number, warns on cost variance, an asset manager approves, and the item is added to the register with an auto-generated tag and in-service date — plus a clean CSV export for your asset/ERP system.
Before you start
- A Supabase account (free)
- A Vercel account (free)
- Exports you already have: an open-purchase-orders CSV (expected items + cost) and a vendor/model list
- Your asset-tag numbering scheme (the prefix and format your tags use)
- Claude Code or any AI coding agent
The problem this kills
A box shows up on the dock. Inside is a $3,000 laptop, or a forklift battery, or a new monitor — something that's supposed to become a tracked asset the second it lands. But the person who signed for it is busy, the asset register lives in a spreadsheet someone updates "when there's time," and so the gear gets handed to whoever needs it now. No tag. No serial captured. No link to the PO that bought it.
Then the trouble compounds. The same item gets received twice because two people both keyed it in. A delivery shows up that nobody ordered and it just... disappears into the building. The vendor billed for the deluxe model but shipped the basic one, and nobody compared the cost on the box to the cost on the PO. At audit time, finance has a purchase order with no matching asset, or an asset with no serial number, and reconciling it is a week of detective work.
You don't need a six-figure asset management platform to fix this. You can build the intake gate yourself, this weekend — so nothing gets used before it's on the books.
What you'll build
An internal web tool your receiving and facilities team logs into. You import your open purchase orders (the CSV you already pull, with expected items and their cost) and your vendor/model list. When a delivery arrives, staff scan or type the item, and the tool finds the matching PO line — confirming you actually ordered this, in this quantity, at this price. They capture the serial number, model, location, and cost, and the tool checks it against what was expected: too many, too few, an item nobody ordered, a cost that doesn't match the PO — each one gets flagged out loud.
The tool dedupes on serial number so the same physical unit can't be received twice, and auto-generates the next asset tag in your numbering scheme. Then comes the gate: an asset manager reviews the intake record — matched to its PO line, variances and all — and approves. Only then does the item land in the official register with its tag and in-service date, and you click once to export a clean CSV in the exact columns your asset or ERP system wants.
What's inside the Implementation Plan
The downloadable plan is a single markdown file you paste into an AI coding agent. It opens by interviewing you about your own receiving process — your PO and vendor field names, how a delivery links back to a PO line, your asset-tag format, which item types even need tags, your real volumes, and your messiest edge cases (drop-ships, partial deliveries, swaps) — and then it reads a short spec back for your thumbs-up before it builds a thing. That's the difference between a tool shaped to your stockroom and a generic template you have to fight.
From there it walks the agent through the data model (POs and PO lines, vendors/models, intake records, the asset register, and the audit trail), the importers, the scan-and-match flow, the over/under/unexpected-receipt logic, the serial-number duplicate guard, the cost-variance warning, the auto-tag generator, the review-and-approve screen, and the final export. Every step ends with a ready-to-copy prompt. There's a full "No API yet?" path: import POs from a Google Sheet or CSV, export new-asset rows as a clean CSV — you never have to touch your ERP's API to ship.
The governance it includes (this is the point)
This is the asset register — the controls are the product. The plan builds them in: a login so only your team can use it; row-level security so each site or organization only ever sees its own deliveries and assets; a complete audit trail of who received, matched, approved, and tagged each item, and when; a hard human-approval gate so nothing reaches the official register until the asset manager signs off; and a duplicate guard on serial number so the same unit can't be intaked twice. An over-receipt, an unexpected delivery, or a cost variance physically cannot be added to the register until someone with authority approves the exception. That's the clean audit trail finance has been begging for.
Who it's for
Receiving and facilities coordinators, asset managers, and IT stockroom staff who own the moment between "it arrived" and "it's officially ours." If you can explain to a new hire how a delivery becomes a tracked asset and what makes one worth holding, you can build this — no developer required.
You've got this — open the plan, paste the first prompt, answer a few questions about how your receiving actually runs, and you'll watch your first delivery turn into a tagged, on-the-books asset.