Serial Numbers and PIN Programming

What 'serial numbered' means in practice

There are two different requests behind the phrase, and they need different handling:

• A visible number on each lock, so a unit can be identified and recorded by staff or by a tenant.
• A number matched to something else — a combination, a tenant record, a unit number — where the pairing matters as much as the number.

The first is a marking job. The second is a data job, and the failure modes are different.

The file you send, and what we check

Data orders run on a simple file: one row per unit, with the serial or unit reference and, where applicable, the code that goes with it. Excel and CSV both work.

Before production we check the file for the errors that cause most rework:

• Codes that are shorter than the mechanism allows — a four-digit combination cannot be set from a three-digit entry
• Duplicates — the same number appears twice, or two units share a code
• Missing rows — the file has fewer entries than the order has units
• Formatting drift — mixed lengths, stray spaces, or characters the engraving process cannot reproduce

If we find a problem, we tell you before production starts rather than shipping around it.

Why codes and serials must be reconciled

A number on the outside of a lock is only useful if it tells you something about the inside. If serial 0001 carries combination 4821, that pairing has to be recorded — by us at production, and by you at handover.

Unreconciled data is worse than no data: it looks authoritative while being wrong. The practical answer is a single master file, agreed before production, that both sides hold and that lists every unit with its number and code.

Marking, and what survives handling

How the number is applied matters as much as the number itself. A mark that survives a warehouse but not a winter on a door is not a serial number, it is a temporary label.

Engraved or laser-applied marks are permanent; printed labels are not, and on a product handled outdoors a label is usually the wrong choice. Where the mark has to be read at a distance, size and contrast matter more than the method.

Errors we catch before production

The commonest data faults are mundane and cheap to fix in advance: codes that are too short, duplicated serials, a file with the wrong row count, and formatting that varies within the same column.

None of these are exotic. All of them are expensive if they are discovered at packing, because by then the goods exist and cannot be corrected without rework.

What we typically see

• A code file where a portion of the combinations are shorter than the mechanism supports.
• Serials specified in a format the customer's own systems cannot import.
• A request for a number on the lock and a code on the packaging, with no link between the two.
• A data set prepared after the order instead of before it, holding up production.

How to prepare your file

One row per unit, a consistent format within each column, the serial and the code in separate columns, and a row count that matches the order. Send it before production is scheduled rather than alongside it. We will confirm what is feasible and flag anything that needs correcting before anything is engraved.