Almost every POS lets you bring your products in from a spreadsheet. The upload itself takes minutes. What takes time, and what decides whether your first week is smooth, is the state of the file. A messy CSV produces duplicates, missing prices and stock that is wrong from day one. This checklist walks through how to prepare a spreadsheet so your POS product import goes cleanly the first time.
Start by exporting what you have
Pull a full item export from your current system, or gather the spreadsheets you use today. Keep an untouched copy as a backup, and work on a duplicate. If you are leaving another POS, our guide to switching POS systems without losing data covers what else to export, such as customers and sales history, and the spreadsheet to inventory software checklist helps if your catalog lives in Excel.
The columns most imports expect
- Name: a clear, consistent description.
- SKU: a unique code per sellable item.
- Barcode: the UPC or EAN, stored as text so leading zeros survive.
- Price: the selling price as a plain number.
- Cost: what you pay, so margin reports work.
- Category: one consistent list, not free text.
- Vendor: the supplier, spelled the same way each time.
- Quantity on hand: the counted stock, per location.
- Tax treatment: taxable or exempt, matching your tax setup.
- Variants: size, color or other options, if you have them.
Not every system needs every column, and column names differ, so check your target system’s template or help page and match its headings. It is easier to rename headings in your sheet than to fix mismatches after the upload.
Clean the data
Remove duplicates
Sort by name and by barcode and look for items that appear twice with slightly different spellings. Two rows for one product split your stock count in half and distort reports. Merge them before the import.
Make SKUs and barcodes unique
Every sellable item needs its own SKU. Check that no two items share a barcode unless they are truly the same product. Our post on setting up SKUs and barcodes explains how to build a SKU scheme that lasts.
Protect leading zeros and long numbers
Spreadsheet programs love to turn barcodes into scientific notation or strip leading zeros. Format the barcode column as text before you paste, and save your file as CSV in UTF-8. Open the saved CSV in a plain text editor and confirm the barcodes still look right.
Standardize categories and vendors
Pick one spelling per category and vendor. "Mens," "Men’s" and "Men" become three categories in a report. A short, consistent list makes reporting, reordering and filtering far easier.
Check prices and costs
Look for blank prices, zero costs and prices with currency symbols or commas that may not parse. Sort by price and by margin and look at the extremes. An item priced below cost, or at ten times the normal price, is probably a typo.
Handle variants carefully
If a shirt comes in five sizes and three colors, decide how your target system models that: one parent product with fifteen variants, or fifteen separate items. Variants keep reports tidy and let you see stock by size. Ask for the import format for variants before you reshape your sheet, then test with a handful of items first.
Opening stock: count it, then load it
Imported quantities are only as good as your last count. Plan a physical count close to your go-live day, and load those numbers, not the old system’s figures. If you have several locations, give each its own quantity column. A clean opening count sets up later cycle counting to work properly.
Test with a small file first
Never load the whole catalog as your first attempt. Take 20 to 50 items that cover your messy cases: a variant item, one with a leading-zero barcode, an exempt item, an item with no vendor. Import them, then check each one on screen. Look at the name, price, cost, category, barcode and stock. Fix the sheet, delete the test items if the system allows it, and only then import the rest in batches.
Naming that helps your staff
A good product name tells a cashier what to pick up and tells a customer what is on the receipt. Put the brand and product first, then the distinguishing detail, for example size or color. Avoid internal shorthand that only the owner understands, and avoid all capitals, which are hard to read on a small screen. Consistent names also make search at the register faster, which matters when a queue is waiting. If you have thousands of items, fix the top few hundred sellers first and tidy the long tail as you go.
After the import
Spend an hour verifying before you open the doors. Sample twenty items at random and compare each against the source sheet. Scan twenty barcodes at a register to confirm they find the right item. Run a stock report and check that total units and total value are close to your count. Run a sales test with each tax treatment. Then keep the original CSV and the cleaned version together in a dated folder, so you can trace any odd value back to its source later.
What Retailer OS supports
Retailer OS supports CSV import for items, customers and vendors, and an AI-assisted import for other file formats. It also offers a full account export, in NDJSON, so your data stays portable. Moving a Shopify store is handled differently: the Retailer OS team moves the catalog, customers and orders for you, and it is not a self-serve import. The trial is 14 days with no card, so you can test an import with your own file before you commit. Pricing is $99.99 per store and $9.99 per user seat a month, from $109.98, billed monthly.
If the import fails or looks wrong
Read the error message first, since most point to a row and a column. The usual causes are a missing required value, a price with a currency symbol, an extra comma inside a name that is not wrapped in quotes, or a heading that does not match. Fix the sheet rather than the imported data, and re-run the small test batch. If a few hundred items land with the wrong category or price, it is usually quicker to delete the batch and re-import than to edit each one by hand.
Keep the sheet alive
After go-live, the POS becomes the source of truth, and the spreadsheet should retire. Do not keep editing both, or they will drift apart. Make one person responsible for adding new products in the system, and use the same naming and category rules you set during cleanup.
A pre-upload checklist
- Backup copy saved and the working copy identified.
- Duplicates merged and SKUs unique.
- Barcodes formatted as text and verified in a text editor.
- Categories and vendors standardized.
- Prices and costs reviewed for blanks and outliers.
- Tax treatment filled in for every item.
- Variants shaped to the system’s format.
- Opening stock from a fresh count.
- Small test batch imported and checked.
An hour spent on the spreadsheet saves days of cleanup afterward. When you are comparing systems, ask each vendor to import a sample of your real file during the trial, since that shows how it handles your data better than any demo. Our buyer’s guide and the retail POS system overview can help you choose, and you can request a demo to see an import with your own items.
Last updated October 5, 2026