示意预览A build-to-order Odoo module that captures live weight readings from your hardware scales and writes them
directly into Odoo inventory, POS, and quality flows.
ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment.
什么是 Universal Scale Reader？
A build-to-order Odoo module that captures live weight readings from your hardware scales and writes them directly into Odoo inventory, POS, and quality flows. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线，并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
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 one working week from confirmed scope, ending with UAT on a staging database, deployment to your production instance, and a support window. Pricing starts from $999 (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.
你得到什么
- Installable Odoo module source code for your edition (17.0/18.0/19.0), built to your confirmed scale protocols and target flows
- Installation and configuration on your environment, including device profiles, station assignments, and the local bridge agent where serial scales are involved
- Technical documentation: models, fields, security rules, protocol-parser design, and configuration reference
- End-user guide plus a live training session for weighing-station operators and administrators
- UAT on a staging database against your real scale hardware, with a documented rollback plan before production cutover
- Post-go-live support window for defect fixes and configuration adjustments
- Git repository handover with full commit history and tagged release
- Version-compatibility notes and upgrade guidance across Odoo 17.0/18.0/19.0
这是给谁的
Warehouse & Inventory Manager
Runs receiving, put-away, and shipping in Odoo and needs actual weights captured at the dock instead of re-keyed. Wants catch-weight accuracy on `stock.move.line` and an audit trail that survives disputes over short or over shipments.
Food, Produce & Chemical Operations Lead
Handles variable-weight products where every unit differs and pricing follows measured weight. Needs the scale reading to drive quantities and weigh-slips reliably, with tolerance checks to catch mis-weighs before they hit invoices.
Manufacturing / Quality Manager
Records weight-based measurements during production or QC and wants them written straight into `mrp` consumption or `quality.check` measures, not transcribed later, with the raw reading kept for traceability.
IT / Odoo Systems Owner
Responsible for the Odoo instance and integrations. Wants a properly structured addon with clean security (`ir.model.access.csv` + record rules), maintainable protocol code, RPC access for downstream systems, and a supported upgrade path across editions and versions.
Universal Scale Reader 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Fit to your exact scales | Parser built to your confirmed indicator models and protocols | Possible but you specify and validate every protocol yourself | Supports a fixed device list; your scale may not be covered | No scale support at all — manual weight entry only |
| Capture into Odoo flows | Writes to stock, POS, MRP, and Quality flows you choose | Whatever you scope and build in-house | Usually one flow (often POS or receiving) only | Operators re-key weights by hand on each document |
| Audit trail | Immutable `scale.reading` records with gross/tare/net retained | Only if you design and build it | Often none — reading overwrites the field | No record of what the scale reported |
| Time to value | Scoped quote, typically one working week to production | Hire, spec, build, and test from scratch — months | Fast install if your device is supported | Immediate, but the manual process never improves |
| Security & access control | `ir.model.access.csv` + record rules per weighing station | You implement and audit it | Generic access; per-station scoping rarely included | Standard Odoo access only; nothing scale-specific |
| Version & edition support | Built for 17.0/18.0/19.0, Community or Enterprise | You maintain compatibility yourself | Depends on vendor's release cadence | Native to each version but offers no scale features |
| Ownership & lock-in | Full source in a git repo you own | You own it but carry all maintenance | Licensed binary/source per vendor terms | N/A — no product to own |
| Support & changes | Post-go-live support window; follow-on work scoped | Your team or none | Vendor support tiers, variable responsiveness | General Odoo support; no scale expertise |
关于Universal Scale Reader的常见问题
How long does delivery take?
This is a build-to-order module, not an instant download. After a short scoping call and a fixed written quote, typical delivery is one working week from confirmed scope. Timeline depends mainly on how many distinct scale protocols and Odoo flows are involved; we confirm the date in the quote before any work starts.
Will it work with my specific scales?
That is exactly what scoping determines. Hardware scales and weight indicators speak many different protocols — continuous ASCII streams, poll-response command sets, and various framing schemes. We confirm your exact indicator models and protocols during the scoping call and build the parser to match them. If a device speaks over serial/USB we include a local bridge agent; network-capable indicators are read directly over TCP or HTTP.
How does pricing and scoping work?
Pricing starts from $999 as an indicative, single-company base scope for one scale protocol into one Odoo flow. It is not a fixed final price. After a scoping call we send a fixed written quote for your actual requirements — additional protocols, more indicator families, multi-company or multi-warehouse rollout, POS/MRP/Quality depth, and many concurrent stations all increase scope. You approve the quote before we build.
Which Odoo versions and editions do you support?
We build for Odoo 17.0, 18.0, and 19.0, on both Community and Enterprise. Enterprise unlocks additional targets we can hook into directly, such as the IoT Box and the Quality app; on Community we implement equivalent capture through the addon and a local bridge. We confirm your edition during scoping because it affects which integration paths are available.
What about support and updates after go-live?
Every engagement includes a post-go-live support window for defect fixes and configuration adjustments, and you receive the full source in a git repository so you are never locked in. Version upgrades (for example moving from 17.0 to 18.0 or 19.0) and new scale devices added later are handled as scoped follow-on work, quoted separately.
Can captured weights be used by our other systems?
Yes. Readings and devices are standard Odoo models, so they are available through Odoo's JSON-RPC and XML-RPC API. External MES, LIMS, or WMS platforms can read captured weights programmatically, and we scope any specific integration endpoints you need as part of the build.
How do you make sure it is correct before it goes live?
We run UAT on a staging database against your real scale hardware, so you validate captured weights, tolerance rules, and reports before anything touches production. Cutover follows a documented rollback plan, and readings are stored as immutable `scale.reading` records so there is always an audit trail of what the scale actually reported.
相关模块
Universal Scale Reader
A build-to-order Odoo module that captures live weight readings from your hardware scales and writes them directly into Odoo inventory, POS, and quality flows. ECOSIRE scopes, builds, installs, and supports it for your Odoo 17/18/19 environment.
- Device registry model (`scale.device`) storing connection type (serial/TCP/HTTP), protocol profile, baud/framing, and per-station assignment via record rules
- Protocol parser built to your exact indicator — continuous-stream ASCII frames, poll-response command sets, or vendor STX/ETX framing — with stability-flag detection so only settled weights are committed
- Live weight OWL widget embedded in the target view (receiving, delivery, POS, or quality check) showing stabilized reading before one-click capture
- Immutable `scale.reading` audit records (gross, tare, computed net via `@api.depends`, unit, captured_at, device, user) retained independently of the document