OEM & Customization: How We Configure UAV Systems for Integrators
Integrators — the firms that build the mission around the machine — buy differently from end users. An end user buys a product page; an integrator buys a specification line that has to survive being embedded in someone else's aircraft, vehicle or control room. This article is the honest description of what we configure, what we do not, and the commercial rules around it, aligned word-for-word with our published FAQ and after-sales policy.
What "OEM configuration" means here
We are a manufacturer and supplier of unmanned systems and components, founded 2018, producing across VTOL fixed-wing aircraft, ground vehicles, and a components catalogue spanning ground stations, links, pods, motors and batteries. Configuration happens inside that production reality:
- Matched component sets. The FAQ wording is exact: motor, ESC and propeller combinations matched to a platform's thrust and voltage needs. Our drone motors and battery lines carry published KV, wattage and C-rating specifications, so a thrust build is an arithmetic exercise we can verify — not a guess from a stock list.
- Link band and interface options. The AEROLINK series specifies 1.4 GHz operation with support for custom frequency bands, and the larger nodes expose configurable serial interfaces (RS232 switchable to RS422/485). For an integrator embedding a link into a vehicle with existing 422 looms, that switchability is the difference between a plug and a protocol converter.
- Payload-mount and airframe configuration. Complete aircraft are quoted per SET: the MT100 heavy-lift quad ships with flight controller, power system, remote controller, camera and RTK as a configured build; the AT-G45 carries a large payload cabin whose fit depends on the mission sensors. Mount interfaces, payload station counts and radio fitments are the configuration conversation.
- Bundles. The catalogue already ships logical bundles — MK15 Enterprise and HDMI combos, HM30 Standard and Fly More, dual-operator ground combos — and custom bundles around an operational requirement (aircraft + pod + link + spare air unit, one order) are the normal way integrators consolidate.
- Branding. White-label and co-branding on supplied hardware is handled per programme; the written quotation names exactly what is branded and what is not.
What we do not do
Boundaries stated early save both sides months:
- No clean-sheet design. We configure and build what our production lines make. A mission requiring a fundamentally new airframe gets a configuration study against the closest catalogue members — and an honest "no" if the gap is real.
- No counter-drone mitigation. Jamming, spoofing and interceptor hardware are out of scope for legal and export-control reasons. Passive detection and tracking is where our line ends, deliberately.
- No invented certifications. Where a model carries CE/FCC marking it is stated on the product page; we do not add certificates a unit does not hold, and integrators should audit any supplier who does.
The commercial rules that change with configuration
Three clauses from our published policy that integrators are surprised by — so they are stated here in the same words as the FAQ:
| Situation | Rule |
|---|---|
| Quotation validity | 14 days from issue, written, EXW Hong Kong |
| Stock items | Eligible unused items returnable within 30 days with prior written authorisation, subject to inspection |
| Configured / customised / branded items | Not returnable unless confirmed defective or incorrectly supplied |
| Lead time | As stated on the order confirmation for made-to-order; in-stock components generally prepared within 1–3 business days after payment clears |
The asymmetry is deliberate: a configured build cannot be restocked, so the quotation is where the risk gets retired. This is why our quoting process asks for the mission parameters before the price — payload mass and shape, band and licensing context, interface list, destination country — and returns a specification sheet attached to the number.
A worked example: the corridor-inspection kit
An integrator deploying powerline crews typically consolidates into one order:
- Platform: AT-G07 configured with the chosen pod mount — 7 kg payload covers the sensor class.
- Sensing: ZR30 optical pod (30x optical, 4K, Ethernet + HDMI out) — see the selection matrix.
- Link: AEROLINK member sized to corridor length with the band option the country's regulator permits — the link comparison article is the sizing primer.
- Ground: UniRC 10 Pro with hot-swap endurance for full-shift sorties.
- Spares: one air unit per link family, one battery set per sortie cycle — the compatibility checklist is the review document.
Five catalogue lines, one configured quotation, one order confirmation with one lead time. That is what OEM configuration means at this scale: not bespoke engineering, but verified integration across a production catalogue — with the interface, mass and power facts on the table before anything is built.
Starting the conversation
Send the mission spec — payload, radius, environment, destination country, quantities — through the contact page or WhatsApp. You will get a written configuration proposal with the exact model variants, the band/interface choices, the lead time and a price valid 14 days. Integrators who have done this once send a bill of materials the second time; that is the sign the process is working as intended.
Frequently asked questions
Do you build custom aircraft from scratch?
No. We manufacture and supply a defined catalogue — VTOL fixed-wings, multi-rotors, ground vehicles, links, pods, ground stations and components — and configure within it. Customisation means matched component sets, link band and interface options, payload mounts, bundling and branding, not clean-sheet design. If a mission needs an aircraft that does not exist, the honest answer is a configuration study, not a promise.
Are configured or branded items returnable?
Customised, configured or branded items are not returnable unless confirmed defective or incorrectly supplied — this is stated in our FAQ and after-sales policy. Stock items follow the standard 30-day return window with prior written authorisation. Budget for the difference: get the configuration right before the order, which is what the written quotation and 14-day validity are for.
What lead time should an integrator plan around?
Made-to-order and configured items follow the lead time stated on your order confirmation; in-stock components are generally prepared within 1–3 business days after payment clears. The order confirmation is the contract document — we do not quote one lead time and confirm another.
Working on a requirement like this one? Send us the mission — payload, endurance and the terrain — and we will say which platform fits and which does not.
Ask on WhatsApp