Home › Insights › From Datasheet to Volume: How a Custom Radar Programme Runs

From Datasheet to Volume: How a Custom Radar Programme Runs

The part of a radar supplier you actually buys is the process. This is how ours works, stage by stage.

Launston Engineering•2026-10-30•8 min read

Most radar module suppliers sell a catalogue. The ones that win OEM programmes — the ones whose modules are inside a drone, a truck or a harvester that ships in volume — sell a process. This article describes how we work, because the process is the part a customer actually buys.

Stage 1: Requirement clarification

We do not quote from a datasheet on the first contact, and we ask for more than most buyers expect. Typically we need:

  • Detection requirement in the worst case — maximum range at a stated target RCS, in the worst weather or dust condition.
  • Target mix — how many targets, what types, whether they are moving, and whether they must be classified.
  • Installation envelope — mounting position, available volume, orientation, and what the radar may or may not be blocked by.
  • Electrical and interface — supply voltage, current budget, connector standard, protocol, message rate.
  • Environmental and compliance — IP rating, temperature range, the target markets and their approval requirements.
  • Volume and timeline — sample quantity, first production order, and the date the programme ships.
Ask us the hard questions early. If a requirement cannot be met with the technology as it exists, we say so at this stage — not after you have designed the housing around our answer.

Stage 2: Feasibility and architecture

Our engineers review the requirement against what our RF, algorithm and mechanical teams can actually do, and respond with one of three outcomes: a standard model already meets it; a configurable variant of a standard platform meets it; or a genuine development programme is required.

We also flag things the customer has not considered — a target that will be masked by the mounting structure, a refresh rate the host bus cannot carry, an ambient temperature that derates the transmit power, or a region whose radio rules your band must satisfy. These are cheap to fix in week one and expensive to fix in month six.

Stage 3: Samples

Sample units are built on the same production line that will build the volume order, with the same firmware branch and the same test fixtures. You receive units that behave like the eventual product, not like a laboratory demonstrator. Typical sample lead time is 5–7 business days by DHL or FedEx.

We ship a protocol specification and a reference parser alongside the units, so bench validation can start the day they arrive rather than after a clarification email chain.

Stage 4: DVT and validation

During design validation we test against the full environmental envelope: temperature cycling, vibration and mechanical shock, EMC, IP ingress, and RF performance measured in a chamber with realistic target conditions. If the application is automotive or agricultural, the plan includes the field trials that build the evidence base for functional safety or OEM approval.

Stage 5: Production and sustaining

Production runs on the same line that validated the design, with in-process RF test and a full end-of-line test on every unit. Because SMT, assembly and RF test are all in-house in Shenzhen, Changsha and Guangzhou, we control the process directly — there is no outsourcing gap between the sample and the hundred-thousandth unit. Our engineering team typically replies within 24 hours.

What makes this faster than a trading company

The honest answer is that most of the time is saved in the middle, at Stages 2 and 3. A distributor cannot tell you whether your 80 m detection requirement is physically realistic at 77 GHz in your housing, because they do not have the RF models. We do. That single conversation often removes a month from a programme and occasionally prevents a programme that should never have started.

Start a programme. Send your requirement — even a rough one — and we will come back with a specific model, a feasibility note and budgetary pricing within 24 hours.

Frequently asked questions

What is the minimum order quantity?

Standard MOQ is 50–100 pieces for most radar modules, and lower quantities are available for evaluation and sampling. For a custom development programme, the economics work differently and we scope the tooling and NRE accordingly.

Can you work from our drawings, or must we use yours?

Either. We can supply a module that fits your existing bracket, or we can adapt the mechanical envelope to your requirement. If you have a specific form factor, vibration or ingress requirement, we will tell you honestly whether it is achievable and what it costs.

Do you sign NDAs and support IP transfer?

Yes. We routinely work under NDA, and we can assign design IP to the customer according to the contract. Where a programme is entirely customer-specific, the resulting firmware and hardware design can be treated as customer-owned.

Do you offer OEM branding?

Yes — your label, your protocol, your housing, our board inside. We also provide OEM/ODM support on the existing catalogue products where you need a variant rather than a fully new design.

How do you handle certification for my target market?

We work with CE, RoHS, FCC and CCC requirements and hold ISO 9001, with IATF 16949 in progress. For any new region we will confirm the applicable radio and EMC requirements early, because the band choice and the certification path are linked and one can constrain the other.

No exact spec match?

We can customize to your detection range, form factor and interface protocol.

Start a custom inquiry