EU lvd smart lock RFQ clause: clause wording that splits a smart lock package by power source, names the document type and turns a Low Voltage question.

Publicado em: mar 03, 2023

The Electrical Safety Route in a Smart Lock RFQ: What a Mains-Powered Part Changes

The Electrical Safety Route in a Smart Lock RFQ: What a Mains-Powered Part Changes

Eu lvd smart lock rfq clause is the subject of this piece, and every claim below is written so a buyer can check it. Ask five smart lock suppliers to confirm Low Voltage Directive compliance for a battery-powered mortise lock sold into Germany with a Wi-Fi gateway in the box, and you will collect five different artefacts. One sends a photograph of a mark printed on a carton. One sends a certificate issued to a company with a similar name, covering a product line that has nothing to do with doors. One sends the declaration of conformity for the gateway and calls it product-level evidence for the whole package. One sends a technical file extract with the model list redacted. One sends the right document, for the right models, with a number a buyer can check.

Direct answer. In short, eu lvd smart lock rfq clause is the subject of this piece. eu lvd smart lock rfq clause is where the work on eu lvd smart lock rfq clause sits. eu-lvd is what has to be evidenced before anyone signs. An eu lvd smart lock rfq clause puts self-declared evidence beside third-party confirmation. Every eu lvd smart lock rfq clause claim carries a document type. eu lvd smart lock rfq clause is where those documents are demanded.

  • What the seller can produce — supplier declarations and drawings for eu lvd smart lock rfq clause
  • What only an issuer can verify — third-party certificates covering the exact scope of eu-lvd
  • What to request — the document set that matches the SKU behind eu lvd smart lock rfq clause
  • eu lvd smart lock rfq clause runs this sequence, and eu lvd is the record it produces.

All five answered the same clause. The clause is the variable.

That is the whole argument of this article. A conformity clause is not a formality at the bottom of a procurement document; it is a machine with four bolts, and a buyer who has not specified all four will receive conversation instead of evidence. The bolts are the document type, the model, the issuing party, and the moment by which the artefact must exist. Remove any one of them and the clause still reads as though it means something.

The Low Voltage Directive makes this sharper than most, because its reach depends on how the product is powered rather than on what the product does. A lock body running on cells and a gateway sitting on a shelf in the corridor are governed by different questions, held by different parties, documented in different files. A single blanket clause covering "the smart lock and its accessories" cannot carry both, so it carries neither. Splitting the bill of materials by power source therefore comes before writing a single sentence about it.

What follows is a working clause language for that job, arranged as an argument rather than a manual, ending in a block that can be lifted into an RFQ annex.

A conformity clause is a machine with four missing bolts

Take the sentence that appears in a startling number of smart lock RFQs: the supplier shall provide CE certification for all products. It is short, it sounds unambiguous, and it is unfalsifiable. A supplier can satisfy it with a photograph. Nobody can fail it, because no document type, no model list, no issuer and no date appear anywhere in it. The clause creates no obligation; it creates an opening.

Compare it with a clause that works. The supplier shall, for each model listed in Annex A, provide the declaration of conformity for that model, together with the third-party certificate whose scope names that model, stating the issuing body, the certificate number and the conformity assessment procedure applied, no later than the date on which the first production order is released. That sentence is longer and harder to satisfy, and that is why it produces something a procurement team can file.

Four things are now fixed. The document type is named twice, because a declaration and a certificate do different work. The model is fixed, so the response cannot be a generic family argument. The issuing party is named, which means the buyer can ask whether the body is competent for that assessment. And the moment is fixed, which converts a supplier's vague willingness into a dated obligation attached to a commercial event.

The deeper problem sits underneath the drafting. A standard describes what gets tested. It does not certify a factory, a site or a product line. A certificate is issued by a body that attests conformity within a stated scope and validity. A declaration of conformity is the manufacturer's own legal claim, signed and dated. Marking is the mark itself, applied to a product, a package or a document. These four get collapsed into the phrase "CE certification" more often than any other language problem in this field, and the collapse is what makes clauses vague: once the noun is undefined, nothing else can be checked. Against the catalogue, start from the smart door locks.

