Import issues
Setup import asks for review when spreadsheet data is unclear.
That is intentional. Import should stop on weak data instead of silently creating bad reusable records.
Columns do not map correctly
Check that your spreadsheet has clear column names such as:
- company name
- material name
- unit
- rate
- phone
- code
- description
You can manually choose the matching Kwantflow field during review.
Rows are blocked
Rows may be blocked when required information is missing, duplicate, ambiguous, or invalid.
Fix the row in the review step or update the spreadsheet and import again.
Common examples:
- a material row has no name
- a rate row has a unit but no rate
- the same record appears twice with conflicting details
- a company link points to a name that could match more than one record
Company or supplier links are unclear
If a rate refers to a supplier or company, make sure the company name matches an existing or imported company record clearly.
If the match is not clear, import the row first and link it later during review.
Cost codes do not import
Cost codes need a classification system. Import or select the classification system first, then review the cost-code sheet.
When to clean the spreadsheet first
Clean the source file before importing when:
- headings are inconsistent across sheets
- one column mixes units and notes
- supplier names vary from row to row for the same company
- rates use mixed currencies without clear labels
- old archived records are mixed with live records
Best practice
Import clear, reusable setup data first.
Leave one-off job details in the RFQ or estimate instead of forcing them into your long-term catalogue.