For a door or window maker, a smart lock is no longer a curiosity but a range item that customers and architects increasingly ask about. The problem is that building your own access electronics — with biometrics, encryption and connectivity — is a costly, multi-year R&D project. The OEM model solves this differently: you integrate a ready access-control module in your leaf and sell it under your own brand. This post explains how it works, when it pays off and which standards to keep in mind.

In short:

  • An OEM module is ready access electronics for integration in your leaf.
  • You gain a new feature in your range without your own R&D department.
  • Relevant standards: EN 14846 (locks), RED (radio), GDPR (biometrics).
  • White label lets you sell the module under your brand.
  • Integration relies on a documented API/SDK and technical support.

Why a door maker should offer a smart lock

The joinery market is shifting under two forces: rising demand for the smart home, and subsidy programmes that drive door and window replacement. A customer who is buying new doors anyway is in the perfect moment to pay a little extra for convenience and security — and the maker who has such a product in the range wins the order. A missing smart variant, by contrast, means handing margin to lock suppliers who fit them after the fact.

For a joinery firm a smart lock is also a way to a higher basket value and to standing out in tenders — especially in the premium segment, in developer projects and in hospitality, where keyless access is becoming the standard.

OEM module vs your own R&D — return on investment

Building your own access electronics requires a team, certification, a component supply chain and years of software maintenance. That is only sensible at very large scale. For most door makers a ready OEM module is far more favourable: you cut time-to-market from years to months, shift the technology risk to the module supplier, and pay for a finished, tested component.

The ROI comes down to a simple comparison: the cost of integrating a ready module and the margin on selling the smart variant, versus the cost and risk of your own R&D. In practice the OEM module wins wherever the product must reach the market quickly and without building electronics competence from scratch. This is the core of the Perrugi Brain and Perrugi Palm proposition: one module combining biometrics, PIN, NFC and connectivity, ready to go into the leaf.

Standards and compliance: EN 14846, RED, GDPR, cybersecurity

Placing an electromechanical lock on the European market means ensuring compliance with the relevant standards and directives. Depending on use, these include:

  • EN 14846 — the standard for electromechanically operated locks and striking plates, describing classification and requirements.
  • The RED directive (Radio Equipment Directive) — for devices using radio connectivity, e.g. NFC or wireless communication.
  • GDPR — for biometric data, treated as a special category of personal data; local processing and encryption are key.
  • Resistance classes (RC) — relevant for doors with raised burglary resistance.

A good OEM partner supplies documentation that helps you demonstrate compliance — declarations, certificates and technical data. That shortens the process and reduces the regulatory risk on your side.

Add a smart lock to your range — without your own R&D. One module: biometrics, PIN, NFC and connectivity, ready for the leaf and for your brand.

In-leaf integration — requirements

Integration is not only mechanics. You must plan space for the module and sensor, route the wiring, provide power and sealing, and ensure cooperation with the multipoint strip. On the electronics side, secure communication matters — in the Perrugi family this is handled by an encrypted AES-256 bus with the key in the Secure Element, extended with CAN and industrial Ethernet for larger installs.

A well-documented module states the mounting requirements clearly: dimensions, tolerances, interfaces and recommendations for the door profile. As a result your production department deploys it repeatably, rather than by trial and error.

Who it is for: developers, hotels and offices

The OEM model pays off fastest where scale and repeatability are greatest. Residential developers gain a selling point in the premium segment and the ability to manage access remotely during construction and handover. Hotels — boutique and premium especially — use keyless access as part of the guest experience, with one-time codes instead of cards. Offices and commercial buildings need entry logs and integration with building-management systems.

In each of these segments, a door maker that supplies a ready smart variant enters a conversation about larger, repeatable orders — not a single unit.

White label, API/SDK and support — plus how the cooperation runs

The OEM model means the product reaches the market under your brand. The interface and finish are customised, and integration with systems — yours or the customer's — happens via a documented API and SDK. Equally important is support: a dedicated contact, samples, documentation and help during integration. Deployment usually runs in stages: from enquiry and samples, through defining in-leaf integration requirements and brand customisation, to testing and series production. It is worth starting with a specific door profile and volume — that quickly shows whether and how the module fits your product. When choosing an OEM partner, assess not just the module but the stability of the supply chain and the readiness of the documentation.

Frequently asked questions (FAQ)

What is an OEM smart lock?

A ready access-control module you integrate in your leaf and sell under your own brand — without building your own R&D.

Which standards apply to a lock module in doors?

Depending on use, EN 14846, the RED directive and GDPR for biometric data. Documentation confirms compliance.

Can the module be sold as white label?

Yes. OEM assumes customisation to the partner brand and integration via API/SDK with technical support.

Do you make doors or windows, or manage properties? See Perrugi Brain, explore the whole family and ask for documentation, API and samples.