Asset Registry & QR-Tag Builder: One Scannable Record per Piece of Equipment

The problem this kills

Your techs service hundreds of machines across dozens of sites, and the "registry" is three spreadsheets, a shared drive of photos, and a couple of senior people's memories. The same chiller gets entered twice under slightly different serials. A pump moves from one building to another and nobody updates the location, so the next tech can't find its history. When a unit fails, someone burns half an hour just confirming which asset it is and what was done to it last time.

The fix is boring and powerful: one clean record per real piece of equipment, a physical tag stuck to the machine, and a scan that opens that exact record and its full service history. The hard parts aren't the QR codes — they're stopping duplicates from polluting the registry and keeping track of assets that move between sites. You do not need to be a developer to build a tool that does all three.

What you'll build

A simple internal web tool for your asset and field-service team. You import an equipment list per site (make / model / serial / location) from a CSV or Google Sheet, or add assets one at a time. Before anything joins the registry, the tool runs a dedupe check on make + model + serial and surfaces likely repeats and the same unit re-entered after a move. A manager reviews and approves each new or merged record — so duplicates never sneak in. Approved assets get a printable QR-label sheet; stick a label on the machine, and any scan opens that asset's record and service history in a browser. The whole registry (with each label's QR payload) exports to CSV and PDF whenever you need it.

What's inside the Implementation Plan

The downloadable plan is a step-by-step file you paste into an AI coding agent. It opens by interviewing you about your business — how you track equipment today, the systems and sheets you use, your real make/model/serial and location/site naming conventions, your typical and peak asset counts, who is allowed to approve a new asset, and the messy edge cases like blank or stamped-over serials and machines that moved sites. It reads a short spec back to you for a thumbs-up, then builds the tool around your assets and rules instead of a generic template. From there it walks the agent through the data model, the import and manual-entry flows, the dedupe engine, the manager-approval gate, the QR-label generator and the public-by-token scan page, and the CSV/PDF exports. Every step ends with a ready-to-copy prompt.

The governance it includes (this is the point)

This isn't a toy. The plan builds in the controls a real asset function needs: login so only your team can use it, row-level security so people only see their own organization's assets, a complete audit trail of every create / merge / move / approval (who, what, when), a hard human-approval gate so no new or merged asset enters the registry until a manager signs off, and duplicate guards — a unique serial per make/model plus a dedupe check on every import — so the same machine can't be registered twice. The tool exists to make a careful human decision easy: AI proposes the match, a person makes the call.

Who it's for

Inventory and asset controllers, service managers, and technicians who are tired of arguing about which unit is which and digging for service history that should be one scan away. If you can describe how you name and identify a piece of equipment, you can build this.

You've got this — open the plan, paste the first prompt, and you'll be scanning your first real asset's history by the end of the weekend.