Home » News and Updates » GNSS Receiver RFQ: Buyer’s Checklist for the Right Quote

GNSS Receiver RFQ: Buyer’s Checklist for the Right Quote

GNSS receiver RFQ buyer's checklist feature image - spec accuracy, environment, form factor and volume for the right quote

To get the right GNSS receiver quote, your RFQ must specify four things that change price the most: accuracy class (RTK centimetre-level versus sub-metre), form factor (OEM board or enclosed receiver box), interference environment (clean sky or RF-dense — this decides whether you need AIM+ anti-jamming), and quantity. Send those four and a vendor can quote a real part number instead of a “please contact us” placeholder. The checklist below covers the full eight-point specification, so the quote you receive matches the receiver you actually need.

Get a quote / Talk to an engineer

Send your specification and we will price the right receiver or board — with the module, interfaces and accessories named.

Request a quote

The 8-point GNSS receiver RFQ checklist

An RFQ is a specification, not a shopping list. Each field below maps to a design decision that a vendor has to make for you — and that changes the price. Use this table as the template.

RFQ fieldWhat to specifyWhy it changes the quote
Accuracy classRTK centimetre-level (Eview boards/receivers are rated 0.6 cm + 0.5 ppm horizontal, 1 cm + 1 ppm vertical, ~7 s RTK initialisation) vs sub-metre vs decimetreDecides the correction engine and module tier
Form factorOEM board/module to integrate, or an enclosed/rugged receiver box you drop inBoard = lowest cost, highest integration effort; box = connectors, enclosure and I/O included
Constellations & bandsGPS/GLONASS/Galileo/BeiDou; L1/L2/L5; single vs multi-frequencySets the required channel count and module family
Interference environmentClean sky vs urban canyon, port/industrial RF, or deliberate jammingAnti-jamming (AIM+) options are a premium line item — only pay for it if you need it
HeadingSingle antenna (position only) or dual antenna for heading/roll/pitchDual antenna adds a second antenna and RF splitter
Update rate & interfaces1/5/10/20/100 Hz; UART, USB, Ethernet, CAN, PPSHigh rates and industrial I/O raise the module and carrier-board cost
Correction sourceLocal base + radio, NTRIP/network RTK, PPP (e.g. Galileo HAS) or SBASDetermines firmware/service options and link hardware
Quantity & lifecyclePrototype units vs serial production; warranty and support termDrives unit price breaks, lead time and stocking commitments

Accuracy class: give a number, not an adjective

“High precision” is not a spec. State the horizontal and vertical accuracy you must hold, in the conditions you operate in, and whether you need fixed-integer RTK or a float solution is acceptable. A survey workflow wants the full centimetre-level RTK rating; a mower or AMR may only need decimetre repeatability. If you cannot yet name the number, say which decision the position data feeds — stakeout, blade control, geofencing — and a vendor can propose the class. Note the ppm term too: accuracy degrades with baseline length, so tell the vendor how far your receiver will sit from the correction source.

Form factor, interfaces and volume

This is where most first quotes miss. An OEM board or module presupposes that you own the carrier board, power design and enclosure; a receiver box arrives ready to mount and cable. Tell the vendor which one, list your connector and protocol requirements, and give a realistic annual volume — even a “50 units year one” figure unlocks a production price that a one-off prototype will not. State whether you need the antenna and cable in the quote; assuming they are included is a common source of revision two.

Anti-jamming: the line most RFQs forget

If the receiver will ever work near power infrastructure, ports, industrial plant or a known interference source, add one line to the RFQ: “specify interference mitigation.” Septentrio’s AIM+ anti-jamming and anti-spoofing is built into Eview’s receiver line, so the question is not whether it exists but which configuration you need. Leaving it out means the quote comes back cheaper, then the receiver under-performs in the field and the real cost appears later. If the environment is genuinely clean, say so — that lets the vendor quote the leaner option honestly.

What a good GNSS receiver quote includes

  • A part number and the GNSS module inside it (for example mosaic-X5, mosaic-H for dual-antenna heading, or AsteRx-m3 Pro+)
  • The accuracy specification in writing, horizontal and vertical
  • Interfaces and update rate confirmed against your list
  • Antenna, cable and mounting accessories itemised — or explicitly excluded
  • Warranty term, support path and firmware/licence notes
  • Unit price by quantity band, and lead time

A quote missing any of these is a question waiting to be asked. Reply with your filled-in checklist and the second quote is usually the final one. To compare receivers before you RFQ, see the full receiver range or check the mosaic-X5-based receiver options.

Frequently asked questions

What information do I need before requesting a GNSS receiver quote?

At minimum: required accuracy (horizontal and vertical), environment (clean or RF-dense), form factor (board or box), interfaces and update rate, correction source, and quantity. Those six fields let a vendor name a specific part number rather than send a placeholder response.

Should I specify a module or just ask for a receiver?

Name the outcome, not the chip, unless you have already chosen. Say “dual-antenna heading, RTK, 20 Hz, Ethernet” and let the vendor map it to the right module. If you do need a specific module for an existing design, state it — that pins the quote to one SKU.

How long does a GNSS receiver quote take?

A complete RFQ — accuracy, environment, form factor, interfaces, volume — can usually be answered directly because the configuration is unambiguous. Incomplete RFQs take longer because the vendor has to open a clarification thread first. Attaching the checklist is the single biggest speed-up.

Can I request a quote for prototype quantities?

Yes. State both the prototype count and the expected production volume. Quoting the two together gives you a realistic unit price for each phase instead of an inflated one-off number that does not reflect the program.

How do I know the quote includes anti-jamming?

Ask for the interference-mitigation line explicitly and have the vendor confirm it in writing. If AIM+ is stated as included, the quote is complete; if it is absent, the receiver may still work in clean sky but will under-perform near jamming sources.

Get your GNSS receiver quote

Send the filled-in checklist to tina.ng@gnss-solutions.com and we will return a priced configuration with the module, interfaces and accessories named. Prefer to talk it through first? Contact our team and we will help you turn the requirement into a spec.

Latest News & Announcement