Quality & compliance
Score data completeness per locale and evaluate products against DACH food regulations, with fail-closed publish gates.
PIE separates two related checks: data quality (is the product data complete enough?) and compliance (does it satisfy the regulations for its markets?). Both are evaluated per locale and can gate publishing.
Data-quality scoring
You author completeness profiles — rule sets that define which attributes must be present and how they are weighted. Products are scored against the active profile per enabled locale, with fallback disabled, so a product that is complete in de-DE but missing a fr-CH translation scores lower in fr-CH.
A profile can be marked blocking: publishing a product that fails a mandatory rule in any required locale is then blocked until you fix it. The gate fails closed — if a required check cannot be evaluated, the publish is denied rather than allowed through.
Compliance frameworks
The compliance engine evaluates products against pluggable regulatory frameworks using a safe, no-eval condition and validator engine. Frameworks include EU FIC (food information), EU Organic, EUDR (deforestation), FSMA 204, HACCP, IFS/BRC, EU Health Claims, Novel Food, Packaging, and DPP/ESPR.
Open the Compliance Center to evaluate a product, drill into individual rule results, and export a compliance report as PDF (rate-limited and authenticated).
Locale-aware evaluation
Compliance is scoped by market and locale. A product sold in Germany evaluates against German rules; a Swiss product evaluates against Swiss market scoping. The drill-in has locale tabs derived from the product's market-required locales, so a product sold in several markets shows a tab per locale. A locale that has not been evaluated yet shows a disabled "Not evaluated — Re-evaluate" tab; clicking it evaluates that locale and makes the tab interactive.
Compliance scores are kept fresh: editing a translation or changing a product's markets re-scores the affected product, so you never publish against a stale evaluation.
The blocking compliance gate
Compliance gating is opt-in per framework. When you enable a blocking gate, publishing fails closed with a compliance error until the mandatory rules pass. Use it for the frameworks that are hard requirements in your markets.
For buyers: onboarding quality gates
Buyers (PIC admins) can author their own quality profiles and pin one to a supplier-onboarding request, so incoming supplier data must meet the buyer's bar before it is accepted. See the Onboarding guide.