Every Weighing Scale Needs a Name: Why Device Identity Matters

Forty scales, one server. Without a name on each reading, the data is a rumour.

A reading that reaches your server as “512.4 kg at 10:42” tells you almost nothing. Which scale? Which line? Weighing scale serial number identification — the permanent number a scale carries on its plate and quotes on everything it sends — is what turns that number into a record. This article explains why the law, the auditor and the server all insist on it, and how a connected scale from Hindustan Scale Company carries its name from the factory to the record.

Forty scales, one server: why a reading without a name is a rumour

Picture forty scales feeding one server, three thousand readings a day. If the scale that sent one of them is anonymous, that reading is a fact with no owner. You cannot total it by line. You cannot see that one scale has started reading heavy. You cannot answer the customer who says the bag was light.

Regulators have a word for what is missing: attributable. The UK medicines regulator’s 2018 data-integrity guidance says data must be traceable to the person who generated it — or, when a machine generated it, to the original data source; without that context, “the data has no meaning”. The World Health Organization’s 2021 data-integrity guideline uses a weighing example: the number 8 is meaningless without its metadata — the unit, the time, the operator, and “the instrument ID used”.

So the first question to ask of any connected scale is not its capacity. It is: what name does it put on each reading, and can anyone change that name?

Why is weighing scale serial number identification required by law?

Because measuring instruments are regulated by identity.

The international recommendation for weighing instruments, OIML R 76-1, requires descriptive markings on every scale: the manufacturer, the accuracy class and the capacity in all cases; the serial number wherever national rules call for it; and — with no qualification at all — a type designation, a serial number and the manufacturer’s name on every separately tested module (an indicator, a weighing platform) and every peripheral. The markings must be indelible, on a plate or a non-removable part. The US commercial-weighing code, NIST Handbook 44 (2026 edition), says every device must be “clearly and permanently marked” with the manufacturer, the model and “a nonrepetitive serial number” — a rule that applies to every device made since 1 January 1968.

In India the Legal Metrology Act, 2009 works in the same direction. A model must be approved before it is made or imported (section 22), and every instrument used in trade must be verified and stamped before it is put to use (section 24). The Act also makes unverified and non-standard equipment expensive, as the Government of India’s text of the Act and the Delhi Legal Metrology Department’s published penalty table both set out:

What the Act says	Fine, first offence	Second or later offence
Using a non-standard weight or measure (section 25)	up to ₹25,000	up to 6 months’ imprisonment, plus a fine
Selling, transferring or using an unverified weight or measure (section 33)	₹2,000 to ₹10,000	up to 1 year’s imprisonment, plus a fine

Neither penalty is for a missing number. But approval, verification and stamping all attach to a specific instrument, and the number on the plate is how everyone agrees which instrument that is.

The auditor’s first question: which scale did this come from?

Ask anyone who has sat through a pharmaceutical inspection. The first question is never “was the weight right?” It is “which balance?”

Three regulators, independently, require the batch record to name the equipment. The US rule (21 CFR 211.105) is the most explicit: major equipment must carry “a distinctive identification number or code” recorded in the batch record — a plain name is allowed only when the factory has just one of that kind. The EU’s GMP guide (Chapter 4, in force since 30/06/2011) requires the batch processing record to show the “major equipment used”. India’s revised Schedule M, notified on 28/12/2023, says the same.

Laboratories hear the same thing. ISO/IEC 17025:2017 requires a record for every item of equipment that can influence a result, including the manufacturer’s name, the type and “serial number or other unique identification” (clause 6.4.13), and a label or code on each instrument showing its calibration status (clause 6.4.8). ISO 9001:2015 requires measuring equipment to be identified so its status can be determined (clause 7.1.5.2) — identification, not necessarily a serial number.

The moment a plant owns two scales of the same kind, “the platform scale” stops being an identification; the US rule says so in as many words. And when the scale creates the record itself, it has to write its own name. Nobody is standing there to type it.

What happens when two scales share a name

The server is the least forgiving auditor.

The standard machine-to-machine messaging protocol used by IoT devices, MQTT, settles the question in its rulebook. The OASIS standard (version 3.1.1 of 2014 and version 5.0 of 2019) requires the server, when a second device connects with an identifier already in use, to disconnect the first one. Version 5.0 even names the event: “Session taken over”. A major cloud IoT service documents the same behaviour and runs an audit check that flags duplicate device IDs as a fault. On a factory floor, two scales with the same name take turns knocking each other off the server. Readings vanish. No error is shown, because nothing has technically gone wrong.

