Confirm the Exact Sample Being Evaluated
Identify the exact sample: model, configuration, finish, lock body, App or platform where applicable, accessories, packaging, manual, date, reference and approved customization.
Similar-looking samples may use different internal, lock-body, platform or accessory configurations. Keep each result attached to the recorded combination.
Photograph the relevant labels and included items so the tested configuration remains identifiable.
Prepare the Door and Installation Condition
Record the door material, finished thickness, opening, lock body, frame, strike, openings, clearance and restrictions. Confirm which door represents the project.
A successful fit validates only that combination. Review relevant door variations separately.
Use the detailed door and installation compatibility checklist before fitting the sample.
Inspect the Sample Before Installation
Check the delivered sample and its contents before installation begins:
- Model, configuration and label match
- Colour, finish and visible consistency
- Scratches, dents, gaps or visible damage
- Front and rear panel condition
- Handle movement before fitting
- Buttons, sensors and visible components
- Accessible cables and connectors without disassembly
- Lock body and faceplate
- Screws, spindles and installation accessories
- Mechanical keys where included
- Cards or other credentials where included
- Batteries, battery pack or power accessories where included
- Packaging protection
- Manual and accessory list
Review Installation and Mechanical Operation
Installation evaluation should use the representative door and the approved product and lock-body configuration. Where applicable, review:
Any cutting, drilling or structural change must follow the approved installation plan, be reviewed by a qualified local installer and comply with the door manufacturer’s and project requirements. This checklist does not provide universal drilling measurements.
Test Every Included Access Method
Test only the access methods included in the approved sample. Depending on the model and configuration, these may include fingerprint, password, card, mechanical key, mobile App, face recognition, palm-vein recognition, remote access, temporary credentials or another approved method.
These are evaluation categories, not functions included in every SUPTER model.
For each included method, review:
- Enrolment or creation
- Normal authorized use
- Deletion or revocation
- Invalid-attempt handling
- Repeated normal operation
- User instructions and administrator recovery
Do not apply universal speed, accuracy or capacity expectations. Record the configured function and result.
Evaluate the App, Account and Gateway Where Applicable
For a configuration that includes an App, account or gateway, review the practical setup and management process:
Available functions depend on the exact model, platform, configuration, account arrangement and gateway. Confirm the approved setup before the sample test; do not assume universal regional availability, gateway compatibility, cloud service, API access or App branding.
Compare the platform and account questions in the Tuya vs TTLock distributor guide.
Review Power, Battery and Recovery Behaviour
Use the power arrangement included in the approved sample. Where applicable, evaluate:
Repeat Normal Operations and Simulate Daily Use
Repeat ordinary, non-destructive operations to identify inconsistent behaviour that one successful action may not reveal:
- Multiple normal unlock and lock cycles
- Different authorized users
- Inside and outside operation
- Normal door closing
- Repeated handle movement
- App reconnection where applicable
- Temporary credentials where applicable
- Normal battery removal and replacement where appropriate
- Reset and reconfiguration only when included in the approved evaluation
Use a cycle count suitable for the agreed sample plan rather than presenting one number as universal. Where risk or project scale justifies it, compare more than one sample and record whether the same result is repeated.
Routine sample evaluation is not laboratory certification. Formal endurance testing requires a separately defined method, acceptance standard, equipment and reporting process.
Review Packaging, Labelling and Product Identification
Check whether the sample and its presentation can be identified and supported through the intended channel. Review where provided:
Check Manuals and Documentation
The manual and support materials should match the approved product and configuration. Where applicable, check that they explain:
- Installation preparation
- App setup
- Account creation
- User enrolment
- Included access methods
- Reset
- Battery replacement or charging
- Mechanical access
- Gateway setup
- Troubleshooting
- Model identification
- Support contact and included accessories
Do not assume one generic manual is sufficient for every model or configuration. Manual review can identify clarity and consistency issues, but it does not by itself establish legal or regulatory compliance.
Define the After-Sales and Replacement Workflow
Before sample approval, confirm how the exact version will be identified and supported:
- Model and configuration identification
- Information needed when reporting a problem
- Useful photos or short videos
- Reset and troubleshooting boundaries
- Separate accessory identification
- Matching replacement parts or units
- App account or device transfer where applicable
- Packaging and documentation version tracking
- Communication with the end user, installer or distributor
The review should identify responsibilities and evidence, not promise unrestricted spare parts, free replacement, fixed service times, local installation or local consumer support in every market.
Record Results Consistently
Use one evaluation record for the exact sample and configuration. Include:
Use “not applicable” when a function is not included in the approved configuration; do not treat its absence as a failed test.
A conditional pass must state the condition that remains to be confirmed, the responsible party and whether a new check is required before final approval.
Sample Evaluation Record
Adapt this record to the approved configuration and protect credentials and personal data.
| Evaluation Area | What to Check | Evidence to Record | Result Options | Configuration-Dependent? |
|---|---|---|---|---|
| Sample identity | Model, configuration, finish and version. | Labels, reference and date. | Pass / conditional / fail | Yes |
| Physical condition | Panels, finish, handle and damage. | Photos and notes. | Pass / conditional / fail | Yes |
| Door and lock-body fit | Openings, clearance and alignment. | Measurements and installed views. | Pass / conditional / fail | Door-dependent |
| Mechanical operation | Handle, latch, bolt and closing. | Observed result. | Pass / conditional / fail | Yes |
| Access methods | Enrolment, use, deletion and recovery. | Record by method. | Pass / conditional / fail / N/A | Yes |
| App and accounts | Registration, pairing, roles and users. | Notes without credentials. | Pass / conditional / fail / N/A | Platform-dependent |
| Gateway and remote use | Approved setup and functions. | Configuration and result. | Pass / conditional / fail / N/A | Platform-dependent |
| Power and recovery | Indication, replacement, reset and recovery. | Condition and result. | Pass / conditional / fail / N/A | Yes |
| Packaging and labels | Protection, identification and accessories. | Approved or redacted photos. | Pass / conditional / fail | Channel-dependent |
| Documentation | Correct version, setup and troubleshooting. | Version and notes. | Pass / conditional / fail | Yes |
| After-sales workflow | Evidence, responsibilities and replacement. | Process and actions. | Pass / conditional / fail | Project-dependent |
| Final approval | Open items resolved or recorded. | Review and retest references. | Approve / hold | Yes |
Common Sample-Evaluation Mistakes
Avoid these incomplete conclusions:
- Testing appearance only
- Not recording the configuration
- Using a non-representative door
- Testing one access method
- Assuming connected functions match across versions
- Ignoring reset and recovery
- Overlooking packaging or documents
- Not recording accessories
- Approving branding before product fit
- Relying on one operation
- Treating a sample as certification or production proof
- Not recording conditional retests
What to Send When Reporting a Sample Issue
Provide enough evidence to identify the sample and reproduce the condition without disclosing unnecessary private information:
How SUPTER Supports Sample Evaluation
SUPTER is a China-based smart lock OEM and ODM partner. Within the approved project scope, SUPTER can organize:
SUPTER’s support does not replace approval by a local installer, laboratory testing, regulatory review or confirmation of door compatibility, and it does not constitute universal approval of the product.
Final Sample-Approval Framework
Use one review sequence:
- 01
Record the sample
Identify configuration and included items.
- 02
Confirm the door
Document conditions and restrictions.
- 03
Test included functions
Review mechanical and electronic methods.
- 04
Review connected functions
Check App, accounts and gateway where applicable.
- 05
Review the complete product offer
Review packaging, labels, manuals and accessories.
- 06
Classify results
Record failed, conditional and N/A items.
- 07
Retest corrections
Repeat checks and attach evidence.
- 08
Confirm the order
Finalize after completing the record.
A documented evaluation supports the decision without guaranteeing every door, environment or future unit.
Frequently Asked Questions
Is one successful unlock enough to approve a sample?
No. Review the configuration, door, included functions, repeatability, documentation, packaging and support process.
Should every possible function be tested?
Test every included function. Mark excluded functions as not applicable.
Can one sample confirm compatibility for an entire project?
Only when relevant door conditions are equivalent. Review representative variations separately.
What should be tested in the App?
Where applicable, review registration, pairing, roles, users, credentials, records, remote functions, reset and transfer.
What is a conditional pass?
It records a condition that must be confirmed, corrected or retested before approval.
When should branding and packaging be approved?
Confirm final artwork, labels and documents after product and configuration issues are resolved.