The three questions hiding inside every Low Voltage clause

Before drafting, a buyer should be able to answer three questions about the clause, and be able to say what a bad answer to each looks like.

The first is scope: which item on the bill of materials is the clause about? The second is evidence: which document type is acceptable for that item? The third is obligation: which legal entity signs the declaration and stands behind it?

Question the clause must settleWhat a weak clause leaves openWhat the supplier exploitsWhat a complete clause requires
Which item"The smart lock and accessories" as one bundleA certificate for one accessory presented as the packageEvery line in the annex named individually, with a regime answer per line
Which document"Certification"A mark on a carton, a brochure, a family declarationDocument type named per line, with the issuing body identified
Which entityNothingThe seller forwards a file it has no right to rely onThe party that signs, the party that holds the technical file, and the party that answers

A clause that answers the second question but not the first gives the buyer a document with no relation to the goods. A clause that answers the first and third but not the second gives the buyer a promise. Only all three produce a file that survives a question from a client auditor, a tender assessor or a market surveillance authority.

This is the part of the job that gets compressed when the RFQ is drafted by someone who does not have to answer for it later. The clause looks finished, the buyer looks thorough, and the missing answers surface at the wrong moment: after the tooling is cut, after a tender document is being assembled and the supplier's answer turns out to be a mark on a carton. The cost of a missing clause is paid at the moment the evidence is needed and is not there.

Split the bill of materials by power source before you write

Here is the part specific to the Low Voltage Directive, and the reason a generic "is the smart lock LVD compliant" question produces a circular answer.

The Directive applies to electrical equipment designed for use with a voltage input in a specified band, with defined exclusions. The practical consequence for a smart lock package is that the mains-connected items in the box fall inside that description and the battery-powered items generally sit outside it, because there is no mains input to describe. A gateway, a mains power supply, a charging cradle, a door controller, a strike powered at the opening — these are the kind of items that attract the question. A lock body running on cells usually does not, on the basis of its power source alone, although a rechargeable lock with an in-pack charger re-enters the picture through the charger.

The boundary does real work for the buyer, in three ways.

First, it tells you where to send the question. The evidence for a mains-powered gateway sits with whoever built the gateway, which in a smart lock package is frequently a different factory from the one building the lock. A clause addressed to "the supplier" therefore arrives at a company that has never seen the relevant certificate.

Second, it tells you how many conversations you are going to have. If the package contains a lock, a gateway and a charging cradle, that is potentially three separate evidence sets held by two or three parties. One RFQ clause asking for "CE certification for all products" will produce one answer about the lock, because the lock is the only item the responding factory understands.

Third, it stops you from over-claiming in the other direction. A battery lock can still carry a mark for reasons that have nothing to do with mains voltage, because radio equipment and electromagnetic compatibility run on their own tracks. So the correct inference from "battery powered" is not "no mark needed" but "ask which regime the mark was made under". This is the confusion documented in The EU Low Voltage Directive for Smart Locks: Scope, Tests and What the Standard Never Proves, and it is worth reading before drafting so the clause does not demand a document that cannot exist for the model on the order line.

CONFIRM-WITH-LOCAL-REGULATORY-ADVISER: the scope determination for each model in the pack against the current consolidated text of Directive 2014/35/EU, including whether the mains-powered accessories supplied with the lock are treated as placing the package on the market.

The way to express this in the RFQ is not a description of the law. It is an instruction to the supplier to make the determination per line item, in writing, with the reasoning attached. The burden then sits with the party that placed the product on the market and holds the technical file.

