An event rental company and a portable toilet company share trucks, routes and billing, and differ completely in the warehouse. A toilet is one unit with one number. A tent package is a top, a set of sections, legs, sidewalls, stakes and a bag of hardware, and a wedding under it is tables, chairs, linens, glassware and 200 napkins that nobody is going to serialize. The warehouse has to book the package as one thing, pull it as forty things and count the small things back in.
Serialize the assets, count the consumable-adjacent
The dividing line is whether you care which one it is. A chair gets repaired, a table gets a wobbly leg, a tent top gets a tear and a fire certificate, and when one goes missing you want to know which. Those are units, each with a number and a history. A napkin does not have a history. Glassware breaks in bulk, flatware comes back short by a dozen, and the only question is how many you have. Those are counted: a stock number, holds by quantity, and a check-in by count.
The rule that keeps this sane is per product, all or nothing. A product is tracked by unit or tracked by count, never a mix where thirty of the chairs have numbers and the rest are a pile. The mixed model gives every product two answers to "how many do I own" and they drift apart by the second event.
Kits: one line to book, forty to pull
A kit is a product made of other products: the 20x40 frame tent package is the top, the frame sections, the legs, the sidewalls, the stakes and the ratchet straps, with the counts of each. A supply like a bag of stake caps can be a part too. The customer books the kit as one line at one price. Behind that line, the system reserves the specific units for each tracked part and holds the quantity for each counted part, for the event's window.
When a part is short, the booking should still save, with the shortage marked on the line: three sidewalls short of the eight the kit needs. The office sees it, subrents, substitutes or calls the customer. A booking that refuses to save because one sidewall is out is a booking that gets taken on paper instead.
Kits nest: a dance floor kit inside a wedding package. Keep nesting shallow and refuse a loop, or the warehouse will build a kit that contains itself.
The pull sheet
The morning of a delivery, the crew needs a list: every unit by number and every counted item by quantity, for every job on the truck, in the order they load. A kit on the job expands to its parts on the sheet; a counted product shows the number to pull. As units are scanned onto the truck they tick off, and a unit that belongs on another truck says so. The sheet should be printable, because the loading dock is not a place for a phone.
Check-in: what came back, and in what state
After the event everything comes back, and the check-in is where the money is. Each unit is scanned in: clean, dirty or damaged. Each counted product is counted in: how many returned, how many damaged. Dirty units go to cleaning and are not bookable until cleaned; damaged ones go to the workshop; counted items that came back short reduce the stock and can be charged. A product that needs cleaning after every return should carry that rule, with a turnaround in days, so the chairs from Saturday are not booked for Sunday morning.
Laundry is a place, with a date
Linens go out to a laundry service and come back in a week. While they are out they are not available, and after the expected-back date they are bookable again whether or not the van has arrived. Treat the laundry as a location with a batch: what went, when it is due back, what came back clean, what came back damaged. A batch that is overdue tells you the linens for Saturday are at risk before Saturday.
Before the truck leaves
Once the pull sheet is right, the next question is whether it all fits on the truck and in what order it comes off. Load planning is that post. And for a tent, the site plan comes before any of it: layouts and site plans.
