WiFi 6 Access Point (802.11ax OEM / Private Label)

Chipset Selection — Qualcomm vs MediaTek vs Realtek

Three SoC families dominate Chinese WiFi 6 AP manufacturing. Each involves real trade-offs in throughput ceiling, driver ecosystem, and total OEM cost.

Qualcomm IPQ6010 / IPQ6018. These are the reference chipsets for enterprise-grade WiFi 6 hardware. IPQ6018 is a quad-core ARM A53 at 1.0 GHz with integrated NSS (Network Sub System) offload — meaning packet forwarding at line rate without burdening the application CPU. OpenWRT support is mature; Qualcomm’s QSDK (based on OpenWRT 19.07/21.02) has been shipping in production since 2019 and the community backport to mainline OpenWRT is reasonably stable as of 2024. Driver quality is the best of the three families: MU-MIMO scheduler, OFDMA resource unit allocation, and TWT power management all behave close to spec. Trade-off: chipset cost is the highest of the three, pushing ex-factory unit pricing above $55–70 for a finished dual-band AP. Qualcomm also has tighter NDA requirements on full datasheet access, which some OEM factories pass to customers and some do not.

MediaTek MT7915 / MT7916 / MT7981. MediaTek closed the gap significantly between 2022 and 2025. MT7915 (WiFi 6) and MT7916 (WiFi 6 with 6GHz ready architecture) now have strong upstream OpenWRT support — MT7915 was merged into mainline OpenWRT 21.02, and the MT7981 (Filogic 820) platform used in newer designs is well-documented with public SDK. Throughput performance is within 10–15% of equivalent Qualcomm designs in real-world dense deployments. The main gap is OFDMA UL performance under heavy concurrent load — MediaTek’s UL OFDMA scheduling is noticeably less efficient than Qualcomm’s NSS offload at 200+ concurrent clients. For deployments under 100 clients, this difference is largely irrelevant. Ex-factory pricing for MT7915-based dual-band APs typically lands $8–15 cheaper per unit than comparable Qualcomm designs at 500-unit volumes.

Realtek RTL8852BE / RTL8832BR. Realtek dominates the cost-sensitive consumer router segment but is a distant third for OEM AP customization. Their SDK is proprietary and not OpenWRT-based, meaning firmware customization is limited to what the factory has already implemented in their reference design. Getting source code access for the management plane is rare; most factories supply a binary image only. OFDMA and MU-MIMO implementations are functional but less configurable. If your use case requires custom captive portal logic, VLAN tagging behavior, or TR-069 parameter trees beyond the factory default, Realtek-based designs will create friction. For straightforward private-label deployments where you accept the reference firmware as-is, Realtek-based APs offer the lowest entry price — ex-factory around $28–38 for a basic dual-band model.

Practical recommendation: request a development unit before committing MOQ regardless of chipset. Flash the firmware, connect 30–50 clients, and run iperf3 bidirectional tests before approving tooling or certifications. A supplier sourcing engagement should shortlist factories with hardware already certified rather than relying on chipset datasheets alone.

WiFi CERTIFIED 6 Certification vs Chipset Datasheet Claims

“WiFi 6” on a product listing means the device uses an 802.11ax chipset. It does not mean the device holds WiFi Alliance WiFi CERTIFIED 6 certification. These are different things with meaningfully different implications for your sales channel.

What chipset marketing covers. Any AP built on an 802.11ax SoC can legally advertise WiFi 6 speeds because the underlying radio supports the standard. The factory datasheet will show maximum theoretical throughputs (574 Mbps on 2.4GHz, 2402 Mbps on 5GHz) derived from the chipset specification, not from tested interoperability.

What WiFi CERTIFIED 6 actually tests. The WiFi Alliance certification program (Program ID: WFA WiFi 6) runs a mandatory test suite covering: OFDMA downlink and uplink functional verification, BSS coloring activation and performance isolation, Target Wake Time negotiation between AP and client, WPA3-Personal and WPA3-Enterprise support, and backward compatibility with WiFi 4/5 clients under mixed-client load. Passing devices receive authorization to display the WiFi CERTIFIED 6 logo and are listed in the WiFi Alliance product finder database.

