Weighbridge Software That Posts Its Own Invoice

It is the software layer around a truck scale. The scale itself reports a number; the software decides what that number means. It records which vehicle it belongs to, whether the load is coming in or going out, what material it is, what it is worth under the governing contract, and what document that should become in your accounts. Without it, the indicator is just a display that somebody copies onto paper.

In most cases yes. We read the indicator over RS-232 or USB serial and the parser is fitted to whatever string your particular indicator emits, during commissioning. It is vendor-neutral by design rather than certified against a fixed list. The honest answer is that we confirm it against your actual hardware before you commit to anything — capturing the output protocol is the first step of the implementation, not an afterthought.

Then we tell you before you have spent money. If the indicator emits a serial string we can generally read it. If it emits nothing accessible — some very old or fully sealed units do not — the manual-entry path still gives you the complete ticket, pricing and posting workflow, with the operator typing the weight the indicator displays. You lose the automatic capture, not the system.

No, and running both is the situation this replaces. The point of building the weighbridge into ERPNext is that the ticket, the invoice, the stock movement and the ledger entry are one database rather than two systems reconciled at month-end. Keeping a standalone package alongside it would reintroduce exactly the gap we are closing.

Yes. The print layout is customised per site — layout, logo, the terms you print on the back, and the language. Ticket layouts are templates rather than fixed code, so matching the document your drivers and customers are used to is configuration work during implementation, not a development project.

On submit, the ticket creates and submits the correct downstream document itself. An inbound purchase becomes a Purchase Invoice per supplier, priced from that supplier's contract, with the payment schedule and due date taken from the contract's payment terms. An outbound sale becomes a Sales Invoice priced from the customer contract. A stock-only receipt becomes a material receipt into the configured warehouse. Nobody re-keys a weight into an invoice.

Two different failures, two different answers. If the indicator drops out, the operator switches to manual entry and the ticket still flows — nothing stops. If the link to the server drops, a badge warns the operator within thirty seconds so they know immediately rather than discovering it later. To be clear about the limit: the console does not queue tickets locally and forward them when the connection returns. If your weighbridge sits on genuinely unreliable connectivity, tell us and we will scope that properly rather than let you find out after go-live.

Yes, and this is one of the things standalone weighbridge packages generally cannot do. A single load can be allocated across several suppliers or collection points, with a weight against each. Every split line prices against its own contract and becomes its own invoice line or its own invoice. Any unallocated remainder goes to a configured default account so nothing is left floating, and the system will not let allocated weight exceed the net weight actually on the scale.

Yes. A miscellaneous receipt mode takes weight into stock either priced or free of charge, and a weighment can be recorded and printed without becoming a purchase. Where a third-party weighing is a chargeable service, it prices from the customer contract like any other outbound transaction.

With simulation mode, before your hardware is even cabled. It generates realistic fluctuating readings, so operators run the full cycle — first weight, second weight, barcode scanning, printing — against a scale that is not there yet. It also means you can sign the workflow off before commissioning day rather than discovering a process problem with a truck queue building outside.

There is no per-user licence fee, because ERPNext does not have one and neither do we. You pay for implementation and for support. Adding another gatehouse operator, or opening the weighbridge register to your whole finance team, does not change what the software costs. Support runs on the same annual maintenance arrangement as the rest of our ERPNext work.

There is nothing to install. The console runs in a Chromium browser — Chrome, Edge or Brave — on the machine the indicator is cabled to, and that browser talks to the serial port directly. No driver, no local agent, no background service to keep alive. The one physical constraint is that the browser has to be on the machine the cable reaches.