SSABI.COM / AVAILABILITY NETTING
What is availability netting?
Availability netting is how rental inventory stays honest: instead of marking a unit "available" or "out," the system computes what is truly free for any date range by netting physical stock against every overlapping commitment — quotes, holds, dispatches, and returns — as they happen.
The problem with status flags
Most rental operations track availability with a status per unit: in the yard, on rent, in service. That answers "where is this unit right now?" but not the question a booking actually asks: "can I promise eight of these for the 14th through the 18th?" A unit sitting in the yard today may already be committed to three future jobs. A status flag can't see forward, so people check calendars, ask the yard, and eventually promise gear that was never really free. That's how double bookings happen — not through carelessness, but because the tool answers the wrong question.
How netting works
Netting treats availability as arithmetic over time. For each category or serialized unit, the system holds a timeline of every commitment with a date range: confirmed orders, pencil holds, open quotes, and dispatches that haven't returned. When someone asks for eight units across a date range, the system takes physical stock, subtracts every commitment that overlaps any part of that range, and returns the true free count for the worst day in the window.
Ten in stock is not ten available. Netting subtracts every overlapping commitment for the requested dates.
The critical property is that netting is live. The moment a quote is accepted, a hold is placed, or a return is checked back in, every other calendar, quote, and dispatch board reflects it. There is no overnight sync and no "let me confirm with the warehouse" — the number on the screen is the number.
What changes operationally
Quoting gets faster, because the person on the phone can promise against real numbers instead of promising provisionally and confirming later. Double bookings stop being a category of incident, because a request that would collide with an existing commitment is flagged before it is confirmed, not discovered at load-out. And utilization becomes measurable, because the same commitment timeline that nets availability also shows how many billable days each category actually works.
Rule of thumb: if answering "what's free on the 14th?" requires opening more than one screen — or asking a person — availability isn't netted. It's guessed.
How Ssabi implements it
Netting is the core of Ssabi Core, the decision layer that connects inventory, quotes, scheduling, billing, and sites. Every commitment in Ssabi — quote, hold, order, dispatch — carries a date range and nets against stock the moment it is created, updated, or released. Conflicts surface at quote time, calendars update everywhere at once, and the same data drives pricing and invoicing, so what was promised, what shipped, and what gets billed are one record, not three.
See netting on your own categories
A 30-minute live walkthrough, on workflows shaped like yours.
Request a demo