Cost and timeline. Certification testing is conducted at an authorized test laboratory (ATL). Lab fees run approximately $5,000–15,000 depending on which ATL you use and which optional test modules (WPA3-Enterprise, Enhanced Open) you include. Add factory engineering time for the test preparation phase — plan for 4–8 weeks end-to-end if the factory has not previously certified this exact hardware and firmware combination. Some Chinese AP factories have pre-certified reference designs where your private label requires only a brand change review, which can reduce cost to $2,000–4,000 and timeline to 2–3 weeks.

When you need it. Enterprise procurement teams at education, hospitality, and corporate verticals often require the WiFi CERTIFIED 6 logo as a vendor qualification criterion — especially in North America and Western Europe. Major retail distribution (Best Buy, Amazon Basics, carrier bundles) will typically require it. If you are selling to IT integrators for industrial IoT deployments in private networks, or deploying APs in smart home or MDU installations under your own control, you can often defer certification and use the FCC/CE-certified hardware without the WiFi Alliance mark.

FCC certification is non-negotiable for US market regardless. FCC Part 15E authorization covers the radio transmitter. This is a separate process from WiFi Alliance certification and is mandatory for any AP sold or imported into the United States. Confirm the factory holds an existing FCC grant for the specific PCB and antenna configuration you are ordering — antenna changes, even swapping between internal and external, typically require a new FCC filing or a Class II permissive change.

Cloud Management Platform and White-Label Options

Most Chinese WiFi 6 AP manufacturers targeting the reseller and integrator market now bundle a cloud management platform alongside the hardware. For many OEM buyers, the management software is as commercially important as the access point itself.

SaaS API access vs source code. This is the first and most critical question. Some factories provide only API-level integration with their existing cloud — you white-label the frontend but the backend infrastructure, database, and compute remain theirs. Others will supply the full management platform source code (typically a Go or Python backend with a React frontend, hosted on your own cloud). Source code ownership matters if you need to negotiate enterprise contracts where your customers require on-premise management, or if you need to guarantee service continuity independent of the factory’s business. Expect source code licensing to add $5,000–20,000 to the project, and require a software escrow arrangement in the contract.

Per-device SaaS fees. When you do not own the backend infrastructure, the factory typically charges a per-device-per-year cloud management fee — commonly $1–3 per AP per year at volume. At 1,000 deployed units this is manageable; at 50,000 units this becomes a significant recurring cost line that must be factored into your pricing model. Negotiate a lifetime fee cap or a maximum per-unit annual rate in the OEM agreement before MOQ commitment.

TR-069 / CWMP support. For ISP and carrier deployments, TR-069 (CWMP — CPE WAN Management Protocol) is the standard remote management protocol. Confirm the factory’s firmware implements TR-069 with a configurable ACS (Auto Configuration Server) URL. Also verify which TR-069 data model is supported: TR-181 (Device:2) is current; TR-098 (InternetGatewayDevice:1) is legacy but still required by some carrier networks. If your target customer operates their own ACS (GenieACS, FreeACS, or a commercial solution), request a test unit and validate provisioning and firmware update flows before finalizing the order.

Zero-touch provisioning. Enterprise-grade management platforms support ZTP — devices boot, connect to the internet, and automatically register to the correct tenant without manual configuration. This is table stakes for managed service providers deploying APs at scale across multiple customer sites. Ask the factory to demo ZTP with a realistic multi-tenant scenario, not just a single-tenant demo environment.

Rebrandable app and web portal. If your channel includes end-users managing their own networks (hospitality, retail, SMB), evaluate whether the management portal supports custom domain, logo, color scheme, and whether mobile apps (iOS/Android) can be published under your own developer account or require the factory’s app. Publishing under your own App Store account requires separate review cycles and ongoing maintenance responsibility.

For complex white-label platform evaluations, a factory audit that includes a software review session with the factory’s engineering team will surface these constraints early — before you are locked in by MOQ deposit.