Line on the bill of materialsHow it is poweredRegime question the buyer must answerWhere the evidence sits
Lock body, cells onlyCellsDoes a mains input exist at all for this model, and under which regime was any mark appliedWith the lock builder, usually as a written scope statement
Rechargeable lock with in-pack chargerMains chargerWhich party holds the charger evidence, and does every unit ship with that chargerWith the charger's own maker, which may not be the lock builder
Gateway or hubMainsIs the gateway inside the pack being bought, and is its manufacturer the same legal entityWith the gateway maker
Door controller or strike at the openingMains or bus powerIs the field device part of this purchase or a separate submittalWith whoever supplies the field device
Radio module inside the lockRadioWhich regime covers the radio function, and which document is offered for itWith the module maker or the lock builder
Cable and cradle included in the boxMains endDoes the pack contain anything mains-connected at all, and is it declaredWith the accessory maker

The annex this produces is boring and reusable. One row per line item: the model designation as it will appear on the purchase order, the regime question, the document type accepted, the party who holds it, and the date by which it is due. It also lets a buyer compare two suppliers on the same axis, because both answers land in the same row rather than in two different paragraphs of prose.

Name the document, not the mark

The single most expensive word in smart lock conformity language is certification, because it is used for four different artefacts and therefore means none of them. A buyer who wants the declaration and asks for certification will accept the certificate instead. A buyer who wants the certificate and asks for certification will accept a declaration.

DocumentWho issues itWhat it establishesWhat it does not establishThe question to put in the clause
Test reportA test laboratory, on a sampleThat the sample met the test method on the date of the reportThat the model being shipped was the sample, or that production continues to meet itWhich model was tested and how does the sample match what you ship
CertificateA body attesting conformity, with scope and validityThat the named scope is attested, within the stated validityAnything about models outside the stated scopeGive the certificate number, the issuing body and the models listed
Declaration of conformityThe manufacturer, or the party assuming the obligationsThat the party has declared conformity for the named model and cited the requirements it relied onThe underlying test evidence, which may exist and may be withheldWho signed it, in what capacity, and on what evidence
MarkingApplied by the responsible party to product, packaging or documentationThat a mark was appliedThat conformity was assessed, or that anything was testedWhere is the mark applied and which document sits behind it

The wording that follows from this table is short and unglamorous. Use the noun the supplier has to deliver. A test report is not a certificate. A declaration is not a certificate. A mark is not a certificate. Where a clause says "conformity evidence" and lists the accepted document types underneath, the supplier has to choose, and the choice is visible in the reply.

This is also the point at which most RFQ templates quietly widen the net with the phrase "or equivalent". That phrase hands the supplier the argument. An equivalence claim is not an answer, it is a proposal to negotiate the scope of your own requirement, and it will be accepted on the day you are least able to argue. If alternatives are genuinely wanted, make the supplier submit them in advance with a written equivalence argument, addressed to the buyer, before any order is released.

The order of the request matters too. Ask for the document that carries the model list before asking for the document that carries the conclusion. A certificate is a conclusion about a scope; a model list is the scope. Buyers who chase the conclusion first spend the conversation on whether the body is acceptable; buyers who chase the scope first spend it on whether the model is on the list.

Ask for the rung, not the reassurance

Conformity evidence is not binary. It comes in a ladder, and the difference between the rungs is the difference between a file and a folder of photographs.

RungWhat the buyer actually holdsClause wording that asks for itA reply to reject
1 Marketing imageA picture of a mark on a cartonNone, it is not evidenceA photograph, a brochure, a product page extract
2 Self-declared declarationA signed declaration with no third party involvedName the manufacturer, the model and the requirements cited, and require it to be signed and datedA declaration naming a product family rather than a model
3 Test report on a sampleA laboratory report for a sampleRequire the report to identify the sample and the laboratory, and the supplier to state the relationship between sample and modelA report where the sample differs from the ordered model in any material respect
4 Third-party certificate with scope and numberA certificate naming issuer, number and modelsRequire the issuing body, the certificate number, the models covered and the conformity assessment procedureA certificate whose scope does not include the ordered model
5 Certificate covering the exact variantA certificate naming the ordered model and variantRequire a line-by-line confirmation of which annex models appear on the certificateA family level certificate with no mapping table
6 Production control evidenceAudit, incoming control, change controlRequire a statement of the controls that keep the certified configuration in production, and audit rights over them"Production control is in place" with no description

