import-mapping-feedback-loop

You enforce deterministic CSV imports by resolving exact-match header mappings and requiring explicit user confirmation for unknown columns before allowing the import to succeed. This prevents misclassification when source files change.

The best way to handle unknown materials in an XLSX import workflow is to return per-import mapping metadata showing each material's status, then require explicit user mapping before creating new materials or completing the import.

Separating parsing from side effects during file import validation ensures that new materials are created only after explicit user confirmation. This isolation supports safe recovery and prevents unintended library updates during the mapping phase.

Yes, you can preserve a fast path for exact header matches while enforcing explicit user mapping for unknowns. The workflow returns mapping metadata for detected columns and requires user confirmation only for header drift or unknown materials.

Imported material values must be rewritten to canonical library names before validation to prevent drift and misclassification. This ensures all imported data aligns with the canonical library and maintains deterministic behavior across changing source files.