Remote storage logic

[qay21]

I'm having a hard time figuring out how to represent a remote storage area in SnipeIT. Let's imagine a brief use case :

I'm buying loads of K120 keyboards to give to my company's roughly 200 developers. These guys and girls are typing hard and fast, so standard keyboards rarely live more than one year. Moreover, my developers are working from 4 different locations, that I'm able to represent in SnipeIT. In order to replace quickly a broken keyboard, I manage a remote storage room in each of these locations, where I maintain a small buffer of ready-to-use keyboards.

Due to the sheer volume and low cost of keyboards going in and out of stock, I don't really want to manager them individually, collecting Serial Numbers and stuff. I simply want to know, at any time, where are stored and checked out keyboards. So, regarding SnipeIT, these clearly aren't assets. The "Accessories" tab seems the most suited for my use case, but how am I supposed to manage remote locations ?

So far, I have 4 "accessories", looking pretty much like that :

• K120, Office A, 10 available keyboards, 25 checked out
• K120, Office B, 8 available keyboards, 19 checked out
• K120, Office C, 20 available keyboards, 36 checked out
• K120, Office D (main building), 170 available keyboards, 103 checked out

The "accessories" tab also tells me how much keyboards are checked out. But here you can start to see the problem :

• There is 4 rows for a single type of object, this is unconvenient. If I want to handle mouses the same way, it grows up to 8 rows. If I add a fifth office, it jumps up to 10 entries, still accounting for only 2 products.
• I can check out a keyboard from Office A to a developer working here. But if they end up moving with all their stuff to Office B, then my accessories accounting is drifting toward a very undesirable state : the keyboard is still considered a "Office A" checked-out item, while it is actually physically with said developer in Office B. Uncomfortable.
• As long as location for the developer is correctly set, that might not be too much of a problem, until said developer suddenly want to go for a world tour on the back of a saddled hedgehog. At this point I want to check back in my keyboard, which will automatically be accounted as the 11th available keyboard of Office A, instead of becoming the 9th available keyboard of Office B.

With all that in mind, I'm uncertain of what to do. I'm currently considering using 200 assets without Serial Number just to have the ability to :

• Have all keyboards as a single "entry" (aka Asset Model)
• Have each individual keyboard manually stored to a given location, using the Default Location field

At this point I'm a bit confused. I'm trying to "simply" keep track of what amount of high-volume low-value items I have as a buffer in various locations. Is that against SnipeIT's general philosophy and/or identified use cases ?

Thanks (for reading and for this otherwise amazing piece of software !)