Five checks before importing an inventory spreadsheet
Duplicate codes, unclear units and missing values can turn a simple file into an operational problem.
1. Keep item identity stable
An item name may change, but its code should identify one item. Review DEMO-SCREW and demo-screw before import: letter case alone does not establish two different products. Do not invent a new code just to bypass a duplicate warning.
2. Make units explicit
Ten pieces, ten packs and ten kilograms are different quantities. Agree on base units and pack conversions before merging files. Matching column names cannot resolve differences in meaning.
3. Separate blank from zero
A blank price means information is missing; a zero price may have a specific business meaning. Zero stock also differs from unrecorded stock. Ask the data owner for the correct values instead of filling gaps with zeros.
4. Check barcodes and currency separately
An SKU is not necessarily a barcode. Store barcodes with leading zeros as text so spreadsheets preserve them. Review the currency for every price: the current SKU Bridge beta defaults a blank currency to USD.
5. Transfer reviewed rows only
Keep the original file. In SKU Bridge, map columns, analyze and correct issues, recheck, and review which rows are selected for export. A standardized CSV is not a guarantee of compatibility with every ERP. Check the destination format and try a small import first.
Practice without confidential data
The SKU guide includes a small sample file. Ordinary file processing runs in the browser; choosing AI analysis sends headers and sample rows to the service. Use fictional data for practice.