Running a branch 1 min read اقرأ بالعربية

Moving to a new system without closing the branch

Most of the risk in a new system is in the move, not in the software. A checklist for the data, the cutover night and the first shifts.

Clean the data before you move it

Items that no longer sell, duplicate customers, prices nobody has checked in a year: whatever is wrong in the old system arrives in the new one, only faster. Before the move, go through the item list and the prices with the people who actually use them, and decide what the opening stock and balances should be.

Decide what comes across

Not everything needs to. Items, prices, customers and opening balances usually do; years of old tickets usually do not. Keep the old records somewhere you can read them, for returns and reports, rather than forcing them into the new system.

Pick the quietest hours for the cutover

Move after closing, or on the quietest night of the week, and move one branch first. Check the first day's sales and the day-end in that branch before the others follow.

Train on your own menu, in your staff's language

People learn faster on the items they sell every day than on a demo list. Train cashiers and supervisors on your own menu or product list, in Arabic or English as they prefer, and let them ring through a few practice sales before the real ones.

Keep support close for the first shifts

The first busy shift will find the questions training did not. Make sure someone who knows the system is on site or on the phone, and that the staff know how to reach them.

How we do it

ELTS installs its systems on site, brings your data across and trains your staff, in Arabic and English. Talk to us about moving your branches.

An unhandled error has occurred. Reload 🗙