Step 3 of 4 · Software and systems

Check software works on your team’s phones, in their language

A tool that runs on the owner’s phone may stall on a staff member’s budget handset. Test on every device, offline, and in the language your team reads.

Before you commit to any tool, install it on the actual phones your staff carry and the counter device you'll use, and switch it to the language they read comfortably. Then hand it to the least confident person on the team, give them one real task and watch without helping. If they can't finish it, the tool isn't ready for your business.

Why it matters

Owners usually test software on their own phone, which is often the newest and fastest one in the shop. The helper who'll actually use it every day may have a three-year-old handset with full storage, a cracked screen and a prepaid data pack that runs out by the 20th. Software that works for you and not for them simply won't get used.

Language is the other quiet failure. Many staff read Hindi, Tamil, Marathi, Bengali or another language far more easily than English, and some are more comfortable speaking than typing. At this stage you know exactly who's on the team and what they carry, so test for them, not for an imagined user.

How to do it

Do this during your trial, before paying. It takes an hour or two and saves months of staff quietly avoiding the new system.

  1. List every device that will run it

    Write down each phone, tablet or computer: whose it is, the model, how much free storage it has, and whether it's personal or shared. Check the tool's minimum Android or iOS version against each one. A phone with under 1 GB of free space often struggles with any new app.

  2. Install and log in on each one

    Give each person their own login rather than sharing yours, so you can see who did what and remove access when someone leaves. Note how long installation and login take on the slowest phone, and whether it needs an email address the staff member doesn't have.

  3. Switch to their language

    Check whether the menus, buttons and messages come in the languages your team reads. Then check the parts customers see: bills, receipts and WhatsApp reminders. Some tools translate the menus but print bills only in English, which may be fine for you or may confuse customers.

  4. Test typing, voice and font size

    Can staff type item names in their script, or search by a short code? Is there voice input for notes? Can the text be made larger for older staff or anyone who uses reading glasses? Small buttons on a small screen cause wrong entries during a rush.

  5. Turn the internet off

    Switch to aeroplane mode and try to make a bill or a booking. Does it save and sync later, or stop completely? Then try on a weak mobile signal at the back of the shop. Power cuts and patchy networks are normal; the tool has to survive them. Check how much mobile data a day's use consumes too.

  6. Connect the hardware

    If you'll print bills, test with your actual thermal printer over Bluetooth or USB, and your barcode scanner or weighing scale if you use them. Many problems show up only at this point, so test before buying new hardware to match.

  7. Run the one-task test

    Give the least confident team member one real job, such as billing three items with a UPI payment, and watch silently. Note where they hesitate. If two or three people get stuck at the same place, either the tool is wrong or they need a short session; see training staff on a new routine.

Your result

A device-by-device pass or fail, and a clear answer on language and offline use.

Tool tested: ________
Device 1: ____ (whose) | installs: y/n | runs smoothly: y/n
Device 2: ____ (whose) | installs: y/n | runs smoothly: y/n
Menu language available: ____ | bill language: ____
Works offline: fully / partly / no
Printer and scanner work: y/n
One-task test: who ____ | finished? y/n | stuck at ____
Decision: go / go with training / reject

Fill it in on your checklist, next to this topic. It stays in this browser.

Time and cost

Time
One to two hours across the team, done during the trial period.
Cost
Usually nothing. If a key phone can't run the tool, a basic Android handset for the counter is a modest one-time cost compared with a tool nobody uses; get a price locally.

Ballparks to verify: prices and fees change by city and over time, so check current rates before you budget.

Common mistakes

  • Testing only on the owner's phone

    Your phone isn't the one that matters. Test on the slowest phone that will run the tool every day.

  • Sharing one login

    When everyone uses the owner's login, you can't tell who changed a price or deleted a bill, and you can't lock out someone who has left.

  • Ignoring offline use

    If billing stops when the internet drops, the queue grows and staff go back to paper. Test it on purpose.

  • Helping during the test

    Pointing at the right button hides the problem. Watch first, help afterwards.

Go deeper

The playbooks are written for one business each. Start with the full playbook or find yours.

Questions people ask

Should I buy a dedicated phone or tablet for the counter?

Often it's worth it. A shop device keeps business data off personal phones, stays charged at the counter and doesn't leave when a staff member does. Lock it with a PIN and keep it signed in to the business account only.

What if the tool is only in English?

It can still work if the screens are simple and mostly numbers and pictures. Run the one-task test; if staff manage, it's fine. If not, look for a tool with your team's language before paying for training.

← All business basics

Menu

Read

Ask an expert Ask an expertFree, real peopleHub
Ask an expert