Building a homologation file a customs officer and a regulator can both read

Homologation problems rarely arrive as a rejection letter. They arrive as a container held at the port, a broker asking for one more document, and a distributor paying storage while a factory in another time zone looks for a test report from three years ago. The file, not the motorcycle, is what decides whether the shipment clears.
This note sets out the document set for a 150 cc sport model sold into markets that require type approval, what each document actually proves, which ones expire silently, and the four places where files most often fail. It is written from the point of view of the importer who has to answer questions at 9 a.m. with no engineer awake in the producing country.
1. What the file is for
A homologation file exists to prove three separate things: that the vehicle type meets the technical rules of the destination market, that the specific unit shipped was built to that approved type, and that the manufacturer can keep building it that way. Regulators test all three, and a file that only proves the first will stall at the second.
Keep those three claims on the cover sheet of the file. When a customs officer asks a question, the answer is a pointer to one of the three, not a paragraph of explanation. Files that are organised this way clear in hours instead of weeks, because the person reading them can find the evidence without understanding the vehicle.
2. The core document set
Six documents carry most of the weight: the type approval certificate or the equivalent national approval, the test reports behind it, the certificate of conformity for the shipped batch, the VIN decoding statement, the emissions and noise reports, and the manufacturer's declaration of conformity with the approved type. Everything else is supporting evidence.
Each document needs to name the approved type by its approval number, not by a marketing name. A file that lists the 150–200 cc sport model only by its commercial name invites the officer to match it against whatever description is on the invoice. That mismatch is the single most common reason a shipment is held.
3. Test reports and the laboratory behind them
Reports are only as useful as the laboratory that issued them. Most destination markets accept reports from laboratories recognised under a mutual recognition arrangement; a report from an unrecognised lab can be technically perfect and still be refused. Check the lab's accreditation scope before the report is commissioned, not after.
Reports also carry validity periods. Emissions reports for a 150 cc spark-ignition engine are usually tied to the standard in force at the test date, and a standard revision can retire a report overnight. Keep a column in the file index that records the standard, the report date and the date the report stops being acceptable.
4. Emissions: the part that is usually out of date
For a 150 cc four-stroke single, the emissions package is a closed-loop system with a catalytic converter and an evaporative control circuit. The report proves the calibration at the test date; the certificate of conformity proves that each unit carries the same calibration. If the factory changed an ECU map or a catalyst supplier after approval, the file no longer describes the shipped units.
Ask for a change log against the approval. A supplier change that alters the catalyst substrate, the injector flow rate or the oxygen sensor response is a reportable change in most schemes. Distributors discover this when a batch tests differently at a border laboratory, and by then the container is already on the water.
5. Noise: a pass-by test, not a stationary one
Noise approval is based on a pass-by measurement under acceleration, with microphone positions defined by the standard. A stationary rev test in a workshop proves nothing and is not accepted. The report should state the test standard, the microphone geometry, the gear used and the measured level with the measurement uncertainty.
Exhaust systems are the usual point of failure. A slip-on or a locally fitted muffler invalidates the type approval in most markets unless it is covered by the approval. Distributors who fit accessories at the port should keep a separate declaration that the accessory does not alter the approved noise or emissions configuration.
6. Braking and lighting: approvals that travel separately
Brake and lighting components are often approved separately and referenced by the vehicle approval. The file needs the component approvals for the brake hose assemblies, the master cylinder, the lamps and the rear reflectors, each with the approval mark shown on the part. A part that carries a different mark from the one in the file is a mismatch, even if it performs better.
Photograph the marks on three sample units per batch. This sounds excessive until the first batch arrives with a substitute headlamp from a second source, carrying a mark the file does not list. Photos taken at the factory cost nothing and settle the question at the port in one comparison.
7. VIN, plate and the decoding statement
The VIN is the link between the approval and the physical unit. The file should include the VIN structure, the world manufacturer identifier, the position of the plate, and a photograph of a stamped VIN and a plate from a production unit. If the plate is a sticker, state where it is fixed and what happens to it under heat and washing.
A decoding statement prevents the classic argument at the border about whether a character is a one or an I. It also lets a broker verify a unit without contacting the factory. Files without it produce email chains that last for days, and every day of delay costs the importer storage and demurrage.
8. Conformity of production
Approval authorities expect the factory to prove that production stays within the approved specification. That evidence usually takes the form of an annual audit summary, a production conformity declaration, and end-of-line test records for emissions-related parameters such as idle CO and lambda at a defined point.
End-of-line records are the most useful document in the whole file, because they are unit-level. If a vehicle is questioned, the factory can produce the record of the exact unit. A distributor who asks for these records at the time of shipment, rather than at the time of a dispute, never has to reconstruct them.
9. Where files actually fail
Four failures account for most holds: an approval number that does not match the invoice description; a report that expired when a standard was revised; a component mark that does not appear in the file; and a certificate of conformity issued for a different batch than the one shipped. All four are clerical, and all four are expensive.
A pre-shipment check against those four items takes about twenty minutes. It should be done by the person who signs the certificate of conformity, not by the forwarder. A forwarder can move boxes; only the manufacturer's signatory can assert conformity.
10. File hygiene that survives an audit
Store the file as a flat index with numbered documents, each named with the approval number and the date. Keep the index as one page. A regulator who can read the index and jump to document seven does not need to read the other documents, and that is the outcome you want.
Version the file whenever something changes, and keep a one-line change log with the reason. When a question arrives two years later, the change log explains why the 2026 certificate differs from the 2025 one, without reopening the whole approval process.
11. A file for the 150 cc sport class
In the 150 cc sport class, where platforms are shared across markets and minor cosmetic variants are common, the file should map every variant to one approval or a family approval. A family approval covers variants that share the tested technical configuration; a cosmetic decal set does not need its own approval, but a different tyre size probably does.
Keeping a variant matrix in the file prevents the most avoidable rejection of all: shipping a variant that looks like the approved model and is not. The matrix takes one page and answers the question before it is asked.
Frequently asked questions
How long does a homologation file take to assemble? For an existing approval with reports in hand, two to three weeks of document work. If tests must be run, add six to ten weeks depending on laboratory queues.
Can a distributor reuse the factory's file? Yes, but only with a certificate of conformity issued in the distributor's name and a declaration that the units match the approved type. Copying a file without the conformity link is where most disputes start.
Do accessories need separate approval? Anything that changes noise, emissions, lighting or braking does. Cosmetic parts generally do not, but the file should still name them if they are fitted before delivery.
What is the cheapest insurance? A twenty-minute pre-shipment check against the four failure modes, signed by the person who issues the certificate of conformity.