A low ex-factory price can be the correct choice for a stable, proven standard programme. It is not a complete comparison when the buyer also needs branding, firmware changes, an app route, interface validation, market documentation, spare stock or a support process. Those are operating costs and delivery risks, not optional footnotes.
Compare the OEM programme by workstream
| Workstream | Purchase-price view | TCO view |
|---|---|---|
| Configuration | Base product price. | Hardware revision, accessories, firmware, packaging and approved variants. |
| Validation | Sample unit cost. | Representative tests, acceptance criteria, rework ownership and release record. |
| Brand and software | Artwork or app fee. | Account, update, data, store and exit responsibilities. |
| Compliance | Document supplied or not supplied. | Exact model, destination, label, importer and revision evidence. |
| Lifecycle | Warranty statement. | Spare parts, repair route, change control and service ownership. |
Ask the supplier to separate scopes
Request one written quote that separates standard supply, private-label changes, OEM engineering, ODM development, tests, documentation, samples, tooling and exclusions. That prevents a buyer from comparing an incomplete standard offer against a configured offer that carries more obligations.
An OEM purchase decision includes the work that happens before the first production unit and after the first installation. Treating existing model supply, private-label packaging, app or firmware work, mechanical changes, certification documents and support ownership as one line hides the reason one quote is higher and makes a repeat order difficult to control.
Ask for separate lines for sample work, tooling or NRE, artwork and packaging, firmware or API changes, certification review, production, spares and after-sales support. For each line record the deliverable, acceptance event, owner and change trigger. The local OEM supplier scope uses 200 units as a standard-supply planning baseline, 500 for OEM or private-label planning and 1,000 for deeper ODM development. These are planning points; the written quote must still bind the selected model and configuration. For the programme-level choice, see OEM vs ODM smart lock programme and the OEM manufacturer guide.
Model cost by the installed route
Build one scenario for the target market and include sample freight, labels, manuals, commissioning time, account setup, firmware maintenance, spare stock, warranty handling and the cost of a field change. A programme with a lower purchase price can carry more labour if the app, network interface or door fit is left for the distributor to solve. Put the same door count, credential policy and support window into every option so the comparison stays fair.
| Line | Option A | Option B | Owner |
|---|---|---|---|
| Standard supply and accessories | Supplier | ||
| Brand, packaging, manuals, labels | Brand owner | ||
| Firmware, API or app work | Supplier / brand | ||
| Samples, tests, acceptance | Distributor | ||
| Destination documents and labels | Importer | ||
| Spares, repair, technical intake | Distributor |
Leave a cell blank rather than guessing, and mark an excluded item as excluded so it is visible in the comparison.
Lifecycle costs need an owner
Before release, define who owns firmware maintenance, account administration, technical intake, RMA approval, spare parts and any transition when a model changes. A product range can be suitable yet still be unsuitable if that operating ownership cannot be supported in the target market. Related reading: smart lock quality and after-sales cost and reducing smart lock returns and service calls.
Set a release gate
Release only when the sample report, approved artwork, model revision, certification file, firmware build and support route point to the same configuration. Keep the first-order assumption separate from the repeat-order assumption. A change to the lock body, radio module, app account or destination market should reopen the affected test rather than silently changing the approved scope.
Repeat-order economics and change control
The first order proves that the selected configuration can be supplied. The repeat order proves that the programme can be operated. Review whether the app account, firmware maintenance, packaging, certification evidence, spare stock and support route remain the same when quantity changes. A repeat order should reference the approved sample and revision instead of reopening every assumption by email.
Events that reopen cost
- Lock-body or radio-module change.
- New language, market label or destination.
- API or app-account change.
- Revised power adapter or accessory.
- New installer route or support window.
For each event, name the retest, document update and owner. This gives the brand and supplier a shared boundary when a lower-cost alternative is proposed. If the supplier offers a cheaper component or a different package, identify the affected test and document before accepting the change.
Keep commercial and technical approval together
The commercial approver should see the same model, revision, sample result, document set and support boundary as the technical reviewer. When those records separate, a low price can be accepted for a configuration the channel cannot maintain.
What to put in the decision record
- Selected model, revision and destination.
- Confirmed and excluded features.
- Sample and acceptance results.
- Documentation and compliance evidence required.
- Support, warranty, spare-parts and change-control owner.
- Commercial assumptions that must be revisited before repeat orders.
Keep the record short enough for a commercial review but specific enough for engineering and after-sales. It turns TCO into a release decision rather than a spreadsheet that no one owns.
Frequently asked questions
Is the lowest OEM access control price the best choice?
It can be for a stable, proven standard programme. It is not a complete comparison when branding, firmware changes, an app route, validation, documentation, spares or support are also required, because those are operating costs.
What should an OEM quotation separate?
Standard supply, private-label changes, OEM engineering, ODM development, tests, documentation, samples, tooling and exclusions, each with a deliverable, acceptance event, owner and change trigger.
Are the 200, 500 and 1,000 unit figures fixed minimums?
No. They are planning points on the J-BSS OEM supplier page for standard supply, OEM or private-label work and deeper ODM development. The written quote for the selected model and configuration governs.
What events should reopen testing or cost?
A change to the lock body or radio module, a new language or destination label, an API or app-account change, a revised power adapter or a new installer route. Name the retest, document update and owner for each.
What should a repeat order reference?
The approved sample, model, revision and release record, so the order does not reopen every assumption by email. Check that the app account, firmware, packaging, certification evidence, spares and support route are unchanged.
Who should sign off an OEM programme?
Both the commercial and technical owners should sign the same scope: supplied model, revision, evidence, support boundary and the change trigger for the repeat order.
Turn the guide into a project brief
Share the selected model, site conditions, interfaces and destination market so the next review stays within a written scope.
Request a project reviewEditorial review: Updated 25 October 2026 for search intent, scope and project usefulness.