The package
Nobody books forty items. They book the A-cam package.
Gear leaves as a package — body, lenses, batteries, plates, cables, the lot, in six cases on a cart. But it comes back as forty separate things, and it is the separate things that need servicing, get damaged and go missing individually. A system that only understands packages loses the detail; one that only understands items makes every booking a forty-line chore. What actually fixes it: letting the package be a single bookable thing that is still forty tracked items underneath.
- Build a kit once — the case, the cart, the whole package is the container and everything inside it a member — and the list shows the tree as one row you can expand
- Kits nest, five levels deep: primes in a lens case, the lens case in the A-cam package, the package on the cart. Anything can be a member and a container at the same time
- Check out or reserve at any level and everything inside travels with it, availability checked against every member at every depth
- Members keep their own serial number, condition, service history and value: the package is a wrapper, not a black box
- Kits are what books together, locations are where things sit — so the flight case is a kit that ships, and the store, the truck or the unit base is a location that holds
How the registry works