The clause wording is where the ladder gets used. Instead of a general demand for certification, the requirement can be written as a minimum rung with the higher rungs named as the fallback for anything not covered. A clause that accepts a certificate at rung four for models on the certificate, and a test report at rung three plus a signed declaration for models off it, tells the supplier exactly how much work is required and where. That is far more effective than a blanket demand, because the supplier can price the work instead of guessing at it.

The commercial failure mode sits at rung two and rung three. A buyer accepts a self-declared document or a report on a sample, believes the file is closed, and discovers at installation that nothing exists at rung five for the model that actually shipped. By then the design is fixed, the tooling is paid for and the doors are open. Writing the minimum rung into the clause, with the model list attached, closes that gap before it can cost anything.

The detailed evidence ladder is set out in Who Pays for the EU Low Voltage Directive Evidence in a Smart Lock OEM Programme, which is useful at the drafting stage because it separates who should be paying for a rung four certificate from who should be holding it.

Bind the document to the model on the order line

A certificate is a document about a scope, and scopes are written in model designations that rarely match a sales catalogue. The engineering designation, the ordering code, the marketing name and the customer-facing SKU can be four different strings for one article. A clause that names a model loosely, or that lets the supplier nominate the designation after the order is placed, hands over the one piece of information that determines whether the document is relevant.

The clause should require a mapping. For each line in Annex A: the designation used on the purchase order, the designation as it appears on the certificate, and the declaration. Where these differ, the supplier supplies a mapping table that ties them together, dated and signed. That mapping table is also the artefact that survives an internal rebrand, a factory change or a distributor re-listing years later.Variants are where this fails most often. A change of case material, a different radio band, a different power supply, a firmware branch with different radio behaviour, or a different lock case handed to a different door thickness, can each sit outside the certificate scope. None is a trivial variation, and each deserves a line in the annex rather than a footnote in a brochure. Decoding the EU Low Voltage Directive Class and Grade Numbers for Door Hardware handles the numbering side of this problem, which is a different failure mode but the same underlying habit: reading a code in a document as though it said more than it says.

A practical drafting device is to require the certificate list to be returned as data rather than as prose. A single line per model, with four columns, signed and dated, is trivially checkable and impossible to argue with. The alternative, a paragraph describing which models are covered, takes the supplier two hours to write and the buyer an afternoon to interpret.

Decide who signs and who keeps the file

The declaration of conformity is a legal claim, and legal claims have authors. For a package assembled across several factories, the author of the declaration for the mains-powered item is not necessarily the author for the lock body, and the party that sells the bundle to a European customer may hold neither. The clause should therefore name three parties and what each one holds, rather than assuming the word supplier covers all of them.

RoleWhat it normally carriesClause line to addWhere to confirm locally
The legal manufacturer of the modelThe technical file and the signed declarationRequire the manufacturer named on the declaration for each model in the annexWith the supplier, in writing
The party placing goods on the market in the UnionDuties that travel with the goods at the point of placementRequire the supplier to name the party and to say which document set that party holdsWith the importer of record
An authorised representative, where one is usedA mandate to act on the manufacturer's behalfRequire the representative to be named and the scope of the mandate statedWith the importer of record

None of this is a legal opinion, and the clause should not pretend to be one. The clause asks a factual question and demands a documentary answer: who signed, for which model, and where is the file that supports it. A supplier that cannot answer is telling the buyer something important about the supply chain behind the quotation, and the buyer is better off knowing before the first order than during a tender clarification round.

CONFIRM-WITH-LOCAL-IMPORTER-OF-RECORD: which entity in the structure signs the declaration for the models on the annex, which document set that entity must hold, and what must accompany the goods on arrival.

The related question buyers routinely skip is access to the technical file. A declaration that names a document the buyer can never see is a weaker instrument than one that names a document the buyer can request. Where the supply agreement gives the buyer a right to request the technical documentation, the compliance clause becomes easier to enforce.

Keep the door hardware out of the electrical safety clause

