The cheapest system on any shortlist is usually the one that fits exactly one shop. That is not a trick, it is arithmetic: fewer assumptions, less to build, less to support. It is also the reason a lot of Maldivian businesses replace their software in year three, at the precise moment they can least afford the distraction, because they have opened somewhere else.
Growth here has a particular shape. It is rarely a bigger shop. It is a second one, on another island, staffed by somebody you see once a month.
The four questions
Can stock belong to a location? If the system holds one quantity per product, two shops share a number that is true in neither. Every count from then on is an argument.
Is moving stock a document? A delivery lands in Malé and half of it goes on the next boat. If that movement is a phone call, it evaporates the day the person who made it goes on leave. It should be a record with a date, a quantity and two locations, and it should be visible from both ends.
Can each place see itself, and can you see both? A manager who cannot see their own location's numbers cannot be held to them. An owner who can only see locations separately is doing addition every week. Both views should exist without exporting anything.
What can staff do when you are not there? On the island you did not visit this week, permissions are the whole of your supervision. Selling and taking payment is one level. Receiving stock and giving discounts is another. Editing a posted sale, changing a price or exporting the customer list should be yours alone.
The cost nobody quotes
Ask what growing costs. Some systems charge per location, some per user, some per device, and some quietly move you to a different plan at the second branch. Any of those can be reasonable. What is not reasonable is finding out at the moment you sign the lease on the second shop.
Get the second location price in writing before you buy the first one. It is a free question and it changes the total honestly.
The migration you are trying to avoid
Replacing a business system is not a software project, it is an operations project. Product codes change, staff relearn a screen, historical sales sit in a place nobody can query, and every stock count starts from zero. Businesses put it off, which means they run the second shop on a spreadsheet in the meantime, which is where the real damage happens.
Buying something that already holds locations, even when you only have one, costs nothing extra on day one and removes that whole episode.
What to watch in the first month of two
- Transfers sent from one side and never confirmed at the other
- The same product entered twice under different names, splitting your reports in half
- Prices that have drifted apart between locations
- Credit followed by location rather than by customer, so a customer who buys at both has two balances and one memory
Where we stand
The same subject from the other side of the counter, written for the person using the till rather than choosing it, is on the product's own blog: running two shops on two islands from one login.
Every RekordPOS plan allows more than one branch, including the cheapest, because charging a growing business extra for growing struck us as a poor way to be treated. If you are opening a second location this season, talk to us before you set it up, not after: the difference between a second branch and a second business in the data is a decision made in about ten minutes at the start.