The best eCoC software for a manufacturer is the product that can demonstrate its real approval, data, signing and delivery workflow under normal and failed conditions. A polished certificate preview is useful, but the selection should follow the record through the complete process and establish what remains the manufacturer’s responsibility.
Sources checked: 16 October 2026. The scorecard and cost model are proposed procurement tools, not authority certification criteria or a ranking of commercial products.
What should you define before comparing suppliers?
Write a one-page requirement brief: vehicle categories, approval schemes, manufacturing stages, annual and peak daily volume, current data sources, EU/UK routes and the team operating the process. Add an example approval and a redacted vehicle record. Request pricing against this same brief from every shortlisted supplier.
The VCA guidance places file creation with manufacturers or their authorised representatives and does not prescribe a particular software product. Treat software selection and approval-authority acceptance as separate decisions.
Use a weighted eCoC software scorecard
The following weights are an example for a manufacturer supplying both EU and UK programmes. Adjust them before demos, document why they changed and keep mandatory requirements as pass/fail gates. A high total score must not compensate for a failed mandatory route or unusable data export.
Scroll the table horizontally to view all columns.
| Area | Weight | Evidence to request |
|---|---|---|
| Approval and vehicle-data fit | 20 | Your variant/version, stage and technical values correctly represented |
| Validation and correction workflow | 20 | Detected errors, blocked release and traceable correction |
| ERP or file integration | 15 | Source mapping, reconciliation and recoverable import failures |
| Document signing | 15 | Verified final XML with the required identity and profile |
| Destination delivery | 15 | Correct route, environment and receiving-system result |
| Archive and portability | 10 | Usable records, files and evidence exported without supplier intervention |
| Operator usability | 5 | A trained user can resolve exceptions without hidden technical work |
What should the live demonstration prove?
- Load your representative approval context and vehicle data.
- Show where every material output value came from.
- Introduce an incorrect unit, missing required value and mismatched approval reference.
- Confirm the record cannot be released until the relevant issues are resolved.
- Review and sign the final output with the intended configuration.
- Demonstrate destination feedback, including a rejection or unavailable response.
- Correct the record and explain the version history.
- Export the vehicle record, signed files and evidence in a usable form.
Ask the supplier to identify anything simulated, preconfigured or outside the proposed contract. A recorded demonstration of a connector is not the same as proving your manufacturer account has access to that service.
Excel import or ERP/API integration?
A controlled import can be a sensible starting point where volume is low and source data is stable. Define columns, units, permitted codes, version control and who approves the import. Reject ambiguous mappings visibly; do not silently turn unknown values into blanks or defaults.
API integration becomes useful when vehicle data changes frequently or transaction volume makes manual reconciliation costly. It introduces additional questions: which system owns each field, how retries work, how changes are reconciled and what happens when the source is unavailable. Require an import report that counts received, rejected, changed and unchanged records.
For the destination connection, check the current VCA API guidance or your NAP’s contract. Separate upstream ERP integration from downstream authority submission in the specification and the quotation.
How much does eCoC software cost?
There is no useful universal price without a defined scope. Request a transparent cost breakdown rather than comparing an attractive per-vehicle headline with an all-inclusive quotation. Use the same volume, users, entities, routes and support assumptions.
Proposed annual cost model: licence + signing service + destination charges where applicable + support + internal operating effort + the annual share of setup and integration costs. Keep one-off and recurring items visible. This is a budgeting structure, not a published market price.
Scroll the table horizontally to view all columns.
| Cost item | Ask the supplier |
|---|---|
| Licence and transaction volume | What counts as a billable vehicle, correction, retry or archived record? |
| Signing and certificates | Are identity checks, credentials, renewal and batch signing included? |
| Setup and route onboarding | Which manufacturer accounts and destination tests are included? |
| Integration | Which field mappings, environments and recovery scenarios are delivered? |
| Support and exit | What response service, exports and end-of-contract assistance are included? |
Define acceptance before signing the contract
Use deliverables that your team can inspect: approved mapping, representative test cases, validation reports, signing evidence, receiving-system results and a demonstrated export. The EUCARIS architecture provides context for why a software export, a NAP connection and authority access are different handovers.
Illustrative procurement case: two suppliers quote for 5,000 annual vehicles. One includes setup but excludes signing and corrections; the other includes those but requires a separate ERP project. Normalise both offers to the same delivered process before comparing cost. Do not assume “unlimited” covers every operational service.
Frequently asked questions
Is an eCoC software subscription enough to start submitting?
Confirm manufacturer access, signing readiness, destination conditions and tested data mapping. The subscription may cover only part of that work.
Should we build our own XML generator?
Assess the ongoing ownership of schema changes, validation, signing, delivery and support. Compare the complete internal operating model with the supplier scope, not just the initial development task.
Which evidence matters most in a demo?
A complete vehicle case with a failure, a correction, destination feedback and export is more informative than a sequence of prepared screens. Require visibility of the actual artefacts.
Can we pilot one vehicle family first?
Yes, a bounded pilot can establish data ownership and acceptance criteria. Include representative exceptions and agree the conditions for extending it to other approvals or stages.
Prepare a reviewable software brief
Read the signing checklist and IVI validation guide before finalising requirements. Ask Anemon Engineering to review your workflow and evaluation brief using your actual vehicle and approval scope.
Summary
A useful selection proves your actual workflow, including a failure, a correction and an export. Compare the same volume and integration assumptions across suppliers, assign acceptance criteria and confirm destination access before approving rollout.
