The technology at a new restaurant is invisible when it works and painfully obvious when it doesn’t: a POS that won’t connect on soft-open night, a kitchen printer that drops tickets, guest Wi-Fi that takes the card terminals down with it. Almost every one of those problems traces back to something that should have started weeks earlier, usually the internet order.
This checklist is the sequence we use when we help restaurant groups open new locations. Adjust the timing to your build, but don’t skip the order.
90+ days out: decisions and long-lead orders
- Order primary internet now. This is the item that most often delays openings. A new business circuit commonly takes 30 to 90 days, longer if the provider has to build to the building. Get the order in as soon as you have a lease and an address.
- Plan backup internet. A second connection from a different provider or a cellular (LTE/5G) backup, with automatic failover, so a cut cable doesn’t stop card payments.
- Confirm the POS platform and hardware list (Toast, Oracle MICROS, Square, SpotOn or another), including terminals, kitchen display screens, printers and handhelds, with counts per station.
- Confirm the payment setup with your processor: merchant account for the new location and which PCI questionnaire applies.
- Decide on the extras: cameras, music, phones, digital menu boards, guest Wi-Fi, reservation and online ordering tablets. Each one needs power, a network port or Wi-Fi coverage, and a place on the network plan.
60 days out: design and wiring
- Network design. Separate networks (VLANs) for POS and payments, back office, staff Wi-Fi, guest Wi-Fi, and cameras and music. Payment devices should never share a network with guests. Use the same design as your other locations so support is consistent. (See our guide to PCI compliance for restaurant groups.)
- Low-voltage cabling plan. Walk the space with the floor plan: every POS station, printer, kitchen screen, access point, camera and the network rack. Mark power and data at each spot. It’s far cheaper to pull cable before walls and ceilings close.
- Wi-Fi coverage. Plan access points for the dining room, bar, patio, kitchen and back office. Kitchens are hard on Wi-Fi (metal, heat, walk-ins); wired connections are better for anything critical there.
- Network closet. A ventilated spot for the firewall, switches and modem, with a UPS battery backup so a power blip doesn’t reboot the whole store mid-service.
- Order network hardware to your standard: firewall, switches, access points, UPS.
30 days out: build and configure
- Confirm the internet install date and that someone will be on site for it.
- Pre-configure the firewall, switches and Wi-Fi before they arrive on site, using your standard template. Pre-staging saves hours on install day and keeps every location identical.
- Set up accounts: email and Microsoft 365 for managers, POS logins for staff, the back-office PC and printer. Every person gets their own login.
- Set up remote access and monitoring so your IT team can see and fix the location from day one, with MFA on any remote access.
- Schedule vendors: POS install and menu build, camera install, music, phones. Put them on a single calendar so they aren’t on site on top of each other.
2 weeks out: install and test
- Install network equipment and connect primary and backup internet.
- Install POS hardware and connect every terminal, printer and kitchen screen.
- Test everything at every station:
- Run a test order from each POS through to each kitchen printer and screen.
- Run test card transactions on every terminal, including tap, chip and handheld.
- Unplug the primary internet and confirm the backup takes over and cards still process.
- Walk the space with a phone to confirm Wi-Fi coverage, especially the patio and kitchen.
- Confirm guest Wi-Fi can’t reach the POS network.
- Document the location: network diagram, device list, internet account numbers, vendor contacts. File it where your support team can find it at 10pm on a Saturday.
Soft open and opening night
- Have IT support on site or on call for soft open and the first full service. Small issues show up under a real rush that never appear in testing.
- Watch the first busy service: printer queues, terminal connectivity, Wi-Fi load once guests arrive.
- Make sure every manager knows how to reach support, and that a person answers.
First 30 days after opening
- Review any tickets from opening week and fix the root causes.
- Confirm the location’s PCI questionnaire, and quarterly scans if your SAQ requires them, are set up with your processor.
- Remove any temporary vendor access used during the build.
- Update the location’s documentation with anything that changed.
The most common opening-day IT problems
- No internet yet, because the order went in late. The location opens on a cellular hotspot, and card payments struggle.
- Kitchen printers dropping tickets on Wi-Fi that wasn’t designed for the kitchen.
- POS on the same network as guest Wi-Fi, set up “just for opening” and never fixed.
- No backup internet, so one outage stops every payment in the building.
- Nobody knows who to call, because each vendor only owns its own piece.
How R3 helps with new openings
R3 Services supports more than 110 restaurant and hospitality locations in 17 states and DC, and new openings are a big part of that work, including new locations for bartaco. For restaurant groups we coordinate the IT side of an opening from the internet order to opening night: network design to your standard, pre-staged equipment, cabling plans, POS and vendor coordination, testing, and on-site support nationwide. After opening, a real R3 technician answers the phone 24/7.
Opening a new location soon? Request a free IT assessment and we’ll walk through your timeline, or see how we support restaurant groups.
Frequently Asked Questions
How early should I order internet for a new restaurant?
As soon as you have a lease and address, ideally 90 days or more before opening. New business circuits commonly take 30 to 90 days, and longer if the provider has to build to the building.
Does a restaurant need backup internet?
Yes, if you take cards. A second connection from a different provider, or a cellular backup with automatic failover, keeps payments running when the primary line goes down.
Should kitchen printers and screens be on Wi-Fi?
Wired is better wherever possible. Kitchens are hard on Wi-Fi because of metal, heat and walk-in coolers, and a dropped ticket during a rush is costly.
What should be tested before a restaurant opens?
Test orders from every POS to every printer and kitchen screen, card transactions on every terminal, failover to backup internet, Wi-Fi coverage in every area, and confirm that guest Wi-Fi can’t reach the payment network.

