The Bluetooth Smart Lock OEM Guide explains the OEM pattern where the factory's reference design carries the buyer's brand with minimal change.

Opublikowano: cze 01, 2026

Bluetooth Smart Lock ODM Guide

Bluetooth Smart Lock ODM Guide

A Bluetooth smart lock ODM guide is the program document a brand owner uses to plan the five pillars an ODM project on a Bluetooth-class lock must run — design-for-manufacture, firmware localization, accessory menu, packaging, and after-sales training — and the catalog on smartlockfactory.com currently exposes 79 published models across 10 product categories, with the Bluetooth-class app lanes shipping on TTLock, Tuya, and Doodle, alongside hotel PC software on hotel-class models. ODM is the program where the buyer carries the brand and the product spec, and the factory carries the manufacturing, the firmware engineering, the accessory supply and the documentation. The buyer who treats ODM as "OEM with our logo" almost always pays for it later — in tooling rework, app-store rejection, manual translation gaps, and distributor training calls that should have been answered in writing before shipment.

This guide is the second of three Bluetooth-program siblings. The Bluetooth Smart Lock Manufacturer Guide explains what makes a factory capable of producing a Bluetooth-class lock. The Bluetooth Smart Lock OEM Guide explains the OEM pattern where the factory's reference design carries the buyer's brand with minimal change. This article — the ODM guide — assumes the buyer wants a real program: a firmware branch, an accessory menu, a packaging line, and a training program. The Connected Smart Locks: Complete B2B Guide is the cross-cluster index for every connectivity lane.

Read this once before opening the ODM discussion with smartlockfactory.com. Keep it open as a pillar-by-pillar sign-off sheet every time the program crosses a stage gate. The five pillars are sequenced for a reason: skipping one is how a buyer ends up with a beautiful lock that no installer can commission, no end-user can pair, no distributor can support, and no compliance auditor will accept.

What ODM actually means on a Bluetooth-class lock

ODM stands for Original Design Manufacturer. In the smart-lock industry it is the program shape where the factory owns the reference mechanical design and the reference firmware, and the buyer owns the brand, the market positioning, and the program rules. The buyer's contribution is not a logo. The buyer's contribution is a specification: which platform (TTLock / Tuya / Doodle / hotel PC software), which credential mix (PIN, card, fingerprint, mechanical key, app/Bluetooth), which finish schedule, which packaging, which languages, which training assets, which after-sales flow.

A Bluetooth-class lock is a lock whose primary connectivity to the end-user's phone is Bluetooth. The phone-side app is the credential issuer and the audit-log reader; the lock itself does not, on its own, reach the wider internet. Network reach — when it is required at all — is added by a separate gateway, an in-property controller, or a tenant-side router, none of which is the lock. That single sentence is the boundary of this article. Anything described as Wi-Fi, Matter, Zigbee, Apple Home Key, Thread, Z-Wave, UWB, or any equivalent consumer-radio protocol is not the subject of this article and is not asserted anywhere below. If the program requires any of those, the buyer needs a different reference design and a different conversation.

Three honest disclosures that govern every pillar below:

  • The catalog on smartlockfactory.com contains 79 published models across 10 categories (Smart Door Locks 77, Fingerprint 37, Hotel 24, Keypad 18, Outdoor 10, RFID 9, Face Recognition 6, Cabinet 6, Video Camera 3, Glass 3). Bluetooth-class app connectivity is present on a subset, with platform identity (TTLock / Tuya / Doodle / hotel PC software) varying by model — check the model’s published specification for every shortlisted SKU.
  • The catalog does not contain palm-vein, Matter, Zigbee, Apple Home Key, Thread, Z-Wave, or UWB SKUs. If the ODM brief requires any of those, this catalog cannot answer it and the program has to be redirected before any pillar is signed off.
  • The Bluetooth lock is also not an access-control system, a property management system, a credential-issuance platform, or a guest-facing mobile-key wallet. Each of those is a separate procurement, with its own audit, its own compliance surface, and its own liability chain. The lock supplies events; the surrounding system supplies policy.

Why ODM on Bluetooth is its own program, distinct from OEM

