eCoC Requirements for EU and UK Manufacturers

For manufacturers supplying EU and UK markets, eCoC readiness starts with an approval map. List the approval held for each vehicle family, the manufacturing stage, the production date and the receiving authority. This prevents a common planning error: treating one XML file and one connection as sufficient for every market.

Sources checked: 16 October 2026. The routing and readiness controls below are practical recommendations. Confirm the applicable authority instructions for your approval before production release.

Which manufacturers and approvals need a separate scope decision?

Use the actual approval certificate as the starting point. A factory location, sales invoice or vehicle brand does not identify the approval scheme. Include incomplete vehicles and later manufacturing stages in the review; do not assess only the finished vehicle sold to a customer.

Scroll the table horizontally to view all columns.

The VCA scope guidance distinguishes GB/UKNI national small series, which are exempt from mandatory eCoC, from GB medium series and UKNI EU small series, which are included. Record the scheme name before deciding that low production volume creates an exemption.

How should manufacturers interpret the 2026 dates?

The EU legal baseline in Article 37 is 5 July 2026. Operational transition notices need to be assessed separately: Sweden’s notice gives 29 November 2026 for manufacturers holding its relevant approvals. The VCA uses 29 November 2026 for newly manufactured vehicles within its scope. Avoid presenting an authority notice as a universal amendment for every approval.

Maintain a short date register with four entries: approval scheme, relevant production-date rule, authority source and date last checked. If two documents appear inconsistent, ask the issuing authority for written clarification and retain the answer with the programme file. A registration date should not silently replace a production-date condition.

EU NAP and EUCARIS: define the handover

The EUCARIS implementation guidance explains manufacturer access through a national access point and authority exchange through EUCARIS. For your project, turn that architecture into a named handover: who receives your file, what validates it, which response identifies the record and how the approval authority can retrieve it.

1. Choose a NAP based on documented access conditions, technical support and the required approval context.
2. Agree the XML version, document-signing profile and submission contract before developing the connector.
3. Use representative test vehicles, including a rejected file and a later correction.
4. Reconcile the signed file, transaction reference and final receiving-system result.
5. Record support contacts and the process for changes to certificates, schemas or manufacturer details.

Successful transport is one piece of evidence. Treat schema validation, destination acceptance and downstream retrieval as separate checks wherever the selected service exposes them. Define who closes a record when one of those states is missing.

UK VCA: plan a distinct route and validation profile

Build the UK workstream around the published UK IVI XSD and VCA account. An EU-oriented export should not be labelled UK-ready until the applicable UK values and receiving-system checks have been tested. Record the exact schema package used; a filename such as “latest.xml” is not a version policy.

For integration planning, assign separate owners for XML creation, manufacturer-account administration and response handling. The account owner should be able to explain who can submit, who can remove access and where production credentials are managed. Your delivery evidence should identify the environment used, so a successful test cannot be mistaken for an official submission.

Example: one manufacturer serving two markets

Illustrative scenario: a trailer manufacturer supplies an EU programme and a separate GB-approved programme. Its ERP holds a shared production record, but the release process selects the appropriate approval, output profile and recipient. The software should stop a vehicle with an unresolved approval reference rather than choose a destination from the customer’s country alone.

A pilot should include one ordinary vehicle, one with a changed approval revision and one requiring a correction. For each case, capture the source values, reviewer decision, signed output and destination response. This reveals whether the team has a repeatable process rather than a single successful upload.

What should the readiness pack contain?

• Scope owner: vehicle families, categories, approval schemes and production-date rules.
• Data owner: source-to-IVI mapping, units, controlled values and approval references.
• Release owner: review permissions, signing authority and blocked-record handling.
• Integration owner: test evidence, environment separation and response reconciliation.
• Operations owner: correction procedure, support escalation and retrievable archive.

Give every open item an owner, evidence link and closure condition. “XML generated” should close only the generation task. It should not close authority onboarding, signing acceptance or the investigation of a missing response.

Frequently asked questions

Does selling in the UK mean every vehicle uses the VCA route?

Determine the route from the approval scheme and applicable market arrangements. GB, UKNI and vehicles placed on the market under EU approvals need an explicit scope review; sales geography alone is insufficient.

Can a low-volume manufacturer start without an ERP connection?

A controlled file-based process may be appropriate. Check the methods offered by the receiving service and preserve the same review, signing and traceability controls you would require from an API integration.

Is a PDF copy an electronic conformity data submission?

A readable preview can support review, but it does not establish that the required structured dataset has been accepted by the destination. Keep the structured output and receiving-system evidence together.

What should we prepare before requesting implementation support?

Bring a representative approval, a redacted vehicle record, the target markets, estimated production volume and your current CoC workflow. These make scope and integration discussions concrete.

Plan the next step for your manufacturing programme

Continue with the multi-stage eCoC guide or the software evaluation checklist. Discuss your approval and market scope with Anemon Engineering to define a reviewable implementation plan for your own vehicle programme.