The model number is not the specification
Two units, same product name, same listing. Different radio modules, and one of them was missing the frequency bands the deployment depended on.
What happened
A product was ordered on the strength of its stated radio module. What arrived carried a different variant of that module, distinguished only by a suffix. The variant supported a narrower set of frequency bands and, critically, none of the low band coverage the deployment depended on for rural use.
The listing was not wrong exactly. It named the module family. The suffix that mattered was not mentioned anywhere.
Why this is common
Manufacturers substitute components across production runs based on availability and destination market. The model number identifies the product, not its contents. Regional variants are the usual culprit, and the difference is often exactly the thing that matters: supported bands, memory size, chipset revision.
What to do before ordering at volume
- Ask for the exact component part number including any suffix, in writing
- Ask whether it is guaranteed across the production run, or subject to substitution
- Say plainly which capability you depend on, so a substitution that breaks it is their error rather than your assumption
- Order one, verify it, then order the rest. The cost of a sample is always less than the cost of a batch
Verify on arrival
Query the device for its actual module identity rather than trusting the box. Then record it per unit, alongside the serial number, in whatever system tracks your inventory.
The reason to record it per unit rather than per model is that a mixed fleet is the normal outcome. Once you have two variants in circulation, "which units can do the thing" is a question you will be asked repeatedly, and it is answerable only if you wrote it down at intake.
Decide whether it actually matters
Sometimes it does not. A variant that is worse on paper may be fine for where the units are actually going, and holding out for the ideal specification can cost more in delay than the difference is worth. Work out what the capability is genuinely needed for before rejecting a shipment over a suffix.
Need help with any of this?
These notes are free and always will be. If you would rather someone just set it up, or you are stuck on something similar, get in touch at hello@opsira.io.