For vehicle manufacturers, homologation teams and production operations in Europe and the United Kingdom.
A reliable trailer eCoC starts with the approved configuration of the individual VIN. Establish category, approval reference, variant/version, completion stage, axles, masses and dimensions before preparing the electronic record. A commercial trailer model name is not enough to select the certificate data.
This guide is for trailer and semi-trailer manufacturers supplying European and UK markets. It provides an operational data-review method, not a replacement for the category-specific CoC template, approval documents or receiving authority’s instructions. Treat every field in the checklist as a question of applicability to the actual approved vehicle.
Regulation (EU) 2018/858 divides trailers into O1, O2, O3 and O4 by maximum mass. The category should come from the approval and vehicle record; a sales label such as ‘light trailer’ or ‘heavy trailer’ should not determine it.
| Category | Maximum mass | Data decision before release |
|---|---|---|
| O1 | Up to and including 0.75 tonnes | Verify the approved category and the actual configuration. |
| O2 | Over 0.75 tonnes, up to and including 3.5 tonnes | Keep masses and the applicable equipment configuration aligned. |
| O3 | Over 3.5 tonnes, up to and including 10 tonnes | Review axle and coupling-related data against the approval. |
| O4 | Over 10 tonnes | Control configuration-specific masses, dimensions and completion data. |
Use the mass and category interpretation in the applicable approval, including the relevant coupling and load treatment for semi-trailers. The category boundaries do not by themselves identify the approval scheme or prove an exemption from electronic submission. Record the issuing authority, scheme, production date and destination alongside the category. Use the current authority instructions when deciding which route applies.
Maintain a controlled baseline for the approved type, variant and version. Then identify which values are determined by the build or configuration of an individual vehicle. A template can reduce repeated entry, but it also multiplies mistakes when copied values are not reviewed after an engineering change.
| Data group | Controlled source to identify | Release check |
|---|---|---|
| VIN and manufacturer | Production identity record and approved manufacturer details | The exact VIN and responsible entity match the certificate record. |
| Approval reference and variant/version | Current applicable approval documentation | The selected configuration is covered by the referenced approval. |
| Axles and axle spacing | Approved configuration and build specification | The count and spacing describe the built vehicle. |
| Masses and load distribution | Applicable approval values and controlled production inputs | Different mass concepts are labelled and reviewed separately. |
| Dimensions and body configuration | Approved drawing/configuration and completion record | Measurements and units match the actual configuration. |
| Tyres, wheels and coupling data where applicable | Approved combinations and installed-equipment record | The selected combination belongs to the correct vehicle record. |
| Build stage and modifications | Previous-stage documents and final-stage review | Inherited and changed values have an identified reviewer. |
Use the applicable trailer template in Annex VIII of Regulation (EU) 2020/683 to establish which certificate particulars are required. The matrix above assigns operational responsibility; it does not introduce a universal field list for every O-category vehicle.
A frequent source of review difficulty is a spreadsheet column simply labelled ‘weight’. Identify the precise mass concept, unit, source and applicability for each value. Do not substitute a customer’s requested load rating for an approved vehicle value or assume that every mass field should contain the same number.
Where axle loads or a coupling-related value are relevant, the reviewer needs the complete configuration context. If the production input conflicts with the approved limits, resolve the engineering or approval question before release. Passing a structural XML check does not resolve an unsupported configuration.
Illustrative scenario: two trailers share a commercial model name, but the second has a different axle spacing and body length. The certificate preparer copies the first record as a template. The review must establish whether the second vehicle belongs to the same approved variant/version and which particulars must change. A new VIN alone is not a sufficient update.
Keep the build specification, applicable approval reference and review outcome together. If the configuration is not covered by the approval, stop the certificate release and refer the question to the responsible homologation team. If it is covered, update the controlled vehicle record, regenerate the candidate and review the changed values before signing.
VCA’s current guidance includes newly manufactured category O vehicles in its relevant GB and UKNI scope from 29 November 2026. It distinguishes national small-series exemptions from included medium-series and UKNI EU small-series schemes. Establish the actual approval route rather than assuming that low production volume decides the answer.
For an EU destination, document the applicable scheme, receiving route and operator requirements. For a UK route, check the current UK IVI requirements and account arrangements. A trailer data baseline can support both workflows, but each released output and response needs to remain attached to its own destination.
Measure the process with representative builds rather than a perfect demonstration vehicle alone. Include one option change, one missing production input and one inconsistent approval reference. The aim is to show that the team can identify and resolve the difference before it becomes a signed certificate.
Use one trailer family to define the sources, review owners and exception path. The truck and trailer manufacturer solution provides the commercial starting point; the multi-stage handover guide covers inherited values. Discuss a representative build with Electronic COC to assess the workflow against your own approval and production records.
Vehicle category alone does not settle the submission route. Check the actual approval scheme, production date, destination and applicable authority instructions. Do not infer an exemption solely from the trailer being light or produced in low volumes.
A reusable baseline is useful only when it selects the correct approved configuration for each VIN. Identify configuration-dependent values and require review when axles, dimensions, masses or installed equipment change.
Identify the exact mass field required by the applicable template and receiving profile. Keep its meaning, unit and approved or controlled production source explicit; do not use a generic weight value across different mass concepts.
Structural validity does not establish that the built configuration is covered by the referenced approval. Review the source configuration and approval context before the signed release.
Reviewed on 16 October 2026. Authority statements below are distinguished from our suggested operating controls. Receiving-system instructions and the applicable approval scheme govern the actual submission.
Continue with Electronic COC articles that connect eCoC readiness, manufacturer rollout and certificate release control.
A practical guide for body builders and converters managing multi-stage eCoC data handover, inherited values, approval references and version control.
Type Approval Data Checklist for eCoC Preparation: a practical Electronic COC guide for manufacturers planning type approval data for eCoC, Vehicle COC workflow and eCoC preparation.
Trace a missing eCoC from submission to registration. Check VIN, receiving-system acceptance, record version and EU or UK retrieval evidence before resending.