| Bluetooth Technology | State whether the product requires Bluetooth Classic, Bluetooth Low Energy, or dual-mode operation. | Bluetooth Classic Bluetooth LE Dual Mode Bluetooth LE is designed for low-power wireless communication. Bluetooth Classic is commonly used for continuous higher-throughput connections such as streaming. | Confirm previous experience with the selected wireless architecture, module integration, antenna layout, and firmware loading process. | Filters out suppliers that only support general PCB assembly without wireless product experience. |
| Bluetooth Core Version | Specify the required Bluetooth Core Specification version and identify whether the design must support features introduced in a particular version. | Bluetooth Core Specification versions 5.0, 5.1, 5.2, 5.3, and 5.4 are available for product planning. Bluetooth 5.0 introduced features including LE 2M PHY and LE Coded PHY. Bluetooth 5.4 added features including Periodic Advertising with Responses. | Request the wireless module or chipset specification, qualification status, supported feature list, and firmware compatibility information. | Helps match the supplier's component sourcing and programming capability to the required feature set. |
| Wireless Data Profile | Define the Bluetooth services, characteristics, data direction, packet size, update frequency, and connection behavior. | Bluetooth LE applications commonly use GAP for device discovery and connection procedures and GATT for services and characteristics. Standard profiles may be used where applicable; otherwise, a custom GATT service may be required. | Ask for a documented firmware flashing process, test firmware, GATT configuration procedure, and production communication test method. | Reveals whether the supplier can perform functional testing rather than only visual inspection. |
| Data Rate and Latency | Provide the minimum application throughput, maximum acceptable latency, connection interval, and expected number of simultaneous connections. | Bluetooth LE supports LE 1M PHY and, where supported by the device, LE 2M PHY. LE Coded PHY can improve receiver sensitivity and range at the cost of lower effective data rate. | Request radio test results using the intended antenna, firmware, enclosure, and operating environment. | Prevents suppliers from quoting a design that meets nominal Bluetooth connectivity but fails application-level performance. |
| Operating Range | Define the required indoor and outdoor communication distance, line-of-sight conditions, obstructions, and expected radio environment. | Actual range depends on transmit power, receiver sensitivity, PHY selection, antenna efficiency, enclosure materials, interference, and regional radio limits. A Bluetooth specification version alone does not guarantee a fixed range. | Request an antenna matching report, conducted and radiated test results, and sample-based range test data. | Identifies suppliers capable of RF validation and enclosure-aware testing. |
| Power Consumption | Set maximum current targets for advertising, scanning, connected operation, sleep mode, charging, and peak transmit conditions. | Battery life is affected by connection interval, advertising interval, transmit power, radio duty cycle, sensor activity, processor load, and power-management design. | Request a current-consumption test plan, calibrated measurement equipment details, test firmware, and results at defined voltage and temperature conditions. | Distinguishes suppliers with power-validation capability from those relying only on component datasheet values. |
| Antenna and RF Layout | Specify the antenna type, allowed clearance area, RF matching network, enclosure constraints, and whether the antenna is on-board, ceramic, chip-based, or external. | Antenna performance can change because of the PCB stack-up, ground-plane geometry, battery placement, shielding, cables, plastics, and nearby metal parts. | Request PCB stack-up data, RF layout rules, antenna tuning records, impedance-control information, and final-assembly RF test results. | Helps verify that the supplier can preserve RF performance during PCB and box-build assembly. |
| PCB Assembly Scope | Define board dimensions, layer count, component package types, expected annual volume, prototype quantity, and finished-product assembly requirements. | Requirements may include SMT placement, through-hole soldering, selective soldering, conformal coating, shielding installation, cable assembly, enclosure assembly, and labeling. | Request equipment capability, minimum component package capability, inspection coverage, process certifications, and sample manufacturing records. | Ensures the supplier can support the complete manufacturing scope instead of only placing components. |
| Programming and Firmware | Define bootloader requirements, firmware image format, programming interface, device identity data, Bluetooth address handling, and firmware version control. | Production programming may use SWD, UART, USB, or another defined interface, depending on the selected chipset or module. Device-specific data should be controlled through a traceable production process. | Request programming fixtures, firmware revision records, checksum or hash verification, programming yield data, and rework procedures. | Reduces the risk of inconsistent firmware, duplicate device identities, or untraceable production units. |
| Bluetooth Qualification | Determine whether the product will use a qualified Bluetooth component, require a new product declaration, or need additional qualification work. | Bluetooth products are subject to the Bluetooth SIG qualification process. Qualification obligations depend on the product architecture, use of qualified components, implementation, and product listing approach. | Request the applicable qualification documents, component declarations, responsibility allocation, and support for required qualification records. | Helps identify suppliers that understand Bluetooth compliance responsibilities rather than treating the radio as an ordinary unregulated component. |
| Regulatory Testing | List the target sales regions and required radio, electromagnetic compatibility, electrical safety, and environmental tests. | Requirements vary by destination market. Common test areas include intentional radiator or radio tests, electromagnetic compatibility, immunity, safety, restricted substances, and battery-related requirements where applicable. | Request a proposed compliance matrix, test laboratory coordination plan, pre-scan capability, and control of test samples and engineering changes. | Supports comparison of suppliers based on compliance readiness and documentation quality. |
| Quality Inspection | Define acceptable quality limits, inspection stages, critical-to-quality characteristics, and defect classification for RF and electronic assemblies. | Typical controls include incoming inspection, solder-paste inspection, automated optical inspection, X-ray inspection where appropriate, in-circuit or flying-probe testing, functional testing, and final visual inspection. | Request sample inspection plans, control plans, defect photographs, first-article reports, traceability records, and corrective-action procedures. | Makes supplier quality systems directly comparable before production begins. |
| Environmental Conditions | Specify operating temperature, storage temperature, humidity, vibration, shock, ingress protection, and expected product lifetime. | Environmental limits must be defined for the complete product because the wireless module, battery, antenna, solder joints, enclosure, and display or sensor components may have different limits. | Request environmental test plans, chamber capability, material specifications, accelerated-life data, and records for any conformal coating or sealing process. | Helps determine whether the supplier can build products for the intended operating environment. |
| Traceability and Documentation | Define lot traceability, serial-number rules, component records, firmware history, inspection records, and engineering-change approval. | Wireless products may require traceability for radio modules, antennas, firmware versions, calibration results, battery lots, and final functional-test outcomes. | Request example traveler documents, barcode or serial-number workflows, certificate-of-conformance format, and engineering-change notification procedures. | Indicates whether the supplier can support audits, recalls, field analysis, and controlled product updates. |
| Cost and Commercial Terms | Separate non-recurring engineering costs, tooling, test fixtures, certification support, prototype pricing, production pricing, minimum order quantity, and payment terms. | Bluetooth assembly cost is influenced by the radio component, antenna solution, PCB complexity, test coverage, programming time, enclosure integration, compliance work, and forecast volume. | Request an itemized quotation, assumptions list, lead-time schedule, material-validity period, change-control fees, and warranty terms. | Enables an apples-to-apples comparison and reduces hidden costs during design transfer and ramp-up. |