The security world reached the same conclusion. NIST’s 2020 baseline for IoT device security (NISTIR 8259A) lists six core capabilities, and the first is device identification: a unique logical identifier and a unique physical one — and the logical identifier, NIST says, “may require that it be immutable”. Europe’s consumer-IoT standard, ETSI EN 303 645 (2020), requires a hard-coded per-device identity to resist physical, electrical or software tampering — wording India’s Telecommunication Engineering Centre adopted in its 2025 Code of Practice for Securing Consumer IoT.

Unique, permanent, tamper-resistant. That is the whole specification for a device name, whether the device is a smart lock or a 3-tonne platform scale.

Written once, locked for life: how a connected scale carries its name

A connected weighing scale from HSCo leaves the Mumbai factory with a permanent number, written once and locked for the life of the scale. From then on it appears in three places, and it is the same number in all three.

1. The Bluetooth name. A Bluetooth device announces a human-readable “local name”, which the Bluetooth specification defines as the name assigned to the device — it is what a phone lists before anything is paired. On an HSCo Bluetooth platform scale that name is the factory number. Forty scales in range means forty different names, and the operator picks the one on the plate in front of him.
2. The power-on display. Each time the scale starts, the number is shown on the display, so the person at the scale can check it against the plate — the very check OIML R 76-1 describes for a serial number held in software.
3. The machine ID on every reading. Every reading uploaded through HSCo’s cloud relay carries the factory number as its machine ID. The server never guesses, and no operator types a scale name into a form. The data logging and reports built on those records are grouped by that number.

“Locked” is the important word. OIML R 76-1 allows a serial number to be held in software, but only if it is protected against change and any intervention leaves evidence — its example is a non-resettable counter that ticks up every time a protected setting is altered. NIST Handbook 44 likewise requires electronic adjustments to be sealed or logged in an audit trail available at inspection. A name anyone can retype in a settings menu is a sticker, not an identity.

Three things a device name is not:

• It is not a replacement for the plate. The physical marking stays; the law wants it, and NIST’s baseline wants it for the moments when the electronic identity cannot be read — installation, decommissioning, a dead board.
• It is not a nickname. “Line 2 scale” is a fine label inside your software, mapped to the number. But the number is what the scale says about itself, and what goes in the record.
• It is not proof that the reading is right. Identity says which scale; it says nothing about whether that scale is calibrated, verified or stable. It is what makes those facts findable.

What changes for you on Monday morning

1. Every reading has an owner. Total by scale, by line, by shift — nobody adds a column by hand.
2. The auditor’s first question takes a minute. The batch record, the calibration file and the server record all name the same scale. Three documents, one number, no arguing.
3. Nobody re-types a scale ID. The field most often wrong is now written by the scale itself.
4. A drifting scale can be found. If one scale starts reading heavy, you know which one — and can pull every reading it produced since its last verification.
5. Replacement is clean. A new scale arrives with a new number; the old scale’s history stays attached to the old one, where the auditor expects to find it.

Count how often last month someone asked “which scale?” and how long each answer took. That is the time a permanent name gives back.

How to start: name every scale in thirty days

1. Week 1 — take the roll call. List every scale with the number on its plate, its location and the software that receives its readings. A scale without a legible number gets flagged now, not at the audit.
2. Week 2 — connect one scale. Pick the line where “which scale?” is asked most. Connect one scale and confirm that the plate, the Bluetooth name, the power-on display and the machine ID on the server record all show the same number.
3. Week 3 — labels for people, numbers for records. Map each number to a plain-language label in your software (“Line 2”, “Bay 4”).
4. Week 4 — hand the auditor a day. Give your QA head one day’s readings by scale. If she can answer “which scale, when, how much” without asking anyone, roll out the rest.

Hindustan Scale Company has made weighing scales in Mumbai since 1955 and builds the scale, the number, the app and the cloud platform itself — one supplier answers for the whole chain, plate to record.

Frequently asked questions

What is a weighing scale serial number, and where do I find it?

