The Inventory Model
Ohmventory's data model is deliberately small. Six concepts cover the entire product:
Organization
└─ Space (Home, Office, Warehouse — flat, no nesting)
└─ Location tree (Room → Shelf → Bin — nests as deep as you want)
└─ Item (attaches to exactly one Location)
├─ Item Type (defines which Fields the item has)
└─ Field values (Resistance: 10kΩ, Color: Red, ...)
A Label (with a scannable code) can be attached to any Item or Location, connecting the physical object to its digital record. Units and Dimensions (meters, ohms, volts...) back any Field whose value is a measurement, so those values stay comparable and searchable regardless of which unit someone typed them in.
Why the model is split this way
A few of these splits aren't obvious up front, and each one exists for a specific reason:
Spaces are separate from Locations. A Space is a top-level site — a physical location like "Home" or "Main Warehouse." Locations are the nested structure inside one Space — rooms, shelves, bins. This split matters because a Space and a Location behave differently: Spaces are flat and independent of each other (you can't move a Space "into" another Space), while Locations form a real tree that you reorganize, nest, and move things around within. Keeping them as separate concepts means moving a shelf within your workshop is a different, contained operation from anything that would touch a whole separate site.
Items belong to a Location, not a Space directly. This means an Item's "address" is always specific — not just "in the Warehouse" but "in the Warehouse, on Shelf 3, in the small-parts bin."
Item Types are separate from Items. A Type (like "Resistor") is a reusable template that defines what attributes matter for that category of thing. Creating the Type once and reusing it across many Items is what makes the catalog and search features possible — see Item Types & Fields.
Everything is owned by an Organization, not a person. Even a single person using Ohmventory alone is, behind the scenes, the sole member of their own personal Organization. This is what lets the exact same Space/Location/Item structure support both "just me, tracking my garage" and "a whole team managing a shared warehouse" without being two different products. See Organizations & Spaces.
Reading this section
The rest of Core Concepts covers each piece in more depth, roughly in the order you'd encounter them:
For step-by-step instructions on actually doing things with these concepts, see Getting Started and Features.