FAQs about IT services for hospitality
We use Toast, Square, or Clover. Do you support our POS?
Yes. We do not resell the point-of-sale platform, but we run everything around it: the network the terminals sit on, the segmentation that keeps guest Wi-Fi away from payments, the Microsoft 365 tenant and back-office identity, device management, and the backup of the surrounding records. We have hands-on experience with Toast, Square, Clover, Lightspeed, SpotOn, TouchBistro, and Aloha on the restaurant side; Oracle OPERA, Mews, and Cloudbeds on the lodging side; and Commerce7, WineDirect, and Tock for tasting rooms and wine clubs. Keeping your PCI scope small and your terminals online is the job.
Does guest Wi-Fi really have to be separate from our POS and back office?
Yes, and it is the most common thing we fix first. Guest Wi-Fi, the payment terminals, the back-office PCs, and the cameras and door locks each belong on their own network segment, not on one flat network behind the modem the internet company dropped off. If a guest's infected phone shares a network with your POS, an attacker who lands on the guest side can reach the side that processes cards. We build separate VLANs with a captive portal for guests, so visitors get internet and nothing else. It is inexpensive, it is an explicit PCI expectation, and it is exactly what a cyber-insurance underwriter looks for.
How do you keep us taking cards when the internet or the power goes out?
We plan for it before it happens. That means a cellular or 5G internet failover so card processing keeps clearing when the wired line drops, a UPS on the network and payment gear so nothing crashes hard, a documented offline-payment procedure your managers have actually practiced, and a generator plan for kitchens, walk-ins, and crush equipment where spoilage is on the line. On the Central Coast this matters because the PG&E Public Safety Power Shutoff program can take power for 12 to 72 hours during fire season. A dark dining room or tasting room should not also be a closed one.
We're seasonal with high turnover. Can you handle fast onboarding and offboarding?
That is exactly what identity-first IT is for. Every person gets a named account and a named POS login, never a shared server PIN that the whole shift knows. Roles are scoped so a seasonal host or tasting-room pourer can do their job and nothing more, and company tablets and phones are under mobile device management so a lost device can be wiped. When a seasonal hire leaves, we disable one named account and the access is gone the same day, instead of changing a password twenty people memorized. This protects your audit trail, your PCI posture, and your guest data through every summer and harvest surge.
Is a small restaurant or winery really a target for ransomware?
Yes. Hospitality is one of the most-attacked industries because downtime turns into lost revenue instantly and a lot of card data flows through it. You do not have to be a big resort. The attacks that took down major hotel and casino operators in recent years started with a convincing phone call to a help desk and a reset password, and that same social-engineering playbook scales down to a busy independent restaurant or a Carmel Valley tasting room. The defenses are the same proven controls everywhere: MFA on every account, endpoint detection on every device, monitored email, a verify-by-phone rule for money and passwords, and a tested backup so a bad night is a restore instead of a ransom.