A recurring drafting habit in this product category is to ask for evidence covering "the product and all applicable European standards". The clause then collects whatever the supplier finds convenient: a mechanical performance certificate, a radio conformity document, an ingress rating, an environmental test summary, a chemical compliance sheet, and possibly one electrical safety document buried in the middle. The buyer receives a folder and no idea which artefact answers which question.

The four questions that need separating are mechanical lock performance, fire door behaviour, radio and electromagnetic behaviour, and electrical safety. They are different standards with different scopes, and a document answering one of them says nothing about the others. The electromechanical locking function of a battery-driven smart lock sits with the building hardware performance standards, whose scope is treated in Writing EN 14846 Into a Smart Lock RFQ: Clause Language that Gets Real Answers. The radio function is a separate regime again, and the two are frequently confused because both end up under the same marking.

The practical drafting instruction is that every evidence line names both the question it answers and the document type expected. So instead of one requirement covering conformity, the annex carries several lines: one for electrical safety on the mains-connected items, one for radio on the wireless items, one for mechanical locking performance, one for ingress and durability, one for chemical and substance restrictions, one for the battery cells and their transport. Each line has its own document type, its own holder and its own date. When the supplier replies, the reply maps to a line, and any line with no matching document is visible immediately.

This also protects the buyer from the most common over-claim in smart lock supply: a supplier who has a radio conformity document for the module and a mechanical certificate for the lock case presents both as product certification, and the buyer, who asked one question, receives two answers to it. A clause that asks one question per line prevents the substitution.

Two further lines belong on the same annex and are frequently forgotten. Battery cells and their transport have their own requirements, and the forwarder will ask for that evidence before a consignment of lithium-containing goods is accepted. Ingress and mechanical impact codes are quoted in sales literature far more often than they are tested. Both belong inside the RFQ, and neither belongs inside an electrical safety clause.## Do not inherit somebody else's certificate

The private label and OEM programme is where clause language is most often inadequate, because the entity answering the RFQ may have bought nothing, designed nothing and certified nothing. It assembled a package from other suppliers' products, added a brand and a logo, and is now expected to produce evidence for the bundle.

The clause cannot fix that structure, but it can expose it, which is worth a great deal. Four requirements do most of the work. Name the certificate holder for each model, so the buyer knows whether the document was issued to this supplier or to a sub-supplier. State whether the certificate is held in the supplier's name or in the sub-supplier's name, since that determines what the supplier can lawfully pass on. Require written confirmation of what the supplier is entitled to pass on and for which models. Require the supplier to obtain the sub-supplier's agreement to the evidence being shared with the buyer and its client.

The same requirements pay off in the less exotic case of a mains-powered gateway that a lock company bought from a third party and rebadged. If the lock company's certificate file contains nothing for the gateway, the buyer's line item is uncovered and nobody noticed because the question was asked as one clause about one product. Split the annex and the gap shows up as an empty row on day one.

The commercial ownership question sits alongside the documentary one. Smart Lock Supplier Due Diligence Checklist covers the wider verification side, and Who Pays for the EU Low Voltage Directive Evidence in a Smart Lock OEM Programme handles how that verification is paid for.

Bind the evidence to a moment in time

Conformity evidence has a date and a validity period, and a clause that mentions neither produces a file that quietly goes stale. Editions change. A certificate carries a validity window. A model can be revised without changing its designation. A production site can move.

Four requirements close this. The evidence must relate to the current edition of the standards it invokes, with editions stated. The evidence must be valid on the date the first production order is released, and the supplier must say what happens if the certificate expires during the programme. The supplier must notify the buyer of any change affecting the evidence, covering design, component sourcing, production site and the certification route. And the annex must state the deadline by which each document is due, expressed as a commercial event such as release of the first production order.

Tying the deadline to a commercial event rather than a calendar date is worth the small effort. Calendar dates invite a supplier to argue about what counts as a valid document on a given day. Commercial events do not: an order is released or it is not, and a file that is not closed at that point either stops the order or is knowingly accepted with a recorded exception and an owner.

Specify the response, and the return loop