The OEM sibling is the buyer-stamps-our-logo program: take the factory's existing reference design, apply the brand, ship. OEM's pillar count is roughly three (brand application, packaging adaptation, manual localization). ODM adds two more: firmware localization and accessory menu engineering. That is why ODM is five pillars and OEM is fewer.

Bluetooth-class ODM differs from any other ODM category (cabinet, hotel RFID, fingerprint residential) in three specific places. First, the firmware is the product. A fingerprint residential lock with the wrong fingerprint template size is still a lock — it just does not enroll users well. A Bluetooth lock with the wrong firmware branch is a paperweight at the door: the phone cannot pair, the credential cannot be issued, the audit log cannot be read. Second, the accessory menu is unusually wide for a lock. A Bluetooth lock typically ships with strike plates, mounting hardware, a mechanical-override key or two, an IC card or two for the installer, a quick-start card, a positioning template, the battery set (or a battery-cut decision), and — depending on the platform — a gateway or an enrollment encoder. Each of those accessories is a separately-tooled, separately-stocked, separately-priced item, and the ODM buyer decides the menu, not the factory. Third, the after-sales training has a software layer the OEM program does not have. A Bluetooth lock generates support tickets that are credential-management tickets ("how do I revoke a lost phone?"), not mechanical tickets ("why is the bolt stuck?"). The training program has to teach credential hygiene to installers and to end-users, and it has to teach both audiences through assets that the ODM buyer owns.

Pillar 1 — Design-for-manufacture (DFM) on the reference mechanical design

The first pillar is the design choice that happens before the buyer's brand enters the picture. The reference mechanical design — the lock body, the bolt geometry, the cylinder, the reader face, the battery compartment, the cable channels, the gasket seats — is what the factory already knows how to build at scale, on existing tooling, in existing tolerances. The ODM buyer's job is to say which lines on the reference are accepted as-is, which are modified, and which are re-engineered, in that order, with named acceptance criteria for each.

The mistake to avoid is treating the reference design as a starting point for arbitrary customization. It is not. The reference design has been validated by the factory across the doors it fits, the finishes it ships in, the battery format it accommodates, the audit-log depth it stores, and the maintenance cycle it tolerates. Every buyer-driven change to the reference design adds tooling time, adds validation time, and adds the chance that the modified lock fails in a way the reference lock would not have failed. The ODM buyer's discipline is to spend the first pillar on what does not change, then spend the remaining change budget on the lines that genuinely differentiate the brand.

The DFM pillar is run in five pillars, listed in Table 1.

Pillar stepBuyer ownsFactory ownsAcceptance criterion
Reference-design lockupBrand positioning, target price band, target marketMechanical design lockup, valid tool list, current revisionA dated reference-design document with revision number and the lines the factory commits to
Modification listWhich lines change (logo plate, finish, cylinder keyway, accessory menu)Engineering impact, tooling impact, validation impactA modification register with per-line owner, per-line cost-driver, per-line schedule-driver
Door-fit surveyThe doors the lock will ship into (thickness, material, bore pattern)Door-fit envelope the reference design already coversA door-fit envelope matrix matching the buyer's doors to the reference design
Tolerance discussionBrand-level finish tolerance, label acceptance)Factory tolerance the reference design holds todayA written tolerance band per finish, per material, per painted/coated surface
First-article planSample-handling protocol, approval owner, sign-off gateFirst-article production unit, inspection plan, retention sampleA first-article report naming the buyer approver and the factory signatory

Three honest disclosures that govern the DFM pillar:

  • The reference design's door-thickness envelope, finish schedule, battery format, audit-log depth, credential-lane mix, mechanical-override cylinder profile, and reader-face geometry are all per-model. Two numbers on the same factory line, in the same catalog category, are not guaranteed to be the same. Check the model’s published specification for every shortlisted SKU before the DFM pillar is signed off.
  • The factory's reference design includes a current revision number. The ODM buyer's modification register is locked against that revision. If the factory advances the revision mid-program, every signed-off line on the modification register has to be re-checked, and the ODM buyer pays that re-check time whether the change is material or not.
  • The DFM pillar is not a tooling pillar. The factory owns its existing tooling. The ODM buyer does not pay for tooling it does not own, and the factory does not commit to tooling it has not validated on the buyer's doors.

