The everyday problem
Importing a full spreadsheet before checking its structure can multiply a simple mapping error across hundreds of records. Start with a small sample that represents the awkward cases, not only the easiest items.
A workable process
Get the required template for your installed edition. Include examples with long descriptions, leading-zero codes, units and variants where applicable. Review spreadsheet formatting and map each column deliberately. Keep a copy of the original file before changing it for import.
A practical example
An item code such as 00125 can become 125 when treated as a number by a spreadsheet. If the code is used for matching, that formatting change may matter. Inspect the actual imported identifier and compare it with the intended record.
Before you finish
Check the imported items on the lookup screen and relevant reports. Agree how to correct or repeat an import before loading the complete list; do not assume importing the same file again is harmless.
Try this check with your team
Build a trial sheet with ten representative items, including a leading-zero code, a local-language name, a decimal rate and a different selling unit. Import through the supported mapping and inspect those exact fields in the destination records.
What the result tells you
Expand the import only when the trial preserves the intended meanings. If a code or unit changed, correct the spreadsheet format or mapping and establish the retry procedure before processing hundreds of records.
See this workflow in Speed Plus.
Bring a sample transaction and your questions to a product demo.
Book a free demo ↗