Passing a vehicle on as a used vehicle, not as end-of-lifeAll articles

Passing a vehicle on as a used vehicle, not as end-of-life

The classification as a used vehicle is a prerequisite for a transfer; without it, the preflight names a hard blocker. This case shows how it is reasoned and delivered.

Published: 2026-09-12Reading time: 5 mintapinomahub API & workflows
API & processesAPIVehicle dismantling

A damaged vehicle is to be sold, possibly abroad. Whether it is classified as a used or an end-of-life vehicle helps decide whether the preflight names a hard blocker for the transfer — and in daily practice that question is often answered by what suits better. In an inspection nobody then carries the reasoning.

Passing a vehicle on as a used vehicle, not as end-of-lifeInput: a vehicle to be sold although its classification is contestable 1. Assess against Annex I (POST /compliance/cases/{id}/annex-i-assessments): partACriteria, partBCriteria and conclusion, plus the assessor’s independence 2. Evidence roadworthiness (POST /compliance/cases/{id}/roadworthiness-certificates): certificateNumber, issuedAt and assessmentResult from an issuing body 3. Create the transfer dossier (POST /compliance/cases/{id}/used-vehicle-transfer-dossiers): transferWithinUnion, saleMethod and physicalHandover determine the duties 4. Preflight the transfer (POST /compliance/used-vehicle-transfer-dossiers/{id}/preflight): proposedTransferAt against the legal position; blockers name what is missing 5. Deliver the dossier (POST /compliance/used-vehicle-transfer-dossiers/{id}/deliveries): The buyer receives the dossier verifiably, not merely verbally Output: a sale whose classification as a used vehicle is reasoned and delivered The preflight may prevent the transfer. If the facts do not evidence a used vehicle, it names a hard blocker.Passing a vehicle on as a used vehicle, not as end-of-lifeInput: a vehicle to be sold although its classification is contestable01Assess against Annex IPOST /compliance/cases/{id}/annex-i-assessmentspartACriteria, partBCriteria and conclusion, plus the assessor’s independence02Evidence roadworthinessPOST /compliance/cases/{id}/roadworthiness-certificatescertificateNumber, issuedAt and assessmentResult from an issuing body03Create the transfer dossierPOST /compliance/cases/{id}/used-vehicle-transfer-dossierstransferWithinUnion, saleMethod and physicalHandover determine the duties04Preflight the transferPOST /compliance/used-vehicle-transfer-dossiers/{id}/preflightproposedTransferAt against the legal position; blockers name what is missing05Deliver the dossierPOST /compliance/used-vehicle-transfer-dossiers/{id}/deliveriesThe buyer receives the dossier verifiably, not merely verballyOutput: a sale whose classification as a used vehicle is reasoned and deliveredThe preflight may prevent the transfer. If the facts do not evidence a used vehicle, it names a hard blocker.
Five calls from assessment to delivery. The preflight may prevent the transfer.

The contract therefore turns the classification into an evidenced determination with an independent assessor, a roadworthiness certificate and a preflight that may prevent the transfer. If the latest effective roadworthiness and Annex I facts do not evidence a used vehicle, the preflight names a hard blocker.

SurfaceRoles
ComplianceVehicle trading, Vehicle recyclers, Dealership

What this case requires

  • An assessor with evidenced independence. The assessment takes qualification and an independence attestation; a self-assessment is something else.
  • A roadworthiness certificate from an issuing body. Your own estimate is not sufficient here.
  • Clarity about the type of transfer. Whether within the Union, to whom and by which sale method — the duties depend on it.
  • A willingness to accept a no. Treating the preflight as a formality misses the point of the stage.

The sequence

The table names the responsible call per stage and what exists afterwards. The reasoning for why a stage cannot be skipped follows below it.

The call chain of this use case
StageCallWhat exists afterwards
Assess against Annex IPOST /compliance/cases/{id}/annex-i-assessmentspartACriteria, partBCriteria and conclusion, plus the assessor’s independence
Evidence roadworthinessPOST /compliance/cases/{id}/roadworthiness-certificatescertificateNumber, issuedAt and assessmentResult from an issuing body
Create the transfer dossierPOST /compliance/cases/{id}/used-vehicle-transfer-dossierstransferWithinUnion, saleMethod and physicalHandover determine the duties
Preflight the transferPOST /compliance/used-vehicle-transfer-dossiers/{id}/preflightproposedTransferAt against the legal position; blockers name what is missing
Deliver the dossierPOST /compliance/used-vehicle-transfer-dossiers/{id}/deliveriesThe buyer receives the dossier verifiably, not merely verbally

Why each stage is needed

  1. Assess against the criteria. POST /compliance/cases/{id}/annex-i-assessments takes assessor, qualification, independence attestation, the criteria of both parts and the conclusion. Independence is not in the call by accident: an assessment by the seller does not carry the classification.
  2. Evidence roadworthiness. POST /compliance/cases/{id}/roadworthiness-certificates carries issuing body, number, date of issue and result. This is a third-party certificate taken into the file — not an estimate of your own.
  3. Create the transfer dossier. POST /compliance/cases/{id}/used-vehicle-transfer-dossiers takes the prospective buyer, whether the transfer is within the Union, the transferor type, the sale method and the physical handover. The duties follow from these attributes, not from intention.
  4. Preflight the transfer. POST /compliance/used-vehicle-transfer-dossiers/{id}/preflight checks the planned transfer time against the legal position and names blockers. This stage may prevent the transfer — that is its purpose, not its failure.
  5. Deliver the dossier. POST /compliance/used-vehicle-transfer-dossiers/{id}/deliveries carries recipient, type, medium and time. The buyer receives the dossier verifiably; a verbal explanation cannot be evidenced later.
Preflight a used-vehicle transfer
curl -X POST \
  -H 'X-Api-Key: <API_KEY>' \
  -H 'X-Compliance-Organisation-Id: <ORGANISATION>' \
  -H 'If-Match: "<etag>"' \
  -H 'Idempotency-Key: transfer-vorpruefung-4711' \
  -H 'Content-Type: application/json' \
  -d '{"proposedTransferAt":"2026-09-20T08:00:00Z"}' \
  'https://api.tapinomahub.com/compliance/used-vehicle-transfer-dossiers/<id>/preflight'

What you end up with

What remains is a sale whose classification as a used vehicle is reasoned by an independent assessor, supported by a roadworthiness certificate, preflighted against the legal position and delivered verifiably to the buyer.

Where to find this in the documentation

The binding field lists, error codes and sample responses live in this surface’s OpenAPI contract at docs.tapinomahub.com (tapinoma-compliance). All use cases arranged by surface and role: overview of the use cases.

Frequently asked

Can I carry out the assessment myself?

The call takes the assessor’s qualification and an independence attestation. An assessment by the seller therefore does not carry the classification.

What if the preflight blocks?

Then a successful response names hard blockers with their code, for example because the latest effective roadworthiness and Annex I facts do not evidence a used vehicle or the transfer dossier has not been delivered to the prospective buyer in time. If a hard gate blocks the action itself, the server responds with status 422 and an error response.

Is it enough to inform the buyer verbally?

Not for the evidence. Delivery of the transfer dossier is an event of its own with recipient, medium and time.