The supplier due-diligence checklist treats the supplier as an entity you might have to sue and checks whether it can be sued.

投稿日時: 12月 10, 2024

Smart Lock Supplier Evaluation Checklist

Smart Lock Supplier Evaluation Checklist

You picked the supplier. The contract is signed, the first containers cleared, and the locks are on doors. That is the moment most buyer checklists stop working — because they were built to answer should I choose this company, not is this company still earning my business every month after. A supplier you approved in a spreadsheet can quietly rot: shipments drifting later, finish changes you never sanctioned, warranty replies taking a week instead of a day. None of that shows up in a due-diligence report. It shows up only if you score it on purpose.

Definition, up front:A smart lock supplier evaluation checklist is a weighted, repeatable scorecard that rates an incumbent supplier on ongoing performance — delivery reliability, batch-to-batch quality consistency, communication, change-control discipline, after-sales responsiveness, documentation, commercial adherence and corrective-action behavior — so a procurement team can decide, with a defensible number, whether to keep the vendor on the preferred list, place it on watch, or move it to probation.

This is the operational cousin of two other pages on this site. verifying the manufacturer before the order proves the product and the line before you commit. the supplier due-diligence checklist treats the supplier as an entity you might have to sue and checks whether it can be sued. Neither one helps you six months after the PO. This page, 033, is a fill-in-the-blanks form for the relationship you are already in. Print it, weight it, and score the vendor you have — not the vendor you hoped for.

Where this form sits: evaluation, not due diligence or verification

The three activities get blurred in buyer conversations, and the blur is why teams keep re-signing a supplier that is quietly failing them. Put a pin in the differences.

ActivityQuestion it answersWhen it runsWhat it looks atPage
VerificationDoes the product and the production line actually exist and work?Before the first orderDocuments, samples, inspection, pilot batch004
Due diligenceIs the business entity real, solvent and enforceable?Before money movesRegistration, ownership, finances, disputes, references030
Performance evaluationIs the incumbent still good enough to keep, and where is it slipping?Recurring, after awardDelivery, quality, communication, change control, after-sales033 (this page)

Verification and due diligence are one-time gates at the front door. Evaluation is a gauge you read on a schedule. A supplier passes the first two once and can fail the third every quarter if nobody is measuring. The rest of this article builds that gauge.

Answer box:What is the difference between supplier due diligence and supplier performance evaluation? Due diligence screens the supplier entity (registration, finances, disputes) before you buy, to verify in writing it is safe to contract against. Performance evaluation scores the supplier's behavior (delivery, quality, change control, after-sales) repeatedly after you buy, to verify in writing it still deserves the business. One is a front-door gate; the other is a recurring maintenance check.

How to score: the 1–5 anchor scale and the weighting math

Every criterion gets a raw score of 1 to 5. Multiply the raw score by the criterion's weight (expressed as a percentage of a 100-point budget) and divide by 5. Add the eight weighted contributions and you have a total out of 100. That is the entire method — one rule, no exceptions.

Weighted contribution = Weight (%) × (Raw score ÷ 5)
Total score = sum of the eight weighted contributions → maximum 100

Keep the raw scores on the same anchor scale for every criterion so the number means the same thing whether you are grading delivery or after-sales.

RawAnchorPlain meaningConsequence for the relationship
1FailingRepeated misses, no visibility, no fix in sightBreaks the program; grounds for re-sourcing
2WeakFrequently off-standard; you compensate manuallyCostly to work with; probation
3AcceptableMeets the base expectation with occasional slipsKeep, but with a named watch item
4StrongReliably meets the expectation; proactive when it slipsPreferred
5ExcellentBeats the expectation and tells you before you askStrategic / first-call supplier

Two working rules prevent the most common scoring errors. First, score from evidence you logged, not from the last shipment's mood. Second, if you cannot point to a record for a score, it defaults to 2 — the absence of evidence is not evidence of quality.

The eight criteria and how the 100 percent is split

Weights are where your strategy lives. A buyer who runs 24-model hotel programs should weight quality consistency and change control above flashier factors, because a single unnotified component swap can stall an install. A distributor chasing breadth may weight delivery and communication higher. The default split below is tuned for an ongoing B2B lock program; adjust it to your own risk, but keep the weights summing to 100%.

#CriterionWeightWhat it measures
1Quality consistency (batch-to-batch)20%Does every shipment match the approved sample, spec and finish?
2Delivery reliability18%Do promised dates hold, and do you hear about slips early?
3Change-control discipline14%Are component, firmware or process changes notified and re-approved?
4Communication responsiveness12%Reply speed, clarity, and ownership of open questions
5After-sales and warranty support12%Time-to-first-response and time-to-resolution on defects
6Documentation and traceability8%Batch records, test reports, packing accuracy
7Commercial and contract adherence8%PO terms, packaging, labeling, shipping-document accuracy
8Corrective action and improvement8%Does a reported problem actually get prevented from recurring?
Total100%

