Contracting and manufacturing entities
Legal name, site, brand owner, design owner, certificate holder, exporter and related trading companies.
Supplier due diligence
Smart Lock Factory Audit Checklist for Distributors
Assess the legal manufacturer, production site and exact product family offered in the quotation. The audit should establish whether the approved configuration can be reproduced, traced through production, protected from uncontrolled changes and supported after shipment.
10control areas
5verification exercises
3finding states
Audit objective
Verify the supply chain behind the approved sample.
Showroom quality and sample performance do not establish production control. Review records from the actual site and test whether they identify the material, firmware, operator, inspection result and release status of a finished unit.
What should a distributor verify first? Confirm the contracting entity, factory address, manufacturing responsibility and ownership of the product design, tooling and firmware. Where the quotation issuer, factory, exporter, brand owner or certificate holder differ, document the legal and operational relationship between them.
Operations performed on site
Incoming inspection, assembly, programming, functional test, ageing, packing and final release.
Configuration and change control
Approved BOM, firmware baseline, serial or batch traceability, deviation approval and corrective action.
Ten-part checklist
Collect evidence against the offered product and programme.
Record the document name, revision, date, owner and closing action. “Available” is not an audit result until the evidence is reviewed.
Company and site identity
Business registration, factory address, organization chart, manufacturing responsibility, certificate holder and export entity.
Product ownership
Design owner, tooling owner, firmware owner, third-party modules, licensing dependencies and permitted branding scope.
Incoming quality control
Supplier list, inspection criteria, sampling plan, rejected-material control and records for motors, PCBs, sensors, batteries and mechanical parts.
Production controls
Work instructions, fixture calibration, operator training, torque or assembly checks, programming stations and line clearance between models.
Traceability
Serial or batch structure, BOM revision, firmware version, production date, inspection result and ability to isolate affected stock.
Reliability validation
Cycle, environmental, battery, communication and abuse tests relevant to the intended model; sample size, method and pass criteria.
Firmware and app control
Release approval, signing, rollback, OTA ownership, vulnerability handling, cloud dependency, user-data route and end-of-support process.
Non-conformance handling
Segregation, root-cause method, corrective action, effectiveness check, concession approval and customer notification.
Capacity and subcontracting
Demonstrated output, current loading, bottlenecks, surge plan and disclosure of outsourced assembly, finishing, testing or software services.
Field support and closure
DOA and RMA workflow, diagnostic inputs, spare-parts route, firmware escalation, responsibility matrix and reporting cadence.
Disqualification ruleDo not use a total score to hide a critical gap. Unclear product ownership, missing traceability, uncontrolled firmware or a certificate that does not identify the quoted configuration should remain a blocking issue until evidence closes it.
Verification exercises
Test the records instead of reviewing them in isolation.
Select samples during the audit and follow them through the supplier's own records. The purpose is to confirm that the control system works in practice, not only that a procedure exists.
| Exercise | Audit method | Expected evidence |
|---|---|---|
| Backward trace | Select a packed unit and trace its serial or batch to BOM, firmware, production date and final test | Records agree without manual reconstruction |
| Forward trace | Select a controlled incoming lot and identify the finished stock or work orders that consumed it | Affected quantity and location can be isolated |
| Configuration check | Compare the approved sample and quotation with the current BOM, drawings, firmware and packaging | Differences have formal approval and an effective date |
| Firmware release | Review one recent release from change request through build, test, approval and deployment | Version, target hardware, approver and rollback position are recorded |
| Corrective action | Review one closed production or field issue and challenge the root cause and effectiveness check | Containment, permanent action and recurrence evidence are linked |
Evidence register
Record findings so another reviewer can reproduce the decision.
Each conclusion should identify its scope, source and effect on sample approval, quotation, pilot build or production release.
| Field | Record | Insufficient wording |
|---|---|---|
| Scope | Site, line, product family, model and process observed | “Factory audited” with no stated boundary |
| Evidence | Document or record name, revision, date and owner | Unreferenced photos or verbal assurance |
| Status | Confirmed, open or excluded | Pass/fail before the closing evidence is available |
| Action | Required evidence, responsible party and review date | “Supplier to improve” without a closure condition |
| Release effect | Sample, quotation, pilot or production decision affected | Finding recorded without a procurement consequence |
Channel evidence cluster
Continue the distributor review.
Use each page for one decision. The distributor programme is the hub; the supporting resources provide the evidence route.
Supplier qualification
Request evidence against a defined model and market.
Provide the destination market, customer segment, product configuration, forecast range and required documents. We can then identify the applicable factory records, outstanding evidence and validation work before a commercial decision.