Pillar 1.1 — Door-fit envelope as the program governor

The single most consequential line on the DFM pillar is the door-thickness envelope. A Bluetooth-class lock's reference design covers a band — typically narrower at the low end, wider at the high end — and the ODM buyer's door population sits somewhere inside it. The buyer who treats the door-thickness envelope as a single number, rather than a band, ends up discovering at installation that 12% of the doors in the program do not accept the lock without rework. The door-fit envelope is, in effect, the program governor: every other pillar (cylindrical vs mortise, rim vs surface, fire-rated vs non-rated, indoor vs outdoor) sits downstream of the envelope.

The door-fit envelope is not portable across models. The reference design for the hotel-class hotel lock (for example the SLK-9936S block on the site — 36–100 mm door thickness, 5-pin cylinder, 3-point latch, stainless steel + alloy body) belongs to that hotel model and does not transfer to any other model in the catalog. The ODM buyer who reads one model's envelope and assumes another model shares it is reading the wrong page. The DFM pillar sign-off has to include a dated envelope matrix, model by model.

Pillar 1.2 — Modification register as the change-control ledger

The modification register is the single document that travels with the OBM program across every other pillar. It is also the document the factory's engineering team will return to whenever a question lands during production. Every buyer-driven change — a logo plate dimension, a finish option, a keyway profile, a battery compartment boss, an accessory addition — is one row in the register. Every row carries: the change description, the factory's engineering impact, the tooling impact, the validation impact, the owner, and the sign-off gate. The register is locked against the reference-design revision in step 1.

The modification register is not the price list. Pricing, MOQ and lead time are factor-structure discussions and they resolve to /request-a-quote, not into the DFM pillar. The register is the engineering document. A row in the register is engineering work; a row in the quotation is commercial work. The ODM buyer who mixes the two ends up with engineering decisions being re-opened at the price-conversation stage, which costs both sides time.

Pillar 2 — Firmware localization across platform branches and language trees

The second pillar is the firmware choice. Firmware is the program inside the lock: the pairing flow, the credential issuance, the audit-log format, the BLE advertisement cadence, the low-battery warning, the mechanical-override interlock, the OTA path (if any), the factory-reset behavior, and the platform binding. On a Bluetooth-class lock, firmware is also the bridge between the lock and the platform owner — TTLock, Tuya, Doodle, or the hotel PC software lane. The ODM buyer's job on this pillar is to say which platform the lock binds to, which language tree the lock ships in, and which feature branches the lock carries.

Three platform realities govern this pillar:

  • TTLock and Tuya and Doodle are the three app-platform lanes present in the smartlockfactory.com catalog. They are not interchangeable. Each has its own credential model, its own audit-log format, its own gateway-or-no-gateway policy, and its own end-user account model. The ODM buyer who assumes the three platforms are equivalent ends up choosing a platform whose credential model does not match the brand's distribution model.
  • Hotel PC software is a fourth lane, used on hotel-class models (for example the SLK-9936S class — multilingual management software, standalone or centralized database, audit/event records up to 1,000). Hotel PC software is not a consumer app lane. The two are not interchangeable, and the ODM buyer who tries to put hotel PC software on a residential-class Bluetooth lock, or vice versa, gets neither.
  • App-platform support is per-model. Two locks in the same factory line, in the same catalog category, do not necessarily share the same platform. Check the model’s published specification for every shortlisted SKU before any platform is locked into the firmware pillar.

Pillar 2.1 — Platform binding as the single irrevocable decision

Platform binding is the single irrevocable decision in the firmware pillar. Once the firmware is compiled against TTLock credentials, it does not run against Tuya's ecosystem, and vice versa. The ODM buyer who tries to keep both options available "until we see which one the distributor prefers" is not keeping options open — they are committing to neither, which means the firmware is committed to neither, which means the lock has no end-user app story at all. The platform decision is made first. Then the firmware is compiled. Then the accessory menu is sized for that platform's onboarding flow. Then the manuals are written for that platform's vocabulary. Then the training is taught on that platform's vocabulary.

The platform binding decision is recorded as a single line in the firmware pillar document: Platform = TTLock / Tuya / Doodle / hotel PC software, revision-locked, dated, signed by the ODM buyer. Any later change requires one-line, dated re-sign-off across every other pillar.

