Smart Lock Procurement for Office Buildings
The procurement packet below is the office-building working document: a per-door schedule, a credential class matrix, a to verify in writing spec capture for every shortlisted model, packaging and marking asks, and a four-stage acceptance table that walks the order from model selection through quantity and customization confirmation, through production, and onto the shipping manifest. No price, MOQ, lead time or warranty column appears in it. Every figure that varies by model is a line the supplier has to fill in writing on the product page, never a value the procurement manager assumes from the brochure.
The packet sits at the back end of a chain the sibling articles own. The office building as a layered specification — what belongs to the building, what belongs to the door, and what crosses between them honestly — is the framing in smart locks for office buildings. The base-building versus tenant-demised scope split is the technical resource in smart locks for large office buildings. The single-tenant corporate-credential governance view is the guide in smart locks for corporate offices. This article converts those arguments into the paper a procurement manager can actually send: the door schedule the facilities lead signs, the credential class matrix the CISO signs, the to verify in writing capture the supplier answers in writing, the packaging and marking ask the warehouse accepts against, and the acceptance table that makes a 200-door to 800-door order auditable from kickoff to dock.
The site flow this packet runs is the factory's standard four-stage procurement flow: (1) select model, (2) confirm quantity and customization, (3) production, (4) shipping. The packet is organized to match. Sections 1 to 3 close out Stage 1. Section 4 and Section 5 close out Stage 2. Section 6 carries the per-stage evidence through Stage 3. Section 7 carries the per-carton evidence into Stage 4. Section 8 closes the packet with the sign-off block.
The packet is written for two readers. The facilities lead or building owner reads it as a coverage document — does every door in the building have a row, and does the row cover what the building actually needs. The procurement manager reads it as an order document — does every value the supplier will quote against have a confirmation in writing behind it, and does the acceptance table catch a defective lot before it ships.
How to Use This Packet
The packet runs in one direction. Each stage produces artefacts that the next stage cites.
Stage 1 — Select model. Section 1 names every door in the building by its scope layer, hardware context and risk class, and produces the Per-Door Schedule. Section 2 maps each door to a credential class — tenant-staff, contractor-windowed, visitor-windowed, executive, IT-room, glass-partition — and produces the Credential Class Matrix. Section 3 captures, for every shortlisted model, the to verify in writing attributes the supplier has to answer in writing on the product page before the model is allowed into Stage 2. The exit artefact from Stage 1 is a signed per-door model line with no remaining open specification items.
Stage 2 — Confirm quantity and customization. Section 4 aggregates the per-door lines into the Quantity and Customization Confirmation, which carries door counts, finish, handing, app/admin platform, language pack, lock-side options, mechanical-key plan, packaging and marking ask, and the order-cohort cut. Section 5 closes the customization asks. The exit artefact from Stage 2 is a signed line-by-line confirmation that locks the order against late drift.
Stage 3 — Production. Section 6 carries per-stage acceptance evidence — sample approval, first-article inspection, mid-run sample, pre-shipment inspection — and is the packet's quality ledger.
Stage 4 — Shipping. Section 7 carries the per-carton manifest, the packing list, the per-door-class carton tag, the batch/lot code, and the dock-receipt acceptance table.
The packet's design discipline is consistent across all four stages: no value the supplier asserts without the supplier writing it back. That discipline is what makes the packet enforceable.
A note on what is not in the packet. There is no price column, no MOQ column, no lead-time column, no warranty column, and no certification column. Pricing, MOQs, lead times, warranty and certifications are quote and contract documents, not procurement packet documents, and the factory's quote-based commerce means the figures only arrive at the quote stage. The packet carries every fact that must be true about the order; the quote carries every figure the supplier will charge for it. The two are deliberately kept apart.
Section 1 — Per-Door Schedule
The per-door schedule is the spine. It captures every smart-locked door in the building, in the order the procurement manager needs to buy them, and against a row schema the supplier can answer.
| Column | Definition | Format / Source |
|---|---|---|
| Door ID | Building-floor-room code or suite number | Internal site code |
| Scope layer | Tenant-demised / common (in-suite) / back-of-house / glass partition / IT / plant | Sibling 339 scope split |
| Door type | Solid-core timber / hollow metal / aluminum-framed glass / solid-core fire-rated / narrow-edge aluminum | Site survey |
| Door thickness (mm) | Measured leaf thickness at latch height | Site measurement |
| Handing | Left-hand (LH) / Right-hand (RH) / Left-hand reverse (LHR) / Right-hand reverse (RHR) | Site measurement |
| Existing bore / prep | TRUE — single bore / cross bore / no bore / mortise / cylinder-only | Site measurement |
| Frame / reveal | Aluminum frame / hollow metal frame / wood frame | Site survey |
| Environment | Interior dry / interior humid (kitchen, plant) / exterior canopy / loading dock | Site survey |
| Egress class | Free egress / controlled egress / fire-rated egress door | Site survey + AHJ |
| Risk class | High (IT, archive, finance, executive, glass partition) / Standard (leather, meeting) / Low (back-of-house service) | CISO / facilities lead |
| Credential class | OPEN E — see Section 2 | Credential class matrix |
| Shortlist model | Candidate model from catalog | Section 3 to verify in writing |
| Qty | Number of doors on this line | Quantity roll-up |
| Finish | Matte black / satin nickel / stainless 304 / stainless 316 (for custom housing) | Supplier finish sheet |
| Notes | Anything the supplier should know about this door | Permitted by row |
A building's per-door schedule will typically run from sixty rows for a single-tenant mid-rise to several hundred rows for a multi-tenant class-A tower. The packet does not constrain row count; it constrains schema. Every door that carries a smart lock has to have a row, and every row has to have all fourteen columns.
The door-thickness column is a measurement the facilities lead signs, not a number the supplier assumes. Most smart locks in the 79-model catalog fit a stated door-thickness band — for hotel-class hardware such as the SLK-9936S the published band is 36–100 mm, for narrow-edge class hardware the band is narrower — but the per-door measured figure at latch height is what the supplier matches against, not the band. Mismatch between the measurement column and the supplier's door-fit envelope is the single most common cause of a smart lock arriving on site that does not physically fit the door.
The existing-bore column decides whether retrofit or new-build hardware goes on the door. An existing mortise pocket that is 100 mm wide and a new lock that wants 54 mm cross bore is a non-trivial re-work the procurement packet has to surface before the order, not after. The packet leaves the retrofit decision to the site survey but refuses to let the survey arrive as a phone call the day before delivery.
The egress column decides whether the door is in scope for a smart lock at all. Doors that are required by local code to fail-secure on power loss with mechanical-only egress, doors that are part of a fire-rated means-of-egress, and doors under panic-hardware control all need the authority having jurisdiction (AHJ) sign-off before they enter this schedule. A procurement packet that omits the AHJ sign-off on an egress-class door is a packet the supplier will rightly refuse to ship against.
Section 2 — Credential Class Matrix
The credential class matrix maps each door's risk class to a credential vocabulary — who can be issued what, on what lane, for what window. The matrix is the input the supplier needs to size the credential capacity, the audit-log depth, and the per-credential time-bounded support on each shortlisted model.
| Class | Population | Primary credential | Secondary lane | Window | Audit | Mechanical override | Open network? |
|---|---|---|---|---|---|---|---|
| A — Tenant staff (permanent) | Full-time employees on the lease | PIN or RFID card | App token (TTLock / Tuya / Doodle lane per model) | Standing | Per-event, retained for door-life | Required, two keys | Yes, app lane |
| B — Tenant staff (after-hours) | Late workers, weekend staff | PIN (time-bounded) | RFID card (standing) | Time-window only, e.g. weekday 18:00–23:00 | Per-event, time-window flag | Required | Yes |
| C — Contractors (windowed) | Plant, cleaning, fit-out vendors | Time-bounded PIN (start/end datetime) | Card (named) if recurring | Hard cutoff, no implicit renewal | Per-event, contractor-ID linked | Required | Yes |
| D — Visitors (escorted) | Pre-booked guests, candidates | One-time PIN (date-valid) | Reception-issued card | Issue-window only | Per-event, host linked | Reception-only | Yes |
| E — Executive | C-suite, board, HR / finance / legal | PIN + biometric (fingerprint) | Card (named) | Standing | Per-event, segregation from tenant class | Required, two-key | Limited |
| F — IT / Server / Archive | IT staff, audit, named server access | Biometric + PIN (dual-auth where supported) | Card (named, rotation) | Standing with per-credential expiry | Per-event, retention longer than Class A | Required, two-key, sealed envelope | Yes |
| G — Glass partition (interior) | Tenant staff, visitor (escorted) | PIN | Card (standing) | Standing | Per-event | Optional | Yes |
| H — Back-of-house service | Cleaning, plant, vending | Time-bounded PIN (window) | Card | Daily window | Per-event, retained briefly | Required | Yes |
A building's credential class plan typically uses five or six of these classes, not all eight. A small office will run A + C + G + H. A multi-tenant class-A tower will run all eight because each tenant takes a different mix of executive floors, general workspace, IT, glass-partition meeting rooms, and back-of-house service corridors.
The matrix is the CISO's document, not the procurement manager's. The procurement manager uses it to set the to verify in writing questions the supplier has to answer — per-credential time-bounded support, per-credential revocation latency, audit-trail retention per model — but the population and window columns belong to the security and HR director.
The "open network?" column is honest about scope. It names whether the credential can be administered by the tenant's IT or admin team from a phone or web console. App-lane administration exists on the catalog models that carry a TTLock, Tuya or Doodle lane, but not on every model, and the to verify in writing capture for each shortlisted model has to specify which lane that model supports. The factory makes no claim about enterprise SSO, channel-manager / OTA / access-control-panel / BMS integration — those are upstream systems the door layer does not address and the credential class matrix does not promise.
The mechanical-override column is mandatory on every door that is not a fire-rated means-of-egress door under panic-hardware control. A smart lock without a mechanical override is a door the fire service cannot reliably open under power loss; the credential class matrix flags this as required on every row, and the acceptance table in Section 6 makes it a per-door check.
Section 3 — to verify in writing Spec Capture (Stage-1 Exit Gate)
The to verify in writing capture is the discipline that makes the rest of the packet enforceable. For every model on every door in the per-door schedule, the supplier has to answer the same set of questions in writing on the product page or in a signed letter. The capture sheet is a worksheet the procurement manager fills in once per shortlisted model, with a column for each question, a column for the supplier's written answer, and a column for the procurement manager's sign-off.
| # | Question the supplier has to answer in writing | Why it matters | Where to verify |
|---|---|---|---|
| 1 | Door-thickness range this model fits (mm) | Match against the per-door measured figure | Product page spec block |
| 2 | Door-hand compatibility (LH / RH / LHR / RHR) | Mismatch locks the door | Product page spec block |
| 3 | Bore / cross-bore dimensions (mm) | Retrofit-vs-new-fit margin | Product page spec block |
| 4 | Credential classes supported (PIN / RFID / fingerprint / face / app / mechanical) | Match against Section 2 class | Product page spec block |
| 5 | Per-credential time-bounded support (yes / no, min/max window) | Class B / C / D / H windows | Product page + admin manual |
| 6 | Per-credential expiry / auto-revocation | Class B / C / D drift prevention | Product page + admin manual |
| 7 | Maximum credential count per lock | Class A roster size | Product page spec block |
| 8 | App platform supported (TTLock / Tuya / Doodle / none) | Class A / E / G app lane | Product page spec block |
| 9 | Audit / event records buffer and retention behavior | Class A / E / F evidence | Product page spec block |
| 10 | Audit retrieval surface (app / web / export format) | All classes, but especially E / F | Product page spec block |
| 11 | Mechanical override cylinder spec (5-pin / 6-pin / other) | All classes, mandatory | Product page spec block |
| 12 | Battery format (AA / AAA / 18650 / other) and battery-cycle claim | Rotation cadence | Product page spec block |
| 13 | Battery low-warning channel (LED / beep / app push / none) | Rotation cadence | Product page + admin manual |
| 14 | Power-loss behavior (fail-secure / fail-safe / configurable) | All classes | Product page spec block |
| 15 | Environmental range (operating temp / humidity) | Class H, exterior canopies, humid plant | Product page spec block |
| 16 | Finish options available | Per-door finish column | Supplier finish sheet |
| 17 | Handing options available | Per-door handing column | Supplier finish sheet |
| 18 | Mechanical-key plan (keyed-alike / keyed-differently / master-key) | All classes | Supplier keying plan |
| 19 | Multi-door admin structure (single lock / multi-lock per app / multi-property) | Multi-tenant buildings | Product page + admin manual |
| 20 | Spare-parts and firmware policy (versioning, change-control, end-of-life) | Long-life procurement | Supplier letter |
Twenty questions. Every model on the shortlist carries a row of twenty. If any cell of any row returns blank — or returns a brochure value the supplier will not sign for in writing — the model is not allowed into Stage 2. That is the discipline. The packet refuses to let a brochure value masquerade as a procurement value.
Two cells of the capture sheet are first-party data and the rest are documentation. The product-page-documented first-party block for the SLK-9936S — 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, multilingual management software, standalone or centralized database modes — is the documentation-granularity ruler the packet names once. It belongs to the SLK-9936S hotel lock. The packet will not port the 36–100 mm figure to a narrow-edge class lock or the 4 × AA cell-format to a 18650-class lock. Every non-SLK-9936S cell in every row returns the verb "check the model’s published specification" by supplier discipline.
The fact_requirements line on the article front-matter echoes the discipline. No per-model attribute is asserted in the packet text. Where the packet names a figure (the SLK-9936S door-thickness band, the SLK-8831 5-in-1 multi-method class), the figure is anchored to the product page or to a catalog fact used only as a confirmation surface. Where the packet needs a per-building answer (the per-door measured thickness, the per-credential time-bounded window on the Class C line), the answer is captured by signature, not assumed from a brochure.
Section 4 — Quantity and Customization Confirmation (Stage-2 Entry)
The Quantity and Customization Confirmation rolls the per-door schedule into the order. The schema is one row per unique configuration. A building with 200 doors may have 14 configurations (one row per model × finish × handing × keying-plan combination) rather than 200 rows. Each row carries a unit count, a customization block, and the to verify in writing reference.
| Config ID | Model | Finish | Handing | Bore / prep | App platform | Credential class set | Keying plan | Language pack | Qty | Reference |
|---|---|---|---|---|---|---|---|---|---|---|
| C-01 | — | — | Per door | Per door | TTLock / Tuya / Doodle / none | A, B | Per door | Per door | Per door | S-3 row N |
| C-02 | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... |
| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... | ... |
Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.
The unit count column is the quantity that goes on the purchase order. It is not the per-door count from Section 1 alone — it includes the order-cohort cut (initial tranche vs reorder tranche), the sample-fit quantity, the production spread (per cohort per month), the sample-replacement quantity, the warranty-replacement reserve, and the demo / showroom reserve. Each sub-line is documented.
The customization block lists every change the supplier has to make to the catalog SKU before production. Customization is the OEM/ODM lever: logo on the housing, finish colour, language pack, packaging artwork, manual language, app white-label, carton marking, batch/lot code format, mechanical-key numbering, and instruction insert. Each ask is named in the customization block, and each ask is paired with the asset the buyer has to provide (artwork file, language list, key-numbering scheme, carton artwork) and the format the asset has to arrive in. Customization asks that arrive without assets stop the line.
The order-cohort cut is the discipline that keeps the procurement from collapsing into one giant order. A 600-door order is typically split into tranche 1 (sample fit, ~6–12 units), tranche 2 (pilot floor, ~10–20% of total), and tranche 3 (the balance). The packet treats each tranche as its own order on the same pricing schedule but with its own acceptance test, its own to verify in writing re-confirmation, and its own sign-off. The cohort cut is what makes a 200-door or larger order auditable.
The sample-fit quantity is small but non-negotiable. The packet refuses to let tranche 2 ship before the supplier has shipped a sample-fit quantity that the facilities lead has measured on real doors. The sample-fit is not a free unit. It is a procurement line with its own acceptance criteria (door thickness measured, bore measured, handing observed, finish verified, mechanical override verified, app lane verified, audit verified) before tranche 2 is released.
Section 5 — Customization Asks (Stage-2 Detail)
The customization block from Section 4 expands into a stand-alone register. Each ask is one row. The register is the input the supplier's OEM coordinator and the buyer's brand / facilities lead both sign.
| Ask | Asset buyer provides | Format | Owner | Sign-off |
|---|---|---|---|---|
| Logo on lock housing (front) | Vector artwork (AI / EPS / PDF) | Per supplier template | Brand | Required before production |
| Logo on lock housing (rear) | Vector artwork | Per supplier template | Brand | Required before production |
| Finish colour (non-catalogue) | Reference sample or RAL / Pantone code | Physical sample or code | Facilities lead | Required before production |
| Language pack — admin manual | Translated file per language | Per supplier template | Brand lead | Required |
| Language pack — quick-start insert | Translated file per language | Per supplier template | Brand lead | Required |
| Language pack — carton marking | Translated file per language | Per supplier template | Brand lead | Required |
| App white-label (logo, colour, name) | App-store assets | iOS / Android spec | IT lead | Required for app-lane models |
| Carton artwork | Print-ready file | PDF / AI per supplier die-line | Brand lead | Required before production |
| Carton marking — batch / lot code | Code scheme | Per supplier template | Procurement | Required |
| Mechanical-key numbering | Numbering scheme | Per supplier template | Facilities lead | Required |
| Master-key profile | Keying plan | Per supplier template | Facilities lead | Required for keyed-differently plans |
| Instruction insert | Copy / artwork | Per supplier template | Brand lead | Required |
Customization asks that affect more than one batch need a sign-off block named "for this order and any reorder against the same SKU within 12 months." The packet refuses to re-run a customization ask every time a reorder goes through. The OEM coordinator agrees once to the asset package, and the brand / facilities lead agrees once to the asset receipt, and reorder overwrites nothing except re-running.
Customization asks that change the door-fitting envelope of the model — modified bore, modified handing, modified latch — are not allowed at the customization stage. Those asks change the model itself, not the brand on the model. They are routed back to Section 3 as a different shortlist model, not forward as a customization. The packet refuses to let a hidden re-engineer masquerade as a logo change.
Section 6 — Production Acceptance Table (Stage 3)
Production acceptance is a four-pass table that walks the order from sample fit through pre-shipment inspection. Each pass produces a sign-off line. No pass can be skipped. No pass can be batched.
| Pass | What the supplier demonstrates | What the buyer verifies | Acceptance test sign-off | Failure consequence |
|---|---|---|---|---|
| P1 Sample fit | One unit per shortlisted model, configured per the customization block, on the sample-fit doors | Door thickness measured, bore measured, handing observed, finish verified, mechanical override verified, app lane verified, audit verified | Sample-fit acceptance form | Tranche 2 cancels |
| P2 First-article inspection | First 5–10 production units of tranche 2 against the Section 4 configuration | Door thickness measured, bore measured, handing observed, finish verified, mechanical override verified, app lane verified, audit verified, to verify in writing re-confirmed | First-article sign-off | Production restarts |
| P3 Mid-run sample | A unit pulled at the mid-point of the production run, configured per the configuration row | Mechanical override verified, app lane verified, audit verified, finish re-checked, batch / lot code matches carton marking | Mid-run sign-off | Production re-samples |
| P4 Pre-shipment inspection | A unit-per-cohort sample before carton sealing, configured per the configuration row | Mechanical override verified, app lane verified, audit verified, batch / lot code matches carton marking, language pack matches, carton artwork matches | Pre-shipment sign-off | Shipment halts |
The four-pass table is the per-stage evidence the packet carries into Stage 4. The sign-off lines live in the same document as the per-door schedule, the credential class matrix, the to verify in writing capture, and the quantity confirmation. There is no separate "QC report" — there is one document the procurement manager and the supplier both sign at each gate.
The P1 sample fit is the gate the factory takes most seriously. If the sample-fit unit fails on door thickness, the order shortlist changes — not the sample. The packet's discipline is that a failing sample is evidence about the model, not about the door, and the wrong response to a failing sample is to push the order through anyway. The right response is to re-run the shortlist.
The P3 mid-run sample is the gate that catches drift. Production runs drift when a mould wears, when a batch of components arrives with a tolerance change, when a finish supplier changes a process. The mid-run sample pulls a unit at the production midpoint and re-verifies the to verify in writing items. Drift caught at mid-run cost is a re-sampling, not a re-order.
The P4 pre-shipment inspection is the last gate the packet owns. After P4, the order is in cartons, on a pallet, and out of the factory's hands. Section 7 carries the per-carton evidence into Stage 4.
Section 7 — Packaging and Marking Asks (Stage 4 Entry)
Packaging and marking are the buyer's last chance to control how the order is received. The packaging-and-marking ask table is the discipline that catches a missing unit, a mis-carton, a wrong batch code, a forgotten mechanical key, a wrong-language insert, before the carton is opened on site.
| Ask | Format | Per-carton | Per-door | Sign-off |
|---|---|---|---|---|
| Carton weight (kg) | Per supplier standard | Required | N/A | Required |
| Carton dimensions (L × W × H, mm) | Per supplier standard | Required | N/A | Required |
| Cartons per pallet | Number + pallet pattern | Required | N/A | Required |
| Pallet weight (kg) | Per supplier standard | Required | N/A | Required |
| Pallet dimensions (L × W × H, mm) | Per supplier standard | Required | N/A | Required |
| Pallet wrap / weather protection | Per shipping lane (sea / air / courier) | Required | N/A | Required |
| Per-door-class carton tag | Sticker / print on carton, naming door class and cohort | Required | N/A | Required |
| Per-carton batch / lot code | Format agreed in Section 5 customization | Required | Required | Required |
| Per-carton count vs order count | Packing list line per carton | Required | N/A | Required |
| Mechanical-key per carton | Sealed envelope per carton, key count named, key numbers listed | Required | Required | Required |
| Master-key envelope per cohort | Sealed envelope per cohort, key count named, custody signature line | Required | Required | Required |
| Per-door mounting drawing | Per model, sealed in plastic, language per carton | Required | Required | Required |
| Per-door installation hardware bag | Sealed bag, screws / spindle / strike / fixings, count matched to door count | Required | Required | Required |
| Quick-start insert | Per language card, one per door | Required | Required | Required |
| Warranty card | Per supplier template, one per door | Required | Required | Required |
The per-door carton tag is the single most important packaging ask on a multi-door order. A 600-door order that arrives on six pallets without per-door-class carton tags is a 600-door order the warehouse cannot stage. Per-door-class tags — naming the model, the finish, the handing, the cohort, the door count — turn a pallet into a kit the warehouse can deliver to the right floor without re-counting.
The mechanical-key per-carton ask is the second most important. A smart lock that arrives without its mechanical override key is a door the building cannot open under power loss. The packet refuses to let a sealed envelope go un-named. Key counts, key numbers, sealed-envelope integrity, and the custody signature line are all per-carton line items.
The batch / lot code is the discipline that makes the warranty-honest documentation possible. When the building's facilities lead files a service event six months after handover, the supplier needs to know what batch the unit came from. The batch / lot code on the carton, on the lock body, and on the warranty card all match. The packet refuses to let one of those three match the other two.
Section 8 — Dock-Receipt Acceptance Table (Stage 4 Exit)
The dock-receipt acceptance table is the gate that catches a defective order before it crosses the loading dock. The packet treats the dock receipt as a per-carton audit, not a per-pallet handshake.
| Check | Per-carton | Per-pallet | Per-order | Sign-off |
|---|---|---|---|---|
| Carton count vs packing list | Required | Required | Required | Required |
| Per-carton batch / lot code matches Section 5 | Required | Required | Required | Required |
| Per-door-class carton tag matches the cohort | Required | Required | Required | Required |
| Per-carton mechanical-key envelope present and sealed | Required | Required | Required | Required |
| Per-carton mechanical-key count matches carton count | Required | Required | Required | Required |
| Per-carton installation hardware bag present and count matched | Required | Required | Required | Required |
| Per-door mounting drawing language matches the cohort | Required | Required | Required | Required |
| Quick-start insert language matches the cohort | Required | Required | Required | Required |
| Warranty card count matches door count | Required | Required | Required | Required |
| Pallet weight and dimensions match Section 7 | N/A | Required | Required | Required |
| Pallet wrap / weather protection intact | N/A | Required | Required | Required |
| Visible damage to carton (water, impact, crush) | Required | Required | N/A | Required |
| Visible damage to lock body on first-carton open | Required | N/A | N/A | Required |
A damage with failed dock receipt is a refusal, not a discount. The packet treats a damaged unit on a sealed pallet as evidence that the order did not survive the shipping lane, not as evidence of a unit the buyer can accept at a discount. The dock-receipt refusal is the buyer's right under the per-carton audit, and the supplier's signature on the packet is the buyer's authority to exercise it.
The first-carton open is the buyer's right and the buyer's responsibility. Opening one carton per cohort to inspect the lock body, the finish, the mechanical override cylinder, the app lane, and the audit log is the antenna the packet refuses to skip. The factory expects this. The supplier expects this. The packet refuses to let the first-carton open be a courtesy.
The dock-receipt acceptance table is signed by three named people. The warehouse lead signs the per-carton lines. The facilities lead signs the per-door mechanical-key and installation hardware lines. The procurement manager signs the per-order lines. A signature with a name is the only thing that travels forward into the building's installation phase.
Illustrative Scenario — A 240-Door Multi-Tenant Class-A Office
Consider a 240-door multi-tenant class-A office tower. Three floors are anchor-tenant-demised, two floors are speculative, and the ground floor holds reception, two meeting-room suites, the IT server room, and a back-of-house service riser. Roughly 180 doors are smart-locked under the packet; 60 are mechanical or hold-open fire doors and do not enter the schedule.
The per-door schedule runs to 180 lines. Each line carries fourteen columns. The door-thickness column averages 45 mm for interior solid-core and 55 mm for the entrance and stair-discharge doors. The handing column splits roughly 50/50 LH/RH. The egress-class column flags eight doors for AHJ sign-off before the schedule can be sent to the supplier. The risk-class column flags 14 doors — the IT server room, three HR / finance suites, two archive rooms, the executive boardroom, four glass-partition meeting rooms, two glass-partition reception areas — as Class E or F.
The credential class matrix runs to seven classes: A, B, C, D, E, F, G. The H class (back-of-house service) is on the building's BMS / access-control scope, not the door layer, and is named in the matrix but routed to the upstream scope per the sibling article on large office buildings.
The to verify in writing capture runs to seven shortlisted models. Six are catalog SKUs; one is a custom-finish variation of a single SKU and is captured as a customization ask against the base model. Twenty questions per model, seven rows, 140 cells — each cell returns a signed supplier value or is blank. Two cells return blank on the cylindrical-latch Tuya-class model (the per-credential time-bounded support and the audit retention behavior); those two cells become a re-shortlist conversation that lands on a different model with confirmed written answers, and the packet refuses to let the cylindrical-latch Tuya-class model carry the order without the two answers.
The Quantity and Customization Confirmation rolls the 180 per-door lines into 11 configurations. Tranche 1 sample-fit is 9 units (one per configuration plus spares). Tranche 2 pilot floor is 22 units. Tranche 3 is the balance. The customization block lists the logo on housing (vector artwork from the brand), the finish on one non-catalogue SKU (reference sample from the facilities lead), the language pack (English only on this building), the carton artwork (per supplier die-line), and the mechanical-key plan (keyed-alike on the tenant-demised doors, keyed-differently on the IT and executive doors).
The four-pass production acceptance runs clean. P1 sample fit passes on the 9 units with two observations — the bore on one configuration was 2 mm wider than the catalogue figure and the supplier confirmed a shim; the finish on the non-catalogue SKU was a half-shade off the reference sample and the supplier re-sprayed. P2 first-article passes with no observations. P3 mid-run passes with one observation — the batch / lot code format drifted on 30% of mid-run units and the supplier corrected the carton print mid-run. P4 pre-shipment passes with no observations.
The dock-receipt acceptance table catches one damaged carton. A single carton on the second pallet arrives with visible water damage. The packet's dock-receipt rule refuses the carton, the supplier replaces the unit under warranty, and the building's installation phase is not delayed because the refused carton would have surfaced as a failed unit on day three of installation.
The scenario is illustrative — a shape of project the packet is sized for, not a record of a specific project. The factory has shipped smart-lock components into projects of comparable shape in offices across more than 80 countries over 10+ years. The packet is the document that makes the shape legible before the project starts.
Where This Packet Stops
The procurement packet stops at the dock. From the dock forward, the work moves to the building's installation phase, which is a different document — a per-door install sequence, a per-floor commissioning sign-off, a per-cohort handover file. Those documents are downstream of this packet and are not in scope here.
The packet also stops at the per-door evidence. From the per-door evidence forward, the work moves to the building's operations phase, which is a credential-class-cadence document — a move-in ceremony, a move-out takedown, a lost-credential runbook, an annual reissue rotation. Those documents are also downstream of this packet and are not in scope here.
What the packet does cover is the four-stage flow from model selection through shipping, with each stage's acceptance evidence captured in writing and signed before the next stage begins. Every per-door fact is on the schedule. Every per-model fact is captured on the to verify in writing sheet. Every per-cohort quantity is on the confirmation. Every per-carton artefact is on the dock-receipt table. Every customization ask is named with its asset. Every sign-off is named with its owner.
The packet's discipline is the factory's discipline: a fact not on the product page is a fact not in the order; a fact not in the order is a fact the buyer cannot enforce; a fact the buyer cannot enforce is a fact the building will discover on the day it matters.
For the boundary that this packet sits inside, smart locks for office buildings is the editorial frame and smart locks for large office buildings is the technical scope split. For the single-tenant corporate angle, smart locks for corporate offices is the guide. For the catalog of door types the packet can fit against, the keypad door lock, fingerprint door lock, RFID door lock, Bluetooth lock, and glass door locks category pages index the candidates.
To run this packet against a real building, the procurement manager opens a quote request carrying the per-door schedule and the credential class matrix as the inputs the supplier quotes against. To bring a sample-fit unit into the building for the P1 sample-fit pass, the sample order page starts the tranche 1 conversation. To send the same packet to a multi-property procurement team, the catalog request page is the route. The manufacturing page is the route to the OEM / ODM coordination that the customization block in Section 5 sits inside.
The packet is the paper. The building is the work. The two meet on the dock.