It is the permanent, non-repeating number a manufacturer gives each scale, marked on a plate or a non-removable part of the instrument. On a connected scale it should also be shown on the display at power-on and carried on every reading the scale sends.

Is a serial number legally required on a weighing scale?

The international recommendation for weighing instruments, OIML R 76-1, requires a type designation, a serial number and the manufacturer’s name on every separately tested module, and the US code requires a nonrepetitive serial number on every device. In India the Legal Metrology Act, 2009 requires the model to be approved and every trade instrument to be verified and stamped before use — and that verification attaches to a specific instrument.

Can the device ID of a connected scale be changed?

It should not be. Metrology standards allow the serial number to be held in software only if it is protected against change and any intervention leaves evidence, and IoT security baselines say the identifier may need to be immutable. On an HSCo connected scale the factory number is written once and locked for the life of the scale.

Why does the Bluetooth name of a scale matter?

Because the Bluetooth name is what the phone shows in its device list before anything is paired. When the name is the scale’s factory number, the operator can match the phone to the plate in front of him, even with dozens of scales in range.

What happens if two connected scales have the same ID?

On the standard IoT messaging protocol the server must drop the existing connection when a second device connects with the same identifier, so the two scales take turns knocking each other off — and readings go missing without an error. A major cloud IoT service audits for exactly this fault.

Does a device ID replace the stamped plate?

No. The physical plate remains a legal requirement and is the fallback when the electronic identity cannot be read — at installation, at decommissioning or after a failure. The device ID is the same number, carried into the Bluetooth name, the display and every record.

Next step

Tell us how many scales feed your records today, and we will show you what one day’s readings look like with a name on every one.

Hindustan Scale Company (HSCo) · Mumbai · est. 1955 · www.hindustanscale.com · hsc@hindustanscale.com

Sources

1. OIML R 76-1:2006 (E) — Non-automatic weighing instruments, Part 1: Metrological and technical requirements — Tests, clause 7.1 (descriptive markings: 7.1.1–7.1.5) and clause 4.1.2.4 (securing of device-specific parameters; event counter; stored serial number).
2. NIST Handbook 44 – 2026 edition, Section 1.10 General Code: G-S.1 Identification (“a nonrepetitive serial number”, nonretroactive as of 1 January 1968) and G-S.8 Provision for Sealing Electronic Adjustable Components.
3. The Legal Metrology Act, 2009 (Act 1 of 2010), Government of India, sections 22, 24, 25 and 33; Department of Legal Metrology, Government of NCT of Delhi — Penalties table.
4. US Code of Federal Regulations, Title 21, §211.105 Equipment identification (FDA Current Good Manufacturing Practice).
5. European Commission — EudraLex Volume 4, EU GMP Guidelines, Chapter 4: Documentation, para 4.20(e) (revision in force 30/06/2011).
6. Ministry of Health and Family Welfare, Government of India — G.S.R. 922(E), 28 December 2023: revised Schedule M to the Drugs Rules, 1945, Part I para 17.3.8.3(g) and API part para 6.5.3(ii).
7. ISO/IEC 17025:2017 — General requirements for the competence of testing and calibration laboratories, clauses 6.4.8 and 6.4.13; ISO 9001:2015 clause 7.1.5.2 Measurement traceability.
8. MHRA (UK) — ‘GXP’ Data Integrity Guidance and Definitions, Revision 1, March 2018.
9. World Health Organization — WHO Technical Report Series No. 1033 (2021), Annex 4: Guideline on data integrity.
10. OASIS — MQTT Version 3.1.1 (OASIS Standard, 29 October 2014), sections 3.1.3.1 and 3.1.4; MQTT Version 5.0 (OASIS Standard, 7 March 2019), section 3.1.4; AWS IoT Core Developer Guide — “Conflicting MQTT client IDs” audit check.
11. NIST — NISTIR 8259A, IoT Device Cybersecurity Capability Core Baseline (May 2020), Table 1; ETSI EN 303 645 V2.1.1 (2020), Provision 5.4-2; Telecommunication Engineering Centre, Department of Telecommunications, Government of India — Code of Practice for Securing Consumer IoT, TEC 31318:2025 Release 2.0, section 3.4.
12. Bluetooth SIG — Supplement to the Bluetooth Core Specification v14 (2025), Part A, section 1.2 Local Name.