Export Certification File: What to Request and Verify

Ask a supplier whether the charger is certified and the reply is usually a single attachment: a certificate, or a screenshot of one. It is rarely the answer to the question actually being asked — whether the specific unit on the order, made at the specific factory, can be placed on the market in the destination country. Those are different questions, and only a document set answers the second one.

This is a guide to that document set: what each layer proves, who issues it, which parts a buyer can reasonably request before an order, and how to check that the scope covers the unit rather than a sibling model. None of it substitutes for advice from a compliance professional in the destination market, but it does make the first exchange with a supplier far more productive.

"Do You Have CE" Is Not a Document Request

In the European Union, CE marking is in most cases a manufacturer's own declaration: the manufacturer assesses the product against the applicable requirements, compiles a technical file, signs a declaration of conformity, and takes responsibility for the result. A notified body is involved only in certain routes. So "the product has CE" can mean a signed declaration, or it can mean a third-party certificate — and the two carry different weight.

North America works differently. There, the accepted evidence is a listing by a recognised testing laboratory, with a mark on the product and periodic follow-up inspection of the factory. A European declaration does not transfer, and a North American listing does not satisfy the European route. This is the single most common misunderstanding in cross-market procurement: one region's paperwork is routinely offered as evidence for another.

The practical consequence is that the request needs to be specific about the market, and about which document is expected. A generic certificate attachment cannot be evaluated against either route.

Four Document Layers, Four Different Claims

Compliance paperwork is not one document. It is a stack, and each layer supports a narrower claim than buyers usually assume.

Layer	Issued by	What it actually claims	What it does not claim
Declaration of conformity	The manufacturer, under its own name	That the named product conforms to the listed requirements, and that the signatory accepts responsibility	That an independent body tested it, or that any particular sample was examined
Test reports	A testing laboratory	Measured results for the sample identified in the report, against the standards listed in it	That every unit in the series behaves the same way, or that untested functions were assessed
Third-party certificate	A notified body or equivalent	That the type, or the production system, was assessed within a stated scope and validity period	Anything outside that scope, or anything after the certificate lapses
Technical file	The manufacturer	That a design record exists — drawings, calculations, component evidence, risk assessment, instructions	That it is complete, or that it has been reviewed by anyone outside the manufacturer

A buyer rarely receives the technical file in full, and asking for it as a condition of quotation tends to end the conversation. What can reasonably be requested is its index — the list of contents — because the index shows whether the design record includes the elements a reviewer would look for. A file with no risk assessment entry, or no component evidence section, is thin regardless of what the declaration says.

Scope Is the Part That Gets Skipped

Every certificate and every declaration describes a defined product. That definition sits in a schedule, annex or model list — and it is the first thing to read, not the last. A certificate covering a product family does not automatically cover a variant added later, and a declaration naming a model designation does not cover a different rating sold under a similar name.

The check is mechanical. Put the rating plate photograph next to the scope schedule and compare six fields:

• Model designation, exactly as printed, including suffixes that denote a market variant or connector type
• Rated power and input configuration, since a family approval often covers one rating and lists others as separate entries — or omits them
• Connector type and cable assembly, which is where market variants diverge most often, as with the outlets on an ultra-fast charging station built for different regions
• Enclosure and environmental rating, because an outdoor cabinet and an indoor unit are not the same product even when the electronics are
• Optional modules fitted to the order — payment terminal, display, modem, additional power modules. Each one can bring a separate requirement, and a unit with them is a different configuration from the one tested
• Manufacturing location, where the certificate names a site. A second plant producing the same design under the same certificate is a question worth asking rather than assuming

If any of the six differs from the schedule, the paperwork describes a different machine. That is not an accusation of bad faith — families grow, options are added, and documentation lags. It is simply the point at which the conversation needs to move from "do you have a certificate" to "which entry in the schedule covers what I am buying".

Who Holds the Certificate Changes Who Carries the Obligation

The named holder on a certificate is an economic operator with duties attached. It can be the factory, a group entity, a trading company, or — in an OEM arrangement — the buyer. Each arrangement is legitimate, and each distributes risk differently.

Where the holder is not the party selling to you, a short authorization letter or a statement of the relationship is a reasonable request. Without it, a buyer can end up holding a valid certificate issued to a company that has no legal connection to the invoice.

