Un 38 3 smart lock evidence failures: three UN 38.3 evidence failures blindside smart lock buyers, from sample-only test reports to documents that expire.

Közzétéve:: máj. 01, 2023

Three Ways UN 38.3 Evidence Disappoints Smart Lock Buyers

Three Ways UN 38.3 Evidence Disappoints Smart Lock Buyers

Un 38 3 smart lock evidence failures is the subject of this piece, and every claim below is written so a buyer can check it. A qualification file for a smart lock programme can look finished long before anyone opens it. Specification sheets, a certificate scan, a cell datasheet, and a catalogue line saying the battery is compliant — that is the packet most buyers first receive. Then the consignment is offered to a carrier and the file comes apart in three specific places.

Direct answer. In short, un 38 3 smart lock evidence failures is the subject of this piece. un 38 3 smart lock evidence failures is where the work on un 38 3 smart lock evidence failures sits. un-38-3 is what has to be evidenced before anyone signs. An un 38 3 smart lock evidence failures separates what a supplier can show from what only a body can confirm. un 38 3 smart lock evidence failures is where the two columns start. Each un 38 3 smart lock evidence failures claim names its document.

un 38 3 smart lock evidence failures is used here in the narrow sense set out in un 38 3 smart lock evidence failures. It is a working definition built for un 38 3 smart lock evidence failures. It is not a statutory one, and it has to be read against the market and product concerned.

  • What the maker can evidence — supplier declarations and drawings for un 38 3 smart lock evidence failures
  • What a third party must attest — third-party certificates covering the exact scope of un-38-3
  • What to ask for — the document set that matches the SKU behind un 38 3 smart lock evidence failures
  • Treat this as the un 38 3 smart lock evidence failures sequence, with un 38 3 as the reference.

The three recurring un 38 3 smart lock evidence failures are ordinary, and each one is visible early if you know which document to ask for. This is the account of how they surfaced in one supplier qualification round, told in the order they were discovered: at my desk, at the supplier's, and finally at the port.

The first disappointment begins with a cell, not a lock

The first failure is a scope mismatch that looks like success. You ask a smart lock manufacturer for its lithium transport evidence and receive, within a day, a PDF from a cell producer: a test report on one cell, plus a certificate naming that cell and its manufacturer. You read the title, see a cell, and assume the lock is covered because the lock ships with that cell.

That assumption survives until the pack is opened. The lock ships with four cells of a particular model and a protection board; the report covers a single cell; the certificate scope names a cell rather than a lock; and the bill of materials names a second cell supplier who joined the programme after the report was issued. Nothing dishonest has happened. The evidence is genuine and simply describes a different object.

The remedy is unglamorous: record the cell model, the cell count and the pack configuration for the exact variant on the order, then ask the supplier to confirm in writing that the cell inside the shipped pack is the cell named in the report. Where the bill of materials has moved, request a current report rather than a historical scan. Reading such a report in detail is handled separately in Reading a UN 38.3 Test Report Page by Page: A Smart Lock Buyer Walkthrough. What the buyer's own file needs is in Smart Lock Procurement Checklist for B2B Buyers. The product family this applies to is the smart door locks.

The second disappointment is a document wearing the wrong name

The second failure is administrative, and it is the one most often offered as success. A supplier forwards a file titled Certificate of Conformity. It carries a logo, a date and a signature — and no issuing body, no certificate number and no scope statement, because it is the manufacturer's own declaration, signed by the factory. You file it as third-party evidence and the qualification looks stronger than it is.

This is the most frequent of the un 38 3 smart lock evidence failures and the cheapest to catch. Ask for three things in one line: who issued the document, what is inside its scope, and what number can be verified. If the answer is that the factory issues its own, then the file is a self-declaration and you have bought a lower rung of the evidence ladder than the one you assumed. A marking printed on the product or its label adds nothing further: the marking is the maker's own claim, not a certificate, and it tells you who said what but not who tested what.

The third disappointment happens at the forwarder's desk

The third failure appears late and costs the most calendar time. A carrier or freight forwarder accepts lithium-containing consignments against a bundle: the cell or battery test summary sheet, the safety data sheet, the state of charge, the cell count and watt-hour, the packing instruction and a shipper's declaration. You forward what the supplier sent, and the forwarder asks a question the file cannot answer — how many cells are in the pack on the pallet, and at what charge state.

The second half of this failure is temporal. Certificates carry validity dates and model scopes, while a report describes a sample that existed on a date. Between qualification and container stuffing, the cell was substituted, the pack configuration changed, or the certificate reached the end of its validity and nobody renewed it. The evidence was correct when issued and out of date when needed. Who owns that renewal is a commercial question, not a technical one, and it is worth settling in writing before the order is placed.

What UN 38.3 asks of a battery, and what it never asks

UN 38.3 is a transport test regime for lithium cells and batteries. It asks whether a cell or battery design can be carried safely under the conditions a shipment will impose on it. It does not ask whether a smart lock locks, whether it survives rain, whether it may be fitted to a fire door, whether its radio is approved, or how long its battery lasts. Those are separate questions with separate standards and separate evidence.

The scope discipline is set out in full in UN 38.3 for Smart Locks: Scope, Tests and What the Standard Never Proves. The neighbouring confusion worth naming here is ingress protection, because a lock's IP rating and its transport test results answer entirely different questions, as explained in UN 38.3 Versus IEC 60529 IP Ratings: Which One Applies to Your Smart Lock Door.