The response format is part of the clause, not part of the buyer's inbox preferences. Without it, three identically compliant suppliers answer in three formats, one of which is a screenshot of a web page, and the buyer spends the comparison effort on document handling instead of on the commercial comparison.

Require legible copies of the original documents. Require each to show the issuing body, the document number, the date, the models covered and the validity period where one applies. Require the certificate model list as a table rather than as prose. State explicitly that a product page extract, a brochure, a catalogue line and a presentation slide are not acceptable responses to an evidence line. And state what the supplier will do if it cannot produce a document, because a supplier that knows what happens on failure answers differently from one that expects the gap to be discovered later.

The return loop matters as much as the format. A clause that defines only the acceptable answer invites a single round of replies and then silence. A clause that defines the acceptable answer, the escalation route and the consequence of an unmet line produces a controlled process: a written clarification request naming the specific unmet line, a stated period for the supplier to answer, and a defined commercial consequence if the line stays open. That consequence is the clause's teeth, and it has to be one the supplier accepts at the point of quotation.

stateDiagram-v2
    [*] --> Requested
    Requested --> Returned : supplier replies in the required format
    Returned --> Classified : buyer sorts each reply by document type
    Classified --> Ranked : buyer places each document on the evidence ladder
    Ranked --> Accepted : rung matches the line and the model is covered
    Ranked --> Clarified : rung is short or the model is not listed
    Clarified --> Returned : written follow up issued on the specific line
    Ranked --> Refused : no document of any kind is offered
    Accepted --> Archived : filed against the model in the annex
    Archived --> [*]
    Refused --> [*]

The lifecycle above is what a well-run clause produces, and it is not a straight line, because a weak answer sends the file backwards rather than ending it. A clause with this shape in it produces fewer surprises than a clause that asks for everything at once, because each line has one open question and one answer. The tender-side version of the same evidence set is laid out in The EU Low Voltage Directive in a Smart Lock Tender Pack: the Evidence Checklist, and the failure patterns this loop is designed to catch are described in Three Ways the EU Low Voltage Directive Evidence Disappoints Smart Lock Buyers.

The clause set as one block

The following block is the working text of the annex. It is written to be lifted, edited for the programme and sent with the RFQ. Square brackets mark the points where a buyer must supply something specific.

ANNEX A - LOW VOLTAGE AND RELATED CONFORMITY EVIDENCE

A1  Scope and regime mapping
    For each model listed in A2, state whether the model is within the scope of
    Directive 2014/35/EU, state the basis for that determination, and identify
    the separate regime under which any marking on the model has been applied.
    A written scope statement is required. A marking photograph is not a
    response to this line.

A2  Model list
    [list models with the designation to be used on the purchase order]

A3  Evidence per model
    For each model listed in A2, provide the declaration of conformity for that
    model, signed and dated, naming the manufacturer, the model designation and
    the requirements relied upon, and the third-party certificate whose scope
    names that model, stating the issuing body, the certificate number and the
    conformity assessment procedure applied.

A4  Model designation mapping
    Where the designation on the purchase order differs from the designation on
    the certificate or the declaration, provide a dated and signed mapping table
    linking the two, one line per model.

A5  Certificate model list
    Provide the list of models covered by the certificate as a table with one
    line per model. Confirm line by line which models in A2 appear on it.

A6  Separate evidence lines
    Provide evidence for each mains-powered item supplied with the package under
    its own model designation and its own document, separately from the lock
    body. Identify which party holds that evidence.

A7  Party and file
    Name the legal manufacturer of each model, the party placing the goods on
    the market, and the party holding the technical documentation. State the
    scope of any authorised representative mandate.

A8  Currency and change
    State the edition of each standard invoked and the validity period of each
    certificate. Confirm the evidence is valid on the date the first production
    order is released. Notify the buyer of any change affecting the evidence,
    including design, component sourcing, production site and certification
    route.

A9  Production control
    Describe the controls that keep the certified configuration in production,
    including incoming component control and periodic verification, and confirm
    audit rights over them.

A10 Response format
    Supply legible copies of original documents showing issuer, number, date,
    models covered and validity. A product page extract, brochure, catalogue
    line or presentation slide is not an acceptable response.