Pillar 2.2 — Language tree as the firmware's localization footprint

The language tree is the set of languages the firmware carries out of the box: voice prompts, on-device menus, LED color codes, error beep patterns, low-battery warning phrases, mechanical-override instruction copy. The ODM buyer who treats language as a manual-translation task and not a firmware task ends up with a lock whose on-device voice prompt says "low battery" in English while the manual says "Batterie faible" in French, while the installer's quick-start card is in Spanish. The three surfaces have to be coherent.

The language tree is sized by the ODM buyer's distribution plan, not by the factory's reference language list. If the program ships into three markets, the language tree ships with three language sets. If the program adds a fourth market mid-program, the firmware is re-compiled and the manual is re-translated and the installer's quick-start card is re-printed. None of that is free.

Pillar 2.3 — Feature branches the lock carries (and the ones it does not)

The feature branch list is the list of firmware features the lock exposes to the platform app. A typical Bluetooth-class lock carries: PIN code issuance, time-window PIN, one-time PIN, e-key issuance to a named account, e-key revocation, audit-log read, audit-log export (format varies), battery-level read, low-battery warning, mechanical-override interlock, factory-reset, and a small set of admin operations (add/delete user, change master code, set time). What it does not carry — because the catalog does not contain it — is anything depending on Matter, Zigbee, Apple Home Key, Thread, Z-Wave, or UWB. If the ODM brief requires any of those, the firmware pillar redirects before any branch is signed off.

The feature branch list is locked against the platform binding. The two are not negotiated independently.

Pillar 3 — Accessory menu as a separately-engineered, separately-stocked list

The third pillar is the accessory menu — the set of items that ship in the box (or are ordered as line items alongside the box). The ODM buyer's job is to write the menu, not to discover it. Every line item on the menu is a separately-tooled, separately-stocked, separately-priced item, and every line item the ODM buyer adds or removes changes the box weight, the box dimension, the packing labor, and the after-sales support flow.

A reference accessory menu is given below. The ODM buyer treats it as a checklist against which to mark ACCEPTED, MODIFIED, REMOVED, or ADDED. Every mark has an owner.

Accessory linePurposeDefault inclusionODM mark
Strike plate (or strike box)Door-frame reinforcement at the bolt seatIncluded(ODM buyer marks)
Mounting hardware packScrews, sleeve anchors, alignment pins, cable tiesIncluded(ODM buyer marks)
Mechanical-override key (one or two per lock)Battery-dead or firmware-fault fallbackOne key per lock(ODM buyer marks)
IC card or RFID card (one or two per lock)Installer enrollment, primary-credential demoOne card per lock(ODM buyer marks)
Quick-start cardPairing, PIN reset, mechanical-override procedureIncluded(ODM buyer marks)
Positioning templateDoor-prep alignment, especially for retrofit installsIncluded on retrofit-class locks(ODM buyer marks)
Battery setAlkaline cells sized to the lock's battery compartmentOptional — many markets supply locally(ODM buyer marks)
Gateway / enrollment encoderRequired if the platform or property model demands itPer-program (by buyer architecture)(ODM buyer marks)
Spare-label primerReplacement of brand label or compliance markingPer-program(ODM buyer marks)
Inner-box / master-carton labelPer-market language, per-market regulatory markingPer-program(ODM buyer marks)

Three rules govern the accessory menu pillar:

  • The accessory menu is not the BOM. The BOM (bill of materials) is the factory's internal document listing every component, fastener, and sub-assembly that goes into the lock. The accessory menu is the buyer-facing list visible in the carton and on the product page. The two overlap but they are not the same document, and the ODM buyer does not own the BOM. The buyer owns the accessory menu.
  • The accessory menu is a logistics document, not just a packaging document. Every line item the ODM buyer adds or removes changes carton dimension, master-carton quantity, pallet pattern, container utilization, customs declaration line count, and inbound inspection labor. The menu is a logistics conversation as much as a branding conversation.
  • The accessory menu does not include certification, warranty card, instruction manual, or compliance insert. Those live in the packaging pillar (Pillar 4).

Pillar 4 — Packaging as a five-surface decision

