Blog
Smart Watch Sensors for B2B Buyers: PPG, ECG and SpO2
Smart Watch Sourcing Guide
PPG, ECG and SpO2 Sensors: What B2B Buyers Should Verify
A procurement-focused guide to sensor configuration, firmware, app support, claim boundaries and evidence — without treating a sensor name as proof of medical accuracy.
Start with the claim category, not the sensor label
PPG, ECG and SpO2 are technologies used in different ways across the smart-watch market. Two products may list the same sensor abbreviation while providing very different functions, algorithms, documentation and user experience. Buyers should first decide what the product is allowed to claim in the destination market and sales channel.
A wellness feature that estimates a trend is not the same as a medical device that measures, diagnoses or monitors a condition. The product page, retail packaging, manual, app text and advertising all need to use consistent wording. A supplier that promises “medical-grade accuracy” without a clear model-specific evidence package creates regulatory and after-sales risk for the buyer.
What each sensor type can mean in a product brief
| Sensor or function | Typical wellness use | Questions for the supplier | Evidence to request |
|---|---|---|---|
| PPG | Optical pulse or trend-based wellness features | Which LEDs and photodiodes are used? What algorithm and firmware version are involved? How is motion handled? | Exact sensor configuration, sample test method, app screenshots and claim wording |
| ECG | A feature described as ECG in a watch or app | Is this a single-lead recording function, a wellness signal, or a regulated medical feature? Who is the intended user? | Model-level technical description, electrode configuration, algorithm source, applicable test evidence and intended-market review |
| SpO2 | Blood-oxygen-related wellness indication | Is the value continuous, on-demand or trend-based? What conditions affect the reading? What wording is approved for the packaging? | Sensor specification, algorithm controls, sample comparison data and clear limitations in the app and manual |
| Sleep and activity | Lifestyle tracking and habit insights | Which data comes from the watch, which is estimated by the app, and how are missing readings handled? | App version, data-flow description, screenshots and user instructions |
This table is a sourcing framework, not a medical or regulatory conclusion. Claim requirements vary by market and intended use.
Define the product before comparing quotations
Hardware and sensor configuration
Ask for the exact model, hardware version, display specification, battery target, charging method, water-resistance claim, strap interface and sensor configuration. A generic family name is not enough if the buyer will approve packaging or make performance claims. Require the quotation to identify the version being offered.
Firmware and app dependency
Many watch features depend on the phone app, cloud service and firmware. Confirm which functions work without the app, which require a login, which languages are supported and how updates are handled. Review the app with the exact iPhone and Android versions used in the target market. Ask what happens if the app is unavailable or a service changes.
Claim wording and user instructions
Request a copy of the proposed retail claim, app text and manual. Check that the words match the evidence and the intended use. Avoid unsupported comparisons to clinical equipment, hospitals or laboratory testing. If a feature is described as wellness only, the packaging and app should not imply diagnosis or treatment.
Build an evidence pack before approving samples
A sample can show appearance and basic operation, but it does not automatically prove the accuracy, durability or compliance of the production version. Build a written evidence pack for the model and keep it with the order file.
- Locked specification sheet with model, hardware and firmware versions.
- Sensor configuration and a clear description of each feature’s intended use.
- App name, version, supported operating systems, language list and permissions.
- Sample test record covering pairing, charging, display, buttons, calls, sensors and app data flow.
- Proposed claim wording for the product page, packaging, manual and retail listing.
- Available compliance and test documentation for the exact model and destination market.
- Production inspection checklist, defect definitions and firmware verification method.
QC points for a smart-watch programme
Function and pairing
Test boot, charging, touch, buttons, Bluetooth pairing, notifications, calls where supported, app login and data synchronisation.
Sensor workflow
Verify the sensor menu, measurement conditions, result display, stored history and warning text against the approved sample.
Firmware control
Record the approved firmware version and prevent mixed versions in the same carton or order.
Battery and charging
Check charging behaviour, connector condition, heating under normal use and the battery-life claim method.
Appearance and durability
Inspect display, case, strap, buttons and water-resistance sealing where applicable.
Packaging and manuals
Confirm language, barcode, model number, accessories and claim wording before final packing.
For broader product selection, see our guide to smart-watch features your customers will actually pay for and the smart-watch OEM supplier review checklist.
Market and channel questions
A watch sold through a telecom bundle, a fitness retailer and an online marketplace may need different packaging, support and documentation. Before selecting a model, confirm the channel’s requirement for product language, warranty, returns, app privacy information and claim review.
The U.S. article is a related market-planning example; for a different country or channel, send the destination and requirement with your inquiry.
Frequently asked questions
Does listing PPG, ECG or SpO2 prove medical accuracy?
No. It only identifies a technology or feature. The buyer must verify the intended use, algorithm, firmware, sample behaviour, claim wording and the documentation required for the destination market.
Can Yiting customize the app or watch UI?
Customisation depends on the exact model, software platform, requested changes, quantity and manufacturing partner. App branding, language support and feature changes must be reviewed technically before any promise is made.
What should be included in a sample test record?
Record model, hardware and firmware versions, app version, phone used, pairing result, sensor workflow, charging result, display and button checks, battery behaviour and photos of the approved sample.
Can a supplier change a sensor or firmware after approval?
It should not change without written buyer approval. The purchase order and inspection plan should require notification and re-approval for changes to components, firmware, app version, claims or packaging.
Review the exact watch, not only the category
Send the destination market, sales channel, target features, app requirements, estimated quantity and claim limitations. We will review the appropriate next step and documentation questions.