Scales that actually talk to the batch record.
Cloud-only QMS tools stop at the form field. V5 reads the scale itself — Bluetooth, serial, USB or straight over the network — pipes live tare/zero/weight into the dispense step, enforces tolerance against the formula, and seals the reading into the batch record with the operator's e-signature. No 're-key the weight' step. No paper variance.
What changes once Connected scales & weighing is live.
Indicative ranges from V5 pilot deployments. Your numbers will land near these once the workflow is operator-led and e-signed at the step.
What changes the day you switch this on.
Manual, paper-driven, and only audited after the fact.
Tribal knowledge in spreadsheets and shared drives.
Errors caught at month-end — too late to fix the batch.
Different teams keep their own version of the truth.
Bluetooth, serial, USB and network
Networked floor scales & PLC-fed indicators
Tolerance bands per formula line
Tare, zero, captured at every step
What you actually get
Operator-led, e-signed, immutable. Engineered for regulated manufacturers — not retrofitted.
Bluetooth, serial, USB and network
Supports Bluetooth scales (Mettler Toledo, Sartorius, A&D, HID Bluetooth-keyboard wedges), serial scales via a small device bridge, USB HID scales straight into the kiosk browser, and networked scales over Ethernet/Wi-Fi (TCP/IP, Modbus TCP, OPC UA, REST) — including floor scales and bench balances already wired into the plant LAN.
Networked floor scales & PLC-fed indicators
Ethernet-connected indicators (Mettler IND/ICS, Rice Lake 1280, Avery E1310, Sartorius Combics) stream weight over TCP/IP or Modbus to the kiosk in real time — no per-station USB cable, one scale can serve multiple stations, readings still pinned to the operator and station that took them.
Tolerance bands per formula line
Each BOM line carries target ± tolerance; the kiosk dial turns green only inside band. Out-of-band weighings require an explicit override e-signature and open a deviation.
Tare, zero, captured at every step
The reading sealed to the eBMR includes tare and gross — auditors can reconstruct the weighing, not just the net.
Per-station device bindings
Each kiosk station is bound to its scale, label printer and scanner in admin — no operator picks the wrong device, no driver-juggling on shift change.
Calibration on a schedule
Devices have calibration_at; due/overdue surfaces on the daily brief and the .ics calendar feed. An out-of-cal scale refuses to write to a regulated record.
Campaign weighing & parallel stations
Multiple operators weigh in parallel against the same WO; shared-container groups consolidate. Every reading carries its station ID into the BMR.
Curious how this lands in your environment?
From the operator's first scan to the signed record.
The operator journey is guided by logic, not memory. Every step is signed, sequenced, and immutable.
- 01
Bind a scale to a station
Admin binds a scale (Bluetooth, serial, USB, Ethernet/IP) to a kiosk station. Operators never see device picker dialogues.
- 02
Operator opens a dispense step
Kiosk pulls the target weight and tolerance from the formula; the live reading dial turns green only inside the band.
- 03
Tare & zero captured
The reading sealed into the eBMR includes tare and gross — auditors reconstruct the weighing, not just the net.
- 04
Out-of-band override
Outside tolerance? Step requires explicit override e-sig and opens a structured deviation linked to operator, equipment, lot and step.
- 05
Sign, advance, next
Operator e-signs; the BOM line advances; the next dispense loads. Campaign weighing supports parallel operators on the same WO.
Want to dig deeper into the workflow?
Concrete scenarios, not slideware.
Mettler XPR over Bluetooth, target 12.500g ± 0.050g, the operator pours into the green, the system writes 12.487g, tare 245.1g, witness Smith.
Mettler IND570 + Avery floor scale on Ethernet, tote dispense, target 25.0kg ± 0.5kg, scanned tote ID pins the read to the right container.
Three operators weighing in parallel against the same WO; readings carry station IDs; shared-container groups consolidate to the BOM line.
Does any of this look like your day?
Hardware, ERP, the rest of V5 — already wired.
Mettler Toledo, Sartorius, A&D, plus HID keyboard-wedge fallback for legacy devices.
Small device-bridge box pipes RS-232 readings into the kiosk over the LAN — no per-station USB cable.
Straight into the kiosk browser, zero driver install.
Mettler IND/ICS, Rice Lake 1280, Avery E1310, Sartorius Combics — TCP/IP, Modbus TCP, OPC UA, REST.
One network scale can serve multiple stations; readings still pinned to the operator and station that took them.
Don't see your system?
The edge cases buyers always ask about.
Refuses to write to any regulated record. Daily brief surfaces the due date so it never bites mid-shift; emergency cal is supported with full audit trail.
Re-tare is captured as a structured event with reason; the original and corrected readings both stay in the audit trail.
New tare captured; the WO step links both events; the BMR shows the full sequence so QC can trace the operator's actions.
Have your own edge case in mind?
One operator action — a complete, signed record.
What it leaves behind
- Bluetooth + serial + USB + Ethernet/IP supported
- Networked floor scales (Mettler/Rice Lake/Avery) stream over TCP/IP
- Tolerance enforced in real time
- Calibration overdue blocks regulated writes
- Reading + tare + operator e-sig sealed to the eBMR
The clauses this satisfies
What buyers ask before they switch on Scales that actually talk to the batch record..
The rest of the platform this plugs into.
V5 isn't a bolt-on. Every module shares the same data, the same audit trail, the same operator. Pick where to look next.
MES
Operator-led execution: scan-gated dispense, step-by-step kiosk, equipment + scale integration, live yield. Built for regulated process & discrete manufacturing.
WMS
Receiving, putaway, transfers, cycle counts, picks, pack & ship — all lot-aware, bin-accurate, FEFO/FIFO-enforced and barcode-driven.
QMS
Built-in QMS: deviations, CAPA, supplier scorecards, in-process AQL, release-by-exception. Aligned with 21 CFR 211/820, ISO 13485 and 111.
Got questions, or want to see it on your shop floor?
Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.