elevate techConsulting Group

Multi-location and franchise systems

The technology checklist before you open your next location

Before you open your next location, settle eight things: a POS built from a standard template, a master list of items or services, accounting mapping, payroll and timekeeping, inventory, network and devices, reporting, and a named owner for each. If all eight are decided before opening day, the new site starts on the same footing as the rest of the company.

Every location you open is either a copy of your standard or a new exception. Exceptions are cheap on day one and expensive for years. This checklist is for the owner or operating executive of a multi-location or franchise business. Use it with why POS and accounting numbers do not match, which explains what happens when the checklist is skipped. More on our approach is on the multi-location and franchise systems page.

Why does the checklist matter?

Most technology problems at multi-location companies are people and process, not the software. They come from each location being set up by whoever was available, in whatever way worked at the time. A checklist replaces memory with a repeatable process, and gives you a place to record decisions so the next opening is faster.

We saw this on a long-running engagement with a specialty bakery franchise. David was lead consultant and technology lead while the network grew from about 105 to over 200 locations. The work produced a phased roadmap across ERP, point of sale, franchise management and CRM, and a cloud ERP went live about 18 months after first discovery. The point of a roadmap like that is simple: when a network is doubling, you cannot afford for each new opening to reinvent its systems. The standard has to exist before the openings do.

1. Is the POS built from a standard template?

Do not configure the new register by copying whichever store is closest. Keep one master template, and build every new location from it. The template should include:

Test it with a script: ring every kind of sale, then confirm each one appears correctly in the reports.

2. Is there one item or service master?

Items, menu entries, products or service codes should come from a single master list, not be created at each location. Each location should be able to turn items on or off and set local pricing where you allow it. They should not be able to invent new items without approval. A drifting item list is the root of most reporting arguments later.

3. Is the accounting mapping decided?

Decide, before the first sale, which account and which location or entity tag each POS category lands in. Include clearing accounts for card and cash deposits, gift card liability, tips and tax. Test the path from a sale to a posted entry, with a real or test transaction, and confirm the location shows up on the report. If a new legal entity is being created, set up the bank account, merchant account and ledger entity in time.

Want to see where your current locations already differ from each other? Start with a quick check.

Take the Systems Check

4. Are payroll and timekeeping ready?

A new site means new employees, probably in a new state or jurisdiction. Settle which payroll and timekeeping system the staff will use, how clock-in links to the schedule, how tips and overtime are handled, and who approves hours. Confirm that new-hire paperwork, tax registrations and benefits enrollment are in place before the first shift. Link the labor cost back to the location in the same way sales are tagged, so you can see profit by site.

5. How will inventory be handled?

Decide how the new location orders, receives, counts and records waste or shrink. Whether you use a formal inventory system or a simple count process, the rules should match the rest of the company. Set up suppliers, delivery schedules and the approval path for orders. Confirm that purchases flow to accounting in the same way as elsewhere. Without that, cost of goods sold at the new location will not be comparable with the others.

6. Are the network and devices in place?

Registers, printers, tablets and Wi-Fi are boring until they fail on opening day. Plan the following well ahead, as internet service installation can take time:

7. Will reporting work from day one?

A new location should appear in your reports as soon as it sells something. Check that the location is in the daily sales report, the labor report, the exception report and the monthly financial package. Confirm who reads each report. If you give franchisees or managers a dashboard, make sure the new site is on it. Reports that need rebuilding by hand each time a location opens will fall behind, and then people stop trusting them.

8. Who owns each item?

Every line above needs a named owner, a due date and a sign-off. Not a department, a person. The most common failure is a task everyone thought belonged to someone else. A simple table does the job.

AreaDecision or checkOwnerDueSigned off
POSBuilt from the standard template and tested with every sale type☐
Item masterItems loaded from the master, no local invention☐
AccountingMapping, clearing accounts and location tags tested end to end☐
Payroll and timeRegistrations, system access and tip rules set☐
InventorySuppliers, ordering, receiving and counts defined☐
Network and devicesPrimary and backup service, hardware configured, support contact named☐
ReportingLocation appears in daily, labor and monthly reports☐
Go-live testA full dry run from sale to ledger before the doors open☐

What systems does a new location need on day one?

Eight things need to be working before the first customer: a point of sale built from your standard template, an item or service list drawn from one master, accounting mapping that lands each sale in the right account and location, payroll and timekeeping, inventory ordering and receiving, network and devices with a backup connection, reporting that shows the new location from its first sale, and a named owner for each of these.

If any one of them is missing, the location opens as an exception, and exceptions are what make month-end slow later. The table above turns the list into an owner, a due date and a sign-off for each line.

Who orders and configures them?

Split it by what each person is good at, and name one coordinator above them all. Operations or finance should own the decisions: the standard, the item list, the account mapping and the reports. IT, or your managed provider, orders and configures the devices, network and POS from the template. Payroll or HR owns registrations and timekeeping setup. The location manager and the purchasing lead own inventory counts and supplier setup.

The coordinator, one person with authority across operations and finance, makes sure none of it is assumed to be someone else's job. Order hardware and network service early, since both can take time, and have the devices configured before they ship to the site, not by the manager in opening week.

What breaks most often at opening?

In our experience the same few things break, and almost none are the software itself. The item list was copied from the nearest store and carries its old exceptions. Tax is set wrong for a new jurisdiction. The accounting mapping was never tested with a real sale, so the first deposits do not match. A network or payment device that was not tested under real use fails on opening day. And the new location is missing from a report that someone reads daily.

A full dry run from a sale to a posted entry, before the doors open, catches every one of these. Watch the first two weeks closely, compare against a sister location, and update the template with what you learn.

What should you do after the location opens?

Watch the first two weeks closely. Read the daily exception report and compare the new location's numbers with a sister location of similar size. Note what went wrong, and update the template and the checklist. A checklist that is improved after every opening becomes the main asset of a growing network.

If you are growing through acquisition rather than new builds, see the first 100 days of technology integration. If you want help building the standard itself, read more on multi-location and franchise systems.

Common questions

How far ahead of opening should systems work start?

Start well before the lease is signed or the build-out ends, because several items, such as network service and device delivery, have lead times. Leave time to test the full path from a sale to the books before opening day.

Who should own the systems checklist?

One named person with authority across operations and finance, not just IT. Each line on the checklist also needs its own owner, so that nothing is assumed to be someone else's job.

Should every location run the same systems?

Within a company, yes, wherever possible. Standard systems make training, reporting and support simpler. Exceptions should be deliberate and written down.

What if existing locations are already inconsistent?

Start the new location on the standard setup, and then plan the clean-up of existing sites in order of risk. Do not copy an old location's setup just because it is the nearest example.

Not sure where to start?

Take a free three-minute score. If a conversation makes sense, it will offer one.