The math is deliberately conservative on the two factors that compound: quality consistency and delivery reliability together carry 38% because a defect or a late container lands on a job site, not in a filing cabinet. Change control carries 14% because it is the failure mode buyers describe as the one that hurt most — a supplier who quietly substituted a part is not making a mistake, it is making a decision about your project without you.

Answer box:Which supplier-evaluation criterion is most often under-weighted by buyers? Change-control discipline. Buyers score delivery and quality heavily but leave change control unweighted, so a supplier that swaps a cylinder, reader module or firmware version without re-approval never loses points — even when that single silent change triggers field failures weeks later.

The blank scorecard — tear-off evaluation form

This is the form. Fill one row per criterion, then total the last column. The evidence column is what makes the score survive a management review — keep it to one line each, dated.

#CriterionWeightRaw (1–5)Weighted = Weight × Raw ÷ 5Evidence (record + date)
1Quality consistency20%______
2Delivery reliability18%______
3Change-control discipline14%______
4Communication responsiveness12%______
5After-sales & warranty support12%______
6Documentation & traceability8%______
7Commercial & contract adherence8%______
8Corrective action & improvement8%______
Total100%—___ / 100Reviewer / date / signature

Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.

Run one sheet per supplier per review period. Three sheets from three consecutive quarters, side by side, tell you more than any single score: direction matters more than the snapshot. A supplier at 78 and climbing and one at 78 and sliding are not the same vendor.

Delivery reliability: measuring the thing you actually care about

Delivery reliability is not "did it arrive." It is three questions the blank form collapses into one score.

  • Date integrity. Of the shipments in the period, what share arrived inside the confirmed window? Score a slip only against the committed date, not the date you wanted — otherwise you are grading your own optimism.
  • Notice quality. When a slip happened, how far ahead did you learn? A three-day-early heads-up on a two-week delay is a 4; finding out when the truck failed to show is a 1 even if the delay was the same length. The variable you control is your own schedule, and the value of a supplier is how much of that control they hand back.
  • Split and completeness. Partial shipments that strand a job site half-finished count against the date. For a hotel rollout where doors on a floor must be commissioned together, a 70% delivery is a missed delivery, not a small win.

Record the raw counts (shipments planned, on-time, late-with-notice, late-without-notice) in the evidence column. The ratio is your proof; the 1–5 is your judgment sitting on top of it. Do not invent a tolerance band you cannot enforce — if your contract has no agreed delivery window, the honest fix is to add one, not to score against a feeling.

Quality consistency: batch-to-batch conformity on a lock

One approved sample proves a supplier can build the lock. Ongoing quality scoring asks whether it does, every time. Anchor your evidence in the spec you approved, and treat any deviation as a scoring event.

Take a first-party spec you can hold a vendor to — the SLK-9936S hotel lock block, for example: door thickness 36–100 mm, RFID Mifare 1 at 13.56 MHz, read distance 0–5 cm, read time under 0.25 s, 4 × AA power, battery operating cycles above 15,000, audit and event records up to 1,000, 5-pin cylinder, 3-point latch, stainless-steel and alloy body. When a shipment's read range drifts to the edge of that 0–5 cm window, or a cylinder no longer seats to the 5-pin build you signed, the approved spec is the yardstick and the deviation is the score.

Grading prompts for this line:

Signal toward 4–5Signal toward 1–2
Incoming defect rate steady across batchesDefects spiking on a batch you were told was "the same"
Finish/color consistent across lots of the SLK-9962S classVisible finish variation between cartons on the same PO
You run the same checks every receipt and log themYou only discover issues when an installer complains

Consistency scores reward a supplier whose second and twentieth container match the first, which is exactly what the pre-order sample bench in How to Verify a Smart Lock Manufacturer Before Placing an Order cannot tell you.

Communication and change control: the two that surface after the PO

Communication is easy to rate badly ("they're friendly"). Score the mechanics instead: time to first substantive reply, whether one named person owns your account, and whether open questions stay open or get tracked to closure. A supplier that answers a technical query in two days with the right answer scores higher than one that answers in two hours with a guess.

Change control is the criterion buyers wish they had. A lock is firmware, a reader module, a battery plan, a cylinder, a latch mechanism — and any of those can be substituted for a "better" or cheaper part without the price moving. If your supplier changes them without notifying you and getting your sign-off, it has made a decision about your warranty exposure using your money.

