Upload a dealership's Excel parts data and get a storage plan: every part categorized, zoned by how fast it sells, and matched to the right storage, with whole-unit counts for each BlkStocks system.
Built by Freebranch for BlkStocks
A parts room that grows by gut feel costs money: bins in the wrong sizes, wasted walking, stockouts, and no baseline design to work from. BlkStocks (Blackstocks Optimized Systems) is a storage systems and facility integration company in Monroe, Georgia, established in 1949. Its customers include dealership parts departments, and it needed a repeatable way to turn a customer's data into a storage plan.
StockMap is BlkStocks' own product, and Freebranch built the software behind it: a web app where a parts department uploads its Excel exports (parts list, sales history, and on-hand inventory). A rules engine categorizes every part into a part family, zones parts by how fast they sell, and recommends stocking levels from lead time, minimum order quantity, and safety stock. It then assigns each part to a BlkStocks storage system and counts the whole units of each system needed, with a buffer.
Every run is saved with a snapshot of its inputs, so any plan can be traced back to the data it came from.
From the first Excel upload to the final unit counts, StockMap takes a parts department's own data all the way to a storage plan.
A step-by-step upload wizard with column mapping takes .xlsx and .xlsm files. It works with partial data: sales as monthly totals or line items, with or without on-hand inventory.
The engine works through each stage in order, as one run: categorize, zone, replenish, assign storage, and allocate bins. One set of inputs goes in, and one storage plan comes out.
Parts are zoned by how fast they sell, so fast movers land in the most accessible zones. Recommended stock for each part comes from its lead time, minimum order quantity, and safety stock.
Each part is matched to a BlkStocks storage system: bulk rack, box and clip shelving, high-density drawers, battery rack, windshield rack, or hooks and pegboard. The results roll up into whole units of each system, with a buffer.
Every run is stored with a snapshot of its inputs, and a history shows recent runs. Results can be exported to Excel or CSV.
Every facility has its own zones, storage makeup, and category and replenishment rules. Each one sees only its own data, with an admin role for oversight.
StockMap deliberately uses no AI. For this job, a transparent rules engine was the right tool, and we recommend AI only where it clearly helps.
StockMap's results are deterministic, with no randomness involved. The same data and settings always produce the same plan.
Categorization and replenishment rules are visible, and each facility can adjust its own. The logic behind a plan is out in the open, not hidden inside a model.
Each run saves a snapshot of the data it used. Any result can be traced back to exactly what went in.
Sign-in scopes every user to their own facility's data, so no facility can see another's. An admin role provides oversight.
Every project here started with a specific problem. Tell us about yours, and we'll give you an honest read on what a custom build would take.