Weighing is where physical reality meets your ERP, and it is usually where the data goes wrong. Warehouse and shop-floor teams read a number off a scale display and re-key it into Odoo by hand, which introduces transposition errors, slows down receiving and packing, and makes catch-weight products (meat, produce, chemicals, metals, textiles by roll) a constant source of stock and invoicing disputes. Odoo core has no notion of a serial-port or network scale: stock.move.line quantities, POS order lines, and quality measurements are all manual entry fields. There is no driver layer, no reading buffer, and no way to prove that the weight on the document is the weight the scale actually reported.

Universal Scale Reader is the integration layer we build to close that gap. On the technical side we deliver a proper Odoo module — a __manifest__.py declaring the addon and its dependencies (stock, and optionally point_of_sale, mrp, or quality), new models such as scale.device and scale.reading (models.Model with fields.Float weight, fields.Selection unit, fields.Datetime captured_at, and @api.depends computes for tare-adjusted net weight), plus the transport code that talks to the hardware. Serial (RS-232/USB) scales are read through Odoo's IoT-style agent or a lightweight local bridge; TCP/IP and HTTP-capable indicators are polled directly. Readings stream into the browser via a small OWL widget on the relevant view, so an operator sees the live stabilized weight and commits it to the stock.move.line, POS line, or quality check with one click — the raw reading is retained in scale.reading as an audit trail. Access is governed by ir.model.access.csv and record rules so weighing stations only see their own devices, and captured readings can flow onto QWeb weigh-slip reports or trigger automated actions (for example, blocking a receipt whose net weight deviates beyond tolerance from the expected quantity).

Because scale hardware and protocols vary enormously — continuous-print ASCII frames, poll-response command sets, checkweighers, floor scales, and bench indicators each speak differently — this is deliberately a made-to-order build rather than a one-size download. During scoping we confirm your exact indicator models, their protocol and framing, the Odoo edition (Community vs Enterprise — Enterprise unlocks IoT Box and Quality/quality app hooks we can target directly), and which flows you want weight written into. We then implement and parse your specific protocol, expose the readings over Odoo's JSON-RPC/XML-RPC API where you need external systems to consume them, and validate everything against your real devices.

Delivery is build-to-order: after a short scoping call and a fixed written quote, typical delivery is 2–4 weeks from confirmed scope, ending with UAT on a staging database, deployment to your production instance, and a support window. Pricing starts from $249 (indicative, single-company base scope for one scale protocol into one Odoo flow); additional protocols and indicator families, multi-company or multi-warehouse rollout, POS/MRP/Quality integration depth, and IoT-agent packaging for many concurrent weighing stations increase the quoted scope.