Import data (CSV/XLSX)
Before you start
Section titled “Before you start”- A CSV or XLSX file with one row per record.
- Click “Import” from the feature you’re importing to (or from Settings → Data Import).
- Pick the upload type (e.g., “Supplier–variant links”).
- Choose your file.
- Map columns to fields. Logistified auto-detects common column names and reuses a saved template’s mapping. For columns it still doesn’t recognize, it can suggest a field using AI — suggested fields are highlighted (hover: “AI suggestion — review before importing”), so check each one and change it if it’s wrong. If suggestions are unavailable, map those columns by hand.
- If any mapped column holds dates, choose how they’re written (e.g. DD-MM-YYYY) — you must pick a format before you can continue.
- Preview parsed rows. Validation errors are highlighted.
- Fix errors (or remove bad rows). Re-preview.
- Click Import.
Worked example
Section titled “Worked example”Bulk-updating lead times for 200 supplier–variant links. CSV has columns “supplier_id”, “variant_sku”, “lead_time_days”. I map those to the matching Logistified fields, preview, fix two rows that had invalid SKUs, and import.
Common failure modes
Section titled “Common failure modes”| Symptom | Likely cause | Fix |
|---|---|---|
| Column mapping wrong | Auto-detect or an AI suggestion picked the wrong field. | Manually correct each — highlighted fields are AI suggestions worth a second look. |
| Can’t get past the mapping step | A date column is mapped but no date format is chosen. | Pick a date format (or Custom, with your own pattern) in the mapping step. |
| Many “duplicate SKU” errors | File has duplicate SKUs. | Dedupe in your spreadsheet first. |
| Import succeeded but values look unchanged | Mapping was wrong; values went to a different field. | Re-export from Logistified to see what landed where. |
See also
Section titled “See also”