EU Battery Passport Validator & DPP Generator

Turn incomplete battery product data and evidence into traceable EU Digital Product Passport (DPP) readiness assessments and preparation packages.

This Actor is a readiness aid, not a legal certification, conformity assessment, official DPP, or EU DPP Registry submission service. It never logs in to, registers with, or submits data to the EU DPP Registry.

Start here — free, deterministic, and credential-free

Run the built-in example unchanged:

{
  "mode": "audit-and-build",
  "sector": "battery",
  "useExampleData": true,
  "strictness": "official-evidence-only",
  "outputFormats": ["json", "csv", "html", "qr"]
}

It processes three synthetic battery records: a nearly complete EV record, an incomplete LMT record, and a deliberately conflicting industrial-battery record. Missing evidence and conflicts are returned as readiness data, never hidden or treated as a fatal exception. This fixture makes no external request, requires no buyer credential, does not contact a Registry, and emits no buyer-value event.

Input contract

The public form and runtime use one canonical input contract. sourceDatasetId is the dataset field and maxProducts is the workload field. Earlier existingDatasetId and maxItems names are accepted only as non-public compatibility aliases; new integrations must use the canonical names.

Field	Use
mode	audit, audit-and-build, validate-existing, or monitor.
sector	battery only. No unfinished sectors are exposed.
useExampleData	Run the deterministic free fixture instead of buyer data.
strictness	official-evidence-only or allow-unverified.
language	en only in this release.
records, productUrls, evidenceUrls, sourceDatasetId	Audit-mode product and evidence inputs.
dppRecords	Existing structured DPP/product records, primarily for validate-existing.
dppUrls, monitorChecks	Public deployed DPP URLs and monitor controls, primarily for monitor.
outputFormats, includeQrCodes, includeHtmlReport	Package controls. JSON readiness data and DPP preparation JSON/XML remain machine-readable core artifacts.
maxProducts, requestTimeoutSecs, maxDocumentSizeMb	Bounded work controls: 1–500 products, 5–120 seconds per request, and 1–25 MB per document.

Public URL inputs accept credential-free HTTP(S) JSON, XML, CSV, text/HTML, and text-based PDFs. Every hostname and redirect is checked against private, local, and reserved address space. The Actor never bypasses a login, paywall, CAPTCHA, or access control.

Examples

Product and evidence URLs

{
  "mode": "audit-and-build",
  "useExampleData": false,
  "productUrls": ["https://example.com/battery-product"],
  "evidenceUrls": ["https://example.com/battery-technical-sheet.pdf"]
}

The example domains are placeholders: replace them with public documents you are entitled to retrieve. Each successfully completed buyer-supplied product-model assessment may trigger the documented pay-per-event charges.

Battery product records

{
  "mode": "audit-and-build",
  "useExampleData": false,
  "strictness": "official-evidence-only",
  "records": [{
    "productId": "BAT-100",
    "productName": "Example industrial battery",
    "manufacturer": "Example Manufacturer",
    "batteryCategory": "industrial",
    "model": "BAT-100",
    "capacityKwh": 4.2,
    "batteryChemistry": "LFP",
    "carbonFootprintKgCo2e": 220,
    "manufacturingLocation": "DE",
    "evidence": [{
      "field": "capacityKwh",
      "value": 4.2,
      "sourceType": "manufacturer_technical_document",
      "sourceUrl": "https://example.com/battery-technical-sheet.pdf",
      "documentHash": "sha256:replace-with-real-hash"
    }]
  }]
}

Strict mode accepts official_regulatory, manufacturer_technical_document, manufacturer_declaration, verified_test_report, and conformity_document, each with a stable URL or document hash. It never manufactures provenance, chooses between conflicts, or infers omitted values.

Existing Apify dataset

{
  "mode": "audit",
  "useExampleData": false,
  "sourceDatasetId": "DATASET_ID"
}

The dataset must be readable to the run. Rows are evaluated as battery product records.

Existing DPP validation

{
  "mode": "validate-existing",
  "useExampleData": false,
  "dppRecords": [{}]
}

An empty object intentionally returns structured missing-data findings; it is useful for checking that your DPP mapping supplies all required fields.

Monitoring

{
  "mode": "monitor",
  "dppUrls": ["https://example.com/battery/BAT-001"],
  "monitorChecks": ["availability", "https", "structured-document"]
}

Monitor mode checks bounded availability, credential-free HTTPS URL syntax, and a recognizable structured-document content type. It does not claim Registry validation, identifier-authority checks, QR-target verification, or evidence-link crawling.

Outputs

Each readiness result contains a transparent score and status, scope note, missing data/evidence, conflicts, validation findings, deterministic preparation identifier, QR target, and draft DPP preparation object. The default key-value store uses the DPP- prefix and can include:

• DPP-SUMMARY.json
• DPP-EVIDENCE.csv and DPP-MISSING-DATA.csv when CSV is selected
• DPP-VALIDATION-ERRORS.json
• DPP-PREPARATION.json and DPP-PREPARATION.xml
• DPP-REPORT.html when HTML is selected
• DPP-QR-MAPPING.json and one PNG per product when QR is selected
• DPP-ARTIFACT-INDEX.json, plus DPP-PREPARATION-PACKAGE.zip when ZIP is selected

A QR code targets a supplied valid HTTPS DPP URL only when one is present. Otherwise it encodes a visibly non-deployable Zentra preparation URI.

Pricing

The built-in fixture is free. A successful buyer-supplied product-model assessment charges $1.50 once via product_model_audited. In audit-and-build and validate-existing, a real machine-readable preparation record can charge $0.01 via dpp_record_generated. Retries, invalid input, skipped duplicates, and the synthetic fixture do not double-charge or emit buyer-value events.

Regulatory sources and limits

The transparent 2026-08-14-verified ruleset is intentionally partial. It cites the current consolidated Battery Regulation, the European Commission’s Digital Product Passport overview, DPP Registry guidance, and ESPR. Consult qualified legal and technical advisers for applicability, final access-rights rules, official data semantics, technical hosting, identifiers, and any Registry interaction.