Traceability, or how serial numbers decide whether anything can be fixed
Knowing which machine has which parts, and why it decides everything after.
A serial number's real job is not to identify a machine at all, since a model name already does that well enough, its real job is to identify exactly which parts, which revision of each part, and which build decisions went into this one specific unit rather than any other unit that came off the same line looking identical.
Why identical-looking machines are not actually identical inside
Two machines of the same model, built a few weeks apart, can look completely interchangeable from the outside and still differ in ways that matter enormously the day something goes wrong: a supplier switch partway through the run that swapped one bearing for a nominally equivalent one from a different manufacturer, a firmware update applied to units built after a certain date but not before it, a design revision to a bracket that fixed a fault nobody had noticed yet in the earlier units. None of these differences show up in a casual inspection, since the machines were designed to be interchangeable in every way that matters to the end user, and most of the time they genuinely are. The differences only become significant the moment a fault is traced back to one specific version of one specific part, at which point the question stops being "does this model have the fault" and becomes "which individual machines actually have the part that causes it," and a model name alone cannot answer that question for a single one of them.
The library-copy comparison
A library holds many identical copies of the same book, all the same edition, all printed from the same plates, and to a browser scanning the shelf they are entirely interchangeable. Each individual copy still carries its own due-date card in the back, though, recording exactly which reader has had that specific copy and when, entirely separate from the record kept for every other copy of the same book on the same shelf. If one particular copy turns out to have a page torn out, the librarian does not need to withdraw the whole edition, only that one card's copy needs attention, since the tear happened to one book rather than to the print run as a whole. But if the fault instead turns out to be a printing defect affecting one specific batch, missing pages in every copy bound on a particular afternoon, the same card system is what lets the librarian identify exactly which physical copies came from that batch and pull only those, rather than emptying the whole shelf on a guess.
Why a serial number is a pointer rather than a label
A serial number by itself carries no useful information; its value comes entirely from what it points to in a separate record, which is normally a build log tying that one number to the exact parts, suppliers, and revisions used on that specific unit at the moment it was assembled. Stamping a number onto a machine without keeping that record behind it accomplishes almost nothing beyond letting two otherwise identical units be told apart by eye, which is not what traceability is actually for. The record has to be captured at the moment of build, too, since reconstructing it afterward from memory or from purchasing records that were never tied to individual units in the first place is unreliable at best and often simply impossible once enough time has passed and enough people involved in that specific build have moved on to other work.
The number that matters here
Without a working traceability record, a defect traced back to one bad batch of a single component can force a recall or an inspection of every single unit of that model a company has ever built, even though the faulty part in question might genuinely be present in only one machine out of every several hundred, the rest having been built before the bad batch arrived or after it was already used up. A working serial number and build log turn that same defect into a short, specific list of the actual affected units, at a fraction of the cost and the disruption of treating the entire fleet as suspect.
Why a technician needs the same number a recall does
A recall is the dramatic case, but the same information earns its keep on a far more ordinary day, whenever a technician opens up a machine in the field to fix it. A spare part ordered against the model name alone assumes every unit of that model is built the same way, and where a mid-run supplier switch or a design revision has quietly changed a bracket's hole spacing or a connector's pin count, that assumption fails at the least convenient possible moment, with the wrong part already unboxed and the correct one still sitting in a warehouse two days away. Reading the serial number and looking up its build record tells the technician exactly which revision of every relevant part this particular machine actually carries, turning a repair that might otherwise start with a guess into one that starts with a confirmed order. Machines that live a long service life accumulate this problem gradually rather than all at once, since a fleet bought over several years can easily span half a dozen quiet component revisions nobody outside engineering ever announced, and the serial number is the only thing standing between a technician and treating every one of those machines as though it were built on the same day as the newest one in the fleet.
What follows from this
Traceability only pays for itself once something has already gone wrong, which is exactly why it is so easy to underinvest in while everything is still working, and exactly why the investment has to be made before the first unit ships rather than after the first field failure makes the gap obvious. A build log kept faithfully from day one costs comparatively little to maintain alongside a production process that is already recording quantities and dates for other reasons, but a build log started only after a defect appears has already lost the information for every unit built before that point, and no amount of later diligence can recover what was never written down for those machines in the first place.