Use validation packs and understand the score
What the packs contain, what a validation run evaluates, and where the engine's authority ends.
DPP Shield editorial team · Updated:
What a pack is
A regulation pack is a versioned combination of a JSON Schema and a rule set for one product category. Packs carry a status (draft, active, retired) and an effective date.
The platform ships starter packs for 17 categories. They are enough to structure data and to catch missing or contradictory declarations, and they are not a legal interpretation of the delegated act.
Running a validation
- Open a passport and choose the market scope you care about.
- Run validation - the result is stored as a validation run against that version.
- Read the findings by severity, and use the next action as the shortest path to a better record.
- Re-run after you fix the data; the score moves with the record.
Market scoping
Rules can be scoped to markets, so the same passport can be evaluated for the EU, the UK or both, with per-market scores and missing fields and a conservative aggregate. Market scoping is how the platform avoids pretending that one jurisdiction's rules are universal.
Upcoming dates
The dashboard and the regulations page surface dated rules that apply to your categories, with the days remaining. Use them to plan evidence collection before a deadline rather than after it.
Your own rules
Company-specific requirements belong in Custom rules rather than in a pack, so a customer or retailer requirement never gets mistaken for a regulation. See the custom rules and extensions guide.
The boundary worth remembering
The engine is deterministic: given the same data and pack it returns the same answer, which is what makes it reviewable. It evaluates declared data against declared rules. It does not verify that a test report is genuine, and it does not certify a product. A qualified person remains accountable for the compliance claim.
Screen-by-screen reference
These pages were checked in the organization console on 8 October 2026 using an isolated sample organization. Controls can differ by role, plan, record state and configured providers. Each page below explains its purpose, a practical workflow, the visible controls and what to verify afterward.
Validation packs (/regulations)
The pack index lists category rule sets, versions, statuses, markets and effective dates used by the validation engine.
Start at the index to identify the category pack, its version, market, and current status. Open the pack to see what the validator actually checks, then use Watch when you need to compare captured versions over time. A starter or draft pack can guide preparation but should not be described as a completed legal assessment.
The bundled starter packs require legal review before production compliance claims.
Controls and options
- Open a pack to see its rule definitions and guided form schema.
- Regulatory watch compares captured pack versions and their portfolio impact.
- Read the pack status before relying on a result; a draft readiness pack is not an approved legal assessment.
Pack detail (/regulations/[category])
This page separates a pack's record, intended use, executable rules and form fields.
Read the pack record before the rule list: intended market, source, status, and effective dates determine how to interpret findings. A rule entry explains its condition, severity, field, and message, while the form schema shows what the editor can collect. Organization rules and custom extensions may add separate checks beyond this pack.
An organization rule or extension may add further checks beyond this pack.
Controls and options
- Check source, market, status and effective dates in Pack record.
- Read each rule's condition, severity, message and source in Validation rules.
- Use Guided form schema to understand which passport fields the category editor offers.
- Assess changes opens watch when an earlier capture exists; All packs returns to the index.