Ldora.
Learn25 October 20264 min read

Switching Supermarket POS Without Losing Data

What I learned moving 6,327 products from a supermarket's old POS to a new system: exporting and cleaning data, testing scale labels and checking customer credit.

Changing the checkout software in a supermarket sounds simple until you think it through: thousands of products with barcodes and prices, regular customers who buy on credit, a scale that prints weight labels, and a queue that will not wait while you figure things out. Many shop owners keep old POS software they dislike for years, simply because they are afraid of losing data in the move.

I understand that fear. I built a POS system called Sepehr for a supermarket. It replaced the shop's old POS software and is now in use at the shop, while I keep developing it. In that move, 6,327 products came across from the old system. Here is what I learned, in case you are thinking about switching too.

Know exactly what you are moving

Before anything else, write down which data must survive the switch. Usually that means:

  • Products: name, barcode, selling price and any categories you use.
  • Customer accounts: name, phone number and each person's balance.
  • Scale labels: how weighed items are encoded on the labels your scale prints.

Owners often think only about products and forget customer balances. For a neighbourhood supermarket, the credit book is worth as much as the shelves. If a customer finds their balance wrong, you lose their trust.

Export from the old system, then clean the data

Most older POS programs offer some kind of export — a spreadsheet, or a database that takes patience to read. Get the data from the system itself, not from paper or memory, and keep an untouched copy.

Then clean it before importing:

  • Find duplicate products sharing one barcode.
  • Separate items with no price or a zero price.
  • Unify Arabic and Persian letters (such as «ي» and «ی») in names, or search in the new system will miss products.

With Sepehr, this is where most of the time went: not building screens, but making sure every product arrived with the right barcode and price.

Test barcodes and scale labels separately

A supermarket has two kinds of codes: normal barcodes on packaged goods, and labels the shop's scale prints for weighed items like fruit, cheese or meat. In Sepehr these scale labels carry a 20-digit code that holds the product and its weight or price, and the checkout must read it correctly.

Test this on its own. Weigh a few real items, print labels and scan them in the new system. A misread weight or price is not a small error — it repeats every day, against you or against your customer.

Check customer credit one by one

Don't stop at "the number of customers matches". Pick a few customers you know well and compare their balances in the old and new systems side by side. If those are right, the rest probably are too; if not, you found the problem before a customer is standing at the counter.

In Sepehr each customer has an account, and credit purchases and payments are recorded there — no paper notebook next to the till.

The first day on the new system

Choose a quiet day to start, not your busiest one. A few things help:

  • Test receipts. Sepehr prints on 80 mm paper; make sure the printer is connected and receipts are readable.
  • Keep cash and card separate. Sepehr keeps a cash ledger and a card-reader ledger, so at closing you know what should be in the drawer and what came through the card reader.
  • Prepare your staff. Even simple software needs a few days of getting used to.

When software is built for your own shop, any screen where staff get stuck can be made simpler. I did the same for the Cafe Barama system, shaping screens around the staff's real work.

Checklist for switching your POS

  1. List the data to move: products, barcodes, prices, customer accounts.
  2. Export everything from the old software and keep an untouched copy.
  3. Clean the data: duplicate barcodes, zero prices, mixed Arabic/Persian letters.
  4. Compare product counts in both systems.
  5. Test real scale labels with weighed items.
  6. Compare a few known customers' balances in both systems.
  7. Test receipt printing and the cash and card ledgers.
  8. Start on a quiet day, with staff trained beforehand.
  9. Keep the old system available for reference until you are sure nothing is missing.

Wrapping up

Switching POS feels risky because the whole shop depends on it. But with a proper export, clean data and careful tests of barcodes, scale labels and customer balances, you can leave old software behind without losing anything.

If you run a supermarket or shop and want to see how a custom POS could work for you, request a free demo. See it first, then decide.

More guides

24 October 20263 min read

Building a Website That Keeps Working in Iran

Why many sites load slowly or break in Iran, and how a local server, HTTPS and no foreign services like Google Fonts or reCAPTCHA keep yours working.

Read

23 October 20263 min read

Why a Café Menu Should Show Calories and Protein

What I learned building Cafe Barama's menu: showing calories, protein, carbs and fat per dish, totalled in the cart, builds customer trust.

Read