Hotel Smart Lock System Procurement Guide
Hotel smart lock system procurement is the act of turning a property floor plate, a guest-and-staff operating model, and a procurement budget into a structured packet — a per-room schedule, a per-feature ask worksheet, and a to verify in writing spec confirmation register — before the first supplier call is placed. The packet is the difference between walking into a hotel lock quotation asking "how much for the locks?" and walking in with a bill of materials, a spec register, a defined system mode, and a structured way for every supplier to respond on the same lines. This article is the packet itself: eight numbered procurement sections, a per-room schedule template, a per-feature ask template, a to verify in writing spec confirmation table, an RFQ hand-off, and a closing handoff to the next stage of the procurement conversation.
The procurement packet lives one rung above a quote request and one rung below a system design. It is not the architectural conversation (Hotel Smart Lock System Architecture) and it is not the request-for-quotation conversation (Hotel Smart Lock System RFQ Guide). It is the bridge between them: the document that converts the architectural decision into a per-room, per-feature, per-SKU worksheet a supplier can quote against. A buyer who has read the architecture pillar and is about to write the RFQ starts here; a buyer who has a property under survey and a budget to defend starts here. A buyer who has neither should read the architecture first, because the procurement packet assumes the architectural decision — standalone or centralized database mode, Mifare-family credential platform, multilingual management software class, mechanical emergency access included — has already been made.
The packet is built on three disciplines. Per-room discipline: every door on the property maps to a SKU class on the bill of materials, and the bill of materials names a primary candidate model per door class plus alternates by door condition. Per-feature discipline: every architectural commitment (credential platform, hierarchy depth, audit retention, encoder discipline, PC-software environment, mode, mechanical fallback) becomes a written ask the supplier has to respond to line by line. to verify in writing discipline: every per-model capability cell in every worksheet is marked "documentation" so no spec on the packet comes from anywhere except the SKU's own published page and the supplier's written confirmation. These three disciplines are the architecture of the packet.
Section 1 — The Eight-Dimension Hotel-Line Procurement Frame
Before a single line of the worksheet is filled in, the property has to commit to what it is buying. The hotel line in our catalog contains 24 models organized around eight dimensions that determine every SKU choice downstream. Every procurement packet captures all eight dimensions in writing before the supplier is engaged, because the supplier's response on a missing dimension is always "we assume your standard." A property that does not write down its standard inherits the supplier's.
| Dimension | What the dimension decides | Default buyer assumption to surface in writing |
|---|---|---|
| Door class population | SKU mix across guest rooms, suites, common-area doors, back-of-house doors, plant rooms, perimeter doors, parking gates | "Standard guest room" and "suite" treated separately; common-area, back-of-house and perimeter often need a different SKU class or a different reader type |
| Credential platform | Card family, sector map, anti-clone sequence | Mifare 1 @ 13.56 MHz is the SLK-9936S anchor; documentation for every other hotel-line SKU |
| Hierarchy depth | Number of card tiers (guest / duplicate / extended / master / floor / staff / day-staff / vendor / one-shot) and their validity windows | "Six tiers" is a reasonable starting point for a 3-star; seven or eight is common at 4–5 star |
| Audit discipline | Retention period on the lock, on the encoder, and on the PC software; export format; backup discipline | "On-lock buffer holds the last N events" (the SLK-9936S spec sheet cites up to 1,000 audit/event records); PC-side retention and export format documentation |
| Encoder discipline | Write–read-back–verify enforced at every issue; firmware-version discipline across encoder and lock; portable vs. fixed encoder, Q1 deck-room coverage | "Every card is read-back verified" is a property commitment, not a supplier assumption |
| PC software environment | Operating system, language set, audit-export format, backup-and-restore discipline, standalone vs. centralized database mode | "Multilingual" on the SLK-9936S spec sheet means the desk operates in its working language; the exact language list, OS list, export-format list are documentation |
| Mechanical emergency access | 5-pin cylinder cut count, key custody, key rotation, mechanical path exercise cadence | The SLK-9936S ships with a 5-pin cylinder for mechanical emergency access; the cylinder cut and custody are property decisions |
| Operational budget envelope | Blank-card fleet size, replacement rate, encoder wear items, battery replacement cadence | A property running 70% occupancy issues roughly 1.5–2 × room key per night; a card fleet sized to one × room count covers three to four months at most |
These eight dimensions are the columns of the per-feature ask worksheet. A buyer who captures them in writing before engaging a supplier writes a procurement packet that survives one quote, two quotes, and the inevitable comparison round that follows.
Section 2 — Per-Room Schedule: From Floor Plate to Bill of Materials
The per-room schedule is the document the property's facilities or engineering team produces once and the supplier reads once. It converts a hotel floor plate into a SKU-by-SKU bill of materials a supplier can quote against line by line. The schedule below is a blank template a property fills in; the example column shows the kind of entry a 120-room property would write if it were filling the template today.
| Door ID | Door class | Door type | Door thickness (mm) | Existing prep | Reader requirement | Primary candidate SKU | Alternate SKU | Qty |
|---|---|---|---|---|---|---|---|---|
| G-101 to G-130 | Standard guest room | Hinged, single-leaf | (measured 40–55) | None or partial | Dressed-face reader visible from corridor | One cart, hotel-line anchor model | Hidden-reader variant for design-sensitive floors | 30 |
| S-201 to S-205 | Suite | Hinged, single-leaf | (measured 45–55) | None | Dressed-face reader, suite-tier finish | One cart, hotel-line anchor model, suite finish | Hidden-reader variant | 5 |
| CA-01 to CA-06 | Common area (gym, business centre, lounge) | Hinged, single-leaf | (measured 40–50) | None | Dressed-face or shared-controller — documentation | Hotel-line SKU with common-area tier; specifics documentation | — | 6 |
| BOH-01 to BOH-12 | Back-of-house (engineering, housekeeping, storage) | Hinged, single-leaf | (measured 38–45) | Existing mechanical | Reader suited to staff tier hierarchy | Hotel-line SKU with staff-card hierarchy support; specifics documentation | — | 12 |
| EXT-01 to EXT-03 | Exterior / perimeter (plant room, service entry) | Hinged or steel | (measured 45–55) | Existing mechanical | Higher-cycle reader suited to staff frequency | Hotel-line SKU with extended-duty cycle; specifics documentation | — | 3 |
| PRK-01 | Parking gate (vehicle) | Boom / gate | N/A | Existing gate operator | External reader integration with gate; specifics documentation | Hotel-line SKU with external-relay option; specifics documentation | — | 1 |
| PRK-02 | Parking pedestrian door | Hinged, single-leaf | (measured 40–50) | None | Same reader family as rooms | Hotel-line anchor SKU | — | 1 |
| EMS-01 to EMS-04 | Emergency egress (stair-backed, exit-only) | Fire-rated hinged | (measured 45–55) | Existing mechanical | Hardware-only egress; no electronic lock | Hardware-only mechanical lock, not in scope of the hotel-line; documentation | — | 4 |
Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.
Two notes on how the schedule is filled. Door thickness is measured, not assumed. The SLK-9936S spec block cites door thickness 36–100 mm; every other hotel-line SKU has its own door thickness envelope, documentation for the SKU you specify. Existing prep changes the SKU class. A door that already has a 22 mm × 165 mm bore for a mechanical cylinder takes a different lock body than a door with no prep; a back-of-house door with a 5-pin mechanical cylinder already installed needs the electronic lock sized to replace the existing prep cleanly. The schedule's "existing prep" column is the column suppliers read first; the supplier who responds "we assume your standard" to an existing-prep question has not read the schedule.
A second table the procurement packet owns is the per-distance and per-environment envelope. Hotel locks are specified for room interiors; exterior, plant-room, parking-pedestrian, and pool-deck doors carry environmental asks the room schedule does not capture on its own.
| Door class | Environmental ask | Buyer commitment to capture in writing |
|---|---|---|
| Standard guest room (interior corridor) | Dry interior, ambient temperature, no direct weather | No environmental envelope ask beyond standard interior |
| Suite (interior corridor) | Same as guest room | No environmental envelope ask beyond standard interior |
| Common-area interior (gym, lounge) | Dry interior, variable humidity (gym), low-temperature (air-conditioned lobby) | Documentation for any humidity- or temperature-graded SKU |
| Back-of-house interior (storage, housekeeping) | Dry interior, occasional chemical exposure (cleaning supply) | Documentation for chemical-resistance envelope |
| Exterior perimeter (service entry, plant room) | Weather-exposed, temperature swing, dust | Documentation; the hotel line is interior-focused and exterior doors may need a different category SKU |
| Parking pedestrian | Semi-exposed, weather, vehicle proximity | Documentation; consider the outdoor or aluminum-door series in the outdoor category for the door envelope |
| Pool deck, beach gate, exterior amenity | Weather-exposed, humidity, salt-air for coastal | Documentation; this is often where a buyer discovers the hotel line is not the right SKU class |
| Emergency egress (stair-backed, fire-rated) | Hardware-only; no electronic lock | Out of scope of the hotel line; covered by the property's fire-egress hardware |
The two schedules together are the per-room discipline of the procurement packet: a bill of materials the supplier can quote against, and an environmental envelope the supplier can refuse to quote against when the door class falls outside the SKU's documented envelope.
Section 3 — Per-Feature Ask Worksheet: Eight Lines the Supplier Has to Answer
The per-feature ask worksheet is the document the property's procurement lead writes and every responding supplier reads before writing the quote. Each row names one architectural dimension, asks one question on the property's behalf, leaves the supplier a column to answer in, and names the to verify in writing discipline the answer has to obey. A supplier that skips a row is not quoting the system; the property should treat the skipped quote as a non-response.
| # | Architectural dimension | Property's written ask | Supplier's response (must be written) | Confirmation discipline |
|---|---|---|---|---|
| 1 | Credential platform | Card family, sector map, and anti-clone sequence shared by encoder, lock, and blank stock across the property | Card family compatibility statement, supported sector map, sequence protocol version | Documentation for every hotel-line SKU; SLK-9936S spec cites RFID Mifare 1 @ 13.56 MHz; cross-SKU compatibility matrix required |
| 2 | Hierarchy depth and tiers | The number of card tiers (guest / staff / supervisor / master / floor / engineering / vendor / one-shot) and the validity windows per tier | Per-tier credential format, default validity windows, override behavior, audit issuance flow per tier | Documentation per SKU; per-tier classification windows are a property-set value |
| 3 | Audit retention | On-lock event retention count, encoder-side retention, PC-software retention, archive format, backup-and-restore procedure | On-lock retention count and how it rolls over, encoder-side and PC-side retention and export format, archive format, backup procedure | On-lock count on the SLK-9936S is up to 1,000 audit/event records (product-page-documented); every other hotel-line SKU on-lock retention documentation |
| 4 | Encoder discipline | Whether write–read-back–verify is enforced at every card issue and how the encoder logs the verification | Encoder behavior on read-back failure, encoder firmware version control, encoder-software compatibility statement | Documentation for encoder hardware and firmware version; firmware discipline is a property commitment that the encoder has to support |
| 5 | PC software environment | Operating system(s), language list (the property's working languages), audit-export format(s), backup-and-restore discipline, standalone or centralized database mode | OS compatibility statement, supported language list, supported export formats, backup/restore procedure, mode supported | SLK-9936S spec cites multilingual management software and standalone or centralized database modes; specific OS, specific language list, specific export formats documentation |
| 6 | Mechanical emergency access | 5-pin cylinder cut count, key custody, key rotation, mechanical-path exercise cadence | Cylinder cut and keying plan, key-control and copy-restriction procedure, mechanical path test plan | SLK-9936S ships with a 5-pin cylinder; cut plan and custody are property decisions; supplier's role is verified in writing cylinder availability per SKU |
| 7 | Battery and operating envelope | Battery type, expected cycles per battery set, low-battery signal mechanism, battery-replacement cadence | Battery type, cycle count, low-battery signal, replacement cadence | SLK-9936S spec cites 4 × AA power and more than 15,000 battery operating cycles; cross-SKU battery type and cycle count documentation |
| 8 | Operational budget envelope | Blank-card fleet size, replacement rate, encoder wear items, battery replacement budget per year | Blank-card consumption estimate per quarter, encoder wear-item cost, battery replacement cost per year | Pricing is not in scope of this packet; the worksheet asks the supplier to commit to the consumption model so the budget envelope is realistic before pricing |
The worksheet's discipline is that the supplier's response is in writing, line by line, on the supplier's letterhead or in the supplier's email. A response that says "our standard system supports everything you described" is a non-response on every line. A response that says "supported on SLK-9936S, documentation for SKU X" is a real response and the to verify in writing column is satisfied.
Section 4 — to verify in writing Spec Confirmation Table
The to verify in writing table is the document the supplier signs before the quote becomes a contract. It captures every per-SKU capability the property needs to verify against the published product page and the supplier's written confirmation. The table is the property's defence against "that feature is standard" answers that turn out, on the day of install, to be wrong.
The SLK-9936S hotel-class spec block is the packet's first-party data anchor and is shown only once, attributed to the SLK-9936S. Every other hotel-line SKU has its own row with every cell documentation; the property reads the table, asks the supplier to fill every cell from the SKU's published page, and treats the table as a contract appendix.
SLK-9936S anchor row (product-page-documented)
| Spec cell | Value (product-page-documented for SLK-9936S only) | Source |
|---|---|---|
| Door thickness | 36–100 mm | SLK-9936S product page (product-page-documented) |
| RFID carrier | Mifare 1 @ 13.56 MHz | SLK-9936S product page (product-page-documented) |
| Read distance | 0–5 cm | SLK-9936S product page (product-page-documented) |
| Read time | <0.25 s | SLK-9936S product page (product-page-documented) |
| Power | 4 × AA | SLK-9936S product page (product-page-documented) |
| Battery operating cycles | >15,000 | SLK-9936S product page (product-page-documented) |
| Audit / event records on-lock | Up to 1,000 | SLK-9936S product page (product-page-documented) |
| Mechanical emergency cylinder | 5-pin cylinder | SLK-9936S product page (product-page-documented) |
| Latch | 3-point latch | SLK-9936S product page (product-page-documented) |
| Body material | Stainless steel + alloy | SLK-9936S product page (product-page-documented) |
| Finish options | Multiple finish options | SLK-9936S product page (product-page-documented) |
| Mechanical emergency access | Yes | SLK-9936S product page (product-page-documented) |
| Hotel PC management software | Multilingual management software | SLK-9936S product page (product-page-documented) |
| Database mode | Standalone or centralized database modes | SLK-9936S product page (product-page-documented) |
| Positioning | 1–5 star hotels | SLK-9936S product page (product-page-documented) |
The SLK-9936S row is the only row in the to verify in writing table that quotes published numbers directly. Every other row is the supplier's written confirmation against the SKU's own published page.
Per-SKU to verify in writing rows (supplier confirms each cell from the published product page)
| Spec cell | SLK-9936G (check against the model specification) | SLK-9905A hidden-reader (check against the model specification) | SLK-9951TH (check against the model specification) | SLK-9962S (check against the model specification) |
|---|---|---|---|---|
| Door thickness | documentation | documentation (~38–100 mm, product-page-documented for 9905A) | documentation | documentation |
| RFID carrier and credential family | documentation | documentation | documentation | documentation |
| Read distance | documentation | documentation | documentation | documentation |
| Read time | documentation | documentation | documentation | documentation |
| Power | documentation | documentation | documentation | documentation |
| Battery operating cycles | documentation | documentation | documentation | documentation |
| Audit / event records on-lock | documentation | documentation | documentation | documentation |
| Mechanical emergency cylinder | documentation | documentation | documentation | documentation |
| Latch | documentation | documentation | documentation | documentation |
| Body and finish options | documentation | documentation | documentation | documentation |
| Reader style | documentation | Hidden reader (door-mounted, not visible from corridor) per catalog-spec naming | documentation | documentation |
| Hotel PC software class | documentation | documentation | documentation | documentation |
| Database mode support | documentation | documentation | documentation | documentation |
| Cross-SKU credential compatibility with SLK-9936S | documentation | documentation | documentation | documentation |
The cross-SKU credential compatibility cell in row 14 is the cell that decides whether the property can mix SKUs across floors without forcing a property-wide card re-issue. A supplier that confirms SLK-9936S, SLK-9936G, SLK-9905A, SLK-9951TH and SLK-9962S all sit on one credential family allows the property to put the hidden-reader 9905A on a design-sensitive suite floor and the dressed-face 9936S on the standard floor and still issue one card at the front desk. A supplier that says "we recommend one model across the property" is asking the property to give up design flexibility — that answer belongs on the packet, in writing, before the contract.
The same to verify in writing discipline extends to the legacy RFTC / RF card-and-code family (model codes 118, 118E, 228, 230, 232, 238, 239, 253, 305, 306, 308, 309, 502, 620, 621, 911, 002, 019, 022, 2020, 760) and the stainless-keypad options (019, 022, 309) — every spec cell for every model is documentation from the supplier's written response. The property never assumes a catalog-listed model code has a feature on a given SKU.
Out-of-catalog firewalls
The to verify in writing table includes a row of cells the property has to keep empty in every SKU column. These are the out-of-catalog capabilities our hotel line does not include; a property that writes "documentation" on any of these cells has been mis-quoted and the contract should be re-read.
| Capability class | Hotel-line availability (per our catalog) | Property-side handling |
|---|---|---|
| Palm-vein credential | Not in catalog | Do not include in any per-room schedule cell; do not ask the supplier to verify in writing |
| Matter / Zigbee / Z-Wave / Thread radio | Not in catalog | Do not include in any per-room schedule cell; do not ask the supplier to verify in writing |
| Apple Home Key credential | Not in catalog | Do not include in any per-room schedule cell; do not ask the supplier to verify in writing |
| UWB (ultra-wideband) credential | Not in catalog | Do not include in any per-room schedule cell; do not ask the supplier to verify in writing |
| Wi-Fi as the door radio | Not the hotel-line architecture | Do not include in any per-room schedule cell; the hotel line is encoder + card architecture, not Wi-Fi-at-the-door |
| Mobile key as hotel credential | Not in hotel-line catalog | Do not include in any per-room schedule cell; mobile key is per-SKU and documentation |
The firewall discipline is the packet's defence against the supplier who wants to talk about features the catalog does not include. The packet names what is in the catalog and writes the rest out.
Section 5 — Blank-Card Fleet and Encoder Procurement Ask
The blank-card fleet and the encoder are the procurement line items most often under-budgeted in a hotel lock purchase. A property that orders locks and cards in the same conversation and encoders in a different conversation will discover, on opening day, that the card fleet is sized to one × room count and the encoder is sized to a single desk — which works until peak arrival and the second property decides to centralize.
| Procurement line | What the property commits in writing | Quantity rule of thumb | Confirmation discipline |
|---|---|---|---|
| Blank cards for guest keys | Mifare-family card compatible with the property's encoder and lock family | 1 × room count for steady state; 2 × room count to absorb issuance peaks; +20% for loss / demagnetization / destruction queue | SLK-9936S spec cites Mifare 1 @ 13.56 MHz; cross-SKU card compatibility documentation |
| Blank cards for staff / master / floor | Same family, often with different visual marking (color or print) | Sized to headcount × 1.5 (one on lanyard, one spare, plus loss reserve) | Same family discipline as guest cards |
| Encoder station | One per front desk; one spare on the property; one for engineering bench | A 120-room property runs one encoder at peak; a 300-room property often runs two at peak | Encoder-software contract is a per-supplier detail; firmware-version control is a property commitment |
| Card stock lot retirement discipline | Per lot register; retirement date for any lot in the destruction queue | Card stock has a shelf life; the lot register tracks the lot and the retirement decision | Property discipline; supplier confirms the card's storage envelope |
| Battery stock (4 × AA per door) | Sufficient stock to cover one full battery replacement cycle across the property | 4 × AA per door × 1 cycle = 4N batteries for N doors | SLK-9936S spec cites 4 × AA; cycle count >15,000 (product-page-documented); replacement cadence is property-set based on usage |
The blank-card fleet is a consumable line in the operating budget, not a one-time purchase. A property that budgets one × room count for cards and zero for replacement will run out of cards in the second quarter and re-order at retail. The packet's blank-card ask captures the consumption model so the supplier's quote can carry the line correctly.
Section 6 — PC Software and Architecture Mode Procurement Ask
The hotel PC management software and the architecture mode (standalone or centralized database) are the procurement line items the supplier most often quotes last and the property most often accepts without a written spec. The packet captures both in writing before the quote is requested.
| Software and mode ask | What the property commits in writing | Supplier's written response | Confirmation discipline |
|---|---|---|---|
| Multilingual interface — language list | The exact list of working languages the desk operates in | Language list confirmed for the SLK-9936S; documentation for every other hotel-line SKU | SLK-9936S spec cites multilingual management software; specific language list documentation |
| Operating system compatibility | The OS the property will run the PC software on (Windows version, etc.) | OS compatibility statement for each hotel-line SKU | Documentation per SKU |
| Audit-export format | CSV / Excel / PDF / PMS-specific format — the property's chosen export format | Export format list per SKU | Documentation per SKU |
| Backup and restore procedure | Backup frequency, retention period, restore test cadence | Backup and restore procedure per SKU | Documentation per SKU |
| Standalone mode support | Confirmed for the property's PC environment | Standalone mode supported per SKU | SLK-9936S supports standalone mode per spec; cross-SKU documentation |
| Centralized database mode support | Confirmed if the property joins or already belongs to a group | Centralized database mode supported per SKU | SLK-9936S supports centralized database mode per spec; cross-SKU documentation |
| Migration path between modes | What changes if the property moves from standalone to centralized, and vice versa | Migration procedure, license implications, encoder-card compatibility implications | Documentation per SKU |
| Hierarchy tier editor | The number of tiers the property will define; the per-tier validity windows; the override hierarchy | Tier editor supports the property's tier count and validity windows | Documentation per SKU |
| Audit-event vocabulary | The event classes the property's operations needs (door open / credential issued / credential revoked / low battery / tamper / forced entry / mechanical override / configuration change) | Event class list per SKU | Documentation per SKU |
The PC software and architecture mode ask is the row of the packet most often skipped. A property that walks into the supplier call with this row complete walks out with a quote that names the OS, the language, the mode, the export format, the backup procedure, and the tier editor capability. A property that skips this row walks out with a price list and a vague promise of "the software supports what you described."
Section 7 — Per-Project Risk Register
The risk register is the packet's discipline for surfacing the issues that do not show up on the schedule but show up on the day of install. Every row is a risk the property has to either mitigate or accept explicitly before the contract is signed.
| Risk | Where the risk lives | Property-side mitigation |
|---|---|---|
| Door thickness falls outside the SLK-9936S 36–100 mm envelope | Door prep not measured accurately; door has been re-skinned since the original survey | Measure every door before the supplier cuts the SKU order; surface every out-of-envelope door as an alternate SKU |
| Existing door prep not compatible with hotel-line SKU body | Property assumed new prep, door has 22 mm × 165 mm bore for legacy mechanical | Survey existing prep for every door before SKU class is finalized |
| Encoder firmware version drifts from lock firmware version | Firmware updated on one component and not the other; mixed revisions produce silent platform mismatch | Encoder-locked firmware discipline; firmware version register; supplier commitment to firmware-version compat across encoder and lock |
| Property clock drifts from authoritative time | The PC clock drifts; lock clocks drift independently; card validity windows computed from inconsistent clocks | PC clock discipline; lock-clock discipline (where supported by SKU); audit retention policy covering the drift window |
| Card fleet under-sized at opening | Blank-card order sized to room count; replacement rate ignored | Order 2 × room count to start; monitor issuance rate monthly; reorder in cycle |
| Mechanical key custody not assigned | Property cuts mechanical keys, never assigns custody, never tests the mechanical path | Assign mechanical-key custody in writing; name the exercise cadence; document the cut path |
| Audit archive at risk of diminishing | Audit retention on-lock rolls over (the SLK-9936S spec cites up to 1,000 audit/event records on the lock) and the PC-side export cadence is too slow | Set the PC-side export cadence below the on-lock rollover horizon; archive the export off-property |
| Operating system upgrade mid-contract | Property upgrades the PC OS; PC software breaks | OS compatibility statement in writing; supplier commitment to support the upgrade path |
| Architecture mode change after install | Property joins a group or leaves a group; standalone vs. centralized decision has to be revisited | SLK-9936S spec cites support for both standalone and centralized database modes — documentation for every other SKU |
The risk register is the section most often written down after the contract is signed, when the property has already accepted the risk. The packet's discipline is to write it down before.
Section 8 — Procurement Packet Hand-Off to the RFQ
The packet is complete when every cell in sections 1 through 7 has either a property commitment in writing, a supplier response in writing, or a "documentation" cell with the product-page source cited. The hand-off to the RFQ is the moment the packet becomes a request for quotation. Two documents leave the property's desk on the same day: the procurement packet (the per-room schedule, the per-feature ask, the to verify in writing table) and the RFQ itself, addressed to the supplier, with a reference list of suppliers invited to quote. The Hotel Smart Lock System RFQ Guide carries the packet into the formal RFQ structure; the Hotel Smart Lock System Vendor Selection article carries the comparison across multiple quotes.
The packet survives one quote, two quotes, and the inevitable comparison round. A property that walks into the comparison round with the packet has a written spec register, a written per-room schedule, and a written per-feature ask; the comparison becomes a question of which supplier's response is strongest on the lines that matter, not which supplier quoted the lowest price. A property that walks in without the packet has a price list and a vague promise; the comparison becomes a question of which supplier's price is lowest, and the property discovers, on opening day, that the lowest-priced system did not include the features the architectural conversation required.
Seen from the buyer's side of the table, the packet comes together in one arc that starts at a door and ends at a signed comparison.
journey
title Hotel lock procurement packet walk
section Survey
Measure every guest door: 5: Facilities team
Classify door types and preps: 4: Facilities team
section Specify
Capture the eight hotel-line dimensions: 4: Procurement lead
Route per-SKU cells to product pages: 3: Procurement lead
section Quote
Hand the packet into the RFQ: 4: Procurement lead
Read supplier answers side by side: 5: Buying group
Illustrative Scenario: A 240-Room Mixed-Use Property Building the Packet
Consider a 240-room mixed-use property — 180 standard rooms, 40 suites, 20 serviced apartments — converting from a legacy mechanical master-key system to a hotel-line electronic lock system. The property has a small existing group affiliation that wants centralized audit visibility across its four properties but does not want to centralize day-to-day operations.
The property's procurement packet walks through the eight dimensions. Door class population captures 180 standard rooms, 40 suites, 20 serviced apartments, 6 common-area doors (gym, business centre, lounge, mezzanine, pool deck gate, parking pedestrian), 12 back-of-house doors, 3 exterior perimeter doors, and 4 emergency egress doors (out of scope of the hotel line). Credential platform captures the Mifare 1 family at 13.56 MHz on the SLK-9936S, with cross-SKU compatibility confirmation requested for the SLK-9936G (one design-sensitive floor) and the SLK-9905A (the lobby-adjacent conference floor). Hierarchy depth captures eight tiers (guest / duplicate / extended / master / floor / supervisor / engineering / one-shot) with validity windows per tier. Audit discipline captures on-lock retention (the SLK-9936S spec block cites up to 1,000 audit/event records), encoder-side retention, PC-side retention, export format (CSV for operational archive; PMS-format for guest profile integration), and backup-and-restore procedure.
The second half of the eight dimensions is where the operating model shows up on paper. Encoder discipline captures write–read-back–verify enforced at every card issue, encoder firmware version locked, encoder portable unit for off-desk events. PC software environment captures the language list (four languages the desk operates in), the operating system (Windows version the supplier must confirm), the standalone-mode deployment with optional centralized-mode connection to the group's four-property database. Mechanical emergency access captures a single 5-pin cylinder cut, key custody assigned to the chief engineer, mechanical-path exercise on a documented cadence. Operational budget envelope captures 480 blank cards to start (2 × room count), an additional 60 cards to absorb issuance peaks, an encoder wear-item reserve, and a battery replacement budget for the first cycle.
The per-room schedule fills the eight door classes against the SKU catalog: 220 hotel-line anchor locks for the 180 standard rooms and 40 suites, with 10 of the suites taking the SLK-9905A hidden-reader variant for design reasons; 20 SLK-9936G locks for the 20 serviced apartments on a separate floor with separate audit visibility; 6 hotel-line locks on the common-area doors; 12 hotel-line locks on the back-of-house doors; 3 hotel-line locks on the exterior perimeter doors (with environmental envelope attestation); 1 hotel-line lock on the parking pedestrian door; 4 mechanical-only egress locks out of scope.
The worksheets then do their job on the supplier side. The per-feature ask worksheet sends the supplier eight written questions; the supplier responds with written confirmation against each, citing the SLK-9936S product page where the SLK-9936S is the answer and citing documentation for every cross-SKU cell. The to verify in writing table captures the SLK-9936S anchor row in full and captures per-SKU confirmation rows for the SLK-9936G, the SLK-9905A, the SLK-9951TH (the property's alternate for any out-of-envelope door), and the SLK-9962S (the property's alternate for any common-area door requiring extended cycle count). The blank-card fleet ships as 480 guest cards, 60 staff cards, 6 master cards, and 4 floor cards. The encoder ships as one desk unit, one spare, one engineering-bench unit. The PC software ships with the four-language list, the Windows OS confirmation, the standalone-mode deployment, the centralized-mode option for the group, and the CSV / PMS export format list.
The packet leaves the property's desk on the same day as the RFQ, addressed to two invited suppliers, with a quote deadline. The suppliers respond with line-by-line packets on their own letterhead; the comparison round reads the packets against each other, finds one supplier's card-family confirmation stronger, finds the other's firmware-version commitment more rigorous, and walks the property to a written decision. The packet survives the round; the price list does not.
Out-of-Catalog Firewalls the Packet Carries Forward
The packet includes the out-of-catalog firewall list as a closing discipline. The catalog has 79 published models; 24 sit in the hotel category; 9 sit in RFID; the hotel line is the right answer for the rooms and certain back-of-house doors, but is the wrong answer for several doors on the property where the supplier might be tempted to over-extend.
| Out-of-capability | Why the packet says "do not include" |
|---|---|
| Palm-vein credential on any hotel-line door | Not in catalog; do not write the cell on any schedule |
| Matter / Zigbee / Z-Wave / Thread radio on any hotel-line door | Not in catalog; do not write the cell on any schedule |
| Apple Home Key credential on any hotel-line door | Not in catalog; do not write the cell on any schedule |
| UWB credential on any hotel-line door | Not in catalog; do not write the cell on any schedule |
| Wi-Fi as the door radio on any hotel-line door | Hotel-line architecture is encoder + cards, not Wi-Fi-at-the-door |
| Mobile key as the standard hotel credential | Mobile key is per-SKU and documentation; do not assume |
| PMS, elevator, parking, ACS brand names in any spec cell | Architectural vocabulary only; brand interop documentation for both sides |
| Any published price, MOQ, lead time, warranty year, certification mark | Out of scope of the procurement packet; resolve via /request-a-quote |
The firewall discipline is the packet's last line of defence. A property that keeps the firewall in every worksheet writes a procurement packet the supplier cannot inflate with features the catalog does not include. A property that drops the firewall writes a packet the supplier fills with promises the catalog cannot keep.
Closing Note: From Procurement Packet to Operating System
The procurement packet is the bridge between architectural commitment and supplier commitment. The property that finishes the packet has a written schedule, a written ask, a written to verify in writing register, a written risk register, and a written hand-off to the RFQ. The property that walks into the supplier conversation with the packet walks out with a written response on every line. The property that walks in without the packet walks out with a price list and a vague promise.
For the next stages of the procurement conversation: the Hotel Smart Lock System RFQ Guide carries the packet into the formal request-for-quotation structure, with the supplier-evaluation columns and the comparison-round discipline. The Hotel Smart Lock System Vendor Selection article carries the comparison across multiple quotes into the final selection. The Hotel Smart Lock System Architecture pillar is the document the packet was built from; the packet is the document the architecture is bought against. To turn the packet into a quote: request a quotation with the per-room schedule, the per-feature ask, and the to verify in writing table attached. To evaluate the locks physically first: order samples of the SKUs in the packet and walk the SLK-9936S, the SLK-9936G, and the SLK-9905A through the same to verify in writing table before the quote is signed. To review the broader hotel-line capability: request a catalog for the full 24-model hotel line and the cross-category context (9 RFID / 18 keypad / 37 fingerprint / 10 outdoor / 6 face / 6 cabinet / 3 video / 3 glass across the 79 published models).
The packet is not the end of the procurement conversation. It is the document that makes the rest of the procurement conversation disciplined.

