Several shops: what changes in the till

A multi-site POS has to answer a question a second till does not: must both shops see the same sales and stock immediately? Several terminals inside one shop can share the BelloPOS Pro database over the local network. Two distant shops cannot: BelloPOS synchronises no data between sites. A database and licence per branch with weekly consolidation may suit two small branches. If stock, customers or prices must be shared live, choose a cloud system built for that job.

Four situations, four answers

Multi-site often mixes four architectures. Place your project in one row before buying.

Your situation	Useful architecture	BelloPOS
One till, one shop	One local database	Lite, Go or Pro
Several tills, same building	Server database and terminals on the LAN	Pro
Two shops, weekly reporting	One database per branch and consolidated exports	Possible, with manual work
Several shops, live stock and sales	Common cloud database and synchronisation	Not suitable
Franchise, autonomous shops	Database per franchisee and common export format	Possible if delayed reporting is enough

Do not artificially stretch Pro’s local network through a VPN between cities. An outage, changed address or switched-off server would make the remote branch depend on infrastructure the product was not designed to carry.

---

What actually needs to be shared

“See all my shops” is not a precise requirement. List each object and give it an acceptable delay.

• Catalogue and prices: A weekly update can serve two stable shops; a promotional chain needs immediate central publishing.
• Stock: A transfer needs two consistent movements. Without sync, global stock is exact only after consolidation. See our inventory guide.
• Customers and loyalty: If points earned in one city must be spent in another a minute later, you need one database.
• Sales and margin: Dated exports can run the week. They arrive too late for today’s stock move.
• Users: Local accounts work when teams stay put. Mobile employees need shared identities.
• Backups: Every local database needs its own external copy; two shops double the routines, not the safety.

Write immediate, daily or weekly beside every line. That delay chooses the architecture. Our local versus cloud POS guide explains remote access, outages and backups.

A realistic routine for two branches

This works when the owner accepts a weekly view and each branch sells autonomously. It does not imitate synchronisation that does not exist.

1. Create one database and licence per branch. Give products a common code from day one.
2. Set one closing day and time. Both managers close the same period before new sales.
3. Export sales, payments, stock and margin. Put site and period in the filename and never overwrite the prior export.
4. Consolidate in a master workbook. Add revenue and payments while keeping a column per branch.
5. Record every transfer twice. An exit at the sender and entry at the receiver with the same reference.
6. Check four exceptions. Unknown codes, duplicates, overlapping periods and negative stock.
7. Back up every database separately. A consolidated file is not a till backup. Read the weekly retail indicators only after this check.

With clean codes this can take under an hour for two branches. At five, multiplying files and transfers is the signal to change architecture, not hire someone to repair spreadsheets.

When cloud is genuinely the right buy

Choose cloud multi-site POS when head office must publish prices, see sales, move stock or block a user without waiting for Friday’s export. The subscription then buys a real service: a common database, synchronisation, backups and remote access.

Ask for a demo with two pretend sites. Sell the last item at A and watch when it disappears from B. Cut A’s internet, keep selling, reconnect and create a conflict. The vendor must show the resolution rule, not only the dashboard.

Then compare the market in our Morocco POS comparison. The right candidate proves sync, export and outage recovery with your scenarios; it does not merely print multi-site in a feature list.

• Require: Branch permissions, activity log, complete export, conflict handling, documented outage mode and restorable backups.
• Cost: Subscription per site and terminal, installation, migration, support, connectors and data-exit cost.
• Test: Last unit sold concurrently, central price change, inter-site transfer, return at another branch and offline close.

The specification in ten questions

Send identical questions to every vendor and require a demonstrated answer.

• How many sites, terminals and users in two years?
• Which data must be instant and what can wait?
• What can one branch see about another?
• What happens when two sites sell the last unit?
• How does a branch work through an outage?
• How are conflicts resolved after reconnection?
• Can a central price preserve a local exception?
• How is a stock transfer traced end to end?
• Can products, customers, sales and stock be exported?
• What is the five-year cost including migration and exit?

Mistakes to avoid

• Confusing terminals with sites. The first is local networking; the second is synchronisation.
• Saying real time without a measured delay. Every fifteen minutes is not instant for the last unit.
• Treating consolidated stock as a backup. A total cannot restore receipts and customers.
• Forgetting transfers. They leave one site and enter the other under one reference.
• Buying for today’s two shops. Cost sites, terminals and users two years out.

---

Frequently asked questions

Can BelloPOS connect several tills?

Yes. BelloPOS Pro links several terminals to one database inside one shop over the local network. It does not synchronise distant shops.

Does BelloPOS manage branches in real time?

No. Each branch has a local database and nothing syncs to a cloud. Use delayed exports or choose cloud multi-site POS.

How do I consolidate two shops without cloud?

Use common product codes, close the same period, export each branch and combine the results in a master workbook with one column per site.

Can two shops share stock?

Not live with BelloPOS. Each shop holds stock; transfers are recorded at both ends and the total becomes accurate after consolidation.

When should I choose cloud POS?

When prices, stock, customers, loyalty or control must be shared between branches without waiting for a manual export.

What is the difference between multi-till and multi-site?

Multi-till means several terminals on one local database. Multi-site means separate premises that exchange or consolidate data.

What to take away

BelloPOS Pro answers several tills inside one shop. Two small autonomous branches can run separate databases and consolidate weekly. When the project’s value is live shared stock, customers or control, choose genuine cloud multi-site POS: that is precisely what BelloPOS does not do.

Read next

Other practical guides on the same subject:

• Offline POS or cloud POS: how to choose in Morocco
• POS software compared in Morocco 2026: nine systems, honestly reviewed
• The ten numbers to check every week
• Stock management step by step: a guide for small shops