A11 Deadline and consequence
    Each line above is due by [event defined by the buyer]. A line that remains
    open at that event stops release of the first production order, or is
    accepted as a recorded exception with a named owner and a revised date.

A12 Boundary
    This annex covers electrical safety only. Evidence for radio, electromagnetic
    compatibility, mechanical locking performance, ingress and impact, chemical
    and substance restrictions, and battery cells and their transport is
    provided under the separate lines of this RFQ and may not be substituted here.

Two features of that block are worth defending. The first is A1: a scope determination in writing is cheaper than a certificate that turns out not to be needed, and it puts the determination on the party that made it. The second is A12, the boundary clause. It exists because the failure mode in this product category is substitution, a supplier offering one piece of evidence in answer to a question it was not asked, and a boundary stated once stops that at the first line rather than the fourth.

Retire ten phrases

Every one of these has been found in a live smart lock RFQ issued by a competent buyer with a good reason for the wording. The phrasing looks professional, and it is the phrasing that makes the clause unenforceable.

Phrase in the RFQWhy it failsWording that works
The supplier shall provide CE certification for all productsNo document type, no model, no issuer, no dateProvide the declaration of conformity and, for models in its scope, the certificate naming that model, with issuer and number stated
All products shall comply with applicable European standardsApplicable to whom, judged how, evidenced in what formEvidence shall be provided per line in Annex A, each line naming its document type and holder
Test report available on requestA report proves a sample passed, not that the shipped model is coveredThe evidence relied upon shall be a certificate with a stated scope and a verifiable number covering the Annex A models
Supplier to confirm CE marking on all hardwareMarking is applied by a party to a product; confirming it is not evidenceThe document supporting the marking is to be provided per line in Annex A
Conformity shall remain valid for the duration of the contractValidity is a property of a document, not a promise by the supplierThe supplier shall maintain the controls that keep the evidence valid and notify the buyer of any change
Evidence of compliance shall be provided for all componentsComponents carry their own scopes, and the clause collapses separate regimes into oneEach mains-powered item supplied in the package is a separate line with its own document
Supplier shall be responsible for all regulatory complianceNames no deliverable, no holder and no date, and cannot be failedThe party holding each document in Annex A is named, and the document is due by the event stated in A11
Documentation to be provided prior to shipmentTiming without consequence, which is a preference rather than a clauseA line that remains open at the stated event stops release of the first production order
Any equivalent certification acceptedHands the supplier the argument about the scope of the requirementAny alternative evidence shall be submitted in advance with a written equivalence argument
The gateway and accessories shall be covered by the lock certificationThe most frequent error in smart lock packages, and frequently untrueEach mains-powered item is evidenced separately under A6, with the holding party identified

Two more phrasings deserve attention because they sound stronger than they are. "Full certification" is meaningless without a model list attached, since the whole difficulty of certification is scope. And "tested to the latest standard" is only meaningful if the buyer asks which edition the supplier tested against.

When the answer is that the company is certified

Some suppliers answer an LVD question with a statement about the organisation rather than about the product. It is a warm answer, it arrives early, and it is one of the two or three documents a supplier is most likely to produce on demand, because an organisation-wide management system document is a stable asset while product conformity evidence is per model.

The follow-up does not need to be adversarial. It needs to convert the organisation statement into a product statement in one step, by asking for the artefact that carries the model. Something along these lines: thank you for the company overview; please provide the declaration of conformity for the models in Annex A, and the certificate whose scope names those models, with the certificate number, issuing body and models list. A supplier with genuine product evidence answers immediately, because the request is specific and the file exists. A supplier with only an organisation document answers with another organisation document, and the buyer now has a clear signal about what the quotation is actually buying.

There is a second-order lesson here. A management system document proves something about the organisation's processes and nothing about any specific model. It is a legitimate thing to assess, and it belongs in a supplier qualification questionnaire, where it is a genuine indicator of how the supplier works. It is not a substitute for product evidence and should never appear in the compliance annex.

