Multiple locations: how do you organize your till system?
Moving from a single point of sale to several changes the nature of the decisions to be made: shared or adapted catalogue, modification rights, reporting and consolidation of sales, comparison between locations, harmonisation of equipment and procedures. This guide reviews the decisions to be made to organise a till system across several locations, including when the legal entities differ.

In this guide
At a single point of sale, the organization of the till is sorted out on the spot. Prices are changed by the person who knows them, figures are read in the evening, a correction is made on the fly. None of this automatically carries over when there are two, three, or ten locations.
What changes is not primarily technical. What changes is that you have to decide in advance what is common and what is specific to each site, and who has the right to modify what. These decisions then structure everything else: the configuration, the reporting of sales, the training, the opening of an additional site.
This guide reviews the questions to settle, in the order in which they generally arise.
What really changes with multiple locations
Three effects almost always appear.
Consistency becomes an issue. If a product is named differently from one site to another, or is filed under a different category, sales are no longer comparable. The problem isn't visible at a single site; it becomes central as soon as you want to add the figures together.
Distance introduces delay. You cannot be everywhere. A setup error at one location can go unnoticed for several days. Clear rules are therefore needed, rather than constant monitoring.
The decisions repeat themselves. A price change, a new menu, a new payment method: what was a single task becomes a task multiplied by the number of locations, unless the system lets you do it once.
Catalog, prices and permissions: the fundamental decisions
Two questions are dealt with together, because they answer each other.
Common or adapted per site
Many organizations opt for a middle-ground principle: a common base of products and categories, identical everywhere, with some room for local adaptation. This adaptation can relate to prices, when costs or customer base differ, to the availability of certain items, or to products specific to one location.
The common core is what makes analysis possible. The local margin is what makes the system acceptable to site managers. The balance between the two is a management choice, not a technical one.
Who changes what
Once the base has been defined, you need to say who can touch it. This question arises for creating products, changing prices, discounts, cancellations, till openings, and the establishment's settings.
| Decision | Rather at central level | Rather at site level |
|---|---|---|
| Product creation and naming | For everything that needs to be compared between sites | For products that are genuinely specific to one site |
| Selling price | When pricing policy must remain consistent | When the local market or costs differ |
| Discounts and goodwill gestures | To define the types of discounts allowed | To apply them within the defined framework |
| User accounts and permissions | For the general framework and profiles | For assigning the people present |
Writing out this table for your own organization, before any setup, avoids a long series of adjustments after going live.
Sales reporting and reading results
Consolidation involves gathering the sales from all locations into a single view. It assumes the data is comparable, which relates to the common core, and that the reporting works, which relates to the architecture chosen.
On this point, two approaches exist. In one, each till works on its own local data and transmits it to a central point at a defined frequency. In the other, tills work directly on a shared database. The consequences are not the same in the event of a network outage, nor in terms of how up to date the figures are. The exact terms should be checked according to the solution chosen.
Next comes the question of interpretation. Comparing ten locations across thirty indicators does not produce a decision, only fatigue. It is more useful to keep a few stable benchmarks, tracked over time, and to add a reading by product category to understand the differences. Raw comparisons between locations must be handled with care: floor space, location, opening hours and customer base often explain most of the differences.
On the ground: equipment, outages, opening a site, training
Standardize the equipment
Identical stations from one location to another simplify maintenance, spare parts and mutual support between teams. Full standardization is not always possible, particularly when a location was taken over with its existing equipment. A realistic goal is to converge gradually, as equipment is renewed.
Planning for a network outage
The question is not whether a connection will go down, but what happens on that day. The point to clarify with the installer: is it possible to keep checking out locally, and how do sales made during the outage rejoin the consolidation afterward. The behavior depends on the architecture chosen and must be checked before committing.
Opening an additional location
A well-organised system makes it possible to start from the common base rather than starting again from a blank page. This assumes that the base exists and is kept up to date. Also plan an opening checklist: user accounts, payment methods, printers, closing procedures.
Train everyone consistently
If each site learns in its own way, practices diverge and the figures become difficult to interpret. Short written procedures, the same closing routines everywhere, and one trained point of contact per site provide a common foundation without overloading the organization.
The case of franchising and management arrangements
When the locations do not belong to the same legal entity, as in a franchise or management arrangement, the management logic and the legal logic diverge. A network may want a common product base and reporting of indicators, while each operator remains responsible for their own business and their own obligations.
The points to clarify before any configuration are concrete: who owns the data for each location, who can view what, what the network requires and what it recommends, and how an operator's exit is handled. These answers fall under your contracts and your usual advisors; the till system merely translates them into rights and scopes.
Applicable obligations may change. Check the rules that apply to your situation with the relevant authorities.
Next step
Before comparing solutions, draw up three short documents: what is common to all locations, what remains free at the local level, and who has the right to modify each category of item. Add the list of indicators you will actually track every week.
You can refine this framework starting from the page need: multi-locationand review the fundamentals of the sales terminal on the page need: checkout.
OG Solutions analyses this organisation, then selects and configures the suitable solution from among the technologies it integrates.
Key takeaway
- The first decision in a multi-location project is to define what is common to all locations and what remains locally adaptable.
- A common base of products and categories is what makes sales comparable from one location to another.
- Modification rights must be defined in writing before configuration: product creation, prices, discounts, user accounts.
- The system's behavior in the event of a network outage should be checked before committing, since it depends on the architecture chosen.
- In a franchise or management arrangement, the operational logic and the legal logic are separate: the scope of data and access should be clarified beforehand with your advisors.


