NATIONAL WEIGHS
An end-to-end weighbridge platform: a multi-tenant web platform that runs the business, and a desktop client in the weighbridge cabin that talks to the weighing indicator over serial. Built, shipped and still maintained by Orqave.
An end-to-end weighbridge platform: a multi-tenant web platform that runs the business, and a desktop client in the weighbridge cabin that talks to the weighing indicator over serial. Built, shipped and still maintained by Orqave.
Weighbridge operations running on paper tickets and disconnected desktop software. Each site kept its own records on its own machine, in its own format.
There was no single view across sites, and no way to bill or audit a month without physically chasing printouts. Growth meant another isolated island, not another row in a table.
A multi-tenant web platform for the business above the weighbridges: tenants, stores, staff, subscription licensing with feature-level entitlements, a drag-and-drop print template designer, and reporting the client runs without asking us.
Underneath it, a cloud-synced desktop client for the weighbridge cabin, reading the indicator over serial, capturing vehicle photos, and printing onto the site's own pre-printed stationery.
Every site reports into one system. Owners get their numbers on a schedule instead of asking for them.
Onboarding a new tenant is a configuration change rather than a deployment, which is the difference between a product and a series of one-off installations.
// Web Platform
Where the business is run: who the tenants are, what they are entitled to, which stores exist, who can see what, and what the numbers say.
The dashboard answers the question that made this project necessary: what is happening across all of it, right now. Weighment volume and revenue trend by week or month, and any slip or vehicle number can be found from the search box without knowing which site it came from.
Tenants are not a later feature bolted onto a single-customer product. Subscriptions, tiers and per-feature entitlements are how the platform is structured. Onboarding a new tenant is a configuration change, not a deployment.
Each weighbridge is registered with the things that change how it behaves: capacity, whether it issues a single slip or a unified one, and how long a session stays open before it expires.
Operators are invited rather than created, and each is assigned to the stores they actually work at. An operator at one weighbridge does not see another's records.
Reports are filtered the way the business thinks (by slip number, vehicle, party name or area) across a date range and across whichever stores matter, then exported. Nobody has to ask for a report to be built.
Weighbridges print onto pre-printed stationery that differs at every site, and getting fields to land in the right boxes is normally a developer job. Here the client uploads a scan of their own slip, drags each field onto it, and nudges it into place in millimetres.
Profile and credential management for platform owners, with two-factor authentication available on accounts that control every store's data.
// Desktop Client
Underneath all of it, the machine in the cabin has to work when the internet does not, talk to whatever indicator is already bolted down, and be operable by someone who is not looking at the screen much. Everything here is built around those three facts.
The weighbridge indicator is read over a serial connection, so the weight on screen is the weight on the platform. No one retypes anything. Gross, tare and net resolve automatically, and recall pulls up a vehicle's first weight when it returns for its second.
Sites that need photographic proof can require it. Cameras are configured per station, and the photo policy blocks a weighment from saving if a configured camera fails to produce an image, so the record is never half-complete.
Weighbridges run on indicators from a dozen different makers, each with its own serial frame. Rather than certify one model, the client configures the port and the frame format, so the software fits the hardware that is already bolted down.
The records screen leads with what a weighbridge owner actually asks: how many vehicles, how much revenue, how much still unpaid. Everything below that is filterable, groupable by ticket, and exports without anyone opening a spreadsheet by hand.
A sand quarry and a cement depot do not track the same things. Columns shown in the records table, fields shown on the weighment form, and up to four custom fields are all configurable per store, without a release.
One settings surface covers the store, the hardware, the print templates and the data. Backups upload to the cloud on a two-hour cycle with retry, and any date range can be pulled back down, which matters when the machine sitting in a weighbridge cabin is the only copy.
An operator finding out the indicator is unplugged halfway through a weighment is a queue at the gate. Connection status is shown on the sign-in screen, so the problem surfaces before the day starts rather than during it.
// How It Is Put Together