An eCoC implementation budget should cover the complete operating process, not only the software licence. Add data preparation, approval mapping, signing or sealing, authority-channel onboarding, integration, training and ongoing exception handling. Compare suppliers against the same vehicle scope and calculate cost per issued vehicle over a defined period.
This guide is for European and UK manufacturers planning a business case. It deliberately separates a budgeting method from a commercial offer: actual software scope, provider charges and authority arrangements need written confirmation.
Define the scope before comparing prices
Record issuing legal entities, manufacturing sites, categories, stages, approval schemes, annual certificate volume and destination routes. Include the source systems and the number of reusable templates. Two manufacturers with the same annual output may have very different mapping and review requirements.
A single-category programme with stable source data is different from a multi-stage operation managing frequent configuration changes. The software selection guide helps turn those differences into a representative demonstration rather than an abstract feature comparison.
Use a complete cost register
| Cost area | What to include | Question to ask |
|---|---|---|
| Software access | Entities, users, volume model, outputs and environments | Which usage and limits are included? |
| Data and templates | Source cleanup, approval mapping, applicability and review | Who owns initial and later mapping changes? |
| Trust services | Certificate, signing or sealing service, renewal and operations | Which provider and validation requirements apply? |
| Delivery channels | NAP or VCA onboarding, tests, credentials and support | Which operator work is included or separately charged? |
| Integration | ERP/API mapping, retries, monitoring and maintenance | What happens when a source or interface changes? |
| Internal operations | Training, review, corrections, support and archive export | How much accountable staff time remains? |
Separate implementation from recurring operation
Initial work often includes mapping, migration, test cases and staff onboarding. Recurring work includes software access, provider services, operating support, renewals and internal handling. A change allowance covers new vehicle families, revised approval data, schema updates or an additional market.
Ask each supplier to classify every quoted line as initial, recurring, usage-based or change-related. Identify excluded third-party work and taxes separately. Never assume that software access includes every trust-service charge or that it grants authority production access.
Calculate total cost on a consistent basis
First-year total = implementation + annual fixed charges + usage charges + internal operating effort + agreed change allowance. For a three-year comparison, use the same production forecast and add recurring and planned change costs for each year. Do not multiply first-year onboarding three times unless the proposal actually requires it.
Cost per issued vehicle = total cost for the period ÷ issued vehicles in the same period. State whether the denominator excludes rejected attempts, tests and superseded candidates. A low transaction price is not directly comparable if each correction or retry has a different charging basis.
Measure manual effort before claiming savings
Use a small observed sample to measure preparation, review, correction and follow-up time. Include unsuccessful attempts and waiting-related handling rather than measuring only a clean record. Then compare the same process after a pilot, with equivalent vehicle complexity.
As a synthetic arithmetic example, 1,000 records at 12 minutes of active handling require 200 hours. At 8 minutes, they require about 133 hours, a difference of about 67 hours. These inputs are assumptions, not measured Digital CoC results. Multiply only a validated time difference by your own approved labour cost, and retain any review work still required.
Choose automation around the operating workload
VCA provides portal upload and an API route, explaining that manufacturers can choose according to their needs. Portal-led operation may be a reasonable starting point for a bounded workload; higher volume or complex source data may justify integration. Neither choice removes the need to handle exceptions and reconcile receiving results.
For EU delivery, confirm the selected NAP's onboarding and technical arrangements. Ask about monitoring, response handling, certificate renewal, exports and exit support. A proposal should state who owns those tasks when the supplier, trust provider and national operator are different organisations.
Request a quote that can become an implementation plan
Provide one representative vehicle record, production forecast, approval scope, data sources, required outputs and intended routes. Ask for acceptance criteria, dependencies, responsibilities and a treatment of future changes. Include an export demonstration so switching systems does not depend on reconstructing certificate history manually.
Digital CoC's implementation and pricing page is the starting point for a scoped discussion. Bring this cost register to that discussion, then compare the written proposal against the workload you actually need to operate. Authority acceptance and certificate-provider status need their own evidence, regardless of the commercial model.