In an OEM project the certificate is sometimes registered in the buyer's name. That is attractive for market access and for control of the brand, and it also means the buyer inherits the surveillance obligations, the renewal calendar, and the duty to keep the technical file available for the authorities. It is a trade, not a free upgrade, and it belongs in the commercial discussion rather than in the appendix.

A related point that catches importers: in the European Union the importer is itself an economic operator with its own name-and-address obligation on the product or its packaging. A non-European manufacturer's declaration does not remove that duty, and a private-label arrangement does not move it to the factory.

Three Markets, Three Different Logics

The document that satisfies one market tends to be the wrong document in another. The table below is a starting point for the request, not a legal opinion for a specific product.

Market	Route to market access	Core document to request	Supporting evidence
European Union	Manufacturer's declaration, technical file held by the manufacturer; third-party involvement only on certain routes	Declaration of conformity, in a language accepted by the member state of sale	Test reports covering the listed requirements; technical file index
North America	Listing by a recognised testing laboratory, with factory follow-up inspection	Listing record naming the model and the factory	Test report, mark on the product, evidence of current factory inspection
United Kingdom	Its own marking regime, separate from the European route	UK declaration of conformity naming the UK responsible person where required	Test reports, plus confirmation of current acceptance rules — treat these as policy, not as fixed

Two habits are worth building around this table. First, treat a document issued for one market as evidence only for that market, however similar the product. Second, confirm the current acceptance rules for the destination rather than relying on a summary — marking regimes change, transitional arrangements expire, and a file that was sufficient two years ago can be insufficient now.

Where a project involves a high-power hub or a multi-unit installation, the public fast-charging solution introduces one more layer: the site as a whole can be subject to grid-connection and installation requirements that sit outside the product's own approval. Product documents do not cover installation compliance, and installation documents do not cover the product.

Reading a Test Report in Five Checks

Test reports are the layer buyers skim and suppliers prefer not to discuss in detail. Five checks catch most of what matters:

1. Sample identification. The report names a sample — model code, rating, sometimes a serial. If that identifier does not appear in the certificate scope, the report supports a different product.
2. Date against design changes. A report predating a hardware revision is evidence about the earlier design, unless a delta assessment exists.
3. The standards list, read in full. Partial coverage is normal and legitimate. Presenting partial coverage as complete is not.
4. Accreditation scope of the laboratory. A laboratory can only issue accredited results for tests inside its scope; outside it, the report is still a document but carries less weight.
5. Page count and annexes. Sales packs regularly contain excerpts. Ask for the complete document with its annexes, and compare the page numbering — a report that starts at page fourteen is an extract.

The Request List to Attach to an RFQ

A document request works better as a numbered list inside the inquiry than as a question in an email thread. Eight items cover the stack:

Two of these items are usually missing from sales packs and matter more than the rest: the scope annex (item two) and the statement of holders (item six). The first determines whether the paperwork describes your unit; the second determines who is answerable if it does not.

Where the product is a configured cabinet rather than a catalogue item, the configuration itself belongs in the contract, not only in the quotation. A frozen configuration list — power modules, connector types, payment hardware, firmware branch — is what makes the scope check repeatable at delivery, and it is also what an HPC terminal order needs when the same cabinet can be built in several outlet arrangements.

Five Signals That the File Is Incomplete

None of these is proof of a non-compliant product. Each is a sign that the documentation has not been assembled for scrutiny, which is a different problem and an easier one to fix before the order rather than after.

What the File Is For

The purpose of the document set is not to decorate a tender response. It is to establish, before capital is committed, three things: that the product being bought has been assessed against the requirements of the market it is going to; that the assessment covers the configuration actually ordered; and that someone with a legal identity is answerable for both statements.

A supplier that can produce the scope annex, the rating plate and the holder statement in one reply has a documentation process. One that sends a certificate image and a brochure has a sales folder. The difference shows up years later, at the first customs query, tender audit or site inspection — which is precisely when it is most expensive to discover.

The complete product documentation set, including the technical material behind these declarations, is the reference point for what a full file looks like; the download library is one place to compare structure, and the same eight-item request can be put to any supplier in the category.