
Factory parameter configuration versus custom firmware branches, language and access-logic options, OTA update routes and serial-level version traceability — with the customization boundary and IP terms agreed before production.
Most “firmware customization” requests are not new firmware at all. They are parameter configuration on the existing, field-proven build: default auto-lock delay, voice and display language, prompt volume, wrong-attempt lockout rules, public versus private locker mode, RFID card sector and key selection, Bluetooth device naming and time handling. These are set in production, carry little risk and require no engineering branch. A genuine custom firmware build — new access logic, a changed protocol, a third-party integration or altered power management — is a different engagement: it runs as an engineering project with agreed requirements, a versioned branch, non-recurring engineering terms, its own test cycle and explicit agreement on who owns the result. Between them sits the update path: connected SKUs can receive over-the-air updates through the app or gateway, while offline SKUs are updated at a service point or during production only. Every unit leaves the line with a firmware version recorded against its serial number, so field behavior is traceable years later.
| Two customization levels | Production parameter configuration on the standard build, or a separately scoped custom firmware branch for genuinely new behavior |
| Typical parameters | Auto-lock delay, language and voice pack, volume, lockout rules, locker mode, RFID sector and key, BLE name and time settings |
| Custom builds | New access logic, protocol or integration work: requirements document, NRE terms, version branch, test plan and IP agreement before kickoff |
| Update paths | OTA through app or gateway on connected SKUs; offline SKUs updated at service points or factory only, per the platform's documented mechanism |
| Version traceability | Firmware version recorded against serial and batch at end of line; changelogs supplied so field units can be identified precisely |
| Quality gates | End-of-line flashing and functional checks, plus regression testing on custom branches covering credentials, power and lockout behavior |
| IP and ownership | Platform firmware remains with its developer; ownership and licensing of brand-funded custom work follow a written agreement signed before development |
The distinction controls risk, lead time and cost. Choosing configuration when a branch is actually needed stores up a failed project; asking for a branch when settings suffice wastes months.
| Dimension | Parameter configuration | Custom firmware build |
|---|---|---|
| What changes | Values inside existing firmware: timing, language, modes, card keys | New logic, protocol behavior or integration code |
| Engineering risk | Low; same validated binary, different settings | Material; new code requires regression and field validation |
| Lead time | Set during production planning | Requirements, build and test cycle scheduled as a project |
| Cost model | Usually absorbed into the OEM program | NRE and licensing terms agreed in writing up front |
| Examples | 30-second auto-lock, Spanish voice, private locker default | Proprietary card format, named third-party protocol, new lockout policy |
| IP outcome | No IP question; platform stays standard | Ownership of funded work defined by signed agreement |
Yes — voice and display language, auto-lock delay, prompt volume, wrong-attempt lockout, locker mode, RFID sector keys and Bluetooth naming are standard production parameters on covered platforms. They are recorded on the production configuration sheet and applied to the validated firmware build, so there is no need for a custom engineering project for this level of branding.
When the requirement changes behavior rather than a setting: a new access rule, a proprietary card format, a named third-party protocol or integration, or altered power management. Custom work starts with a requirements document and acceptance behavior, carries non-recurring engineering terms and a separate test cycle, and IP ownership is agreed in writing before development — it is never quoted as a free variation on a standard order.
On connected SKUs, over-the-air updates run through the app or Wi-Fi gateway, following that platform's documented update and rollback mechanism. Offline SKUs without a radio path can only be updated at a service point with the appropriate tool, or replaced. Which path applies is a platform fact checked at model selection — see the app program page for the connected side.
The approved version is flashed at end of line and recorded against the unit serial and batch, with a changelog supplied per release. If a field issue is reported, the serial number identifies the exact build and the configuration applied, which is how regressions are isolated instead of guessing across a container of apparently identical locks.
The underlying platform firmware remains with its developer; ownership, exclusivity and licensing rights for brand-funded work are set case by case in a written agreement signed before development starts. Typical arrangements range from a brand-exclusive feature on shared hardware to a licensed module, and the agreed terms then drive how the build is maintained and updated over the product lifecycle.
Send the required settings or behavioral spec, target SKUs and quantities — receive a configuration sheet or a scoped engineering proposal with written terms.
Discuss firmware scopeODM engineeringLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team