From Spreadsheets to Scanned Shelves: How We Built Part Shelf OS

The clipboard is the competition

Walk into most independent auto parts shops and you'll see the same thing: a clipboard hanging off a shelf, pages covered in scribbled part numbers and handwritten counts. If they're "digital," there's an Excel file somewhere — usually last updated three weeks ago and maintained by whoever drew the short straw that month.

Nobody planned to run their business this way. It just happens. A shop starts small — a few hundred parts, a couple shelves, a guy who "just knows where everything is." Then the business grows. More shelves. More SKUs. More "I swear we had three of those" moments. And suddenly you're spending 20 minutes looking for a brake caliper while the customer waits.

We spent months talking to shop owners and parts managers. Not surveys — actual conversations. Standing on shop floors at 7 AM, watching them open up, watching how they actually worked. What we saw was consistent: the inventory system wasn't a system at all. It was tribal knowledge held together by caffeine and desperation.

The spreadsheet trap

A spreadsheet is better than a clipboard — barely. It's searchable. It can do math. But it has a fatal flaw: nobody on the shop floor is going to open a laptop, find the file, scroll to the right row, and type in a new count every time they pull a part. So the spreadsheet drifts. Three weeks later it's wrong. Six weeks later it might as well be fiction.

The shops that tried to solve this usually went one of two ways. Either they bought an expensive ERP system built for a warehouse — overkill, clunky, designed for a desktop — or they cobbled together something with barcode scanners and hoped for the best. Neither worked.

What actually works on a shop floor? Your phone. It's already in your pocket. It has a camera. It's always connected. And every person on the floor already knows how to use it. That was the insight that shaped everything.

QR codes, but not the gimmicky kind

QR codes got a bad reputation during COVID — every restaurant slapping a sticker on the table for a PDF menu. But a QR code is just a machine-readable label, and that's exactly what a part shelf needs. Each shelf gets a printed label with a QR code. Scan it with your phone. That shelf's inventory — what's supposed to be there, what's actually there, when the last restock happened — comes up instantly.

No laptop. No login. No navigating menus. Point, scan, see. That's the kind of speed a shop floor demands.

We built the label system first. Each part gets a shelf location, a QR code, and a printed label with the part name, number, supplier, and reorder point — all generated automatically from your inventory data. Import a CSV, we generate the labels. Done.

PWA first, not as an afterthought

We made a deliberate choice early on: Part Shelf OS would be a Progressive Web App. Not a native iOS app. Not an Android APK you have to sideload. A PWA — installable from the browser, works offline, gets updates instantly, same experience on every device.

Why? Because shop floors have terrible Wi-Fi. Because people bring their own phones. Because nobody wants to manage app store deployments just to fix a bug in the label printing flow. PWAs solve all of that. Install it once from Safari or Chrome. It lives on your home screen. It works even when the internet doesn't — syncs back up when you're back online. This isn't a compromise. It's the right architecture for the environment.

What we shipped

Part Shelf OS launched with the core loop we wanted from day one:

• CSV import — dump your spreadsheet, we structure it. Part numbers, suppliers, quantities, shelf locations all parsed automatically.
• Shelf label generation — printable QR labels with part info, reorder points, and scannable location codes.
• Mobile scanning — open the PWA on your phone, scan a shelf label, see live inventory. Update counts in two taps.
• Low-stock alerts — configurable thresholds. When a part drops below its reorder point, the system flags it.
• Supplier tracking — link parts to suppliers, track order history, see who has what on order.
• Real-time dashboard — stock levels, recent movements, low-stock items. The stuff you actually need to see.

No feature bloat. No modules you'll never use. Just the loop: import → label → scan → track → reorder.

What we learned

Building for the shop floor teaches you things you can't learn from user stories. Here are three:

1. The phone camera is the only scanner that matters. Dedicated barcode scanners are expensive, need charging, and break. Every phone already has a camera. Build for that.

2. Labels are UX. A shelf label isn't just a sticker — it's the primary interface between your system and the person pulling parts. If the label is clean, scannable, and informative, adoption follows. If it's ugly or confusing, nobody scans it.

3. Offline-first isn't a feature. It's table stakes. Shop Wi-Fi is unreliable at best. If your app shows a spinner when the connection drops, you've already lost. The PWA caches everything locally and syncs when it can. The user never sees the difference.

---

Part Shelf OS isn't trying to be an ERP. It's not trying to replace QuickBooks or your shop management system. It does one thing: make inventory visible, scannable, and accurate — without getting in the way.

If you're still running your parts inventory on a clipboard or a spreadsheet that nobody updates, you already know the problem. We built the fix.