Hardware for more than one location

How to spec POS hardware across several restaurant locations: one standard kit, device counts by station, the network, spares and a swap plan.

A guest orders at the counter while a staff member rings it up on a tablet register with a card reader.

The short answer: buy a standard kit, not a different setup for every store

Spec one hardware kit for each type of location you run, write it down, and buy every store to that list. Decide device counts by station (registers, kitchen screens, kiosks, displays), treat the internet connection as part of the kit, and keep spares on a shelf so a dead screen is a swap, not a crisis.

Most groups end up with a different mix at every site. The first store got whatever the opening budget allowed, the second inherited a previous tenant's gear, and the third was set up by a manager who liked a different tablet. Every difference becomes a separate support question, a separate charging cable and a separate thing nobody remembers how to fix at close. The aim of this guide is to get you to one list you can hand to anyone opening or repairing a store.

Build one kit per location type

Start by sorting your locations into types, not into addresses. A counter-service store, a full-service dining room and a small express site inside a food hall need different kits, but two counter stores should look identical behind the counter.

For each type, write a one-page kit sheet that lists:

  • Every device by role: register, kitchen screen, kiosk, customer display, menu board, tableside handheld.
  • The exact tablet model and screen size for each role, so a replacement matches the original.
  • Mounts, stands and enclosures for each role, including which ones go near heat or grease.
  • Peripherals: card readers, the receipt and kitchen printer, the cash drawer and which device each one plugs into.
  • Cables and power: lengths, chargers and which outlets they run to.
  • Network gear: router, any access points and where they sit.

Keep tablet models few. One size for registers and kitchen screens, and one larger size for kiosks, is a reasonable starting point. Fewer models means fewer chargers, fewer mounts and one set of instructions for staff who move between stores.

Write down the boring parts

The kit sheet is most useful for the details people forget: cable lengths, which outlet the printer runs to, which tablet hosts the printer by USB. Those are the things a new manager cannot guess at seven in the morning.

Count devices by station, not by square footage

The number of screens a store needs follows how orders move through it, not how big the room is. Walk the path of one order at each location type and put a device wherever someone takes an order, takes payment or reads a ticket.

  • Registers: one for each point where a person takes orders at the same time. If two people ring at lunch, you need two, plus a plan for the second one during quiet hours.
  • Card readers: one for every register or kiosk that takes cards. A reader shared between two screens means guests and staff waiting on each other.
  • Kitchen screens: one per station that reads tickets separately (grill, fry, cold, expo), placed where the cook can see it without turning around.
  • Kiosks: set by peak queue length and available floor space, not by a rule of thumb. The related guide on kiosk counts walks through this.
  • Customer displays: one facing the guest at each register where you want them to see the order and choose a tip.
  • Menu boards: a TV for each board position, mounted where the queue actually stands.

Do this exercise on paper for one store, then test it during a real rush before you copy it to every location. Stand behind the line and note where people wait for a screen. That is where you are short a device.

Treat the network as part of the hardware

Cloud POS hardware is only as dependable as the connection under it. Every screen needs a working internet connection, so the router and access points belong on the kit sheet next to the tablets, bought to the same standard at every store.

  • Use a business-grade router and put it somewhere staff cannot unplug it to charge a phone.
  • Check signal at each device position, especially kitchen screens behind steel shelving and walk-ins.
  • Keep guest Wi-Fi on a separate network from the devices that run the restaurant.
  • Put the router and modem on a small battery backup so a short power flicker does not drop every screen.
  • Write a short, printed outage procedure: who calls the internet provider, how orders are written by hand, and how they are entered once the connection returns.

The outage card is the part most groups skip. It does not need to be clever. It needs to be taped inside the office door at every store so the answer does not depend on who is on shift.

Spares, labels and a swap plan

With several locations, something will break most weeks. The difference between a nuisance and a lost service is whether a replacement is close by and set up the same way.

  • Keep at least one spare tablet per tablet model, charged and updated, at a central store or office.
  • Label every device with its role and location on the back (for example, Store 3, Register 2). Match the label to the name you give it in your software.
  • Keep a spare charger and USB cable for every role in each store, in a labelled box.
  • Write a swap procedure for each role: which cables come off, how the new tablet is signed in, who can approve it.
  • Keep a simple log of what failed, where and when. Patterns show up quickly: one kitchen that eats chargers, one mount that cracks screens.

When you open a new location, build it from the kit sheet and then stage the whole kit in the office first. Sign every device in, print a test ticket, open the drawer, and only then box it up for the store. Problems found on a desk are cheaper than problems found on opening day.

How Opero fits into a standard kit

Opero runs on Android tablets only, so a kit built around Opero is built around the Android tablets you already own or buy to your standard. Devices are unlimited on every plan; the Opero plan is $149 and Opero Full-Service is $249, each priced per location. Each register or kiosk that takes cards needs one card reader, bought from Opero. Opero takes no marketplace commission; card processing is quoted per business.

The only supported printer is the Star mC-Print3, plugged by USB into the tablet or kiosk running the Opero app, so check that the tablet can act as a USB host before you standardise on it. The cash drawer is cabled to that printer. Put both details on your kit sheet: which tablet hosts the printer, and which printer the drawer hangs off.

For running many stores, the device registry lists every screen by role and location, with a needs-attention list and an online or offline status showing when each device was last seen. From the office you can change a device's card reader, language, kitchen station and screen scale, and turn devices on, off or retire them. Device logins are locked to one screen and can be revoked remotely. The app is installed from a link your account owner approves. A kitchen screen can be switched into register mode with a staff PIN (off by default, set per device), which makes a spare kitchen tablet a possible stand-in register. Tableside handhelds are part of Full-Service and run on Android phones or tablets.

What to do this week

  • List every device at every store by role, model and location. Note anything that does not match the others.
  • Group your stores into location types and draft one kit sheet for each.
  • Walk one order through your busiest store during a rush and mark where people wait for a screen.
  • Check router placement and signal at each device position in one store.
  • Write and post the outage card.
  • Set aside one spare tablet per model and label every device to match its name in your software.

None of this needs new equipment to start. The list of what you have is the first useful document, and the kit sheet grows from it.

See what each location needs, which Android tablets work, and how card readers and printers fit together.

Review hardware requirements

Frequently asked questions

Should every location have identical POS hardware?

Every location of the same type should. A counter store and a full-service dining room can have different kits, but two counter stores should match, so spares, instructions and staff move between them without relearning anything.

How many card readers does a multi-location restaurant need?

Count one for every register or kiosk that takes cards at each store, plus a spare plan. With Opero, that is one card reader for each register or kiosk that takes cards, bought from Opero.

Can I use the tablets I already have?

Opero runs on Android tablets only, so the Android tablets you already own are a starting point. Check each model against your kit sheet, and check USB host support on any tablet that will run the printer.

What happens to the POS if a store's internet goes down?

Opero needs a working internet connection on every screen. Plan for it with business-grade network gear, a battery backup on the router and a printed outage procedure that says how orders are written down and entered later.

Which printer works with Opero?

The Star mC-Print3, plugged by USB into the tablet or kiosk running the Opero app. The cash drawer is cabled to that printer. No other printer is supported.

Run your whole restaurant on one platform

POS, kiosk, QR ordering, kitchen display, and payments on one spine, you bring the tablets, and the card reader is the one piece you must buy from us. Unlimited devices, no per-device fees.

Explore the platform

Keep reading

Opero™ is a product of TackOn LLC. · The Restaurant Operating System