From Excel to an Inventory System: How to Prepare Your Data Before Importing

Most businesses start managing stock in an Excel file, and that is a sensible choice at first: a spreadsheet is flexible, quick and familiar. As items, branches and staff grow, the file becomes a burden — several copies, balances nobody can trace, and duplicate items under different names. Moving to a dedicated inventory system is the right step, but its success depends on the quality of the data you bring with you. This guide explains how to prepare your file so you start on a sound footing.

Why copying the file as it is will not work

A file that has worked for years carries small mistakes that built up quietly: one item under three names, different units for the same product, empty cells sometimes read as zero, and balances for warehouses that have since closed. People work around these mistakes from experience; a system takes the data exactly as it is. Import the mistakes and you import the confusion, and the first weeks go to fixing what could have been fixed in a single day before the import.

Clean the file before importing

Names and codes that never repeat

Give every product a unique code (SKU) that does not change, and a clear name that describes the item precisely: type, size and pack. Sort the names alphabetically to find duplicates — you will often find the same item written in several ways. If a product has a barcode, keep it in its own column and do not mix it with your internal code.

Units and pack sizes

Choose a base unit for each product, such as a piece or a kilogram, and always record balances in it. If you buy by the carton and issue by the piece, add one column for the pack unit and another for the number of pieces in it. An illustrative example: a carton of 12 pieces means a balance of 5 cartons is recorded as 60 pieces. This clarity prevents the most common stock error of all — mixing cartons with pieces.

Warehouses and storage locations

Use a single column for the warehouse name, written exactly the same way on every row. If your warehouse is coded by location (zone, aisle, rack), add a column for the location code and make sure those codes are defined in the system before importing; a location the system does not know cannot be trusted.

Batches, expiry dates and serial numbers

For food, pharmaceuticals and anything with a shelf life, record the batch number and expiry date for each balance, and do not merge different batches into one row. Use one date format across the whole file. For equipment tracked by serial number, give each serial its own row or a clear list that matches the quantity.

Opening balances, once

The opening balance is each product's starting point in each warehouse, and it should be recorded only once. Pick a clear cut-off date: work in the file stops there, and movements in the system begin after it. Ideally, run a physical count of your important items before the import, so you start with figures you trust rather than figures you inherited.

A controlled import: check, correct, then confirm

A good import does not upload a file and hope for the best. The right way has three stages:

1. Mapping: the system recognises the file's columns, and you check that each column is linked to the right field and that warehouse names in the file are linked to your actual warehouses.
2. Checking every row: before anything is saved, each row is examined and classed as ready, ready with a warning, or blocked by an error. The reason is stated in plain language: a duplicate code, an unknown unit, a location that does not exist, or a missing expiry date.
3. Confirmation: after you fix the errors in the file and upload it again — or knowingly choose to import only the valid rows — you confirm. Good systems split large files into batches and never record a row twice if the import is retried after an interruption.

Pre-import checklist

• A unique code for every product, and no duplicate names.
• One base unit per product, with a clear conversion for packs.
• The same warehouse name on every row.
• Location codes already defined in the system.
• A batch number and expiry date for every item with a shelf life.
• A fixed cut-off date, and a count of your important items.

After the import

Keep a read-only copy of the original file as a reference that nobody edits, and stop working in it for good, so your business does not live with two versions of the truth. Review the stock report after the import and compare total quantities and values with the file, then start cycle counts of fast-moving items during the first weeks.

Do not forget the human side. Bring the warehouse team together before go-live and explain what changes: every receipt and issue is recorded in the system as it happens, balances are never edited by hand, and any difference is settled with an adjustment that has a reason. A new system with clean figures quickly loses its value if the team goes back to recording movements at the end of the day or on a side sheet of paper.

In MIRSAD, the import wizard recognises Excel and CSV columns in Arabic and English, checks every row before you confirm, shows the errors with a downloadable report, and then records opening balances in the right warehouses, locations and batches. You can explore the platform features.

Conclusion

Leaving Excel is not a copy-and-paste job; it is a chance to clean your data once and do it properly. Take the time to align codes, units, warehouses and locations, make the import a controlled process that checks every row, and you will start the new system with figures you can trust from day one.