
Brand owners ask which parts of a lock can change, who owns the tooling, and how a private label run affects certification, cost and lead time.
This FAQ answers the practical questions that come up in OEM and ODM projects: which parts of a lock are mechanical and which are electronic, what a new enclosure, a custom firmware build or a white-label app really involve, who owns moulds and tooling paid for by the buyer, how branding, packaging and manuals are controlled, why custom work carries a different minimum quantity from neutral stock, how existing test evidence transfers to a new model number, and how a project is scheduled from requirement to mass production. The answers describe normal engineering and commercial practice. Tooling scope, NRE, custom MOQ, sample approval steps and lead time are confirmed in writing per quotation, and certificates and test reports for named SKUs are provided per RFQ.
OEM means the buyer specifies or supplies the design and the factory manufactures it under the buyer's brand; ODM means the factory owns the design and the buyer brands an existing platform, sometimes with modest changes; private label is the lightest form, usually the same hardware with the buyer's logo, packaging and app skin. In smart locks the three overlap, because a lock is a mechanical body plus electronics plus firmware plus an app, and each layer can sit closer to OEM or closer to ODM. The practical difference is who carries the design risk and who owns the technical file. Which SKUs can be private-labelled as they are, and which need a genuine ODM development step, is confirmed in writing per quotation.
The layers run from cheapest to most involved: laser or print logo on the escutcheon and keypad; carton, manual, label and accessory artwork; finish and colour of the front plate; app name, icon, colours and language set; firmware behaviour such as code length, lockout timing, sound and language; the credential set, for example adding RFID or a fingerprint module; mortise body, spindle and tail bar for a specific door standard; and a new enclosure or keypad layout, which is a real industrial-design project with tooling. Mechanical changes touch door fit and fire evidence, while electronic changes touch radio certification. What a given SKU allows, and what each layer costs in tooling and NRE, is confirmed in writing per quotation.
Firmware changes fall into three buckets. Configuration changes such as default language, code length, auto-lock delay, volume and display behaviour are normally parameter work on an existing build. Feature work such as a new access mode, a different audit-log format, an extra time-limited rule or a custom API payload needs engineering and testing, and therefore NRE. A complete platform replacement, for example moving from a ready ecosystem to a self-developed cloud, is a separate product decision with its own certification and support burden. Every firmware variant needs its own version record and regression testing, otherwise field units drift apart. Feasibility, NRE scope, testing plan and delivery of the build are confirmed in writing per quotation.
Ownership must be written down, because it decides what happens if you change supplier. Common arrangements are: the buyer pays for the tooling and owns it, with the mould tagged and stored at the factory during the relationship; the buyer pays and the factory retains ownership but grants exclusive use; or tooling cost is amortised into the unit price with no separate asset. Ask for the ownership clause, the storage and maintenance terms, the conditions under which the tool can be moved, and whether a tool-life record is kept. Die-cast and injection moulds wear, so maintenance responsibility matters as much as ownership. Ownership, tagging, storage, amortisation and transfer conditions are confirmed in writing per quotation.
Three routes are realistic. White-label: the supplier platform app is rebranded with your name, icon and colours — fastest and cheapest, but the feature set and release cycle stay with the platform. Self-built app on the supplier SDK or API: your developers build the interface while the supplier keeps device firmware and cloud, which gives control but needs real software capacity and a support agreement. Fully independent cloud and firmware: the largest scope, needing device, gateway, cloud and app work plus new radio and security evidence. Whichever route is chosen, define who fixes a bug, who handles app-store releases and who owns user data. API scope, white-label terms and support boundaries are confirmed in writing per quotation.
Branding is managed as artwork with formal approvals, not as verbal instructions. The usual package covers escutcheon logo, keypad print, carton print, label with model and regulatory marks, a user manual in the required languages and accessory bags. Print files need correct colour references, bleed and safe areas, and a signed proof before production; manuals also need the right language set and accurate regulatory statements, since a manual that misstates certification is a compliance problem in itself. Packaging minimums come from the carton supplier and are usually higher than the lock minimum. Artwork approval, language list, packaging minimum and print lead time are confirmed in writing per quotation before production starts.
Yes, within the mechanical limits of the platform. Mortise bodies differ in case size, backset, faceplate, latch and deadbolt arrangement, and in whether they carry a Euro profile cylinder, a US-style cylinder or a thumb-turn only. Changing the body normally means a different part number, new fit drawings and sometimes a new fire-listing reference, even when the electronics and reader plate stay the same. Spindle and tail bar lengths are matched to door thickness and must be specified per order, because a wrong length causes binding or a lost drive. Door-standard changes are engineering work, not a label change. Compatible bodies, spindle options, cylinder types and drawings are confirmed in writing per quotation.
A logo change is surface work: laser marking, print or a badge, with no effect on radio, mechanics or certification. A new enclosure is industrial design: 3D modelling, mock-ups, die-cast or injection tooling, a revised PCB layout to fit, antenna re-tuning, drop and ingress testing, and usually new radio and safety evidence because the product identity has changed. It also needs a new label, manual and packaging design. The cost and schedule difference is large — weeks for a logo against a full development cycle for a new body. Which route suits your brand plan, and the tooling, NRE and evidence each one needs, is confirmed in writing per quotation.
Yes, when the drawing is complete and measurable. Send 2D drawings, a physical or 3D reference, the door data, the credential list and the target market, and expect a feasibility answer that separates what can be built on an existing platform from what needs new tooling. A reference sample is useful but must be accompanied by tolerances, material and finish specification, because a photograph cannot define a fit. Where the design belongs to another brand, the project needs a written authorization or a genuinely different design; copying a protected shape is not offered. Feasibility, required drawings and the development route are confirmed in writing per quotation.
Only where the product identity stays the same. Certification is tied to the manufacturer, model number, radio module and sometimes firmware, so a private-label run that changes logo, carton and finish usually remains inside the original technical file, with the brand mapping documented and the responsible party agreed. A new model number, a different enclosure, a different radio module, extra circuits or new firmware can invalidate the report and require delta or full retesting. Selling into the EU or UK also raises the question of who signs the declaration and holds the technical file for your brand. Which SKUs the existing evidence covers, and what a new identity requires, are confirmed in writing per RFQ.
NRE is non-recurring engineering: the one-time work that makes a buyer-specific variant possible, as distinct from the recurring cost of each unit. Typical items are firmware feature development and regression testing, a PCB re-layout or small hardware change, app white-label setup and store submission, new artwork and manual work, new test fixtures, and engineering samples before mass production. It is charged once, sometimes staged by milestone, and it is not recoverable by the factory if the project stops, which is why it is normally paid before development begins. Scope, milestones, deliverables, acceptance criteria and any credit against later volume are confirmed in writing per quotation.
Custom work raises the minimum because setup and leftovers serve one buyer only: printed cartons are ordered at the carton supplier's own minimum, laser programs and fixtures are dedicated, and firmware variants must be built, tested and version-controlled separately. The practical consequence is that a light customisation, such as a logo on neutral packaging, can often run at a lower quantity than a full private label with custom cartons, manuals and app. Minimums are usually stated per model and per customisation type, not as one total piece count. Current MOQ policy for each SKU and customisation level is confirmed in writing per quotation.
Schedule the phases rather than one date: requirement and feasibility, industrial design and mock-up, tooling and first article, engineering samples and your validation on real doors, firmware and app milestones, certification work where a new identity is created, then packaging approval, a pilot run and mass production. Each phase has its own review gate, and buyers usually add a feedback loop after sample testing. Delays concentrate in artwork approvals, late specification changes and certification, not in assembly itself. A realistic plan names dates per phase against the agreed scope. Development schedule, sample dates, tooling lead time and the production window are confirmed in writing per quotation.
An NDA is normal for ODM work: it protects drawings, firmware specifications, artwork and commercial data, and it usually runs in both directions because the factory shares platform information as well. Exclusivity is a commercial decision rather than a document: it is normally tied to a defined territory, product configuration, committed volume or a period, and it must state what happens if the volume is not reached. Exclusive arrangements also interact with the mould ownership clause. Ask for the NDA before sending detailed drawings, and read any exclusivity offer against your forecast honestly. NDA coverage, exclusivity terms and volume commitments are confirmed in writing per quotation and contract.
Approval should produce both a physical and a written reference. Typical steps: engineering samples for function, then a golden sample set signed and dated by both sides, a written specification covering materials, finish, colour, firmware version, packaging and accessories, and an inspection checklist for incoming and pre-shipment checks. Photographs help but do not replace the signed sample, and any change after approval needs a written change note, because silent changes are the most common source of disputes. Keep one golden set at each end. Sample stages, golden-sample handling, change control and inspection criteria are confirmed in writing per quotation.
The document package follows the market and the product identity: radio and safety test reports plus the declaration of conformity for CE markets, the FCC grant and ID for the USA, RoHS and REACH statements, ANSI/BHMA reports where North American hardware claims are made, fire-listing cross-references for labeled doors, and battery transport documents for shipping. Brand-related items include artwork files, label templates, a manual in the agreed languages and a firmware version record. Documents must name the shipping model, which is why brand mapping is agreed early. Certificates and test reports for named SKUs are provided per RFQ, and gaps on a model still in development are stated as gaps.
Technically yes, but retail channels bring requirements that belong in the brief: a stable model identity and consistent packaging, barcode and label data, a manual in the marketplace language, safety and radio evidence for the destination, and often a defined warranty process and spare-parts supply. Marketplace compliance also expects honest battery and radio statements and consistent images. Where a retailer audits the factory, the audit scope and any corrective actions need planning before the order. Channel requirements, listing data, label content and any audit support are confirmed in writing per quotation, because they change the schedule rather than the lock.
Failures are handled as engineering findings rather than arguments. A sample that fails fit, radio range, battery behaviour or drop testing gets a written failure note, a root-cause analysis, a corrective action and a re-test plan; the responsible party depends on whether the fault sits in the platform, the buyer's specification or the change itself. Commercial consequences — who pays for rework, retooling or re-testing — should be agreed before development starts, because they are hard to negotiate after a failure. Projects also need a stop condition. Failure handling, rework responsibility, re-test cost and project stop terms are confirmed in writing per quotation and contract.
Custom runs need the same controls as standard ones plus change control: incoming inspection of components and printed packaging, in-process checks on assembly and firmware flashing, functional test of every unit against the approved specification, aging or burn-in where the platform requires it, and pre-shipment inspection against the golden sample and checklist. Firmware needs a version record tied to each batch, and packaging needs a proof against the approved artwork. Records should be retrievable per batch so a complaint can be traced. Inspection standards, sampling levels, record retention and third-party inspection access are confirmed in writing per quotation.
Send your target door data, brand assets, app preference and volume plan. Engineering scope is answered first, then tooling, NRE, custom MOQ and lead time are confirmed in writing per quotation.
Ask Our EngineersRequest a QuoteLast updated: November 1, 2026 · Answers reviewed by the Smart Lock Factory engineering team