1. Why a shop's IT is different from an office's
In an office a broken computer is annoying, but it usually does not stop everyone's work. In a shop, a hotel or a restaurant the infrastructure works while customers are present. Tills, payment terminals, bookings, guest Wi-Fi, cameras, receipt printers and kitchen order printers must all work at the same moment the customer asks for something. A network fault is noticed immediately, often in a queue.
This changes the priorities. A hotel loses check-ins and bookings, a restaurant loses orders, a shop loses takings and sales data. That is why the useful question is not which system is best, but which activities cannot stop and for how long. The answer guides decisions on security, network and continuity, and shows where to invest first.
2. Map of systems, data and responsibilities
The first task is a simple inventory. List the systems you use, such as tills and payment terminals, management or booking software, Wi-Fi, routers and firewalls, cameras, printers and connected equipment in the kitchen or stockroom. For each one, note who supplies it, who manages it and what personal data it holds, such as customer records, payment data, guest data or images.
The table below is a minimal model. You can copy it into a shared spreadsheet and update it whenever a supplier or device changes. An entry without a clear owner is already a risk point, because in emergencies everyone waits for someone else to act. Complete each row with a practical question: what happens if this system stops for an hour? The answers decide the order of interventions far more than the products chosen.
| System | Data involved | Impact of an outage |
|---|---|---|
| Till and payments | Sales and card data handled by the provider | No takings, queues and delays |
| Bookings or management software | Customer and guest data | Diaries cannot be consulted |
| Guest Wi-Fi | Access data and contact details collected | Visible service disruption for guests |
| Cameras | Images of people | No evidence in case of an incident |
3. Network: separating what is public from what is internal
A shop or hotel network should be divided into zones with different rules: one for management systems and staff, one for payment devices and equipment, and one for guests or customers. If everything shares the same network, any device connected by the public or an infected computer can become an entry point to tills and data.
Separation is achieved with distinct virtual networks and with rules on the router or firewall that allow only the traffic that is needed. A small venue does not need a complex design, but it does need a written configuration and someone who can explain it. Ask your supplier for an up-to-date network diagram showing the zones and the rules between them, and review it at least once a year.
4. Payments, tills and card data
The payment point is where financial risk concentrates. Card data must be handled by the terminal or the service of your payment provider. Your job is to keep devices updated, limit who uses them and never store card data in documents, spreadsheets, emails or photos. The dedicated guide on card payment security standards explains what to ask your bank and provider.
For tills connected to management software, separate administrative access from floor staff access and check that discounts, voids and price changes leave a trace. These are the operations most often abused through a shared account, and a periodic review of the logs can check them in a few minutes. Explore the topic in the dedicated guide on POS and connected tills.
5. Guest Wi-Fi and customer data
Customer Wi-Fi is a valued service and also a processing of personal data. If you ask for a name, email address or phone number to connect, you must inform people about what you do with that data and on what legal basis you process it. If you use it for promotions, consent to marketing must be separate from acceptance of the service and must be optional.
Technically, the guest network must be isolated from everything else, with no visibility of printers, tills or internal devices. Also check whether the system records access and for how long. On any obligation to log access to a public network, seek the advice of an adviser, because these depend on the type of business and the service offered.
6. Continuity: what happens when the internet goes down
A shop or hotel must be able to keep working without a connection for a reasonable time. For tills, offline mode or local recording of sales to be transmitted later are choices to assess with your management software provider and your accountant, because they also affect tax obligations. Not every function needs to survive an outage: what matters is knowing which ones are truly needed to take payment and welcome people.
For bookings, a manual plan is needed: an exported copy of the diary, an emergency register and a note of who consults it. For cameras and the router, consider an emergency power supply and, where possible, a backup connection. The most useful test is to disconnect the internet at a quiet time and observe what stops working and what stays active. Ask your supplier to state in writing, for each system, how long it can remain without a connection.
7. Privacy: the obligations that run through everything
The GDPR applies to customers, guests, employees and suppliers. Every system that processes personal data must have a clear purpose, a legal basis, an understandable privacy notice, access limited by role and an entry in the record of processing activities. Cameras, loyalty programmes and Wi-Fi have specific rules, which the dedicated guides explain one by one. If an incident involves personal data, the controller must assess whether to notify the supervisory authority within 72 hours of becoming aware of the event.
The supplier can help you with the technical facts, but the decision is yours. For this reason the response plan must state who assesses the situation, who alerts the supplier and who keeps the incident record. For notification, it is advisable to prepare a communication template in advance, to be completed with the facts known at the time, because deadlines are tight and information arrives in fragments.
8. In-depth guides to read, in order
Each in-depth guide answers a specific operational question. You do not need to read them all at once: start with the one covering the system that worries you most, apply the first step it indicates, then move to the next. This is the recommended order for anyone running a single venue. If you run several outlets, connecting the sites comes before everything else, because it determines how the tills communicate with the centre. The guides on privacy and video surveillance should be read before installing new cameras or a loyalty programme.
- Security of POS and connected tills
- Card payment security standards
- Customer Wi-Fi in hotels and shops
- Till continuity without a connection
- Skimming on online checkouts
- Connecting multiple outlets: SD-WAN, VPN or dedicated lines
- Video surveillance and privacy rules
- Synchronising stock, shop and e-commerce
- Loyalty programmes and customer data
9. How to start
The first step this week is to complete the inventory described in section two: systems, suppliers, owners, data processed and the impact of an outage. A shared spreadsheet and an hour with whoever runs the venue and whoever keeps the management software are enough. Ask your IT supplier to verify the network diagram and explain which zones exist today. Make this request in writing.
The second step is to choose a single area to put in order first, usually tills or Wi-Fi, and complete the actions in the corresponding guide. The third is to run a test: disconnect the internet at a quiet time and note what stops and what remains active. This test tells you more than any document about what needs fixing first.
Frequently Asked Questions
Does a small restaurant really need an IT plan?
Yes, in a reduced form. A long document is not needed, but you do need to know which systems you use, who manages them, what happens if they stop and who decides. A sheet with this information, updated when a supplier or device changes, covers most cases. The rest can be built over time, starting with payment points and Wi-Fi.
Is Wi-Fi for customers a legal requirement?
It is not an obligation in itself, but many customers expect it. If you offer it, the network must be isolated and the processing of the data of those who connect must be made transparent. Check with an adviser which recording obligations apply to your business, because they depend on the type of service and the context in which you offer it.
If the management software is in the cloud, is till security the supplier's responsibility?
Only in part. The supplier protects the platform, but accounts, permissions, devices on site, the network and staff training remain your responsibility. Ask in writing which controls are theirs and which are yours, and collect them in a single shared document with whoever runs the outlet.
Do I have to report an incident to the authorities?
It depends on the type of incident and the data involved. If personal data is affected, the GDPR requires you to assess whether to notify the supervisory authority within 72 hours of becoming aware of the event. For other obligations, such as those set for some sectors by the NIS2 Directive, check with an adviser whether your business falls within scope. In the meantime, prepare a written timeline of what happened.
How long does it take to get a venue's IT in order?
It depends on size, the state of the systems and the supplier's availability, and there are no standard timeframes. A good first result is the inventory and the separation of networks, which can be completed in a few weeks. The other areas follow, according to the priorities emerging from the inventory and the continuity test.
Can I do it all myself?
For the inventory and the emergency procedure, yes, with a spreadsheet and some time. For network configuration, payment systems and account management, it is better to rely on a competent IT supplier, because an error in those areas has immediate consequences. Ask in writing what you must do and what the supplier does.