Case taxonomy

Supported red cases

This taxonomy covers the exception types RegMend currently rescues for EUDR operators and importers. It is deliberately fixed and versioned — new codes are added as new categories of exception prove common, not invented ad hoc per case.

Geolocation

RM-GEO-001Invalid coordinates
RM-GEO-002Invalid geometry
RM-GEO-003Invalid or malformed GeoJSON
RM-GEO-004Open polygon
RM-GEO-005Polygon intersection/overlap problem
RM-GEO-006Invalid geometry type
RM-GEO-007Coordinate precision/rounding issue
RM-GEO-008Coordinate outside valid range
RM-GEO-009Production-country mismatch
RM-GEO-010File-size/geometry-complexity issue
RM-GEO-011Plot area/geometry inconsistency
RM-GEO-012Production-place mismatch

Supplier/Data

RM-DATA-001Required field missing
RM-DATA-002Supplier information incomplete
RM-DATA-003Producer information incomplete
RM-DATA-004Conflicting field values
RM-DATA-005Invalid datatype/format
RM-DATA-006Production-country conflict
RM-DATA-007Product/commodity mismatch
RM-DATA-008Duplicate/ambiguous record

Traceability

RM-TRACE-001Lot-to-plot linkage missing
RM-TRACE-002Supplier-to-producer linkage missing
RM-TRACE-003Product-to-commodity linkage unclear
RM-TRACE-004Origin chain incomplete
RM-TRACE-005Plot-to-lot reconciliation failure
RM-TRACE-006Upstream-reference reconciliation issue

Evidence

RM-EVID-001Required evidence missing
RM-EVID-002Evidence conflicts with record
RM-EVID-003Evidence incomplete
RM-EVID-004Documents conflict
RM-EVID-005Evidence provenance unclear

Supplier Follow-up

RM-SUP-001Supplier follow-up required
RM-SUP-002Supplier clarification required
RM-SUP-003Incomplete supplier response
RM-SUP-004Contradictory supplier response
RM-SUP-005Supplier non-response
RM-SUP-006Producer information required

DDS/System

RM-DDS-001DDS reference problem
RM-DDS-002Reference verification mismatch
RM-DDS-003Existing DDS reconciliation problem
RM-DDS-004Submission validation failure

Escalation

RM-ESC-001Client decision required
RM-ESC-002Legal interpretation required
RM-ESC-003Specialist review required
RM-ESC-004Data cannot be substantiated
RM-ESC-005Case cannot safely be remediated

Don't see your exact case? Tell us about it — the taxonomy grows with real cases.

Request a Rescue