๐๐ง๐๐ฎ๐ฌ๐ญ๐ซ๐ฒ: Automotive parts / warehouse operations / inventory management
๐๐๐ฃ๐๐๐ญ๐ข๐ฏ๐: Design a simple, barcode-first inventory system for small parts distributors that have outgrown spreadsheets but do not need the complexity or cost of a full ERP system.
๐๐๐ซ๐ ๐๐ญ ๐ฎ๐ฌ๐๐ซ: Small distributors managing roughly 1,000โ20,000 SKUs from a single warehouse
๐ ๐จ๐๐ฎ๐ฌ: Receiving, barcode scanning, bin locations, order reconciliation, stock visibility, and low-stock monitoring
The concept was inspired by a common operational problem: small warehouse teams often manage thousands of SKUs using spreadsheets, while still relying on manual checks during receiving and fulfillment.
The goal was to design a system that keeps the simplicity of the spreadsheet workflow while adding the accuracy and visibility of modern warehouse software.
The Challenge
For a small parts distributor, spreadsheets can work surprisingly well โ until the physical warehouse starts moving faster than the spreadsheet.
Typical issues include:
Manual stock updates
Inventory quantities that do not match what is physically on the shelf
Receiving staff manually comparing delivered quantities against purchase orders
Products stored in the wrong location
No easy way to identify shortages or overages during receiving
Difficulty seeing what is currently on order
Limited visibility into safety stock and reorder requirements
For a three-person company with one warehouse worker, implementing a large ERP or warehouse management platform can create another problem entirely: too much complexity.
The challenge was therefore not simply to โbuild inventory software.โ
It was to answer a more specific question:
How can a small warehouse gain barcode-level inventory accuracy without changing the simple workflow the team already understands?
The Solution
I designed StockPilot as a lightweight inventory operations platform built around a simple workflow:
Warehouse staff can upload an incoming purchase order using Excel or CSV and begin scanning the manufacturer barcodes already attached to the products.
As each barcode is scanned, the system:
Identifies the SKU
Displays the product and bin location
Updates the scanned quantity
Matches the scanned quantity against the expected order
Highlights completed items
Flags unexpected products
Detects shortages and overages
๐๐ฑ๐๐ฆ๐ฉ๐ฅ๐:
Toyota Brake Pad Set
Expected: 24
Scanned: 24
Status: MATCHED
NGK Spark Plug
Expected: 30
Scanned: 28
Status: SHORT 2
Denso Sensor
Expected: 12
Scanned: 13
Status: OVER 1
The goal is to surface discrepancies while the shipment is still being received โ not days later when the inventory mismatch becomes harder to investigate.
Instead of forcing businesses to immediately abandon the tools they already use, StockPilot is designed to work alongside existing spreadsheet workflows.
Incoming or outgoing orders can be uploaded through Excel or CSV.
The system then adds operational controls that spreadsheets alone cannot provide:
Barcode verification
Real-time quantity matching
Physical bin locations
Overs and shortages
Low-stock visibility
On-order quantities
Safety-stock monitoring
This creates a simpler transition from spreadsheet-based inventory management to structured warehouse software.
The warehouse worker should understand the system in minutes, not weeks.
Rather than creating a traditional ERP interface filled with menus and configuration screens, the experience focuses heavily on the actions warehouse staff perform every day.
The primary receiving interface shows:
Purchase order number
Supplier
Expected units
Scanned units
Remaining units
Current discrepancies
Barcode scanning area
Last scanned product
Bin location
Expected vs scanned quantities
Receiving status
The interface also simulates barcode scans so prospective users can immediately understand how the workflow would operate in a real warehouse.
StockPilot demonstrates how a small warehouse could move from spreadsheet-based inventory tracking to a barcode-powered operational workflow without implementing a complex ERP.
The concept shows how one receiving process can become significantly clearer:
The project also demonstrates my broader approach to building business software:
I do not start with features.
I start with the existing workflow, identify where manual work is creating friction, and design software around the way the business actually operates.
For StockPilot, the opportunity was not to build another enterprise inventory system.
It was to build something for the businesses sitting between Excel and ERP.
Do you ever try breaking the site you're interacting with?
I'm always thinking "what will people try to do" and then coming up with a solution for it. If I saw a card like this I'd try to pick it up. Then once I discovered it was draggable, I'd try seeing what happens if I throw it outside the browser.
What do you think?
But this Mobbin website made me rethink that approach.
What stood out to me:
โ The website feels like one continuous story
โ Each section naturally leads into the next
โ Typography creates the rhythm
โ Motion adds continuity instead of distraction
โ The visual language stays consistent throughout
The lesson Iโm taking from it:
Donโt design 10 impressive sections. Design one experience.