Moving From Excel to a POS System: A Practical Guide

Almost every shop that moves to a POS system already has its products written down somewhere. Usually Excel. Sometimes a notebook that a nephew typed into Excel once and nobody updated since.

The single most common reason owners delay the move is the belief that they will have to type everything in again. They will not. But there is a right and a wrong way to do this, and the wrong way costs more time than the typing would have.

Why Excel Stops Working

Excel is not a bad tool. It is a single-player tool, and a shop is not a single-player business.

• It is only current if one specific person updates it, and only accurate if nobody else has a copy.
• It does not reduce stock when a sale happens — someone has to remember, and remembering is the part that fails on a busy Saturday.
• It cannot tell you at 6pm what today's profit was, per branch, without somebody doing work.
• Two branches means two files, and two files means two different answers to the same question.

None of that means the spreadsheet is worthless. It means the spreadsheet is your starting point, not your system. We compare the two approaches in more detail in Excel vs POS software.

What a Clean Import File Looks Like

One row per product, one thing per column. At minimum:

• Product name — how you actually refer to it, not a catalogue description
• Cost price — what you pay for it
• Selling price — what the customer pays
• Quantity in stock — what is physically on the shelf right now

Strongly worth adding if you have them: barcode, category, unit (piece, carton, kilo), supplier, and expiry or batch if you run a pharmacy or sell food.

The cost price column is not optional

This is the one people skip, because a selling price feels like the important number. Skip it and your system will report every sale as pure profit, since it has no cost to subtract. The figures will look excellent and mean nothing — the mechanism is explained in why your POS profit figures are wrong.

If you genuinely do not know the cost of some items, import them with your best honest estimate and correct it at the next purchase. An approximate cost is far better than none.

The Five Things That Actually Break Imports

Rough data is fine. These five are the ones that cause real problems:

1. Duplicate product names. "Coca Cola 500ml" appearing three times with different prices is the number one cause of a messy result. Decide which row is right before importing, not after. Duplicates that slip through get merged, and you lose the distinction you meant to keep.
2. Prices stored as text. "GHS 12.50" in a cell is text, not a number. Strip the currency symbol and leave a plain number — 12.50. Mixed formats in one column are worse than a consistently wrong one.
3. Mixed units in one column. A quantity column where some rows mean cartons and others mean single pieces will produce stock figures that are wrong in ways nobody notices for weeks. Split it, or add a unit column.
4. Merged cells and multiple header rows. Beautiful for reading, unreadable for importing. One header row at the top, then data.
5. Totals rows at the bottom. A "TOTAL" row will import as a product called TOTAL with a very large stock quantity. Delete summary rows before you export.

One barcode per product

If the same product has been recorded with two barcodes, keep the one you actually scan. Two barcodes for one product means two stock counts for one shelf, and the shelf will never agree with either.

Validate Before You Load

The difference between a smooth migration and a bad week is whether the file is checked before anything is written.

A half-loaded import is genuinely difficult to recover from: some products exist, some do not, some have stock and some do not, and you no longer know which is which without going row by row. A rejected file costs you ten minutes and a corrected spreadsheet.

SellarPro's Smart Import analyses and cleans the spreadsheet and validates it before loading, so a bad file is rejected rather than partially applied. Whatever system you choose, ask specifically what happens when a file contains errors — "it will show you an error" and "it will stop before writing anything" are very different answers.

A Migration Sequence That Works

1. Export or tidy your current list. If you are leaving another POS, export products and customers from it. If you are on paper, type only your top sellers first — the long tail can wait.
2. Clean the five breakers above. Half an hour here saves a day later.
3. Import products. Names, prices, categories, barcodes.
4. Count physical stock and import quantities. Do this as close to go-live as you can. Quantities counted three weeks ago are fiction by the time you start selling. Where products already exist and only quantities need setting, use an opening-stock update rather than re-importing the whole catalogue — re-importing is what creates duplicates.
5. Import customers and suppliers. Customers need a phone number each, which matters if you sell on credit or intend to send reminders — see managing debtors.
6. Spot-check before going live. Pick ten products across different categories and confirm name, cost, selling price and quantity against the physical shelf. Then check your total stock value against roughly what you expect. If it is wildly out, something imported in the wrong unit.
7. Run test sales, then clear the test data. Confirm the workflow end to end, then wipe the test transactions before real trading starts.

Should You Import Everything at Once?

Two workable approaches, and the right one depends on the state of your file:

Import everything if your list is reasonably current. You get accurate stock control from day one, and it is the cleaner outcome.

Start with your best sellers — the twenty to thirty products driving most of your revenue — if the list is old, badly maintained, or full of things you no longer stock. You will be selling accurately within a day, and adding the rest during quiet periods is far less painful than delaying the whole move until a perfect spreadsheet exists. It never does.

What does not work is importing a list you know is wrong and intending to fix it later. The corrections rarely happen, and every report built on that data inherits the errors.

After the Import

The migration is not finished when the products load. Three things decide whether the system stays accurate:

• Receive all new stock through the system from day one. See purchase orders.
• Set reorder levels on your fast movers so the system tells you what to buy.
• Count a section each week rather than everything once a year — see managing inventory in a small business.

SellarPro imports rough spreadsheets, validates before loading, and gives products without barcodes an automatic SKU. For larger or awkward migrations — exports from another POS, catalogues in the thousands — the team will clean and load the file for you as part of onboarding. See inventory management and POS system.

The spreadsheet you already have is not an obstacle to moving. It is most of the work, already done.

Frequently Asked Questions

Part of our Inventory Management resources — see the full guide and related tools.