The related point about what a standard can and cannot do is worth holding onto during a long qualification: a standard describes what gets tested. It never says that this factory, this site or this product line conforms. Every conformity status in this article is a claim to be confirmed per supplier, per model and per document.

Where this sits in the qualification stage

An LVD clause belongs in the RFQ rather than in the purchase order, and the reason is timing. At RFQ stage the buyer still has leverage, because a supplier competing for a programme will invest effort in producing a document set, and because the buyer can compare two suppliers on the same rows of the same annex. At purchase order stage the buyer has leverage only over money, and the file has to be assembled by the party with the least interest in producing it.

Send the annex with the RFQ, not after the shortlist. Score the responses on the annex rows rather than on a general impression of professionalism, and treat an unanswered line as a scored gap with a named owner. Where a supplier cannot answer a line, ask what would be needed to answer it and at what cost, which the annex makes easy to ask because the line is already defined.

Then split the file between the RFQ and the supply agreement. The RFQ carries the evidence requirement and the annex; the supply agreement carries the notification duties, the audit rights, the access to technical documentation, the sub-supplier evidence pass-through and the consequence of an unmet line. That split is covered in more detail in Smart Lock Supplier Quality Agreement, and the surrounding qualification sequence is set out in Smart Lock RFQ Guide for International Buyers and Smart Lock Procurement Checklist for B2B Buyers.

The commercial cost of the whole exercise belongs in the early conversation too, because it changes what a supplier quotes. Smart Lock Certification Cost covers what the individual regimes tend to cost a supplier to obtain, and Smart Lock Factory Testing: What Should Be Tested? covers the testing side of the same question. A buyer who arrives with a written annex gets a quote that states what the evidence will cost, because the supplier can price it. A buyer who arrives with "please confirm CE" gets a quote that states nothing, because there is nothing to price.

The file you end

The test of a good LVD clause is not whether it is long, and not whether it uses the name of the Directive. It is whether the replies it produces can be laid side by side and compared, and whether the winning reply is a document that can be opened, checked and filed.

The clauses above are built around that test. They split the package by power source before anything else, because that split decides which party holds the evidence and how many conversations the buyer will have. They name the document rather than the mark, because a supplier can always produce a mark and cannot produce a certificate by accident. They bind each document to a model, a holder and a moment, because those three are what separate a usable file from a folder. And they keep the electrical safety line separate from the radio, mechanical, ingress, chemical and battery lines, because a clause that covers everything covers the one thing that mattered.

Three confirmations sit behind the annex and should be closed before any order is released: the scope determination for each model against the current consolidated Directive text, the entity that signs the declaration and the document set that entity must hold, and the production control arrangements that keep the evidence valid after the first sample passed. None of those three is answered by a supplier brochure.

CONFIRM-WITH-LOCAL-REGULATORY-ADVISER: the scope determination, exclusions and any product-specific treatment that apply to the models and mains-powered accessories in Annex A, read from the current consolidated text rather than from a summary.

CONFIRM-WITH-LOCAL-IMPORTER-OF-RECORD: which entity signs the declaration for each model, which document set must accompany the goods on arrival, and what the importer is required to hold on file.

CONFIRM-WITH-LOCAL-INSTALLER-ENGINEER: the power arrangement at the opening for any mains-powered field device in the programme, so that the annex describes the equipment actually installed rather than the equipment described in the catalogue.

When the annex is ready, the practical next step is to put the exact models and the exact power arrangement in front of a supplier and see what comes back within the response period the annex itself defines. That answer, not the clause, tells you whether the programme is ready to proceed. If the programme involves samples before a production order, Smart Lock Sample Approval Process for OEM Buyers is the point at which evidence can be closed alongside the first article, and Smart Lock Gateway Guide is worth reading for the mains-powered half of a typical package. To have the annex reviewed against a specific configuration, Request a Quote is the route; to put a candidate unit on a real door, Order Samples closes that loop faster than a document exchange.

O seu carrinho
A sua experiência neste site será melhorada se permitir cookies Política de cookies
Chat on WhatsApp