Score it like this: any unnotified component, firmware or process change discovered in the period caps this criterion at 2, no matter how good the parts perform in the meantime. A notified change, documented, with an updated sample and your written re-approval, scores 4–5 — even if you ultimately declined it, because the process worked. For OEM/ODM programs, the customization route is where change control bites hardest, because your private-label build is a stack of sub-components a supplier can quietly re-spec. Keep a change log as a standing table; the columns below make it an audit trail rather than a memory test.

Date raisedChange describedParts/firmware affectedSupplier notified in advance? (Y/N)Re-sample provided?Your decisionBatch code first shipped

After-sales responsiveness: warranty support you can time

After-sales is where a supplier's real cost of ownership shows. Score two clocks and one outcome, and resist crediting sympathy.

  • Time-to-first-response. When you open a defect claim, how long until a competent human acknowledges it with something more than "received"? A fast canned reply is not responsiveness.
  • Time-to-resolution. From claim to a working remedy — replacement, rework, or an agreed fix. Track it, because a supplier can be fast at the first and slow at the second.
  • Outcome quality and who carries it. When a batch is genuinely bad, does the supplier own it and ship replacements without a fight, or does every claim become a negotiation? For a lock program, that also means support around the practical: a 4 × AA device deployed across a 120-room property is a different after-sales burden than a wired unit, and whether the vendor helps you manage spare-parts flow is part of the score.

The hidden-reader hotel lock and the 5-in-1 SLK-8831 fail differently — reader faults versus app/connectivity faults — so if you run several categories, score after-sales per category rather than as one blended number. A vendor brilliant at keypad warranty and useless at app warranty is a vendor with a hole in the line.

Documentation, commercial adherence, and continuous improvement

Three criteria, lighter weight, each catching a distinct failure.

Documentation and traceability (8%). Can the supplier produce a batch record, test report, or component provenance on request? Does the packing list match the carton contents? If a field fault traces to lot X, the supplier's ability to tell you what went into lot X is worth scoring — it is what turns a one-off replacement into a contained problem.

Commercial and contract adherence (8%). PO terms honored, labeling and packaging to spec, shipping documents accurate. Failing here costs you demurrage, re-labeling labor and re-work you absorb quietly. Score it so the absorbed cost becomes visible on the vendor file.

Corrective action and improvement (8%). The test is simple and brutal: when you reported a problem last quarter, did it come back? A supplier that fixes the instance scores 3. One that tells you the root cause and the control that prevents recurrence scores 5. One that fixes nothing and hopes you forget scores 1. This is the criterion that separates a vendor you can grow with from one you merely tolerate.

Worked example: scoring a hotel-lock supplier at 74.8

Here is one completed sheet, filled to show the math and the reading. Raw scores are illustrative; the arithmetic is exact.

#CriterionWeightRaw (1–5)Weighted = Weight × Raw ÷ 5
1Quality consistency20%420 × 4 ÷ 5 = 16.0
2Delivery reliability18%318 × 3 ÷ 5 = 10.8
3Change-control discipline14%414 × 4 ÷ 5 = 11.2
4Communication responsiveness12%512 × 5 ÷ 5 = 12.0
5After-sales & warranty support12%312 × 3 ÷ 5 = 7.2
6Documentation & traceability8%48 × 4 ÷ 5 = 6.4
7Commercial & contract adherence8%48 × 4 ÷ 5 = 6.4
8Corrective action & improvement8%38 × 3 ÷ 5 = 4.8
Total100%—74.8 / 100

Add the weighted column: 16.0 + 10.8 = 26.8; + 11.2 = 38.0; + 12.0 = 50.0; + 7.2 = 57.2; + 6.4 = 63.6; + 6.4 = 70.0; + 4.8 = 74.8. The weights sum to 100 and no raw score exceeds 5, so the ceiling on this sheet is 100 and the total is internally consistent. The reading is as important as the number: this supplier is strong on product (quality 4) and process hygiene (change control 4, communication 5), but its three 3s — delivery, after-sales, corrective action — are where the program will feel pain. The score tells you what to buy more cautiously, not that you must leave.

Turning the score into a decision: tiers and follow-up

A number without a policy is decoration. Map the total to a standing decision so nobody has to relitigate the relationship from memory.

TotalTierStanding decision
85–100PreferredFirst call for new volume; eligible for framework pricing conversations
70–84Approved — watch itemKeep; name the sub-3 criteria and set a written improvement target for next review
55–69Conditional / probationNew orders require sign-off; cap exposure; start a parallel second-source evaluation
Below 55De-list candidateRe-source unless a documented cure plan lands inside one cycle

