Start with the project scope.
To compare DPP proposals, first establish what each includes. Initial configuration, a software licence and ongoing data operations are different components. A price per passport alone does not describe the whole project.
NexusDpp prepares a quotation after reviewing the specific requirements. This page is not a standard price list: it explains the items to discuss so your company can prepare useful information and recognise what an offer includes.
Seven items to clarify.
| Item | What shapes the scope | Question to ask |
|---|---|---|
| Analysis and configuration | Sectors, roles, datasets and approval workflows. | Which processes will be configured and tested? |
| Data preparation | Available files, missing fields and evidence quality. | Who cleans, completes and approves the information? |
| Suppliers | Organisations, languages and requests to coordinate. | Is support for data collection included? |
| Integrations | ERP, PLM, BMS, APIs and systems requiring ongoing connections. | Are initial imports and maintained connectors separate? |
| Platform usage | Volumes, users, storage and service terms. | Which limits and services does the subscription cover? |
| QR, NFC and external services | Physical carriers and third-party services within scope. | Which costs are included, separate or usage-based? |
| Ongoing operations | Updates, support, revisions and export. | Who acts, and under which service levels? |
For trust services, independent verification or registration through third-party services, ask the proposal to identify the actual services required, the provider and the relevant terms. Different configurations need different combinations of services.
Models, batches and units measure different work.
Model counts describe how many product configurations need to be organised. Unit counts describe how many individual identities and events may need to be managed. Supplier counts indicate the coordination and data-collection work across the chain.
Two companies selling the same number of products can therefore require different projects. One may have structured data and one source system; the other may rely on varied documents and many suppliers. Present these elements separately to obtain a useful quotation.
“We have 10 models, produce 5,000 units per year, work with 8 suppliers and use an ERP. We want to start with one model and test serial-number imports before expanding.” This is a scope example, not a tariff or commercial commitment.
What to prepare for a quotation.
- Sector, product category and your company’s role in the supply chain.
- Model counts and annual volumes, separating the pilot from expansion.
- A sample of available information: an ERP export, technical sheet and supplier document.
- Systems to connect and technical contacts.
- Access roles, languages and approval responsibilities.
- How QR or NFC carriers will be applied and expected physical volumes, where relevant.
- Target date, expected support and acceptance criteria.
An initial discussion can start with a list of available documents. Share confidential project information later through agreed channels and permissions.
How to compare proposals.
Request a breakdown of initial work, recurring services and usage-based components. Also compare data exports, identifier portability, revision support and arrangements when the service ends.
Connect each item to a verifiable result: importing serial numbers without duplicates, completing an approval, separating access rights or exporting the pilot dataset. This makes the quotation reflect the work to be performed.
The NexusDpp pilot project provides a way to define an initial scope. The platform page describes the architecture and connections to business systems.
Frequently asked questions about DPP costs.
Is there one price for every passport?
A proposal may include a volume-based component, but configuration, data, integrations and support still need to be specified. NexusDpp quotes for the requested scope.
Do we need to replace our ERP?
A project can exchange information with existing systems. Feasibility and implementation work depend on the available interfaces and data quality.
Can we start with one model?
You can propose a limited pilot and agree its activities. Volumes, objectives and terms for a subsequent expansion should be specified separately.