How your catalogue works
Flow tracks gear in three layers, and once the distinction clicks, the whole app makes sense: a model is the spec ("Shure SM58" — rates, weight, photo), an asset is one physical serialised unit of it (with its own tag and history), and bulk stock is a counted quantity of things too cheap to serialise (XLR leads, sandbags).
This page is scaffolded — the outline below is what it will cover. Progress is tracked in gearflow#959.
What this overview will cover
- Model vs asset vs bulk stock — the one concept page to read in this section, with a worked example
- Asset statuses: available, deployed, in maintenance, lost, sold
- Asset tags: the auto-numbered identity your barcodes point at
- Where rates live (the model) and what that means for pricing
- Photos, files, and custom fields on your gear
- The asset registry vs the models list — which screen for which question
In this section
Add your gear
Models first, then units — by hand or by spreadsheet.
Categories
The tree your catalogue hangs off — get it right early, thank yourself later.
Kits
Gear that travels and prices as one thing — build it once, book it as a unit.
Accessories and child assets
The clamp, the cable, the case — gear that belongs to other gear.
Fleet ROI
What each model has actually earned — even gear that only ever ships inside a kit.