Two overrides keep the tiers honest. A criterion capped at 2 by the change-control veto rule (an unnotified component swap) moves the whole supplier down a tier regardless of total — one silent re-spec is a trust event, not an arithmetic event. And a supplier that scores high but trends down two quarters running gets reviewed as if it sat one tier lower. The route from raw logs to a tier call, overrides included, runs like this:

flowchart LR
    A["Per-shipment · per-claim logs"] --> B["Quarterly sheet · eight criteria scored 1-5"]
    B --> C["Weighted contribution = weight × raw ÷ 5"]
    C --> D["Total out of 100"]
    D --> E["85-100 → Preferred"]
    D --> F["70-84 → Approved · watch item"]
    D --> G["55-69 → Conditional · probation"]
    D --> H["Below 55 → De-list candidate"]
    X["Unnotified change · criterion capped at 2"] -.->|tier drop regardless of total| G
    Y["Two quarters trending down"] -.->|review one tier lower| F

Run the sheet on a fixed cadence so the trend line exists:

Review depthCadenceWhat gets scored
Standing scorecardQuarterlyFull eight-criterion sheet, one page per supplier
Transactional logPer shipment / per claimOn-time flag, defect flag, after-sales clocks feeding the quarterly sheet
Strategic reviewAnnualFour quarterly sheets read together; tier change; second-source decision

The per-shipment and per-claim logs are why the quarterly score is defensible — they turn the 1–5 from opinion into aggregation.

Illustrative scenario: a 120-room property standardizing on one lock supplier

Consider a boutique hotel group that has standardized room-door access on one vendor across a 120-room property and two smaller annexes. First-year verification and due diligence were clean; the vendor stayed on the preferred list untouched. In year two nobody scored it. Delivery slipped from "confirmed window" to "sometime that week," and because no one logged it as an on-time miss, the ops team quietly re-sequenced installs and absorbed the cost. Then a mid-program reader-module revision shipped without notice — it worked fine, but the group had to re-test commissioning software against a build it had not approved.

Had the quarterly sheet been running, the same facts would have landed as: quality 4 (field failure rate stayed low), delivery 2 (a logged pattern of unannounced misses), change-control 2 (the unnotified module revision, hard-capped by the veto rule), after-sales 3. Three weighted lines would have pulled the total under 70, moving the vendor from Preferred to Conditional and forcing a second-source conversation before the next property, not after a bad batch strands it. The scenario is illustrative — the point is that none of it required a disaster, only an unmeasured drift. Ongoing evaluation is what converts absorbed pain into a number that triggers a decision.

What this looks like from the factory side

A buyer reading only the left-hand page of this relationship would assume a weighted scorecard is adversarial. It is not, and the manufacturers worth keeping tend to prefer it. A supplier that knows it is scored on change control, documentation and after-sales time-to-resolution is nudged toward the behaviors that make your program cheap to run, and a factory that has invested in an OEM/ODM process is not threatened by a buyer asking for batch records. If you want the relationship to be productive, hand the vendor the same sheet you grade it on and agree what a 4 and a 5 look like. A supplier that flinches at transparent criteria is telling you something; a supplier that asks for the log format is behaving like a partner. Scoring an incumbent is not punishment — it is how a preferred list stays earned rather than inherited.

When a review puts a supplier on watch or probation, that is also the trigger to test the market with clean information: what you now know you need (change-control guarantees, faster after-sales clocks, tighter delivery windows) is exactly the specification to carry into a fresh comparison, so a second source is chosen against your real requirements rather than a price column.

Answer box:How often should a smart lock supplier be re-evaluated? On a fixed quarterly cadence for the full weighted scorecard, with per-shipment and per-claim logs feeding it, plus an annual read of four quarters together to set or change the supplier's tier. Recurring measurement is the point — a one-time post-award review catches nothing that drifts.

Run the sheet on your current vendor list

Print the blank scorecard, set the weights to your own program's risk (the eight-criterion split above is a starting point, not a mandate), and fill one sheet per supplier this quarter using records you can cite. Where the total drops a tier or a 2 appears on change control, log the finding and carry the specification into a second-source comparison so your approved vendor list reflects who actually performs — not who signed first.

Start from the manufacturer overview and the OEM/ODM process to define what a 4 and a 5 should mean for your build, keep the buyer-resources library open while you draft the change log, and when a review sends you to market, request a quote against the requirements the scorecard exposed. If the finding is a business-integrity problem rather than a performance one, that is a different tool — reach for the due-diligence checklist (030) and the pre-order verification checklist (004).

カート
このサイトでの体験を向上させるには、Cookieを許可してください Cookieポリシー
Chat on WhatsApp