Smart Lock Factory Audit China — An On-Site Walkthrough Playbook for B2B Buyers
A China smart lock factory audit is a structured on-site walkthrough — pre-visit paperwork, gate-in protocol, workshop tour, laboratory verification, sample-room walkthrough, document hand-back, and post-visit scoring — where each area the buyer enters produces a named deliverable the buyer signs before leaving that area. The audit is not a factory tour with a translator, not a brochure handoff over dinner, and not a single photograph of the reception desk. It is the discipline of pushing a documented catalog — 79 published models across 10 categories (Smart Door Locks 77, Fingerprint 37, Hotel 24, Keypad 18, Outdoor 10, RFID 9, Face Recognition 6, Cabinet 6, Video Camera 3, Glass 3) — across the buyer's eyes, the buyer's hands, and the buyer's documentation so the order that follows the audit rests on named artefacts rather than conversational reassurance.
How this playbook is positioned beside the sourcing flow
This article is written as an SOP / playbook. It reads like an operations manual a procurement manager can hand to a new buyer the week before a factory visit and a quality manager can pick up the morning of. It is deliberately distinct from the broader sourcing hub at How to Source Smart Locks From China (the four-stage sourcing flow this audit slots into as Stage-3 production verification), the supplier-paperwork discipline at Smart Lock Supplier Verification China (the paperwork-side sibling the pre-visit step of this audit consumes), and the factory-evaluation discipline at Smart Lock Factory Verification China (the off-site evidence-gathering sibling this on-site audit complements).
The scope boundary that governs every per-model line
One honest boundary on scope before the protocols begin. Every per-model capability invoked below — door-thickness envelope, credential modalities supported, RFID frequency, battery count and chemistry, audit-event buffer depth, body-material grade, finish options, environmental rating, software lane (TTLock / Tuya / Doodle / hotel PC software) — is check the model’s published specification for the exact SKU in scope. This article invokes the SLK-9936S hotel smart door lock's published "Door thickness 36–100 mm · RFID Mifare 1 @ 13.56 MHz · read distance 0–5 cm · read time <0.25 s · power 4 × AA · battery operating cycles >15,000 · audit/event records up to 1,000 · 5-pin cylinder · 3-point latch · stainless steel + alloy body · multiple finish options · mechanical emergency access · multilingual management software · standalone or centralized database modes · positioned for 1–5 star hotels" spec block exactly once per cited line, and only as a documentation-granularity yardstick scoped to that single hotel SKU.
Nothing in those lines is asserted as a portable specification for the SLK-9936G variant, the SLK-9905A hidden-reader variant, the SLK-9951TH, the SLK-9962S, the SLK-G200 glass-door variant, the SLK-8831 5-in-1, the SLK-1104-class narrow-edge line, the SLK-3108 cylindrical Tuya round-code, the 3D-face remote-intercom model, the outdoor D11 / D12 / D15 / ODS / DQ series, the face 9L5-R / Q7 / Future 1 family, the 516 cat-eye / Q7 intercom / 4G line, the cabinet 6-model family, or the RFTC/RF card-and-code legacy roster (118 / 118E / 228 / 230 / 232 / 238 / 239 / 253 / 305 / 306 / 308 / 309 / 502 / 620 / 621 / 911 / 002 / 019 / 022 / 2020 / 760, with stainless 019 / 022 / 309 noted as a class).
The 79-model catalog's documented unlock-method families span fingerprint, passcode, RFID/IC card, mechanical key, app/Bluetooth (TTLock / Tuya / Doodle), remote control, 3D face (on a few models), hotel PC software, camera/cat-eye, and 4G models. The audit's job is verified in writing what the product page publishes per SKU and to push named documents across the buyer's desk, not to inherit brochure phrases.
The seven audit stages and how they interconnect
The seven audit stages are not all sequential and not all parallel. They run in a fixed sequence the first time the buyer enters the factory (pre-visit → gate-in → workshop → lab → sample-room → documents → scoring), and they re-enter the buyer's file in a fixed sequence the week after (scoring → decisions → next audit). Each stage produces a named deliverable the buyer signs before the next stage opens, and the whole spine sits inside an IF/THEN decision grammar the buyer carries out of the factory in a single binder.
| # | Stage | Single-sentence definition | Primary deliverable | Buyer sign-off |
|---|---|---|---|---|
| 1 | Pre-visit paperwork | The discipline that decides what documents are requested, what samples are reserved, and what questions are queued before the buyer boards the flight | Audit question list + sample reservation note | Buyer pre-visit checklist ticked |
| 2 | Gate-in protocol | The discipline that decides what happens in the first ten minutes on site — reception, NDA, escort, security badge, photo policy | Signed NDA + escort assignment | Buyer acknowledges gate-in card |
| 3 | Workshop walkthrough | The discipline that decides which production lines the buyer enters, in what order, and what each station must demonstrate | Per-station observation note | Buyer signs workshop card |
| 4 | Laboratory verification | The discipline that decides which test rigs the buyer watches run, which tests are demonstrated live, and which results are handed over as documents | Test log + witnessed-test photo set | Buyer signs lab card |
| 5 | Sample-room walkthrough | The discipline that decides which catalog SKUs are physically pulled, opened, and inspected, and which are reserved for inbound QA | Sample inspection note + reserved-sample list | Buyer signs sample-room card |
| 6 | Document hand-back | The discipline that decides which factory documents leave with the buyer that day, which arrive by email within 72 hours, and which are held in escrow pending the trial order | Document manifest + delivery method per line | Buyer signs manifest |
| 7 | Post-visit scoring | The discipline that decides how the seven stages are scored against the buyer's pre-set criteria, what exceptions trigger re-audit, and what the next audit looks like | Audit scorecard + exception list + next-audit plan | Buyer files scorecard with procurement |
Three boundary rules fall out of the table immediately. Rule 0-A: every stage produces a signed deliverable before the next stage opens. A workshop walkthrough that ends with a verbal "looks good" is a workshop walkthrough that produced no deliverable; a buyer who leaves the workshop without a signed card has no defence if the order that follows arrives with a defect the buyer could have caught on site. Rule 0-B: the seven stages do not overlap, and a signed answer to one does not satisfy another. "I saw the production line" does not satisfy "I saw the test rig"; "I saw the test rig" does not satisfy "I saw the open sample"; "I saw the open sample" does not satisfy "I have the document". Rule 0-C: a stage that depends on a capability not on the product page is a stage you cannot score. Check the model’s published specification whether your chosen SKU carries the documented door-thickness envelope, the documented credential modalities, the documented RFID frequency, the documented battery count, the documented audit-event buffer depth, the documented body-material grade, the documented finish options, and the documented software lane before you publish a single line of any audit card as a per-model behaviour.
Read as an object model, the playbook is small: the audit owns stages, each stage owes one deliverable, and only what is signed gets scored — while the product page stays outside the audit, answering the capability question every card must settle first.
classDiagram
class Buyer["Buyer"]
note for Buyer "quality manager escort · sign-off authority"
class FactoryAudit["Factory Audit"]
note for FactoryAudit "IF THEN decision grammar"
class Stage["Stage"]
note for Stage "area entered on site · five-question framework · signed stage card"
class Deliverable["Deliverable"]
note for Deliverable "witnessed test log"
class Scorecard["Scorecard"]
note for Scorecard "grade band total"
class Exception["Exception"]
note for Exception "re-audit trigger"
class ProductPage["Product Page"]
note for ProductPage "per SKU figures · confirm before scoring"
class InboundQA["Inbound QA"]
note for InboundQA "trial order check"
Buyer --> FactoryAudit : runs the visit
FactoryAudit *-- Stage : one stage per area entered
Stage --> Deliverable : produced before the next stage opens
Deliverable --> Scorecard : the only input scoring reads
Scorecard --> Exception : grade band routes the verdict
Stage ..> ProductPage : capability settled before any card is published
Deliverable --> InboundQA : reserved samples carry forward
Exception --> FactoryAudit : re-audit returns to pre-visit
Stage 1 — Pre-visit paperwork
The pre-visit stage is a desk exercise the buyer runs two to four weeks before the factory visit. The buyer emails the supplier a single packet: the audit question list, the sample reservation note, the NDA template, the photo-policy one-pager, and the schedule request. The supplier's reply — what arrives in 48 to 72 hours, what arrives after a week, what never arrives — is itself the first piece of evidence the buyer scores. A supplier who returns the question list inside 48 hours with line-by-line answers is signalling one operating posture; a supplier who returns it after ten days with a single PDF attachment is signalling another.
1.1 Audit question list
The audit question list is the spine of the audit. It is the same list of questions every supplier answers, in the same order, with the same depth of answer. The buyer does not improvise questions on site; the buyer reads from the list and ticks answers as they come. The list covers business registration, factory footprint, production-line layout, component sourcing, test-rig inventory, sample inventory, document hand-back policy, and after-sales posture.
1.2 Sample reservation note
The sample reservation note names the exact SKUs the buyer wants physically pulled, opened, and inspected on site. The note lists every SKU by its product-page slug (for example /products/rfid-hotel-card-door-lock-satin-finish, /products/rfid-hotel-lock-with-hidden-card-reader, /products/rfid-hotel-electronic-door-lock, /products/rfid-hotel-electronic-door-lock-with-slim-handle, /products/smart-lock-for-frameless-glass-doors, 5-in-1-digital-door-lock-with-fingerprint-password-card-key-and-app-slk-8831, narrow-edge-door-lock-4-in-1-electronic-smart-door-lock-with-waterproof-door-lock, /products/factory-keypad-smart-door-lock, cylindrical-latch-grip-to-open-tuya-round-code-smart-door-lock, 3d-face-recognition-finger-smart-lock-remote-intercom-smart-lock), specifies whether the buyer wants a finished-good sample or a sub-assembly sample, and asks the supplier to verify in writing availability. A supplier who cannot reserve the named SKUs within a week is signalling inventory discipline the buyer needs to know about before the visit.
1.3 NDA template
The NDA template is sent ahead of the visit. It is the document that decides what photographs the buyer may take, what specifications the buyer may write down, and what the buyer may share with downstream stakeholders. The NDA should be mutual, time-bounded, and explicit about photographs of finished goods (typically yes), photographs of production lines (typically yes with redaction of operator faces), photographs of test rigs (typically yes), photographs of component brand markings (typically no without the supplier's written consent), and photographs of sub-contractor markings (typically no).
1.4 Photo-policy one-pager
The photo-policy one-pager restates the NDA in operational terms. It tells the buyer's escort which shots are permitted, which require written consent, and which are flatly prohibited. The buyer carries this one-pager on the day and references it every time a camera comes out.
1.5 Schedule request
The schedule request proposes the seven-stage sequence with time budgets per stage: pre-visit paperwork (off-site, two to four weeks), gate-in protocol (on-site, thirty minutes), workshop walkthrough (on-site, ninety to one hundred twenty minutes), laboratory verification (on-site, sixty to ninety minutes), sample-room walkthrough (on-site, sixty minutes), document hand-back (on-site, thirty minutes), post-visit scoring (off-site, three to five days). A supplier who cannot fit a one-day visit into these time budgets is signalling floor-layout discipline the buyer needs to know about before the visit.
| Pre-visit packet item | Buyer-side responsible | Supplier-side answer window | What the answer signals |
|---|---|---|---|
| Audit question list | Procurement manager | 48–72 hours | Communication discipline |
| Sample reservation note | Quality manager | 5–7 days | Inventory discipline |
| NDA template | Legal counsel | 7–14 days | Legal readiness |
| Photo-policy one-pager | Quality manager | 7–14 days | Operational transparency |
| Schedule request | Procurement manager | 5–7 days | Floor-layout discipline |
Stage 2 — Gate-in protocol
The gate-in protocol is the first ten minutes on site. It is the smallest stage in time and the largest in consequence, because everything the buyer learns in the next six stages is filtered through the relationship the buyer establishes in the first ten minutes. The protocol runs in five steps: reception sign-in, NDA execution, escort assignment, security badge issue, photo-policy read-back.
2.1 Reception sign-in
The reception sign-in records the buyer's name, the buyer's organisation, the buyer's government ID number, the date and time of arrival, and the buyer's escort's name. The buyer keeps a copy. A supplier whose reception asks for the buyer's passport number, retains the passport photocopy, or refuses to issue a visitor pass is signalling a gate-discipline posture the buyer needs to record.
2.2 NDA execution
The NDA execution is the moment the buyer and the supplier countersign the NDA template sent in Stage 1. The buyer reads the document on site, negotiates any clause that does not match the buyer's home-jurisdiction standard, and countersigns. A supplier who refuses to countersign an NDA on the day of the visit — or who substitutes a one-paragraph "we keep your visit confidential" letter for the negotiated document — is signalling a documentation-discipline posture the buyer needs to record.
2.3 Escort assignment
The escort assignment names the supplier's representative who will accompany the buyer through Stages 3 to 6. The escort is the buyer's translator, the buyer's route-finder, and the buyer's first line of question-answering on the floor. A supplier who assigns a sales account manager as the escort — rather than a production manager, a quality manager, or a technical lead — is signalling a question-handling posture the buyer needs to record. The escort's role is to answer production questions, not to deflect them.
2.4 Security badge issue
The security badge issue is the moment the supplier hands the buyer a visitor badge that names the buyer, the visit window, and the areas the buyer is authorised to enter. The badge is the buyer's permission slip for the floor. A supplier whose badge restricts the buyer to reception and the sample room — rather than the workshop, the laboratory, and the warehouse — is signalling an access-discipline posture the buyer needs to record.
2.5 Photo-policy read-back
The photo-policy read-back is the moment the escort reads the photo-policy one-pager aloud to the buyer and the buyer reads it back. Both parties acknowledge in writing. A supplier whose photo policy changes between the pre-visit packet and the on-site read-back is signalling a discipline-shift the buyer needs to record.
| Gate-in step | Time budget | Buyer-side artefact | What it records |
|---|---|---|---|
| Reception sign-in | 5 minutes | Visitor-pass photocopy | Gate discipline |
| NDA execution | 10 minutes | Countersigned NDA | Legal readiness |
| Escort assignment | 5 minutes | Escort-name card | Question-handling posture |
| Security badge issue | 5 minutes | Visitor badge | Access discipline |
| Photo-policy read-back | 5 minutes | Countersigned photo-policy | Discipline shift between packet and on-site |
Stage 3 — Workshop walkthrough
The workshop walkthrough is the longest stage on site. The buyer enters the production floor with the escort, walks the lines in the order the buyer pre-declared, and observes each station with the same five-question framework. The five questions are: what is this station producing, what is the cycle time, what is the rejection rate, who is the operator, and what documents back this station's output. The buyer does not touch the line; the buyer watches, asks, and writes.
3.1 Line order
The line order the buyer walks is the order the buyer pre-declared in the schedule request. A typical order for a hotel-line and residential-line audit runs: incoming-component inspection → SMT or through-hole PCB assembly → PCB test → lock-body machining or casting → mechanical sub-assembly → electronics sub-assembly → final assembly → firmware flash → functional test → cosmetic inspection → boxing. The buyer does not skip a station. The buyer does not accept "we'll show you the highlights." The buyer walks every station in the declared order.
3.2 SMT and PCB assembly station
The SMT and PCB assembly station is where the bare PCB becomes a populated board. The buyer observes the pick-and-place machine, the reflow oven, the wave-solder or selective-solder station, and the AOI or X-ray inspection rig. The buyer asks: what is the line's daily throughput in boards, what is the rejection rate at AOI, what is the rework loop, and what lot-code system is on each board. The buyer writes down the line's stated throughput in boards per shift. The buyer does not accept a brochure number; the buyer asks for the line's last-month throughput log.
3.3 Lock-body machining or casting station
The lock-body machining or casting station is where the lock body — stainless steel, zinc alloy, or aluminium — is shaped. The buyer observes the CNC lathe, the milling machine, the casting cell (if applicable), and the post-machining deburring station. The buyer asks: what alloys are in stock, what is the surface-finish vocabulary the factory can produce (brushed stainless, coffee-black, gold, copper, electrophoretic coating, anti-fingerprint coating, etc. — check the model’s published specification for the SKU in scope), and what is the cosmetic-rejection rate at the post-machining station.
3.4 Mechanical sub-assembly station
The mechanical sub-assembly station is where the lock body, the latch or mortise, the cylinder, and the handle come together. The buyer observes the assembly bench, the torque-driver station, and the dimensional-check jig. The buyer asks: what is the documented dimensional envelope per SKU (the SLK-9936S hotel smart door lock publishes a 36–100 mm door-thickness envelope and a 5-pin cylinder with a 3-point latch — check the model’s published specification for any other SKU in scope), what is the assembly cycle time, and what is the rejection rate at the dimensional-check jig.
3.5 Electronics sub-assembly station
The electronics sub-assembly station is where the populated PCB, the antenna (for RFID and Bluetooth), the battery contacts, the motor, and the cable harness come together. The buyer asks: what is the battery count and chemistry per SKU (the SLK-9936S publishes 4 × AA — check the model’s published specification for any other SKU in scope), what is the antenna's published credential-read performance (the SLK-9936S publishes RFID Mifare 1 @ 13.56 MHz with read distance 0–5 cm and read time <0.25 s — check the model’s published specification for any other SKU in scope), and what is the rejection rate at the sub-assembly electrical test.
3.6 Final assembly and firmware-flash station
The final assembly and firmware-flash station is where the lock becomes a finished good. The buyer observes the firmware programmer, the version-control check, and the final-assembly bench. The buyer asks: what firmware version is current, what is the version-control system, what is the rejection rate at firmware flash, and what is the procedure if a flashed unit fails the post-flash test.
3.7 Functional test station
The functional test station is where the finished lock is operated end-to-end before boxing. The buyer asks: what is the test coverage (RFID read at the antenna, fingerprint enrolment and match, keypad entry, mechanical-key override, app/Bluetooth pairing if applicable — TTLock / Tuya / Doodle — check the model’s published specification for the SKU in scope), what is the rejection rate at functional test, and what is the rework loop for a failed unit.
3.8 Cosmetic inspection and boxing station
The cosmetic inspection and boxing station is the last gate before warehousing. The buyer observes the inspection bench, the packaging line, and the lot-coding system. The buyer asks: what is the cosmetic-rejection rate per SKU, what is the lot-code schema, and what is the inner-carton and outer-carton specification.
| Workshop station | Five-question target | Buyer-side artefact |
|---|---|---|
| SMT and PCB assembly | Throughput, AOI rejection, rework loop, lot code | Per-station observation note |
| Lock-body machining or casting | Alloy vocabulary, finish vocabulary, post-mach rejection | Per-station observation note |
| Mechanical sub-assembly | Dimensional envelope, cycle time, jig rejection | Per-station observation note |
| Electronics sub-assembly | Battery count, antenna performance, electrical-test rejection | Per-station observation note |
| Final assembly and firmware flash | Firmware version, version control, flash rejection | Per-station observation note |
| Functional test | Test coverage, rejection, rework loop | Per-station observation note |
| Cosmetic inspection and boxing | Cosmetic rejection, lot code, carton spec | Per-station observation note |
Stage 4 — Laboratory verification
The laboratory verification is the second-longest stage on site. The buyer enters the test lab with the escort, observes the test rigs, watches at least one test run live, and collects the test logs. The lab is where the buyer's per-SKU capability worksheet meets the factory's test capability; the buyer does not accept a brochure, the buyer watches the rig run.
4.1 Test-rig inventory
The test-rig inventory is the list of rigs the lab operates. The buyer asks: which environmental chambers (temperature, humidity), which salt-spray chambers, which cycle testers (motor, lock bolt, latch, handle), which drop testers, which water-ingress testers, which RFID credential testers, which fingerprint enrolment testers, which Bluetooth pairing testers. The buyer writes down each rig's make, model, and calibration date.
4.2 Live test run
The live test run is the moment the supplier runs one of the named tests on a buyer-supplied sample or a factory sample in front of the buyer. A salt-spray test cannot run live (it takes days), so the buyer accepts a running test plus the test log. A cycle test cannot run live (it takes hours), so the buyer accepts a running test plus the test log. A drop test, a water-ingress test, an RFID read test, a fingerprint enrolment test, and a Bluetooth pairing test can run live; the buyer asks for the live run on at least one of these.
4.3 Test log hand-back
The test log hand-back is the moment the lab supervisor hands the buyer the test log for the SKU in scope. The log should name the test standard (or the factory's internal standard), the test parameters, the sample size, the pass criteria, the actual results, and the date. A supplier who refuses to hand over the test log — or who hands over a one-page summary in lieu of the full log — is signalling a documentation-discipline posture the buyer needs to record.
4.4 Calibration discipline
The calibration discipline is the moment the buyer asks for the calibration certificates of the named test rigs. A rig without a current calibration certificate is a rig whose results the buyer cannot rely on. The buyer writes down the calibration dates and the next-calibration dates for every rig the buyer observed.
| Lab artefact | Buyer-side question | What the answer signals |
|---|---|---|
| Test-rig inventory | Make, model, calibration date | Test-rig discipline |
| Live test run | Which test ran, on which sample, with which parameters | Test-rig capability |
| Test log hand-back | Standard, parameters, sample size, results, date | Documentation discipline |
| Calibration discipline | Calibration date, next-calibration date | Result reliability |
Stage 5 — Sample-room walkthrough
The sample-room walkthrough is the stage where the buyer's desk-side model shortlist meets the factory's physical inventory. The buyer enters the sample room with the escort, the sample reservation note from Stage 1, and a calibrated calliper or ruler. The buyer pulls each named SKU off the shelf, opens the packaging, inspects the finish, and — where the buyer's NDA permits — photographs the unit. The buyer does not accept a showroom tour; the buyer opens the SKU.
5.1 Sample pull
The sample pull is the moment the supplier retrieves each named SKU from the sample room's inventory. The buyer ticks the SKU off the reservation note as it arrives. A SKU that is not on the shelf — or that the supplier must retrieve from the production floor — is a signal about sample inventory discipline.
5.2 Sample inspection
The sample inspection is the moment the buyer opens the packaging, inspects the finish, and inspects the mechanical fit. The buyer checks: is the finish consistent across the visible faces, are the fasteners torqued to a consistent feel, does the latch or mortise engage smoothly, does the mechanical-key override turn smoothly, does the cylinder sit centred in the body, does the antenna marking match the product page's credential family. The buyer writes down every defect observed.
5.3 Open-unit inspection
The open-unit inspection is the moment the buyer asks the supplier to open one or more samples for internal inspection. The buyer inspects the PCB, the antenna, the battery contacts, the motor, the cable harness, and the lot-code label. The buyer photographs (where the NDA permits) the lot-code label and the PCB. The buyer does not open the unit themselves; the buyer asks the supplier to open it. The buyer writes down the lot code, the PCB revision, and the firmware version observed on the open unit.
5.4 Reserved-sample list
The reserved-sample list is the list of SKUs the buyer asks the supplier to set aside for inbound QA on the buyer's dock. The list names the SKU, the quantity, the lot-code schema the buyer requires on the carton, and the delivery window. The list is a contract artefact, not a request.
| Sample-room step | Buyer-side artefact | What it records |
|---|---|---|
| Sample pull | Ticked reservation note | Sample inventory discipline |
| Sample inspection | Defect log per SKU | Cosmetic and mechanical consistency |
| Open-unit inspection | Lot code, PCB revision, firmware version | Internal consistency |
| Reserved-sample list | Reserved-sample manifest | Inbound QA preparation |
Stage 6 — Document hand-back
The document hand-back is the stage that converts what the buyer saw on site into what the buyer takes home. The buyer sits at a desk in the supplier's meeting room with the escort and the document manifest, and the two parties walk the manifest line by line. Each document is either handed over in hard copy that day, sent by email within 72 hours, or held in escrow pending the trial order.
6.1 Document manifest
The document manifest is the list of documents the buyer pre-declared in the audit question list. A typical manifest for a hotel-line and residential-line audit runs: business registration, export licence, factory footprint declaration, production-line layout, component vendor list (without brand names unless the supplier consents in writing), test-rig inventory with calibration dates, test logs for the SKUs in scope, sample inspection report, lot-code schema, inner-carton and outer-carton specification, after-sales service policy, and trial-order terms. The buyer and the supplier countersign the manifest.
6.2 Hard-copy hand-back
The hard-copy hand-back is the documents the buyer takes home in the bag that day. Typical hard-copy documents: business registration, export licence, the sample inspection report, the lot-code schema, the inner-carton and outer-carton specification, and the trial-order terms.
6.3 Email hand-back
The email hand-back is the documents the supplier sends within 72 hours of the visit. Typical email documents: production-line layout, component vendor list (if not handed over in hard copy), test logs for the SKUs in scope, and any document the supplier needs to redact or translate before sending.
6.4 Escrow hand-back
The escrow hand-back is the documents the supplier holds pending the trial order. Typical escrow documents: detailed component vendor list with brand names, detailed test-rig calibration certificates, detailed firmware version-control policy, and detailed after-sales service policy. Escrow documents are released on the buyer's written request after the trial order is signed.
| Document type | Delivery method | Delivery window |
|---|---|---|
| Business registration | Hard copy | Day of visit |
| Export licence | Hard copy | Day of visit |
| Sample inspection report | Hard copy | Day of visit |
| Lot-code schema | Hard copy | Day of visit |
| Carton specification | Hard copy | Day of visit |
| Trial-order terms | Hard copy | Day of visit |
| Production-line layout | Within 72 hours | |
| Component vendor list | Within 72 hours | |
| Test logs per SKU | Within 72 hours | |
| Detailed vendor list with brand names | Escrow | On written request post-trial-order |
| Detailed calibration certificates | Escrow | On written request post-trial-order |
| Firmware version-control policy | Escrow | On written request post-trial-order |
Stage 7 — Post-visit scoring
The post-visit scoring is the off-site stage that converts the seven stages of evidence into a single audit scorecard the procurement committee can act on. The buyer sits at a desk three to five days after the visit and scores each stage against the pre-set criteria, lists every exception, and writes the next-audit plan.
7.1 Audit scorecard
The audit scorecard is a single page with seven rows (one per stage) and four columns (criterion, observation, score, exception). The buyer scores each stage on a five-point scale (1 = critical failure, 2 = major gap, 3 = acceptable with caveat, 4 = acceptable, 5 = strong). The buyer writes the observation in one sentence and the exception — if any — in one sentence. The scorecard is the artefact the procurement committee signs.
| # | Stage | Criterion | Observation | Score | Exception |
|---|---|---|---|---|---|
| 1 | Pre-visit paperwork | Communication discipline | Audit list returned in 48 hours with line-by-line answers | 5 | None |
| 1 | Pre-visit paperwork | Communication discipline | Audit list returned after 10 days with single PDF | 2 | Re-audit pre-visit paperwork |
| 2 | Gate-in protocol | Legal readiness | NDA countersigned on day of visit | 4 | None |
| 2 | Gate-in protocol | Access discipline | Visitor badge restricts to reception only | 2 | Re-audit access scope |
| 3 | Workshop walkthrough | Production discipline | All declared stations walked, throughput logged | 4 | None |
| 3 | Workshop walkthrough | Production discipline | Supplier refused to walk SMT station | 1 | Reject supplier pending explanation |
| 4 | Laboratory verification | Test discipline | Live RFID test run witnessed, test log handed over | 5 | None |
| 4 | Laboratory verification | Test discipline | Test log withheld, calibration certificates out of date | 1 | Reject supplier pending re-audit |
| 5 | Sample-room walkthrough | Sample discipline | All reserved SKUs on shelf, open-unit inspection granted | 5 | None |
| 5 | Sample-room walkthrough | Sample discipline | Three of ten reserved SKUs not on shelf | 3 | Re-audit sample inventory |
| 6 | Document hand-back | Documentation discipline | Hard-copy, email, and escrow manifests signed | 4 | None |
| 6 | Document hand-back | Documentation discipline | Supplier refused to sign manifest | 1 | Reject supplier pending re-audit |
| 7 | Post-visit scoring | Audit discipline | Scorecard written within five days, exception list complete | 5 | None |
| 7 | Post-visit scoring | Audit discipline | Scorecard not written within ten days | 2 | Re-audit scorecard discipline |
7.2 Exception list
The exception list is the single page that names every exception from the scorecard, every action the supplier must take, and every action the buyer must take before the next stage opens. A typical exception list reads: "Stage 3 — supplier must submit production-line throughput log for last month by email within seven days; buyer must re-score Stage 3 on receipt." The exception list is signed by the buyer and the supplier.
7.3 Next-audit plan
The next-audit plan is the single page that names the date of the next audit, the stages that must be re-walked, and the buyer-side and supplier-side deliverables the next audit will score. A typical next-audit plan reads: "Next audit in ninety days; re-walk Stages 3, 4, and 5; supplier to deliver updated test logs and sample inventory; buyer to deliver inbound-QA results from trial order."
7.4 Decision matrix
The decision matrix is the single page that converts the scorecard into a procurement decision. The matrix has four rows: green (proceed to trial order), yellow (proceed to trial order with named exceptions), red (re-audit in ninety days), black (reject supplier). The matrix is signed by the buyer and the procurement committee.
| Scorecard total | Buyer-side decision | What it triggers |
|---|---|---|
| 28–35 (green) | Proceed to trial order | Draft purchase order, reserved-sample inbound QA |
| 21–27 (yellow) | Proceed to trial order with named exceptions | Exception list signed before PO |
| 14–20 (red) | Re-audit in ninety days | Next-audit plan signed |
| 7–13 (black) | Reject supplier | No further engagement |
IF/THEN decision rules for the audit
The IF/THEN decision rules are the grammar the buyer carries into the factory and back out. They convert observations into decisions in real time, on the floor, before the buyer leaves the station.
| IF the buyer observes | THEN the buyer records | BECAUSE |
|---|---|---|
| Audit list returned inside 72 hours with line-by-line answers | Stage 1 score 5 | Communication discipline is the first proxy for floor discipline |
| Audit list returned after ten days with single PDF | Stage 1 score 2 | Single-PDF answer signals a low-discipline communication posture |
| Visitor badge restricts buyer to reception only | Stage 2 score 2 | A buyer who cannot walk the floor cannot audit the floor |
| Escort is a sales account manager rather than a production or quality lead | Stage 2 score 3 | Sales-side escort signals a deflection-prone question posture |
| Supplier refuses to walk a declared station | Stage 3 score 1 | A station the supplier will not show is a station the buyer cannot score |
| Throughput stated as a brochure number rather than a log | Stage 3 score 3 | Brochure numbers are not auditable |
| Test rig without current calibration certificate | Stage 4 score 2 | Results from an uncalibrated rig are not reliable |
| Test log withheld or replaced with a one-page summary | Stage 4 score 1 | A summary in lieu of a log is a refusal to document |
| Reserved SKU not on shelf | Stage 5 score 3 | A SKU not on shelf signals inventory discipline gap |
| Supplier refuses to open a sample for internal inspection | Stage 5 score 2 | An unopenable sample cannot be lot-code-traced |
| Document manifest unsigned at end of visit | Stage 6 score 1 | An unsigned manifest is no manifest |
| Scorecard not written within five days | Stage 7 score 2 | Late scoring signals a buyer-side discipline gap |
Exception handling
Exception handling is the lane the buyer enters when the IF/THEN rules surface a gap. Three exceptions are routine; the rest are non-routine and trigger a re-audit.
Exception A — Reserved SKU not on shelf
A reserved SKU not on shelf is a Stage 5 score of 3. The buyer asks the supplier to retrieve the SKU from the production floor within thirty minutes. If the SKU arrives within thirty minutes and passes inspection, the buyer re-scores Stage 5 to 4. If the SKU does not arrive within thirty minutes, the buyer re-scores Stage 5 to 2 and triggers a Stage 5 re-audit on the next visit.
Exception B — Test rig uncalibrated
A test rig without a current calibration certificate is a Stage 4 score of 2. The buyer asks the lab supervisor for the next-calibration date. If the next-calibration date is within thirty days, the buyer accepts the rig and re-scores Stage 4 to 3. If the next-calibration date is past, the buyer rejects the rig and re-scores Stage 4 to 1; the buyer also flags the test log produced on that rig as unreliable.
Exception C — Document manifest unsigned
A document manifest unsigned at end of visit is a Stage 6 score of 1. The buyer asks the supplier to sign the manifest before the buyer leaves the building. If the supplier signs within fifteen minutes, the buyer re-scores Stage 6 to 4. If the supplier does not sign within fifteen minutes, the buyer re-scores Stage 6 to 1 and triggers a Stage 6 re-audit on the next visit.
Non-routine exception — Refusal to walk a declared station
A supplier who refuses to walk a declared station during Stage 3 is a Stage 3 score of 1 and triggers a black-grade decision on the scorecard. The buyer leaves the building without signing any document other than the visitor-pass photocopy, and the buyer files the refusal with the procurement committee. A supplier who refuses to walk a declared station on the second visit is a hard reject.
Non-routine exception — Refusal to open a sample
A supplier who refuses to open a sample for internal inspection during Stage 5 is a Stage 5 score of 2 and triggers a red-grade decision on the scorecard. The buyer files the refusal with the procurement committee and triggers a Stage 5 re-audit on the next visit.
Non-routine exception — Test log withheld
A supplier who withholds the test log during Stage 4 is a Stage 4 score of 1 and triggers a black-grade decision on the scorecard. The buyer files the refusal with the procurement committee and rejects the supplier.
Realistic project scenario — An illustrative 80-room boutique hotel audit walkthrough
Consider an 80-room boutique hotel group preparing a property in a coastal secondary city. The procurement manager arrives at the factory on a Monday morning with the seven-stage spine in a single binder: pre-visit paperwork completed the week before, NDA countersigned at the gate, escort assigned as a quality manager, visitor badge covering workshop, lab, and warehouse, photo policy read back.
The buyer walks the SMT line, the lock-body machining cell, the mechanical sub-assembly bench, the electronics sub-assembly bench, the final-assembly and firmware-flash station, the functional test station, and the cosmetic inspection bench — in that order, no station skipped, every station's five-question framework answered in writing.
The buyer then moves to the lab and witnesses a live RFID credential test on a sample pulled from the production floor, plus a running cycle test plus the calibration certificates of the environmental chamber and the cycle tester. The buyer then moves to the sample room and pulls the named SKU — an SLK-9936S-class hotel smart door lock or its confirmed catalog equivalent (check the model’s published specification for the exact SKU in scope) — opens the packaging, inspects the finish, asks the supplier to open the unit, photographs the lot-code label and the PCB revision, and reserves five samples for inbound QA.
The buyer finishes at the meeting-room desk, walks the document manifest line by line, and leaves the building with a signed manifest, a hard-copy packet, an email-followup commitment within 72 hours, and an escrow list pending the trial order. Three days later, the buyer scores Stage 1 at 5, Stage 2 at 4, Stage 3 at 4, Stage 4 at 5, Stage 5 at 5, Stage 6 at 4, and Stage 7 at 5 — a green total of 32 — and proceeds to the trial order with a reserved-sample inbound-QA plan. This is an illustrative scenario, not a customer story, and the per-SKU specifics are routed to the product page for the exact SKU in scope.
Buyer-side artefacts the audit produces
The audit produces six artefacts the buyer carries home. The artefacts are the spine of the post-audit file the procurement committee reads and the inbound-QA team references when the trial order arrives.
Artefact 1 — Audit scorecard
The audit scorecard is the single page with seven rows and four columns (criterion, observation, score, exception) signed by the buyer. The scorecard is the procurement committee's primary read.
Artefact 2 — Per-station observation note
The per-station observation note is the multi-page document with one page per workshop station, listing the five-question framework's answers and any defect observed. The observation note is the quality manager's primary read.
Artefact 3 — Live test log
The live test log is the test log the lab supervisor handed over during Stage 4, plus the calibration certificates of the rigs the buyer observed. The test log is the technical lead's primary read.
Artefact 4 — Sample inspection report
The sample inspection report is the document that lists every SKU inspected, every defect observed, the lot code, the PCB revision, the firmware version, and the reserved-sample list. The sample inspection report is the inbound-QA team's primary read.
Artefact 5 — Document manifest
The document manifest is the signed list of every document the buyer takes home — hard copy, email, or escrow — with delivery method per line. The manifest is the documentation-discipline audit's primary read.
Artefact 6 — Exception list and next-audit plan
The exception list and next-audit plan is the signed two-page document that names every exception, every action the supplier must take, every action the buyer must take, the date of the next audit, and the stages the next audit will re-walk. The exception list is the procurement committee's primary read for the exception lane.
| Artefact | Buyer-side owner | Primary reader | Shelf life |
|---|---|---|---|
| Audit scorecard | Procurement manager | Procurement committee | Until next audit |
| Per-station observation note | Quality manager | Quality manager | Until next audit |
| Live test log | Technical lead | Technical lead | Until next audit |
| Sample inspection report | Inbound-QA team lead | Inbound-QA team | Until next audit |
| Document manifest | Documentation lead | Procurement committee | Until next audit |
| Exception list and next-audit plan | Procurement manager | Procurement committee | Until next audit |
How the audit connects to the rest of the sourcing flow
The audit is Stage 3 of the four-stage sourcing flow described in How to Source Smart Locks From China. The four stages are model shortlisting (Stage 1), quantity and customization confirmation (Stage 2), production and pre-shipment verification (Stage 3 — the audit lives here), and shipping with post-arrival handoff (Stage 4). The audit's deliverables feed Stage 4's inbound-QA plan; the inbound-QA results feed Stage 7's next-audit plan on the next visit.
Connection to supplier verification
The audit's pre-visit paperwork (Stage 1) consumes the paperwork-side discipline described in Smart Lock Supplier Verification China. The audit question list is the same question list the supplier verification discipline runs against, with the audit adding the on-site verification steps. A supplier who passes the supplier verification paperwork but fails the on-site audit is a supplier the buyer places on a re-audit schedule.
Connection to factory verification
The audit's workshop walkthrough (Stage 3), laboratory verification (Stage 4), and sample-room walkthrough (Stage 5) complement the off-site evidence-gathering discipline described in Smart Lock Factory Verification China. The factory verification discipline runs on documents, public records, and third-party databases; the audit runs on the floor. A supplier who passes the factory verification off-site but fails the on-site audit is a supplier the buyer escalates to a third-party inspector.
Connection to the OEM/ODM process
The audit's reserved-sample list (Stage 5) and document manifest (Stage 6) feed the OEM/ODM process described at OEM/ODM page. A factory that passes the audit with a green scorecard and signs the OEM/ODM terms is a factory the buyer opens an OEM/ODM file with. A factory that passes the audit with a yellow scorecard signs the OEM/ODM terms only after the exception list is closed.
Connection to the quote request
The audit's scorecard (Stage 7) feeds the quote request at request a quote page. A factory that passes the audit with a green or yellow scorecard is a factory the buyer requests a quote from; a factory that fails the audit is a factory the buyer does not request a quote from. The quote request carries the audit scorecard as a procurement-side attachment.
Cost, MOQ, and lead time as audit outcomes
Cost, MOQ, and lead time are outcomes the audit prepares the buyer to receive via quote, not topics the audit decides. The audit's job is verified in writing that the factory can quote on the SKU the buyer shortlists, that the SKU's per-model capability sits on the product page, and that the SKU's lot-code schema is consistent with the buyer's inbound-QA plan. Specific cost figures, MOQ numbers, and lead-time windows are routed to the quote request at request a quote page, where the supplier returns line-item figures the buyer can compare across factories.
Cost factors the audit surfaces
The audit surfaces the cost factors without quoting numbers: alloy selection (stainless steel carries a different cost posture than zinc alloy — check the model’s published specification for the SKU in scope), finish vocabulary (brushed stainless, coffee-black, gold, copper, electrophoretic coating — check the model’s published specification), credential family (RFID Mifare 1 @ 13.56 MHz vs fingerprint sensor vs 3D face — check the model’s published specification), software lane (TTLock / Tuya / Doodle vs hotel PC software — check the model’s published specification), and packaging grade (inner-carton and outer-carton specification — observed during Stage 3 and recorded on the document manifest).
MOQ factors the audit surfaces
The audit surfaces the MOQ factors without quoting numbers: SKU mix (a buyer ordering across multiple categories — hotel, residential, outdoor, glass — faces a different MOQ posture than a buyer ordering within one category), customization depth (a buyer ordering a private-label SKU with custom firmware faces a different MOQ posture than a buyer ordering a catalog SKU — confirm on the private-label posture at private-label page), and packaging grade (a buyer ordering retail-ready packaging faces a different MOQ posture than a buyer ordering bulk-pack).
Lead-time factors the audit surfaces
The audit surfaces the lead-time factors without quoting windows: production-line load (observed during Stage 3 — a fully loaded line signals a longer lead time than a partially loaded line), component inventory (observed during Stage 3 and recorded on the document manifest), firmware freeze date (observed during Stage 3 — a frozen firmware signals a shorter lead time than a firmware still in active development), and pre-shipment inspection window (the buyer reserves a window for pre-shipment inspection during Stage 6's document hand-back).
Closing CTA
The seven-stage audit playbook above is the operations manual a procurement manager can hand to a new buyer the week before a China factory visit and a quality manager can pick up the morning of. It is not a one-page checklist and it is not a brochure handoff. It is the discipline of pushing a documented 79-model catalog across the buyer's eyes, hands, and documentation so the order that follows the audit rests on named artefacts rather than conversational reassurance. To convert the audit scorecard into a quote on the SKU the buyer shortlists — with per-model specifics routed to the product page — request a quote at request a quote page. To reserve the named SKUs for inbound QA before the audit concludes, order samples at order samples page. The factory audit is the spine; the quote and the sample are the bridges that turn the spine into a procurement decision.

