Review import warnings
Check warnings, preserved source fields and possible duplicates before committing rows.
Import Wizard
Review import warnings
Review warnings before commit so your team understands which rows need extra attention.
Types of warnings you may see
Warnings can appear when a row has preserved source fields, possible duplicate matches or values that need review before import. A warning row may still be selectable for commit, so use the issue text and normalised data together.
- Preserved source fields
- Extra columns can be kept as import notes or safe metadata when they do not map directly to a Fencify field.
- Possible duplicates
- Fencify checks for likely existing suppliers, inventory items or leads using tenant-scoped matching.
- Financial access warnings
- Finance-related fields and import types require financial visibility.
Duplicate review checks
For supplier imports, compare the supplier name and email. For inventory imports, check the item name, supplier SKU and supplier match. For lead imports, compare contact details and site address before choosing a duplicate policy.
When to adjust mapping
If a warning appears because an important column was preserved as metadata, go back to mapping and choose a more suitable Fencify field. If the warning is expected source context, keep it preserved and continue.
Before committing warning rows
- Confirm the row status and issue text.
- Check normalised data for names, dates, amounts and record matches.
- Choose a duplicate policy that matches your business process.
- Untick any row that should be handled later.