LoadOut brings stock, orders, availability, crew, transport and invoicing onto a single set of records, from the first quote to the final return scan. Availability is calculated rather than estimated, and the phone app keeps working when the warehouse has no signal.
Most inventory software stops at the stock count. Rental is a loop: quote, reserve, prepare, dispatch, collect, invoice. Every step changes what is available to the next job, and LoadOut is designed around that loop rather than bolted onto a list.
Versioned quotes price equipment, crew and transport on the same lines the warehouse will later pick from. An issued version is fixed; a change creates the next one.
Confirmation places a hard reservation across the full operational window, including preparation and turnaround, and surfaces any shortage the moment it exists.
Pick, stage and load by barcode or RFID. Containers keep their verified contents between jobs and load as a single scan.
A run carries a driver, a vehicle and ordered stops. Walkarounds, odometer readings and delivery outcomes are captured on the phone as they happen.
Collected, received and cleared are three separate facts. Nothing is available to the next job until it has been checked in and cleared for use.
Charges follow the agreement, not the plan. Invoices, payments, credit notes and recurring billing are raised from the same record the job ran on.
Each module is a complete workspace in its own right, and all of them share one set of records. A change made on the order is already on the pack list, the run sheet and the invoice.
A catalogue item is what you rent or sell; stock is the physical units and quantities behind it. Serial-tracked units, bulk quantities, variants, kits and containers, with one availability figure across all of them.
Rental, event, sale or installation: an order carries its lines, crew, transport, documents and money as tabs on a single page. The quote is a versioned view of it, and the accepted agreement is what both the plan and the invoice follow.
Availability is the quantity that can cover an entire operational window after existing reservations and maintenance holds. Shortages are split into those another depot can cover and those nobody can.
Pick, stage, load, return and count are scans against an order, each answered by the office as it lands. A case whose contents were verified loads as one scan without being opened.
A run is a vehicle, a driver and ordered stops serving one or more orders. The office plans it; the driver works it on the phone, and every reading, refuel and outcome reaches the office as it happens.
Shifts are set by work role and headcount. Assignments stay tentative until conflicts clear, and overtime is derived from recorded actuals rather than from what the customer was billed.
A failed check, reported damage or a due service places a hold on a unit. The hold survives the item turning up and the date passing; only a permitted person clearing the unit releases it.
Invoices are issued from charges that are ready, and charges follow the agreement. Payments, allocations, credit notes and refunds are separate facts, so every balance can be explained.
The same records as the office, on a phone designed for people who are not sitting at a desk. Drivers capture the run in the order the work happens, warehouse staff scan against the order, and crew see their day.
A run opens to what is owed before leaving, then each drop with directions and an outcome, then the closing reading and refuel on the way back.
Pick, stage, load, return or count with the camera or a handheld, and see the office's verdict on every read the moment it lands.
On hand, free now, out and booked for every stock item, followed by the jobs that have it and when each is due back.
When the office moves something, the phone re-reads itself over the same connection. A capture held offline is shown as pending until the server has accepted it, never as saved.
Every part of LoadOut keeps the two apart. A delay updates the estimate without rewriting the agreed window, and "received" never quietly becomes "cleared for use".
Every open view follows its data over a single WebSocket. There is no refresh button anywhere in the product, and nothing that is signed in polls.
Scans and captures are written to the device first and sent when the connection returns. Each carries an id minted on the device, so a replay can never create a duplicate.
With a single warehouse the whole dimension disappears from the interface. Add a second and transfers, per-warehouse roles and the scope selector switch on.
Document types, vehicle types, return conditions and work types are defined by your organisation, rather than one country's rules shipped inside the software.
Event time and entry time are both recorded. A collection made yesterday and entered today keeps both dates, and every record keeps the person who made the change.
Dark mode is a token flip, not a second design. Every list ships a phone layout, and the scan station is designed at phone width first.
LoadOut is not yet generally available. Every screenshot on this site is the real product, running against a seeded demonstration company. This is what is in the build today, and what is being worked on next.
We are onboarding a small number of hire companies ahead of general availability, to shape what is built next. Tell us what you rent and how many depots you run, and we will arrange a walkthrough against your own kit list.
Every enquiry is read and answered by a person on the team, not by an automated sequence.
hello@loadout.app