The fourth pillar is the packaging — the outer carton, the inner box, the print stack inside the box, the regulatory marking, and the brand surface. On Bluetooth-class locks the packaging has five surfaces, not one, because the box has to communicate five different things to five different audiences: the end-user (pairing and use), the installer (mounting and commissioning), the distributor (storage and resale), the customs officer (regulatory and compliance), and the recycling/waste trade (material and disposal).

The five packaging surfaces are:

  1. Outer carton — the master-carton level that carries shipping marks, pallet pattern, container utilization, and the regulatory marking required by destination market. The outer carton is typically a brown corrugated print, with black-ink shipping marks and a buyer-side brand mark.
  2. Inner box — the unit-level box that carries the brand surface in full color. The inner box is the only packaging surface the end-user sees in the home, and the ODM buyer's brand lives here. Print, finish, opening mechanism, and unboxing sequence are all buyer decisions.
  3. Print stack — the documents inside the box: quick-start card, full instruction manual, warranty card (if any), compliance insert (if any), regulatory marking insert (if any), and a brand-card. The print stack is per-paper and per-language and is sized to the language tree from Pillar 2.
  4. Regulatory marking — the marks required by destination market on the outer carton and (where applicable) on the lock body. Regulatory marking is the buyer's compliance duty, not the factory's, and the factory's role is to apply marks the buyer provides in the artwork the buyer signs off.
  5. Brand surface — the brand mark on the lock body, on the inner box, on the print stack, on the warranty card, and on the app-store listing. The brand surface is the most-crossed surface in the program, because every other pillar touches it at least once.

Three rules govern the packaging pillar:

  • The packaging is per-market, not per-program. A program that ships into three markets has three print stacks, three regulatory marking sets, three inner-box artworks, and one shared outer-carton artwork (typically). The packaging pillar is sized by the distribution plan.
  • The packaging is per-revision, not per-program-version. When the firmware is re-compiled under Pillar 2, the print stack has to be re-checked for language coherence. When the accessory menu is changed under Pillar 3, the inner-box cavity has to be re-validated. When the brand surface changes under Pillar 4, every surface in the program is re-checked.
  • The packaging is not a marketing decision alone. The packaging is a logistics decision (carton dimension drives pallet pattern drives container utilization), a regulatory decision (per-market marks are not optional), and a sustainability decision (material selection drives end-of-life). The packaging pillar is run as a five-surface conversation, not as a graphic-design conversation.

Pillar 5 — After-sales training as a four-audience program

The fifth pillar is the after-sales training — the assets, the flow, the escalation path, and the cadence that the ODM buyer puts behind the lock after the lock leaves the factory. On Bluetooth-class locks, after-sales training is unusually heavy because the lock generates a non-trivial share of credential-management tickets rather than mechanical tickets, and the credential-management tickets require the buyer's brand to be the bearer of the answer. A Bluetooth-class lock whose end-user calls the factory's support line is a Bluetooth-class lock whose brand has lost an end-user.

The four audiences are:

  • End-user — the person who pairs the phone, sets the PIN, and uses the credential. End-user training is delivered through quick-start card, in-app tutorial (where the platform supports it), and a brand-side knowledge base. End-user training assets are owned by the brand, not the factory.
  • Installer — the person who fits the lock to the door, enrolls the master credential, and hands the lock over. Installer training is delivered through installation manual, an installer-side knowledge base, and (where the program warrants it) an installer certification. Installer training assets are jointly owned: the manual by the brand, the certification by the brand, the platform-side onboarding by the factory.
  • Distributor — the person who stocks the lock, prices it, and trains the installer downstream. Distributor training is delivered through a distributor playbook, a pricing-and-margin guide, and a sell-sheet. Distributor training assets are owned by the brand.
  • Brand-side support agent — the person who answers the end-user's call, the installer's call, and the distributor's call. Brand-side support training is delivered through a support playbook that names the escalation path: which ticket the brand handles, which ticket the factory handles, and which ticket the platform owner (TTLock / Tuya / Doodle / hotel PC software vendor) handles. Support-side training is jointly owned: the brand-side playbook by the brand, the factory-side escalation path by the factory, the platform-side ownership in writing from the platform owner.

