OEM Smart Lock Project Preparation
The base model, door data, branding and software scope, sample goals and who approves what, in one checklist.
Launching a private-label smart lock range means settling the base model, the branding and the sample before anything is tooled. Our smart lock OEM guides cover each step, from the first brief to keeping repeat orders identical to the approved sample. Our own OEM routes and terms are on OEM/ODM.
"Private label" can mean a logo on a box or new tooled parts. Name the scope first: it decides what you send, what the sample must prove, and the MOQ, cost and timing in the quotation.
| Scope | What changes | You send | Check on the sample |
|---|---|---|---|
| Logo and packaging | Logo on the panel; retail boxes or project cartons; manuals in your language | Vector logo, position, box or label reference, manual languages | Logo size, position and contrast on the real surface; box, labels and manual |
| Finish and color | A standard finish from the model's list, or a custom color matched to a physical sample or RAL code | Model, finish name or color sample, photos of the door hardware it must match | Color, texture and gloss next to the door hardware |
| Hardware and door fit | Lock body, spindle, screws and accessories for each door group | Door thickness, stile width, door-edge photos, opening direction | Fit, handle and mortise on a real door |
| New appearance or structural parts | New parts and tooling; scope, cost, ownership and use of tooling agreed in writing before work starts | Drawings or references, target quantity | Prototype parts against the agreed drawing |
| App and functions | The access methods and the TTLock or Tuya version each model supports | How users enter and are managed, and whether remote access is needed | Each access method and the app workflow |
A dedicated app, white-label interface or firmware change is a separate development request. Software customization is scoped separately with our module and software partners; see app vs hardware branding.
The base model, door data, branding and software scope, sample goals and who approves what, in one checklist.
Start from the decision the sample must support: configuration, accessories, door fit, app checks and next steps.
Your logo on the lock is not your own app: platform limits, account ownership, publishing and support.
Packaging, labels, manuals, SKU and barcode data, QR links, proofs and approved revisions.
Separate tooling, engineering, setup and MOQ drivers, and first-order from repeat-order cost.
Turn the approved sample into a production reference, with change approval and repeat-order checks.
Every OEM project is built against one approved sample and a written specification, and new or changed designs also go through a pilot run before regular production. The steps, from brief to repeat order, are on our OEM/ODM pages below.
The base model or door type, your logo and finish, packaging and manual language, target market and rough quantity.
No. Logo, labels, packaging and manuals are hardware branding; a branded app is a separate scope with its own platform terms.
It is recorded with its model, version, finish, lock body, accessories, artwork and packaging, so every repeat order is built and checked against it.