Published 2026-10-20 · LuckyMDM Blog
The bottom line: the model field in a device register is not one field. A serial number identifies the unit, the model number — the A-number — identifies the hardware variant, the part number encodes region, origin, capacity and colour, and the marketing name is a channel shorthand that no system validates. A register keyed on the marketing name looks correct on the day it is built and starts drifting the first time a unit arrives from another region, another channel, or a service replacement.
The cost is not in the data entry. It is in every decision that later reads that column.
A field deserves its own column when the value has a different owner and a different change trigger. These four do.
Open Settings, then General, then About. The row labelled Model Number shows a value like MU2Q3CH/A. That is a part number. Tap the row once and it switches to the A-number, the model number proper; tap again and it switches back.
That one interaction defines the field. The underlying mechanism is that a single label is bound to two values, and neither the screen nor the packaging states which one you are looking at. The same visible label points at two different values, so if a register does not state which one it stores, two importers will record two different things under the same column name and the two columns will never reconcile. One clerk copies the part number, another copies the A-number, and both are "the model".
The first character of a part number describes where the unit came from:
These five origins retire differently. A demo unit has accumulated far more screen-on time than retail stock, and a service replacement carries the original unit's warranty start date rather than the swap date. If the register holds a single model column, that layer is lost at intake and later comes back as a judgement call made from memory.
The A-number identifies the hardware build. The same generation, size and capacity shipped to different regions can carry different A-numbers, because the hardware differs: how many SIM slots exist, whether mmWave antennas are fitted, whether eSIM alone is supported. Those are set on the line, not by a firmware flash.
The layering is therefore clean: the serial number identifies this unit, the A-number identifies this class of hardware, the part number identifies this sales specification. Drop a layer and a whole category of question becomes unanswerable.
Reading "US model, China model, Japan model" as a warranty difference is the most common simplification in the secondary market. It misses the parts that affect operation and disposal. The table below lists only differences a technician can confirm on a bench:
| Dimension | Mainland China (suffix CH/A) | United States (suffix LL/A) | Japan (suffix J/A) |
|---|---|---|---|
| Physical SIM | Dual nano-SIM tray | No tray, eSIM only from iPhone 14 onward | Single nano-SIM tray plus eSIM |
| mmWave antennas | Not fitted | Fitted, bands n260 and n261 | Not fitted |
| Camera shutter sound | Can be silenced | Can be silenced | Cannot be silenced |
| Warranty service location | Mainland China | United States | Japan |
| Extra check at intake | Whether both SIM slots are registered | Whether eSIM-only operation fits the use case | Whether the shutter sound affects the use case |
The point of the table is not memorisation. It is that the suffix changes the acceptance procedure. A US unit run through a China-unit checklist skips the step where the question "there is no tray, so where does the ICCID come from" gets answered. A Japanese unit run through the same checklist produces a false fault report about a shutter sound that cannot be muted by design.
Apple removed the physical tray from US models with the iPhone 14 line in September 2022. From that date onward the region suffix stopped being a warranty footnote and became a field that has to be captured at intake.
This is where the three-layer structure is most often collapsed by accident. A whole-unit warranty replacement usually shares the original hardware variant, so the A-number stays the same while the part number prefix becomes N. Certified refurbished units shift to F. Which means:
The fix is not to choose. It is to give each field one job and join them on the serial number.
How many columns the model layer needs depends on how many questions it must answer. Fill these five and intake stops leaking:
With those columns populated, "the same batch that turns out to be three different machines" is caught at intake rather than at disposal.
A 1,000-device fleet with 5 percent arriving through transfers, secondary channels or service replacement carries 50 affected units. If the model column was filled from the marketing name, one grade of misclassification is enough, and the spread between adjacent grades on the secondary market is commonly USD 30 to USD 55 per unit:
The ratio is the smaller half of the argument, and it depends on how you price an hour. The larger half is the denominator: verification cost barely moves with fleet size, while exposure scales linearly with it. At 1,000 devices the extra two columns already pay for themselves; at 5,000 devices, backfilling the data alone costs 28 hours.
No tooling required, about two minutes:
Step two is the one people skip, and it is the only action that separates the two values that share one label.
It is the part number. The A-number appears only after a tap, and the two answer different questions — the part number tells you region and origin, the A-number tells you the hardware variant.
SIM arrangement, mmWave antennas and shutter sound are hardware or firmware differences that do not follow the warranty policy. For a US unit used outside the US, eSIM-only operation alone can rule out a use case.
Capacity and colour are not encoded in the A-number. Under one A-number, the 128 GB black and the 256 GB white are two different part numbers, and at disposal the spread between them can run to hundreds.
Boundary one: Macs and iPads do not follow this structure. On the Mac side the key is the model identifier in the MacXX,Y form together with the chip designation, and iPad part numbering follows its own rules. Applying the iPhone three-layer model to a Mac register produces a column that is neither a model nor a specification.
Boundary two: bulk service replacement changes the prefix in batches. If the part number is the primary key, one intake batch can create dozens of "new device" records. De-duplicate on the serial number first, confirm it is the same hardware, then update the origin column instead of inserting a row.
They are the region code. CH is mainland China, LL is the United States, J is Japan, ZP is Hong Kong and Macao, KH is Korea, ZA is Singapore. The code lives in the part number, not in the A-number.
Because capacity, colour and origin differ. The A-number locks the hardware variant only; it does not encode storage size or finish.
Usually yes, since a warranty swap provides the same hardware variant. What changes is the part number prefix and the serial number — which is why de-duplication runs on the serial number, not the model.
Yes, but only by reading each device. At 20 seconds per unit, 1,000 devices is 5.6 hours, and that is the floor. Judgements already made from the old column cannot be reversed, only overwritten at the next disposal.
Compare the A-number, not the name. Supplier paperwork generally uses the marketing name, which carries neither region nor origin and therefore cannot support an intake decision.
LuckyMDM (Sichuan Starlight Network LLC) stores the A-number and the part number as two separate fields on the device record, with origin kept as its own field so that a warranty replacement updates origin instead of creating a second record. The point of the split is not field count: it is that when someone asks what a unit actually is, the answer comes from the register rather than from whoever handled the intake.