HomeIndustriesContainer Rental
A container is never just delivered — it rotates
Drop off the empty, leave it on site, come back for the full one, drop off another at the same stop: the rental contract is a single signature, but the container itself lives a full cycle — from the yard to the customer's site, and back. OpsNode tracks that cycle unit by unit, not just the line item on an invoice.
The swap matters more than the delivery
A job site that fills its container before the rental term is up doesn't wait: it needs emptying or swapping, often the same day. A seasonal site can spike demand over a few weeks while other sites keep their container for months without touching it. Somewhere between the two, the fleet has to stay traceable unit by unit — knowing exactly which of your identical containers sits at which customer's site, since when, and until when.
The swap itself is a precise logistics move: the truck that picks up the full container leaves with an empty one to drop at the same stop, not two separate visits on two different dates. Get the site grouping wrong, or lose track of an end date, and that's a wasted truck round trip — or worse, a container promised to a customer that turns out to still be tied up somewhere else.
And the customer really only remembers one thing: whether the promised delivery date was kept. A fleet managed by eyeballing a spreadsheet can't guarantee a reliable date; availability calculated day by day can.
Built for the container's cycle, not just the contract
The data model follows the serialized unit from the yard to its return, not an isolated contract line.
The full cycle, not just the delivery
Every container is a serialized unit tracked from delivery to pickup, with its own rental period — never just a "container" line item on a generic contract.
Tracked by unit, not by categoryThe swap in a single stop
Picking up the full container and dropping off the empty one at the same location is scheduled as one truck trip, not two separate visits to coordinate.
One stop, two movesA delivery date you can actually promise
Availability is calculated by date, directly in the database. It's impossible to promise a container that's already committed elsewhere for the same period.
Overlaps blocked at the database levelRoutes on the real road network
Delivery and swap stops group by address and sequence on the actual road network, not straight-line distance.
Calculated on the real road networkConfirmation before the truck rolls
Delivery or pickup confirmation can be requested from the customer before the truck takes the road — a closed or relocated job site doesn't cost an empty round trip.
Opt-in, no blocking of the rest of the workflowBilling that follows the real contract
Billable swaps are detected automatically from visits actually completed, and the PDF invoice follows without manual reconstruction.
Automatic detection of billable visitsBuilt for this business, not adapted after the fact
OpsNode doesn't have a production customer in container rental yet — the data model was built for this exact business, and we'd rather say so plainly than leave it unsaid. What already exists and runs in production today: date-based availability with overlap blocked at the database level, route sequencing on the real road network, a driver app that keeps working offline and resyncs without duplicating a visit, and billing that detects billable visits instead of reconstructing them by hand.
These are the same foundations that already run, in production, equipment rental with a per-unit service schedule — the same rigor carries directly over to a container's rotation.
A container rotation that no longer depends on a spreadsheet?
Show us your fleet and your current rotation cycles — we'll show you how date-based availability and the single-stop swap would apply starting tomorrow.
See a demo