Skip to content

How do you run several sites or branches on one system?

Short answer. Put every site on one system with one customer list, one product and job catalogue and one set of rules, then give each site its own view. Staff see their location by default, managers see the whole group, and stock, pricing, approvals and permissions are set per site only where they genuinely differ. Roll it out one site at a time, so the first location proves it before the rest move.

Several miniature wooden buildings arranged across a map-like pale surface connected by thin red thread to one central point
In this guide · 6 minute read

One set of records, a view for each site

The starting point is a single database where every record carries the site it belongs to. A job booked at the Geelong branch is a Geelong job, but it lives in the same system, uses the same customer record and the same product codes as a job booked in Dandenong. Each site's staff open the system and see their own jobs, stock and roster first, without wading through everyone else's.

Managers and head office get the group view: the same screens with the site filter taken off. The question “how did we go this week?” is answered once, from one place, instead of by ringing each branch manager and adding up their figures on a Monday morning.

Live freight dispatch map with an AI-suggested reroute
Live dispatch, with AI suggesting a reroute. Example screen; the name on it is invented.

Stock and staff that move between locations

Most multi-site businesses share more than they think. A wholesaler moves pallets between warehouses, a hospitality group sends a chef to cover a shift at its other venue, a trades business lends a technician and a van to the branch that's short. When each site runs its own tools, those moves happen by phone and nobody's records agree afterwards. On one system they become ordinary transactions with a record behind them.

  • 01Stock transfers that reduce one site's count and increase another's in the same step, with goods in transit visible to both.
  • 02One view of stock across sites, so a branch can sell from another location's shelf instead of saying no.
  • 03Staff with a home site who can be rostered at another, with their hours and costs landing against the site they worked at.
  • 04Vehicles and equipment booked by any site, so two branches don't plan around the same truck.

Pricing and approvals set by site

Some things really do differ by location. A regional branch may charge a travel surcharge, a CBD venue may have different menu prices, a new site may run tighter discount limits while its manager settles in. Set these as site-level rules that sit on top of one group price list, so the base price is maintained once and each site's differences are deliberate and visible.

Approvals work the same way. A branch manager might approve purchase orders and credits up to a set amount for their own site, with anything above that, or anything crossing sites, going to an operations manager. The rule lives in the system, so it's applied every time, and you can see who approved what.

★★★★★

“Great team to work with, really strive for success and provide excellent communication with any service provided.”
Pratham Choudhary · Client

Permissions by site and role, and reports that add up

Access is decided by two things together: which sites a person works at, and what their role lets them do. A store supervisor can edit rosters for their own store and see stock at the others. A finance officer can see every site's invoices but can't change a job. A regional manager sees the four sites they look after and nothing else.

Because every transaction already carries its site, consolidated reporting stops being a monthly project. Sales, margins, labour cost and stock value can be shown per site and for the group from the same data, so the branch figures always add up to the group total. If your accounting package uses tracking categories or separate entities for each site, the system can post to them directly.

Electrical trade ordering portal with orders, accounts and stock
Trade orders, accounts and stock in one portal. Example screen; the name on it is invented.

Rolling it out one site at a time

Pick one site to go first. A good choice is a site with a manager who wants the change and a workload that's typical of the group, so what you learn applies everywhere. Run the new system there on real work alongside the existing tools until the numbers match, then move that site's history across and retire its old tool.

The next sites go quicker, because the codes, rules and screens are already settled and the first site's staff can show the others how it works. Head office reporting covers moved and unmoved sites during the changeover, so the group view never goes dark while sites are switching.

The traps that catch most multi-site businesses

The common problems are rarely technical. They come from each site having grown its own habits, codes and files before anyone tried to put them in one place. Every one of them is easier to fix before the move than after it, while the old tools are still there to check against.

  • 01Each site keeping its own spreadsheet, so there are five versions of the price list and none is clearly the right one.
  • 02Inconsistent product or job codes, where the same item is three different codes at three sites and group reports can't add them up.
  • 03Copying the system per site, which brings back every problem of separate tools inside one product.
  • 04Letting every local variation become a setting, until nobody can say what the standard process is.
  • 05Moving every site on the same day, so one site's teething problem becomes everyone's.

Questions owners ask us

How do you stop one site seeing another site's data?

Each person's access is set by the sites they work at and the role they hold, and the system checks both on every screen and report. A site manager can be limited to their own location, given read-only access to stock at other sites, or given nothing beyond their own. Head office roles see the group. Because the rule is enforced by the system rather than by separate logins or files, it holds even when someone moves between sites.

Which site should move to a new system first?

Start with a site whose manager wants the change and whose work is typical of the rest of the group. A keen manager will report problems quickly instead of working around them, and a typical workload means the codes, rules and screens you settle there will fit the other sites. Avoid starting with your busiest site in its busiest month, and avoid an unusual site whose quirks would shape a system the others then have to fit.

Can sites have different prices but share one product list?

Yes, and that's usually the cleanest way to set it up. The product list and base prices are kept once for the whole group, and each site carries its own adjustments on top, such as a surcharge, a regional price or a tighter discount limit. When the base price changes it flows to every site, while each site's differences stay in place and are easy to review in one report.

How do we fix inconsistent product codes before moving?

Agree one master list of codes for the group, then map every site's existing codes to it before any data moves. Export each site's product or job list, line them up side by side, and decide which code survives for each item, keeping the old code as a reference so history still makes sense. It's slow, careful work, and it's far easier done once before the move than repeatedly in reports afterwards.

Show us how you run it today.

Thirty minutes with the people who would build it. We'll map where the hours go and tell you honestly whether custom software is worth it for you.