CONFIRM-WITH-LOCAL-CUSTOMS-BROKER: the transport documents your destination authority and your forwarder require for a lithium-containing smart lock consignment, and the form in which each must be presented.

Four documents buyers keep swapping for one another

DocumentWho issues itWhat it establishesWhat it leaves open
Test reportA laboratory, on a defined sampleThat one specific design was tested to a defined sequenceThat your production units match that design
CertificateA conformity assessment body, with scope and numberThat a defined scope was assessed by a named bodyWhether the scope names your variant, and how long it holds
Declaration of conformityThe manufacturer or importerThe maker's own legal claim for what it places on a marketAny independent verification of that claim
MarkingPrinted on the product or its labelThat the product carries the claim its maker madeWho tested it, against what, and when

When a buyer says a supplier has UN 38.3, the useful question is which of these four is actually on the table, and whether it names the variant being quoted. A certificate for a cell, a declaration for a lock and a marking on a carton are three different conversations, and they are often folded into one another because all three arrive with a logo on top.

Walking the evidence ladder without skipping a rung

flowchart TD
    A["Marketing image on a catalogue page"] --> B["Self declared declaration of conformity"]
    B --> C["Test report on one sample"]
    C --> D["Third party certificate with scope and number"]
    D --> E["Certificate naming the exact cell in the pack"]
    E --> F["Production control evidence that keeps it valid"]
    F --> G["Carrier accepts the consignment"]

For un 38 3 smart lock evidence failures, the position on this ladder is what the purchase decision turns on.

The ladder runs from a marketing image to production-control evidence, and the common commercial failure is buying at rung two or rung three, then discovering at the port that nothing exists at rung five. For transport evidence the top rung is the decisive one: a certificate that names the exact cell or battery in the pack you are buying, kept valid by production control the supplier can evidence rather than by an assurance that nothing has changed. See Who Pays for UN 38.3 Evidence in a Smart Lock OEM Programme for how that maintenance is usually arranged and paid for. For un 38 3 smart lock evidence failures, the position on this ladder is what the purchase decision turns on.

Qualification questions that expose all three failures

Question to put to the supplierEvidence you should receiveFailure it exposes
Which cell model sits in the pack for the variant I am quoting?Report and certificate naming that cell, with the pack configurationScope mismatch at the cell
Who issued this document, under what scope and number?Certificate with issuing body, scope, number and validityA self-declaration mistaken for a certificate
How many cells ship, and at what charge state?Test summary sheet, safety data sheet, packing instructionRefusal at dangerous goods acceptance
What keeps the evidence valid between orders?Production-control or audit evidence tied to the cell lineEvidence that expires silently

These four questions belong in the supplier qualification file itself, not in a later clarification request. Each one costs a supplier a paragraph of work and a buyer a week of chasing.

Where the paper trail turns up in retrofit and tender work

The same three failures reappear under different labels in two other settings. In a retrofit programme they surface during the site survey, because the battery in the existing installed base may differ from the battery in the quoted unit; UN 38.3 When Retrofitting Smart Locks Onto Existing Doors covers how that changes what you must ask for. In a tender, the same evidence arrives as a scored annex, and the checklist that catches it is set out in UN 38.3 in a Smart Lock Tender Pack: The Evidence Checklist.

The place where most failures are actually created is the RFQ clause itself, because a clause that asks only for a certificate invites a certificate-shaped image. Wording that a supplier can answer is covered in The the Lithium Battery Transport Route Clause: How to Write It So a Supplier Can Respond. Local practice also shapes the answer: UN 38.3 in Japan Purchasing Practice: What Buyers Are Asked to Produce shows how the documentation request shifts by market.

Readers comparing approaches usually start with the smart locks for classrooms. That is the same question un 38 3 smart lock evidence failures has to answer here.

The questions your supplier must answer in writing

Put these in the file, not in a call, and require a dated, signed response naming the cell model and the variant:

  • Which cell or battery model is fitted to the variant quoted on this order?
  • Who issued each document in the evidence pack, and what are its scope and number?
  • Does the certificate cover the cell in the shipped pack, and until when?
  • What production control keeps the evidence valid between deliveries?
  • What are the cell count, watt-hour and charge state at dispatch?
  • Which changes to the pack design trigger a new report, and who is notified?

A supplier who answers all six in writing has already done most of the work that the forwarder will later demand. One who answers two has told you where the file will break.

The last hour before the container is sealed

In the round this account comes from, the consignment was finally accepted because the cell model, the pack configuration and the certificate scope had been reconciled on a single page, and the production-control arrangement had been confirmed in writing by the party responsible for it. Nothing about the lock changed. What changed was the file.

This overlaps with the earlier coverage in how to choose a connected smart lock system. That is the same question un 38 3 smart lock evidence failures has to answer here.This is a buying aid rather than legal or regulatory advice: transport rules, marking rules and market-access regimes differ by destination and shift over time, so route every clause-level question to the published standard text and to the authority or forwarder who will sign off on the consignment. CONFIRM-WITH-LOCAL-FORWARDER: the acceptance criteria your carrier applies to a lithium-containing smart lock shipment, and the deadlines for producing the underlying documents.

If you want the file assessed against these three failure modes before your next order is placed, send the evidence pack as it stands and ask for a gap list — cell scope, document type, validity and production control. That single exercise has caught all three failures more often than any certificate review has.

Close the loop with requesting a quote.

Kosár
A cookie-k engedélyezésével javítható a felhasználói élmény ezen a weboldalon. Cookie-szabályzat
Chat on WhatsApp