A reference after-sales scope-by-audience table is given below.

AudienceAssetOwnerDelivery cadence
End-userQuick-start card, in-app tutorial, brand knowledge baseBrandAt install + on update
InstallerInstallation manual, brand knowledge base, optional certificationBrand (manual) + Brand (cert) + Factory (platform-side)At product launch + on firmware revision
DistributorDistributor playbook, pricing-and-margin guide, sell-sheetBrandAt product launch + annually
Brand supportSupport playbook with named escalation pathBrand (playbook) + Factory (escalation) + Platform (in writing)At product launch + on each escalation-pattern review

Three rules govern the after-sales training pillar:

  • The training program is per-revision, not per-program-version. A firmware revision under Pillar 2 triggers a training-asset revision under Pillar 5. A packaging revision under Pillar 4 does not trigger a firmware revision, but it does trigger a print-stack revision check.
  • The escalation path is in writing, not in conversation. The brand-side support agent who needs to escalate a platform-side ticket (for example a TTLock credential-issuance failure) needs a written path to the factory's named contact and a written path to the platform owner's named contact. The escalation path is named in the warranty clause and the support playbook, both signed.
  • The after-sales training is not a warranty. Warranty terms — duration, scope, exclusions, claim procedure — are not asserted in this article. Pricing, MOQ and lead time are factor-structure discussions and they resolve to /request-a-quote, not into the training pillar.

The pillars in sequence — a stage-gate view

The five pillars do not run in parallel. They run in sequence, and each pillar's sign-off gate is the entry condition for the next pillar. The ODM buyer who runs the pillars in parallel saves calendar time at the cost of every later pillar having to re-open earlier pillars, which costs more calendar time overall.

StagePillarEntry conditionExit gateOwner
1Design-for-manufactureBrand positioning + target-market sketch in writingModification register locked, door-fit envelope signed, first-article plan agreedBrand (positioning) + Factory (mechanical lockup)
2Firmware localizationPlatform binding decided, language tree sizedFirmware revision locked, feature branch list locked, OTA path (if any) signedBrand (platform decision) + Factory (firmware compile)
3Accessory menuFirmware platform binding confirmedAccessory menu locked, carton / pallet pattern agreedBrand (menu decision) + Factory (carton engineering)
4PackagingAccessory menu lockedPrint stack locked, regulatory marking set, brand surface signedBrand (artwork) + Factory (print)
5After-sales trainingPackaging and firmware both revision-lockedEscalation path in writing, training assets delivered, support playbook signedBrand (assets) + Factory (escalation) + Platform (in writing)

A reference cross-pillar sanity check is given below. The ODM buyer runs this before any stage gate is signed.

Sanity checkPillar 1Pillar 2Pillar 3Pillar 4Pillar 5
Is the dated reference-design revision locked?RequiredRequiredRequiredRequiredRequired
Is the modification register signed?RequiredRequired(carry-forward)(carry-forward)(carry-forward)
Is the platform binding signed?—RequiredRequiredRequiredRequired
Is the language tree sized?—RequiredRequiredRequiredRequired
Is the accessory menu locked?——RequiredRequiredRequired
Is the print stack locked?———RequiredRequired
Is the escalation path in writing?————Required

Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.

The ODM buyer who runs the pillars in the sequence above, with the sanity check above at each gate, ends the program with a lock that the installer can commission, the end-user can pair, the distributor can support, the customs officer can clear, and the platform owner can recognize. The ODM buyer who runs the pillars in any other sequence ends the program with a brand name on a paperweight.

Read as a chain of sign-offs, where each exit gate arms the next pillar — and a mid-program revision can send the buyer back a step — the sequence looks like this:

stateDiagram-v2
    state "Pillar 1 · Design-for-manufacture" as P1
    state "Pillar 2 · Firmware localization" as P2
    state "Pillar 3 · Accessory menu" as P3
    state "Pillar 4 · Packaging" as P4
    state "Pillar 5 · After-sales training" as P5
    [*] --> P1
    P1 --> P2 : Modification register locked · door-fit envelope signed
    P2 --> P3 : Platform binding signed · feature branch list locked
    P3 --> P4 : Accessory menu locked · carton pattern agreed
    P4 --> P5 : Print stack locked · brand surface signed
    P5 --> [*] : Escalation path in writing · playbook signed
    P2 --> P1 : Reference-design revision advances mid-program

