If you are adding GNSS protection to several platform variants, decide whether one model can remain on every platform’s shortlist before asking for a single fleet quantity. A compact platform and a larger vehicle may need different signal records or have different space limits, even when both retain their existing receivers.
The purchasing decision is whether to evaluate a common model or separate model lines. It is not yet a decision that either installation is compatible or ready to deploy.
Build one shortlist per platform, then look for the overlap
Keep each platform’s mandatory requirements together. A model belongs on a common shortlist only if its documented configuration meets the initial screening requirements of every platform it would serve.
Do not start by assigning the broadest signal requirement to every vehicle and selecting the model with the most listed bands. That model may fail a smaller platform’s physical limit. Conversely, a compact model that fits all the available spaces may lack a published record for a signal required on one platform.
Distinguish a documented mismatch from an unanswered question. A body larger than a fixed available envelope can be excluded for that envelope. An unlisted signal leaves support unresolved; it does not prove non-support. Neither case justifies treating the model as an established common choice.
A two-platform example: the order cannot yet be consolidated
Consider a hypothetical buyer retaining two existing receivers. Platform A needs GPS L1 and BDS B1, with an 80 × 80 mm maximum area for the product body. Platform B also requires GLONASS G1 and allows a 160 × 150 mm body area. These are illustrative screening conditions, not customer specifications or complete installation clearances. This initial screen does not assess product height, mounting hardware, connectors or cable clearances.
The RN-S65-4CH-SNB record lists GPS L1 and BDS B1 and a 65 × 65 × 21 mm body. It remains a candidate for A’s stated signal-and-plan-size screen. Its public signal record does not establish the G1 requirement for B.
The RN-009Pro-8CH-G1-WG-DT record lists BDS B1, GPS L1 and GLONASS G1 and a 150 × 130 × 21 mm body. It remains a candidate for B’s stated screen, but its body cannot fit A’s fixed 80 × 80 mm area.
Among these two candidates, the public records therefore do not establish one model for both platforms. Keep two evaluation enquiry lines: S65 for A and G1 for B. This conclusion concerns the stated screening conditions only, not RF compatibility, installation approval or performance. Review other models in the catalogue if their documented configurations might satisfy both sets of requirements.
When is a common-model quotation worth pursuing?
If A genuinely has room for the G1 model’s body, the stated signal-and-plan-size conflict disappears. G1 could then enter a common-model evaluation for A and B. Do not relax a fixed platform limit just to obtain a single model number.
Next compare the remaining requirements separately for each platform. A shared model can still require different installation items, and its RF output must be assessed against each retained receiver. Use the receiver compatibility guide for that boundary. Passing the initial screen on both platforms does not make one receiver’s integration evidence apply to the other.
Compare common and split offers on the same purchasing scope
For a common-model offer, keep the intended quantities for A and B visible even if the hardware appears on one price line. Identify any platform-specific installation items separately. For a split offer, associate each model and quantity with the platform it is intended to serve. Do not compare a common offer including installation items with a split offer containing terminal bodies alone.
Treat a proposed common spare in the same way. It becomes a usable replacement for both platforms only after both configurations are accepted for that role; a shared product family or similar enclosure does not establish interchangeability.
Start with the S65 or G1 product record above and use its existing model-specific enquiry button. Explain whether you want separate evaluation lines or are considering one common configuration. Quantities can remain undecided at first contact. The useful outcome is a defensible order structure, not an assumed volume discount or a promise that one model fits the fleet.
NEXT STEP
Turn available platform information into an engineering review.
Use the Technology centre to frame the discussion, review relevant application scenarios, then send the available platform and receiver details for confirmation.