Care Platform Procurement: Clauses to Demand Before Deployment

1. Acceptance Test Protocol — Revision-Locked and Witnessed
An acceptance test is not a checklist — it is a witnessed, revision-specific validation against the exact hardware build being deployed. It must cover RF emissions (EN 300 328, EN 301 489), electrical safety (EN 62368-1), and, where applicable, EN 1811 nickel release for skin-contact items such as smart rings. For service robots, the test scope must include EMC and low-voltage compliance, plus a class 1 laser statement for LiDAR. This is not optional: without a signed protocol referencing the hardware revision number, no unit may enter a care environment. The factory testing process includes IQC, IPQC, FQC and OQC gates at AQL 2.5 major and 4.0 minor — but those are internal. Your acceptance test is external, final and binding.2. Firmware Rights — Not Just “White-Label”
“White-label” is ambiguous. What matters is who holds the right to modify, sign and deploy firmware updates — and whether those rights survive termination of the agreement. For care platforms, firmware control must extend to security patches, localisation updates and configuration locks. The minimum MOQ for firmware white-label is 2,000 units, and the agreement must state that source-level access (not just binaries) is granted under a perpetual, royalty-free license — limited to the hardware revision shipped. Without this, you risk vendor lock-in the moment your first update fails. Review how WingPhoenix structures these rights in its OEM/ODM services policy — and compare it to your current supplier’s wording.3. Export Classification — Before Shipment, Not After
Export compliance is not a customs form — it is a product-level determination made before production begins. Every device must carry an explicit ECCN or dual-use classification tied to its hardware revision. For AI wearables, this includes battery-powered models such as the AI wearables line, where UN38.3 test summaries and SDS documents are mandatory per order. For AI robots — including the AI Robots line and the AI Learning & Robotics line — classification must account for embedded sensors, connectivity and processing capability. No shipment proceeds without written confirmation of classification from the supplier.4. Support Window — Fixed Term, No Auto-Renewal
A support window is not “best effort” — it is a defined period during which firmware updates, security patches and technical escalation paths are guaranteed. WingPhoenix offers a fixed 12-month warranty with 2 % free replacement parts shipped with the order, but support beyond warranty must be negotiated as a discrete, non-auto-renewing term. This applies equally to the H3 Health Smartwatch and the E1 AI Learning Robot. Any clause allowing automatic renewal or price adjustment without 90 days’ written notice is non-compliant with standard procurement practice for regulated environments.5. SLA — Measured Against Delivery, Not Promise
An SLA must define measurable failure modes — not vague commitments. For care platforms, response time starts at confirmed fault reporting, not ticket creation. Resolution time begins only after diagnostic logs and firmware version are validated. Escalation paths must name named contacts, not departments. Critically, the SLA must exclude liability for failures arising from unauthorised firmware modification, third-party integrations or unsupported network configurations — all of which are common in fragmented care IT stacks.6. What This Process Cannot Guarantee
No WingPhoenix device is certified for medical use, nor does it meet IEC 62304 or ISO 13485 requirements. There is no clinical validation report, no CE Class IIa designation, and no notified body opinion covering diagnostic or therapeutic claims. Health metrics delivered by the H3 Health Smartwatch are wellness guidance only. Companion robots — including the K1 AI Companion Robot — are not monitoring devices and do not trigger alerts, log incidents or interface with emergency response systems. Any supplier claiming otherwise has misrepresented the product scope.| Clause | Must Reference | Enforceable Trigger | WingPhoenix Minimum MOQ | Documentation Supplied |
|---|---|---|---|---|
| Acceptance Test | Hardware revision number | Witnessed test report signed pre-deployment | 50 units (service robots) | CE RED, FCC Part 15, UKCA on request |
| Firmware Rights | Binary + source-level access | License grant effective on first shipment | 2,000 units | Firmware signing key handover record |
| Export Classification | ECCN or dual-use statement | Written confirmation before production start | Varies by model | UN38.3 summary, SDS, RoHS 3, REACH SVHC |
| Support Window | Fixed calendar term | Start date tied to delivery note | None (negotiated per project) | Warranty certificate, spare parts list |
| SLA Response | Confirmed fault, not ticket open | Escalation path with named contacts | None | SLA annex, contact directory |
| Toy Safety | Age grading on packaging | Lab test booking per build | 1,000 units (companion models) | EN 71-1/-2/-3, EN 62115, Toy Safety Directive |
| Battery Compliance | Watt-hour rating printed on unit | UN38.3 test summary shipped with order | Varies by model | UN38.3 summary, SDS, EN 62368-1 |
- Verify firmware ownership language against WingPhoenix’s OEM/ODM services policy
- Require CE RED test reports referencing the exact hardware revision — not model name alone
- Confirm nickel release testing applies to all skin-contact surfaces, per EN 1811
- Check that EMC and laser statements for service robots are issued per build, not per model family
- Reject any SLA that defines response time from ticket creation rather than fault confirmation
- Ensure toy safety lab booking is tied to the age grade printed on final packaging
- Review import duty responsibilities — WEEE, BattG, DEEE/Triman and EORI/VAT sit with the importer, per how we build and test
Questions buyers ask
What must be contractually secured before any AI device enters a care room?
A signed acceptance test protocol, verified firmware ownership clause, and documented export classification — all tied to hardware revision, not model name.
How do finance and compliance teams verify long-term cost control?
They require a fixed support window with no auto-renewal, a warranty covering replacement parts at point of delivery, and clear assignment of EU/UK importer duties.
What happens when a sample fails EMC or nickel release testing?
The supplier must rework or replace the batch at their cost — no chargebacks — and supply updated documentation per the same hardware revision.
What claim do most suppliers avoid naming explicitly?
That no WingPhoenix device carries medical-grade monitoring capability; health metrics are wellness guidance only, and companion robots like the <a href="https://wingphoenixai.com/products/ai-devices/k1-ai-companion-robot/">K1 AI Companion Robot</a> do not detect falls, call emergency services or interpret clinical data.
Related: more on ai memory platform · buyer guides · customisation tiers