An illustrative ODM scenario — a 90-unit residential property program

To make the five pillars concrete, consider an illustrative program. A brand owner wants to launch a Bluetooth-class lock line under their own brand, for distribution through a small distributor network, into residential and small-commercial doors. The program is for a 90-unit illustrative residential property as the anchor scenario; the same pillars apply to every other property in the distribution plan. Names, numbers and dates in this scenario are illustrative and not a customer reference.

Pillar 1 (DFM) — what the brand owner accepts and what they change. The brand owner accepts the reference mechanical design for one fingerprint + PIN + card + key + app Bluetooth-class model (for example a model in the SLK-8831 5-in-1 class on the catalog — every numeric spec on this category is check the model’s published specification for the shortlisted SKU). The brand owner changes the finish schedule to add one additional finish option and changes the cylinder keyway to a profile the brand specifies. The brand owner does not re-engineer the bolt geometry, the reader face, or the battery compartment. The DFM pillar's exit gate is a signed modification register with three rows (finish, keyway, brand-label plate) and a door-fit envelope matrix covering the 90 doors in the anchor property.

Pillar 2 (firmware localization) — which platform, which language tree, which branches. The brand owner binds the firmware to the TTLock app lane (the platform choice is the buyer's, and it is irrevocable). The language tree is sized to the distribution plan: English, Spanish, French for the anchor markets; additional languages the OEM would not carry because the ODM program has its own market list. The feature branch list is the reference branch list (PIN, time-window PIN, one-time PIN, e-key issuance, e-key revocation, audit-log read, battery-level read, low-battery warning, mechanical-override interlock, factory-reset, admin operations) — no additions, no removals, because the ODM brand does not need a feature branch the reference design does not carry.

Pillar 3 (accessory menu) — what ships and what does not. The brand owner accepts the reference accessory menu (strike plate, mounting hardware, two mechanical-override keys per lock, two IC cards per lock, quick-start card, positioning template, no battery set) and adds one line: a brand-side welcome card. The brand owner does not add a gateway because the reference platform binding (TTLock direct-BLE) does not require one for the anchor property. The accessory menu's exit gate is a signed menu with eight line items, a carton dimension, a master-carton quantity, and a per-market inner-box artwork list.

Pillar 4 (packaging) — five surfaces, per market. The outer carton is a brown corrugated with black ink, shared artwork. The inner box is full-color, per-market (English / Spanish / French). The print stack is per-market (quick-start card in three languages, full manual in three languages, warranty card in three languages, compliance insert in three languages, brand-card). The regulatory marking is per-market. The brand surface is the brand mark on the lock body, the inner box, the print stack, the warranty card, and the in-app brand string. The packaging pillar's exit gate is a signed artwork pack with three market variants.

Pillar 5 (after-sales training) — four audiences, four asset sets. End-user: quick-start card + brand knowledge base (English / Spanish / French). Installer: installation manual + brand knowledge base + installer certification. Distributor: distributor playbook + pricing-and-margin guide + sell-sheet. Brand support: support playbook with named escalation path (brand handles ticket; factory handles escalation; TTLock handles platform-side ticket per the platform owner's written escalation path). The after-sales training pillar's exit gate is a signed training pack with all four audience asset sets delivered, the escalation path in writing, and the support playbook signed by the brand, the factory, and (in writing) the platform owner.

The illustrative scenario's five pillars run in approximately the order above, in approximately the calendar time it takes to sign off each pillar. The brand owner who runs the same five pillars in a different order (Pillar 4 first, then Pillar 2, then Pillar 1) ends the same program with rework at every later pillar and a brand-name on a paperweight.

Cross-cluster routing — where this article hands off

This article is the ODM pillar of the Bluetooth-class program cluster. It sits between the OEM pillar and the supplier-selection pillar, and below the connected-smart-locks umbrella. The cross-cluster routing is:

  • Above — Connected Smart Locks: Complete B2B Guide. The umbrella article that names the BT-program-family across OEM, ODM, supplier, manufacturer and use-case guides. Read first.
  • Parallel — Bluetooth Smart Lock Manufacturer Guide. The factory-capability pillar of the BT family. Read alongside this article when qualifying the factory's reference-design capability.
  • Parallel — Bluetooth Smart Lock OEM Guide. The OEM pillar of the BT family. Read alongside this article when the program shape is OEM rather than ODM.
  • Parallel — Bluetooth Smart Lock Supplier Guide. The supplier-selection pillar. Read when the brand-side choice is between multiple BT-class suppliers, not between OEM and ODM.
  • Site pages — /oem-odm for the cross-program overview, /become-a-distributor for the distributor-program overview, /private-label and /smart-lock-manufacturer for the brand-program and manufacturer-program landing pages.
  • Categories — /bluetooth-lock for the Bluetooth-class category page, /fingerprint-door-lock for fingerprint + Bluetooth hybrids, /keypad-door-lock for keypad + Bluetooth hybrids, /rfid-door-lock for RFID + Bluetooth hybrids, /hotel-lock for hotel-class Bluetooth-class locks where the hotel PC software lane applies.
  • Primary CTA — /request-a-quote for ODM program pricing and program-shape confirmation.
  • Secondary CTA — /order-samples for first-article units under the DFM pillar, /request-catalog for the full Bluetooth-class catalog.

Decision rules for the ODM brand owner

Ten rules the ODM brand owner holds across the program:

  • Rule 1 — The five pillars run in sequence. Skipping a pillar is a re-work budget against the next pillar, not a calendar saving.
  • Rule 2 — The reference design is locked before the modification register is opened. The modification register is the engineering document; it is not a price document.
  • Rule 3 — Platform binding is irrevocable. The platform is decided first, then the firmware is compiled, then every other pillar aligns to that platform.
  • Rule 4 — The language tree is sized by the distribution plan, not by the factory's reference language list.
  • Rule 5 — The accessory menu is a logistics document as much as a packaging document. Every line item changes carton dimension, master-carton quantity, pallet pattern, container utilization.
  • Rule 6 — The packaging is per-market, per-revision, and per-surface. Five surfaces, three markets, one program.
  • Rule 7 — The after-sales training is per-audience. End-user, installer, distributor, and brand-side support each carry a distinct asset set.
  • Rule 8 — The escalation path is in writing. The brand-side support agent who needs to escalate a platform-side ticket needs a written path to a named factory contact and a written path to a named platform-owner contact.
  • Rule 9 — Per-model specs (door-thickness envelope, battery format, audit-log depth, mechanical-override policy, finish schedule, app-platform identity) are confirmed on the product page for every shortlisted SKU, not assumed from category or line.
  • Rule 10 — Pricing, MOQ and lead time are factor-structure discussions and they resolve to /request-a-quote. Warranty terms are not asserted in this article and are named in the program contract, not in the pillar documents.

Where to go from here

The ODM brand owner who has read the five pillars and the cross-cluster routing has the program-shape outline. The next step is the program-specific configuration: which platform binding (TTLock / Tuya / Doodle / hotel PC software), which language tree, which finish schedule, which accessory menu, which after-sales scope. That configuration is named in the program contract, not in this pillar guide, and it is sized by the program-specific RFQ.

The Bluetooth Smart Lock Manufacturer Guide is the parallel article for qualifying the factory's reference-design capability. The Bluetooth Smart Lock OEM Guide is the parallel article for the OEM pillar, in case the program shape re-evaluates to OEM during pillar 1. The Bluetooth Smart Lock Supplier Guide is the parallel article for the supplier-selection pillar, in case the program needs a second-source comparison. The connected-smart-locks umbrella is the cross-cluster index for the full BT family.

When the program-shape outline is firm, request a quote at /request-a-quote with the five pillars named as the request's structure, and the program-specific configuration is built against the pillar-by-pillar sign-off. For first-article units under Pillar 1, order samples at /order-samples with the modification register attached. For the full Bluetooth-class catalog under Pillar 3, request a catalog at /request-catalog with the platform binding already named.

Twój koszyk
Twoje doświadczenie na tej stronie zostanie poprawione dzięki zezwoleniu na pliki cookie Polityka plików cookie
Chat on WhatsApp