ERP integration

Weights go straight into your ERP.

The weighbridge posts each transaction to your ERP as it completes, with the supplier, customer, item and order picked from the ERP's own lists. Nobody re-types tickets at the end of the day, and the figure in your ERP is the figure on the bridge.

The problem

Re-typed tickets are where weighbridge data goes wrong.

On most sites the weighbridge and the ERP are two worlds. Tickets pile up in the office, a clerk keys them into goods receipts and delivery notes at the end of the day, and month-end reconciliation is a hunt for the ones that were mistyped, skipped or entered twice. The weighbridge was accurate. The copying was not.

KiloSahihi closes that gap by making the ERP posting part of the weighing itself. The transaction that prints the ticket is the transaction that lands in the ERP.

How posting works

From the second weight to your ERP.

  1. 1

    Master data comes from the ERP

    Suppliers, customers, items and open purchase or sales orders are pulled from the ERP and offered as pick lists at the bridge. The operator cannot invent a name the ERP will not recognise.

  2. 2

    The transaction completes at the bridge

    The second weight locks the net, the ticket prints and the transaction is written to the local database first. The bridge never waits on the network.

  3. 3

    Queued in an outbox

    Each completed transaction is added to a posting queue. If the ERP is reachable it posts within seconds; if not, it waits.

  4. 4

    Posted and acknowledged

    The ERP's document number comes back and is stored against the ticket. A rejection is recorded with its reason and surfaced for the office to fix, and it never blocks the transactions behind it.

  5. 5

    Never posted twice

    Every transaction carries a stable identifier, so a retry after a network failure updates the same record rather than creating a duplicate.

What gets posted

Everything the ERP needs to raise the document.

Vehicle and driver

Registration, trailer, driver and transporter.

Party and item

Supplier or customer, commodity or item code, and the order it belongs to.

Weights and times

Gross, tare, net, the time of each weighing and which bridge took it.

Ticket reference

The weighbridge ticket number and, on twin bridges, both consecutive numbers.

Operator and flags

Who weighed it and whether either weight was entered manually.

Photographs

Links to the ANPR and overview images stored with the weighing, where cameras are fitted.

Systems

Sage X3, Microsoft Dynamics 365, Odoo, SAP and your own.

We integrate with Sage X3, Microsoft Dynamics 365, Odoo and SAP out of the box, and with in-house and custom systems through their APIs or a database staging table. The integration runs inside the weighbridge software, so there is no separate middleware server to keep alive.

Running several sites? An optional sync service brings every branch into one cloud dashboard, on your servers or ours, alongside the ERP posting. It is an add-on, never a requirement.

  • Sage X3
  • Microsoft Dynamics 365
  • Odoo
  • SAP
  • ERPNext
  • Webhooks, APIs and staging tables for in-house systems

Questions

Frequently asked

Which ERPs does KiloSahihi integrate with?
Sage X3, Microsoft Dynamics 365, Odoo and SAP out of the box. In-house and custom systems are integrated through their API or a staging table. If you run something else, ask; we have integrated with enough systems to be comfortable saying yes.
What happens when the ERP or the network is down?
The bridge keeps weighing and printing. Completed transactions queue in an outbox and post when the ERP is reachable again, in order, without duplicates.
Can the bridge match a purchase order?
Yes. Open purchase and sales orders are pulled from the ERP so the operator, or the ANPR match on an unmanned bridge, ties the weighing to the right order. The ERP then receives the goods receipt or delivery against that order.
Do we need a middleware server?
No. The integration runs inside the weighbridge software on the PC at the bridge. Multi-site sync is a separate optional service.
Can we start without ERP integration and add it later?
Yes. Most sites start manned and offline, then switch on ERP posting once the master data mapping is agreed. Historical transactions can be exported for back-posting.

Get started

Talk to us

Tell us what you weigh and how your site runs. We'll demo KiloSahihi with your own scenario.