SLK-9936S Procurement Guide for International Buyers
Procuring SLK-9936S hotel locks as an international buyer is a staged order, not a single purchase: verify that your doors and front-desk workflow match the model's published class, gate that verification with physical samples, structure the RFQ around the spec block and your door survey, then run production, shipping and documentation as a checkpoint sequence where each stage has an exit criterion before money or steel moves. This document is written as an operations playbook — numbered protocols, IF-THEN decision rules and exception handling — for importers, distributors and procurement agents ordering this model class from a Chinese smart lock factory for the first time, or for buyers who have done it before and want the process written down.
No prices, minimum order quantities or lead-time figures appear here on purpose. On a quote-based B2B catalog, those three numbers are outputs of your inputs — quantities, door survey results, finish selections and destination — and any guide that quotes fixed numbers is quoting fiction. Everything numeric in this playbook comes from the SLK-9936S product page itself. If you are still deciding whether this manufacturer class is the right supplier at all, start with the supplier-level playbooks first: Smart Lock Factory in China: A B2B Buyer's Guide and Smart Lock Manufacturer for Importers. This article assumes the supplier question is converging and asks the narrower one: how do I actually run an end-to-end international order for this specific lock?
Protocol 0 — Scope, Controls and the Anchor Spec Block
Every stage of this playbook tests your real-world inputs against one published reference: the SLK-9936S spec block as listed on its product page:
SLK-9936S hotel smart door lock: 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.
Four control rules govern the whole order:
- No stage skips. Production does not start until the sample gate passes; the sample is not ordered until the door survey is complete; the survey is not useful until you have confirmed the model class. If a supplier offers to compress the sequence by shipping "while you test," that is an exception — handle it in Protocol 7.
- Every claim becomes a checkable line. The spec block above is your checklist parent. Anything your project needs that the block does not state (card encoding workflow, spindle orientation, weather exposure rating for a resort gate) goes into the RFQ as an explicit question, not an assumption.
- Written or it didn't happen. Confirmations, deviations and finish decisions live in email or the quote document, never in a phone call summary.
- The 36–100 mm door range is a gate, not a comfort. A large share of failed international hotel-lock orders trace back to doors measured informally. Protocol 2 fixes that before anything else is spent.
Written as one path, the seven protocols become a stage-gate chain: every diamond is an exit criterion the buyer owns, and no forward arrow is allowed to skip one.
flowchart TD
P0["Protocol 0 · Controls and anchor spec block"] --> P1["Protocol 1 · Model class fit check"]
P1 --> G1{"Survey inside the published band and credential path settled?"}
G1 -- "No" --> RS1["Re-route the model or quote card provisioning as an RFQ line"]
G1 -- "Yes" --> P2["Protocol 2 · Door survey gate"]
P2 --> P3["Protocol 3 · Sample scorecard on a real door section"]
P3 --> G2{"Sample gate passed in writing?"}
G2 -- "No" --> Q4["Convert gaps into RFQ question blocks"]
Q4 --> P4["Protocol 4 · Seven-block structured RFQ"]
G2 -- "Yes" --> P4
P4 --> P5["Protocol 5 · Production checkpoints A to C"]
P5 --> P6["Protocol 6 · Shipping and documentation set"]
P6 --> P7["Protocol 7 · Arrival gate then pilot block"]
P7 --> DONE["Rollout released on signed sheets"]
The factory behind the model is an OEM/ODM operation with 10+ years in smart locks, a 79-model catalog including 24 hotel locks, and shipments into 80+ countries — which matters here mainly because it means the export paperwork steps in Protocol 6 are routine on the supplier side. You are not asking them to learn how to export; you are checking that they export to your country with your documents.
Protocol 1 — Verify You Are Buying the Right Model Class
Before samples, before quotes: a two-question fit check against the published class. The SLK-9936S sits in the hotel lock category alongside sibling models such as the SLK-9905A hidden-reader lock, so class verification also tells you when a sibling is the better fit.
Question A — Is your door in the envelope? The published door thickness range is 36–100 mm. IF your survey (Protocol 2) shows doors materially thinner than 36 mm or thicker than 100 mm, THEN stop: do not negotiate a special fit on this model at the survey stage — ask the factory, via the quote channel, which of the 24 hotel models covers your thickness, and treat a switch as normal, not a rejection.
Question B — Is your credential system Mifare-compatible? The published radio line is RFID Mifare 1 at 13.56 MHz. IF your property today encodes magnetic stripe keys or a different IC family, THEN the RFQ must explicitly ask what card provisioning path exists (new cards, encoders, software workflow) — because the lock reads what it reads, and guest-facing credential decisions cannot be discovered mid-order.
| Fit check | Published anchor | PASS if | IF-THEN on mismatch |
|---|---|---|---|
| Door thickness | 36–100 mm | Surveyed doors fall inside range with margin for hardware | THEN re-route to a sibling hotel model before sampling |
| Credential type | Mifare 1 @ 13.56 MHz | You can supply or switch to 13.56 MHz IC cards | THEN quote card+encoder provisioning as an RFQ line, not a surprise |
| Property tier | Positioned 1–5 star | Model class matches service level planned | THEN compare against other hotel PDPs in the category |
| Audit need | Up to 1,000 event records | Record depth fits housekeeping/security policy | THEN raise record-export expectations in the software question block |
| Deployment mode | Standalone or centralized database | Your IT choice matches one of the two published modes | THEN define mode before the RFQ; it changes the software scope |
Decision rule: sample only what passed. Ordering samples of a model your doors cannot accept burns one gate cycle you cannot get back cheaply.
Protocol 2 — The Door Survey Gate (Entry Criteria for Everything Downstream)
The survey is the buyer's own deliverable, and the RFQ quotes it back to the supplier. Run it per door type, not per property — a hotel typically has three to six door populations (guest room standard, accessible room, back-of-house, suite double, service corridor).
Record, for every door type, on a sheet that becomes an RFQ appendix:
- Thickness at the lock edge, in millimeters, measured at multiple points along the vertical edge — old doors sag and thickness varies top-to-bottom.
- Existing hardware state: mechanical mortise lock present (and its case dimensions), pre-drilled holes, or bare door.
- Edge and frame geometry: rebated or flush, metal-edged or wood, door projection that could foul a 3-point latch stroke.
- Emergency key policy: which master/keying structure you expect to use alongside the published mechanical emergency access and 5-pin cylinder.
- Environment: interior-conditioned guest rooms versus coastal resort or outdoor-adjacent doors — the published body is stainless steel + alloy with multiple finish options, but exposure class is a question you ask, not a box you tick.
| Survey field | Why the SLK-9936S spec block makes it load-bearing | Feeds which stage |
|---|---|---|
| Thickness (mm), per door type | 36–100 mm is a published gate | Protocol 1 fit, RFQ quantity split |
| Existing lock case / bore pattern | 5-pin cylinder, retrofit vs new openings | Sample scope, installation planning |
| Latch stroke clearance | 3-point latch needs clean engagement | Sample-fit test on a real door section |
| Credential infrastructure | Mifare 1 @ 13.56 MHz | Card/encoder RFQ block |
| Exposure notes | Finish options + body materials | Finish confirmation, deviation questions |
IF-THEN: IF you cannot physically measure before ordering samples (remote project, doors not yet manufactured), THEN order the sample as an evaluation unit only, hold the production gate, and re-run this survey against door shop drawings before confirming quantities. A sample that passed bench testing is not a fit confirmation.
Protocol 3 — The Sample Stage
Sample procurement for the SLK-9936S means ordering evaluation units through the factory's sample channel (order-samples) against the exact configuration your survey demands, mounting at least one unit on a door section representative of your worst-case door, and running a written scorecard before the sample gate is declared passed.
Configure the sample request explicitly. The spec block gives you the line items to verify in writing in writing: door thickness range you are testing against, finish selection from the multiple available options, battery format (4 × AA), card family (Mifare 1), and which software mode you want demonstrated — standalone or centralized database — including the multilingual management software in your operators' language, not the demo language.
Run the sample through a fixed scorecard. The columns below are the protocol; the "Result" column is what you fill in and attach to the eventual RFQ.
| # | Test line | Method | Pass criterion | Result |
|---|---|---|---|---|
| 1 | Door-section fit | Mount on a section at your thickest and thinnest surveyed door values | Latches cleanly, no binding, within 36–100 mm | |
| 2 | Card read | Your Mifare cards, repeatedly, at realistic guest distance | Consistent reads consistent with published <0.25 s / 0–5 cm behavior | |
| 3 | Audit trail | Perform operations, pull records via software | Events appear; record handling matches the up-to-1,000 published depth | |
| 4 | Software language | Front-desk operator runs check-in/check-out unaided | Multilingual software is genuinely usable for your team | |
| 5 | Emergency mechanical access | Key path exercised per your policy | Works without power, operable by your staff procedure | |
| 6 | Battery behavior | Monitor over the evaluation period | Voltage/power handling acceptable for your swap policy | |
| 7 | Finish and build | Compare to RFQ-intended finish | Physically matches what you will specify |
Exception rules at this gate:
- IF the sample reveals a software gap your project requires, THEN convert it into an RFQ question block with a written confirmation requirement — do not accept "standard later version will support it" without text.
- IF only one door population fails, THEN you are now a mixed-model buyer: that is normal, and Protocol 4 handles it as two line groups, not a rejection of the order.
- IF the factory declines sample-stage software demonstration, THEN treat it as a supplier-verification signal and revisit Protocol 1's supplier-level checks from Smart Lock Manufacturer for Importers.
Protocol 4 — Structure the RFQ Around What You Now Know
By this point you hold two assets no generic RFQ has: a completed door survey and a signed sample scorecard. The RFQ assembles them. A well-structured SLK-9936S RFQ has seven blocks — identity, quantities per door population, configuration lines, confirmation-dependent questions, documentation requirements, packaging/shipping terms, and the sample-scorecard reference — and names explicitly what is NOT being asked (price is invited, but every quantity and configuration variable is controlled).
| RFQ block | What you state | What you demand back | Common mistake |
|---|---|---|---|
| 1. Buyer & project identity | Company, destination country, project type, role (importer/distributor/end project) | Named contact path | Anonymous "price list please" RFQs get low-priority answers |
| 2. Quantity structure | Units per door population and per finish, from the survey | A per-line confirmation, quantities restated back to you | One blended total that hides a mixed-finish need |
| 3. Configuration lines | Model = SLK-9936S; thickness range per population; finish; card family; software mode; language | Line-by-line conformity marks or flagged deviations | Copy-pasting a previous project's spec |
| 4. Confirmation-dependent questions | Everything the PDP does not state that your survey raised: spindle/hardware orientation for retrofit bores, exposure class for outdoor-adjacent doors, record-export format, master keying structure | Written answers inside the quote document | Sending questions in a separate thread that never merges into the quote |
| 5. Documentation | Pro-forma/commercial invoice content, packing list granularity, shipping mark scheme, any destination-country paperwork your broker requires | Document drafts before shipment, not after | Discovering your customs broker needs a specific document format mid-transit |
| 6. Shipping terms | Your Incoterms preference (EXW, FOB, CIF, DDP are the common ones) and destination port/warehouse; consolidation instructions if you buy other categories too | A quote expressed in the same term you asked in | Comparing an EXW quote against a competitor's CIF quote |
| 7. Sample reference | Which approved sample, approval date, approved configuration | Quote locked to the approved sample build | Ordering "the sample" after the sample was informally modified |
Structure rules for the questions block: every line must be answerable yes/no/confirm-in-writing. IF you ask open questions ("how is the quality?"), THEN you get marketing. The quote arrives, you read it against these seven blocks, and any block the quote silently ignores is re-sent as a numbered follow-up — the Hotel Smart Lock Project Procurement Checklist covers the same discipline at whole-project scale; here it is applied to one SKU group.
MOQ and lead time will appear as outputs in the supplier's quote. Do not reverse them: you cannot infer a trustworthy lead time from a guide, and on a quote-based catalog the credible figure is the one written against your configuration and quantity structure.
Protocol 5 — Production-Stage Checkpoints (Post-Commitment, Pre-Shipment)
After the PO is placed against the confirmed quote, the playbook shifts from asking to verifying. Three checkpoints, each with an entry/exit rule:
Checkpoint A — Configuration freeze confirmation. Within the communication window the supplier commits to, request a restatement: model, per-population quantities, finish codes, software mode and language, card family, marking scheme. IF the restatement deviates from the quote in any line, THEN the deviation is resolved in writing before production proceeds — an exception that resolves silently in a factory becomes a container that resolves expensively at your port.
Checkpoint B — Pre-shipment verification package. Define in the PO what evidence arrives before goods move: photographs of actual finished goods against the approved finish, functional test confirmation per the supplier's standard process, software version confirmation, and packing list draft. You are a remote buyer; this package is your eyes. Request it as a document set, review it against the sample you approved in Protocol 3, and issue either a written release-to-ship or a named deviation list.
Checkpoint C — Booking and handover. Once released, the export logistics handover begins: booking confirmation, container or pallet allocation against your shipping terms, and the document set in Protocol 6 moving to final form. IF your Incoterm is supplier-controlled beyond the factory gate (CIF, DDP), THEN request the carrier and routing in writing so your broker can pre-file; IF buyer-controlled (FOB, EXW), THEN your forwarder's details go to the supplier early enough that warehousing waits on the booking, not on your email latency.
Protocol 6 — Shipping, Customs and Documentation
This stage fails more often for first-time importers than any technical issue with the locks. The model class here ships as hardware with batteries, wireless RF function, and software — and each of those three characteristics touches paperwork.
Documentation checklist — build this as a live table in your own order file and demand drafts of each before goods are released:
| Document | Origin | Verify before receipt | Red flag |
|---|---|---|---|
| Commercial invoice | Supplier | Matches PO lines, values, Incoterm, currency | Invoice that disagrees with the quote structure |
| Packing list | Supplier | Carton count, gross/net weight, marks, and per-carton model/finish split | One combined "assorted locks" line for a mixed order |
| Transport document (bill of lading or air waybill) | Carrier via supplier or your forwarder | Consignor/consignee, Incoterm consistency, goods description | Description too vague for your customs entry |
| Shipping marks & carton labeling | Supplier | Your scheme, legible, one carton = one door-population configuration where possible | Mixed-configuration cartons that make site distribution blind |
| Battery handling declarations | Per carrier/customs requirement | How the 4 × AA configuration ships (installed vs separate), and that your chosen carrier route accepts it | Assumption that installed batteries are automatically acceptable |
| RF-product information | Supplier | Mifare 1 @ 13.56 MHz as declared; useful for destination radio-equipment entry rules | Specs on the invoice that differ from the PDP |
| Destination-specific entries | Your customs broker | HS classification guidance and duty treatment confirmed by your broker, not guessed from the internet | A broker engaged after arrival instead of before booking |
Two rules carry most of the risk:
- Engage your customs broker at PO stage, hand them the invoice and packing-list drafts, and let them name the entry requirements — including classification — before the container moves. Classification for locks with RF functionality is your destination's question, and the competent answer owner is your broker, working from the supplier's drafts.
- IF the packing list cannot tell you which carton holds which door-population configuration, THEN demand a re-cut before shipment. On a 120-key project, a site team that must open cartons to find the right finish loses days; the per-carton split is cheap before shipping and expensive after.
Software and card provisioning cross a border in a different way than steel: management software access, card stock and any encoders travel either with the shipment or separately, and each path has its own paperwork line. Decide the split in the PO.
Protocol 7 — Arrival Inspection, Deployment Gate and Exception Handling
Receipt is a stage-gate, not a moment. Run it in order:
- Container/parcel condition count against the packing list before signing anything beyond "received in apparent condition" — note damage on the delivery document itself.
- Per-carton audit against the packing list: configuration split, finish match to the approved sample, quantity per door population.
- Functional spot-tests on the same scorecard lines from Protocol 3 — reads, latch stroke, audit records, software — before a single lock is mounted. Mounting is acceptance.
- One pilot floor / one pilot room block deployed and operated for your internal review window, THEN full rollout.
Exceptions — the IF-THEN register for the whole playbook:
| # | Exception | IF observed | THEN action |
|---|---|---|---|
| E1 | Door survey was incomplete; some doors fall outside 36–100 mm | Found at install staging | Quarantine that population, re-quote the sibling model via /request-a-quote; do not force-fit |
| E2 | Credential mismatch discovered at provisioning (cards not 13.56 MHz Mifare family) | At software/card setup | Halt rollout; the radio line is fixed hardware — resolve card stock, not the lock |
| E3 | Arrived finish ≠ approved sample | At carton audit | Photograph against the retained sample, file the deviation the same day, hold that carton group out of install |
| E4 | Packing list miscount | At receipt audit | Note on delivery document before signing clean, reconcile from per-carton records |
| E5 | Software language build ≠ confirmed RFQ line | At first front-desk session | Escalate as a configuration deviation, not a training task |
| E6 | Supplier offered to ship before sample-gate confirmation | Earlier than this stage | Decline unless in writing with your named risk acceptance; this is the classic sequence-skip |
| E7 | Broker requires a document the set in Protocol 6 does not include | Before booking | Back to supplier with a named format; do not improvise your own version of a trade document |
Illustrative deployment scenario (representative, not a customer story): consider a 90-key coastal hotel importing for a refresh, where the survey finds two door populations — 82 guest doors near the thin end of the 36–100 mm envelope and 8 thicker suite doors — plus an outdoor-adjacent corridor exposure. The RFQ in that scenario is a split-configuration order from one model class: same SLK-9936S line, two quantity groups, finish and exposure questions written per population, a per-carton packing list cut along exactly those two groups, and the sample order including both thickness extremes. When the order is structured that way, arrival audit takes hours instead of becoming a site crisis — the entire value of this playbook sits in that contrast.
Closing — Run the Sequence, Then Move It Into the Quote
The international order for this model class is won or lost before the PO: doors measured, sample tested against the published spec block, RFQ structured so the quote answers it line by line, and documents defined while the container is still an idea. The SLK-9936S page tells you exactly what the class claims — confirm your configuration against it, and when Protocols 1 through 4 are complete, put the structured order through the request-a-quote channel with the survey appendix and sample scorecard attached. That package is what turns "international buyer asks for price" into an order a factory can execute without a single assumption on your side.

