SkyTab POS Installation Guide: Complete System Setup for Restaurants

TL;DR: Quick Start (10 Essential Steps)

1. Test your network (25+ Mbps download, 5+ Mbps upload, <50ms latency) 2 weeks before installation.
2. Prepare electrical infrastructure with dedicated circuits and UPS for critical devices.
3. Unpack and verify all components against the packing slip immediately upon delivery.
4. Connect hardware via wired Ethernet (Cat6), power, and USB; assign static IPs to printers.
5. Activate the system via Launch Control Wizard in Lighthouse, testing a small transaction.
6. Program your menu (manual or CSV import) with categories, modifiers, and kitchen routing.
7. Create staff accounts with role-based permissions (Server, Manager, BOH).
8. Configure KDS and printers with proper placement and order routing by menu category.
9. Conduct a 2-hour mock service with your full team under simulated peak load.
10. Go live with hypercare support (Shift4 tech on standby for first 48 hours).

---

Pre-Installation: Requirements and Site Readiness

Before a single box arrives, your restaurant needs to be ready. This phase determines whether your go-live happens on schedule or slips by weeks. I’ve seen restaurants skip these steps and pay for it during installation week—rushed network fixes, improper power circuits, and staff scrambling to understand equipment they’ve never touched.

Restaurant POS Network Configuration and Connectivity

Stable network connectivity is the foundation of reliable POS operation. Your terminals can’t process orders, printers won’t print, and payment readers won’t authorize transactions if the network isn’t solid.

Here’s what you need to assess:

Start with your internet connection. Run a speed test to confirm at least 25 Mbps download and 5 Mbps upload with latency under 50ms. If you’re borderline, contact your ISP two weeks before installation; upgrades take time. Test during peak hours—lunch rush, dinner service—to simulate real conditions. Many restaurants have adequate baseline speed but choke under load.

Plan your network architecture. Use wired Ethernet for all fixed devices: main POS terminal, KDS (kitchen display system), and receipt printers. Ethernet is faster, more reliable, and eliminates the Wi-Fi dead zones that plague restaurants. Place a managed network switch (with VLAN capability) near your main POS terminal for clean cable runs.

“POS traffic should be isolated on a dedicated VLAN with access only to payment gateway IPs, with no outbound internet access to guest networks or general office systems.” — Network Security Best Practice (2023).

For mobile devices—SkyTab Glass or Mobile handhelds used by servers—you’ll need secure Wi-Fi. Create a separate SSID for staff devices (e.g., “RestaurantStaff-5G”) and keep guest Wi-Fi on a different network entirely. This segmentation isn’t just convenience; it’s a PCI DSS requirement. Payment systems must be isolated from guest traffic to prevent data leakage.

Network segmentation via VLAN separates your POS environment from office computers and guest Wi-Fi. If your network equipment doesn’t support VLANs, upgrade the switch before installation—it’s one of the most important infrastructure investments you’ll make. Assign your POS VLAN a static IP range (e.g., 192.168.10.0/24), restrict outbound internet access to payment gateway IPs only, and enable WPA3 encryption on all Wi-Fi networks. WPA3 provides superior protection against dictionary attacks and brute-force password guessing compared to WPA2.

Disable WPA2-only fallback mode entirely—it creates security gaps that attackers exploit via Evil Twin techniques.

Position your router and managed switch in a central location—ideally on the second shelf of a wall-mounted cabinet away from heat-generating equipment like ovens or water lines. Cable runs should use Cat6 Ethernet (not Cat5), with runs under 100 feet. Label every cable at both ends with a label maker so troubleshooting later doesn’t become a guessing game.

Test your network before installation day. Many restaurants discover bandwidth issues only when technicians arrive and can’t activate payment readers. Do this yourself: download a large file (500 MB), open multiple YouTube videos simultaneously on different devices (simulating staff and customers), and confirm that everything still loads quickly. If your internet stutters under light load, it will fail spectacularly under peak lunch-hour traffic when 10 servers are ringing orders simultaneously while the host is checking reservations online.

For detailed network infrastructure and compatibility guidance, refer to POS Network Requirements.

---

Site Power, Cabling, and Environment

Your electrical infrastructure matters more than most restaurant owners realize. A power surge that fries your POS terminal or payment reader can cost thousands and sideline your business for days.

Power requirements:

Each POS terminal, thermal printer, and KDS screen should ideally have its own dedicated power circuit (not shared with kitchen equipment like fryers or ovens). Restaurants are prone to electrical noise—commercial ovens, fryers, and HVAC systems create spikes that damage sensitive electronics. Use a surge-protected power strip or, better yet, an uninterruptible power supply (UPS) for critical equipment.

A UPS does two things: (1) it conditions power to smooth out spikes and voltage fluctuations, and (2) it keeps your terminal running for 30–60 minutes if power drops entirely. That’s enough time to gracefully shut down without losing transaction data. Size your UPS appropriately—a small 1,000VA unit works for one terminal and printer; larger setups need 2,000VA or more.

Cabling and cable management:

Run Ethernet cables through conduit or cable channels (not loose along walls where staff trip or doors crimp them). Use Cat6 cabling even if you think Cat5e is “good enough”—the extra cost is minimal ($0.50–$1.00 per foot difference), and Cat6 handles higher speeds if you upgrade your network later. Every cable run should be labeled at both ends with a label maker: “Terminal 1 – Ethernet,” “Kitchen Printer – Power,” etc.

Keep cables away from heat sources (ovens, hot water pipes) and moisture (above or near sinks). In humid environments like bars, moisture can degrade connections and cause intermittent failures—the kind that drive IT support crazy because they’re not consistent.

For detailed power specifications and UPS recommendations, consult POS Workstation technical documentation.

---

Required Components and Unboxing

When your equipment arrives, unpack everything immediately and verify the contents against the packing slip. Missing a cable or power supply discovered after the technician has left means waiting for a replacement—often a week or more.

Standard SkyTab POS bundle includes:

• SkyTab workstation (14″–15″ touchscreen terminal)
• Payment card reader (EMV-enabled, supports chip, swipe, and NFC)
• Receipt thermal printer (with paper roll)
• Cajón de efectivo (stainless steel, fits under counter)
• Network cables (Cat6 recommended; upgrade from Cat5)
• Power supplies and cables
• Employee ID cards (10 count, for initial staff setup)
• Quick reference guide and training materials

Additional equipment you’ll likely need (not always in the standard bundle):

• Sistema de visualización de cocina (KDS) screen or monitor
• Secondary receipt printers (if you have a separate bar or takeout counter)
• Lector de códigos de barras (if you track inventory or use pre-printed menu codes)
• SkyTab Glass or Mobile tablets (for server handhelds)
• Managed network switch (if you don’t already have one with VLAN capability)
• UPS (uninterruptible power supply) for backup power (2,000VA minimum for multi-device setups)

As you unbox, inspect for physical damage: cracks in the terminal screen, bent connectors, or loose internal components. If anything looks damaged, photograph it immediately with the packing materials visible and contact the vendor before the 30-day return window closes. Record the serial number of every device and store it in a spreadsheet—you’ll need these for warranty claims and support tickets.

For detailed component specifications and what’s included, reference Estación de trabajo SkyTab y Sistema de visualización de cocina SkyTab.

---

Security and Firewall Baseline

Descargo de responsabilidad: The following information is general in nature and does not replace consultation with a qualified cybersecurity professional, your payment processor (Shift4), or legal counsel regarding PCI DSS compliance obligations specific to your business.

Before your payment system goes live, your network must meet Payment Card Industry (PCI DSS) security standards. This isn’t optional—failure to comply can result in fines from your payment processor, assessments, and puts customer data at risk. PCI DSS v4.0 (effective March 31, 2025) mandates security measures for all cardholder data environments.

Minimum firewall configuration:

Enable your router’s built-in firewall. Create inbound rules that block all traffic except what’s necessary for POS operation. Your payment gateway provider (Shift4) will give you a list of IP addresses and ports that need access; whitelist those specific IPs and ports and block everything else. This is called a “default deny” posture in security terminology—allow only what you explicitly need, block everything by default.

Change the default admin password on your router and network switch—use something strong (16+ characters mixing uppercase, lowercase, numbers, symbols). Use a password manager like Bitwarden or 1Password to store this securely; don’t write it down on a Post-it. Disable any remote access features (like SSH, Telnet, or remote management) unless you have a specific reason to enable them.

For Wi-Fi security, enforce WPA3 encryption with Protected Management Frames (PMF) if your equipment supports it. If not, WPA2-AES is acceptable as a temporary measure, but plan to upgrade within 12 months. Either way, use a strong pre-shared key (PSK) with 20+ characters and update it every 90 days. Disable WPS (Wi-Fi Protected Setup) entirely—it’s a well-known attack vector that bypasses your password.

Update firmware on your router and network switch before the technician arrives. Many security vulnerabilities are patched in updates, and Shift4’s support team will ask if your firmware is current if issues arise.

Finally, coordinate with your Shift4 support contact about which payment gateway IPs and ports need to be whitelisted. Restrictive firewall rules that accidentally block payment processing can cause transactions to fail mysteriously during testing.

Reference Procesamiento de pagos con tarjeta de crédito for payment system security requirements.

---

SkyTab POS Hardware Setup and Device Configuration

Once your site is ready, it’s time to physically install the equipment. This phase looks simple but has several small details that, if missed, cause frustrating problems later.

Setting Up the SkyTab Workstation

Your main POS terminal is the heart of the system. Placement matters for ergonomics, visibility, and longevity.

Position the terminal on a stable, level surface at counter height where servers and cashiers work comfortably. Avoid placing it directly above a sink (moisture and splashes damage electronics) or in direct sunlight (makes the screen hard to read and causes heat stress). The ideal location is 2–3 feet from kitchen staff sightlines but far enough from the pass to avoid accidental bumping.

Connect Ethernet from the terminal to your managed network switch using Cat6 cable. The cable should route along walls or through conduit, not loose where staff trip over it or doors crimp it. Secure it with cable clips or Velcro straps every 3–4 feet. Gently push the cable into the Ethernet port on the terminal—you should feel and hear a click when it’s fully seated.

Attach the payment reader via USB cable to the back of the terminal (exact port depends on your reader model; check the label on the back). Test that the reader powers on when you restart the terminal—you should see lights on the reader’s front face indicating it’s active.

Connect the backup power (UPS) by plugging the UPS into a wall outlet, then plugging the terminal’s power cable into the UPS rather than directly into the wall. This adds a critical layer of protection against power surges. Don’t plug the UPS into a power strip; plug it directly into the outlet so it’s the first line of defense.

Power on the terminal by holding the power button for 3 seconds. The screen should show a startup sequence, then load the SkyTab login screen within 30–60 seconds. If nothing happens, check that the power cable is fully seated on both ends and that the outlet has power (test with another device like a lamp or phone charger).

Check network connectivity by looking for a green Ethernet link light on the back of the terminal (usually near the power port). If the light is off or amber/red, the cable isn’t connected properly or the switch port isn’t active. Reseat the cable firmly, or try a different switch port.

For detailed workstation setup and specifications, consult Estación de trabajo SkyTab.

---

Connecting Peripheral Devices (Printers, Cash Drawers, Scanners)

Peripherals are where installation often stumbles. Each device needs power, a network or cable connection, and configuration within the SkyTab software.

Receipt printers can connect via Ethernet or USB. Network printers (Ethernet-connected) are more reliable because they stay stable even if cables are bumped or moved. USB printers are simpler to set up but can disconnect if the cable is jostled.

To set up a network printer:

1. Connect the printer to your network switch via Cat6 cable (same as the terminal)
2. Power on the printer and note its IP address (usually shown on a small LCD screen, or print a network configuration page by holding the feed button while powering on for 3–5 seconds)
3. Write down the IP address—something like 192.168.10.50
4. In the SkyTab terminal, go to Manager > Settings > Hardware > Printers, click Add New Printer, and enter the IP address
5. Select the printer model from the dropdown (e.g., “Epson TM-M30” or “Star Micronics”)
6. Choose the function: Receipt Printer, Kitchen Printer, or Bar Printer
7. Click Test Print—a test ticket should emerge from the printer within 5 seconds

If your printer doesn’t have a display to show the IP address, assign it a static IP through your router’s DHCP reservation menu. This ensures the printer always has the same IP address even if the router reboots.

Cash drawers connect via an RJ12 connector (looks like a phone jack) to the rear of the receipt printer. Plug the cable in firmly—it should click and sit flush. In the SkyTab system settings, you’ll map this drawer to the printer, so when the software sends an “open drawer” command during payment processing, it triggers the solenoid and the drawer pops open.

Barcode scanners plug into a USB port on the terminal. Most modern scanners work in “keyboard wedge” mode, meaning they transmit numbers directly as if someone typed them. Test this by opening a text editor on the terminal, powering on the scanner, and scanning a barcode—the numbers should appear as text.

---

Configuring SkyTab Glass & Mobile Handhelds

Server tablets run on Wi-Fi, so they’re more sensitive to network configuration than wired terminals. They also represent a significant mobility and convenience advantage if configured correctly.

For each SkyTab Glass or Mobile device:

1. Power on the tablet and look for the Wi-Fi SSID you created (e.g., “RestaurantStaff-5G”)
2. Tap the SSID and enter the Wi-Fi password (the strong, pre-shared key you set earlier)
3. Open the SkyTab POS app (pre-installed) and log in with manager credentials
4. Go to Settings > Device Name and rename it to something descriptive like “Glass_Server_1” or “Mobile_Bar_Station”
5. Assign the device to a service zone or section (optional but recommended for larger restaurants)

Why rename devices? When a server’s handheld has a generic name like “iPad 5” or “Android Device,” it’s impossible to troubleshoot issues or track which device is causing slow orders. A clear naming convention—including device type and location—saves hours of debugging later.

Test connectivity by placing the handheld on the counter, walking 30 feet away (across the dining room), and trying to load the menu. If it lags or times out, move your Wi-Fi access point closer or add a mesh extender to cover dead zones.

Reference Vidrio SkyTab for mobile terminal capabilities and configuration.

---

Kitchen Display Systems (KDS) and Receipt Printers

Your KDS is where kitchen staff see orders. Placement and configuration directly affect order accuracy, speed, and kitchen workflow.

Mount the KDS screen above the kitchen prep line or window where expo staff have a clear sightline. Height should be at eye level when standing (roughly 5–6 feet off the ground). Tilt the screen slightly downward to reduce glare from overhead lights. If your kitchen is open to the dining room, position the KDS where customers can’t see orders and prices—this is both a security and operational concern.

Connect the KDS to Ethernet (not Wi-Fi—KDS must have stable, low-latency connectivity). Assign it a static IP in the same way as the receipt printer. Test connectivity by opening a web browser on the terminal and pinging the KDS IP: if the response is <50ms, you’re good; if it’s >100ms, you have a network problem to fix.

Configure order routing within the SkyTab system. This is where your menu categories map to specific screens or printers:

• Entrees → Main KDS (displayed immediately)
• Appetizers → Expo Printer (if you have a separate expo station) or Main KDS
• Beverages → Bar Printer (if separate bar) or Main KDS
• Desserts → Kitchen Printer or Main KDS
• Sides → Main KDS

Go to Manager > Settings > Menu > Departments and assign each menu category (Entrees, Appetizers, etc.) to a print station. Then, for each menu item, assign it to its parent department.

Set auto-bump rules so orders automatically move to “cooking” status after a set time (e.g., 2 minutes), or manually when kitchen staff taps “bump.” This keeps orders flowing and prevents bottlenecks.

For KDS placement and configuration best practices, refer to Sistema de visualización de cocina SkyTab.

---

Software Configuration & Activation

With hardware in place and connected, it’s time to configure the system so it knows how to process orders, accept payments, and route tickets.

Accessing the Lighthouse Management Portal

Lighthouse is SkyTab’s back-office system where you manage menus, staff, taxes, and reporting. You access it via web browser from any computer—even your office laptop or home computer.

Log in to Lighthouse:

1. Go to app.skytab.com or the URL provided by Shift4
2. Enter your merchant email and password
3. Once logged in, you’ll see the dashboard with tabs for Locations, Users, Menus, Informes, and Settings

Verify merchant profile:

• Check that your restaurant name, location address, and phone number are correct
• Confirm the timezone is set to your location (this matters for batch settlement times—if your timezone is wrong, deposits hit your bank at odd hours)
• Verify that tax rates for your jurisdiction are accurate (consult your accountant if unsure)

Add users (staff accounts):

Click Users and add each manager, supervisor, or assistant manager. Assign roles carefully:

• Manager: full access to menu, staff, reports, payments, refunds
• Supervisor: access to refunds, discounts, daily reports, but not menu changes or staff management
• Staff: login required but no administrative functions

Each user should have a unique login and a strong password. Don’t use “password123” or “admin”—these get compromised instantly.

For Lighthouse user management and configuration details, consult SkyTab Lighthouse.

---

Initial Activation and Merchant Account Sync

Activation connects your POS hardware to Shift4’s payment infrastructure and your Lighthouse account. This is where payment processing comes online.

On the main SkyTab terminal:

1. Go to Manager > Settings > Business > Activation
2. Follow the Launch Control Wizard step-by-step
3. The wizard will:
   • Confirm your merchant account details (business name, processing entity, address)
   • Set up payment methods (credit cards, mobile wallets, gift cards)
   • Configure settlement: which bank account receives funds and on what schedule
   • Test a small transaction (often $0.01 or $1.00) to confirm payment processing works

What happens during test transaction:

The terminal will prompt you to tap, insert, or swipe a test card (usually provided by your payment processor or a standard test card with number 4111111111111111). If successful, you’ll see “Approved” and the transaction will appear in your Lighthouse reports within minutes.

Common activation issues:

• “Connection timeout”: Your firewall is blocking the payment gateway. Whitelist the IP addresses and ports that Shift4 provides.
• “Invalid merchant”: The account details in Lighthouse don’t match your merchant agreement with Shift4. Contact Shift4 support to verify and correct.
• “Offline mode”: The terminal can’t reach Shift4’s servers. Check your internet connection and router settings; restart both if necessary.

Once activation is successful, your terminal is live for payment processing.

For payment processing setup and integration, reference Procesamiento de pagos con tarjeta de crédito.

---

Menu Programming and Data Migration

Your menu defines what servers can ring up and how it’s organized. Poor menu setup leads to ordering errors, printer mishaps, and frustrated kitchen staff.

Option 1: Manual menu creation (simple, takes 2–4 hours for 50 items)

In Lighthouse, go to Menu Builder and click Add Item. For each menu item, enter:

• Item Name (exactly as it should appear on printed tickets for kitchen staff—be precise)
• Category (Entrees, Appetizers, Beverages, etc.)
• Price (the base price before modifiers)
• Modifiers (size, temperature, special requests)
• Tax (whether this item is taxable, what rate applies)
• Revenue Class (for reporting, e.g., “Food,” “Beverage,” “Alcohol”)
• Print Station (which printer or KDS this item routes to)

Ejemplo:

• Item Name: “Grilled Salmon”
• Category: “Entrees”
• Price: $28.00
• Modifiers: [Doneness: Rare/Medium-Rare/Medium/Well-Done], [Sauce: Béarnaise/Lemon/None], [Side: Asparagus/Green Beans/Fries]
• Tax: Yes (your state’s standard rate, e.g., 8.875%)
• Print Station: Kitchen_Main

Option 2: Import from CSV (faster, requires careful data preparation)

If you’re migrating from another POS, export your menu as a CSV file. You’ll need columns for Item Name, Category, Price, Modifiers, Tax, Print Station. The format matters—if your CSV has headers in the wrong order or missing columns, the import will fail.

Shift4 provides a Menu Submission Form on their website. You upload your CSV, and Shift4 agents process it within 24–48 hours (for up to 5 items per submission; larger menus may take longer).

Modifiers are crucial. These are options that servers select when ringing an item:

• Size modifiers (Small/Medium/Large) that add or subtract price
• Preparation modifiers (Rare/Medium/Well) that don’t change price but inform the kitchen
• Add-on modifiers (Extra bacon, substitute vegetables) that add cost
• Special request free modifiers (No croutons, dressing on side) that don’t add cost but print on the ticket

Properly configured modifiers prevent kitchen confusion and ensure servers don’t forget to ask (e.g., “What temperature would you like that salmon?”).

---

Staff Roles and Permissions

Different staff members need different access levels. A server shouldn’t be able to void transactions or change menu prices, but a manager should.

Define role-based permissions carefully:

1. Server/Bartender
   • Can: create orders, apply item modifiers, process payments, print tickets, view their own sales
   • Cannot: void transactions, apply manual discounts, view other staff’s sales, edit menu
2. Shift Supervisor
   • Can: everything a server can do, plus approve voids/discounts up to $X amount, view daily sales by category
   • Cannot: edit menu, change staff accounts, modify taxes
3. Manager
   • Can: everything, including menu edits, staff management, access to Lighthouse reports, refunds of any amount
   • Cannot: nothing (full access)
4. Back of House (BOH)
   • Can: clock in/out, view assigned orders on KDS, mark orders complete, add notes about special requests
   • Cannot: process payments, view pricing, access reports, edit menu

Set PIN-based login security:

Each staff member gets a unique PIN (4–6 digits). Don’t use sequential PINs like 1111, 1234, 0000, or 5555. A PIN like 7394 or 2561 is much harder to guess. Enforce PIN changes every 90 days—policy driven by your business, not system default.

For staff roles and permission configuration, reference SkyTab Lighthouse.

---

Payment Processing Integration and Security Protocols

Descargo de responsabilidad: The following information is general in nature and does not replace consultation with legal counsel, a compliance professional, or your payment processor regarding PCI DSS obligations specific to your business.

Your payment system must comply with PCI DSS (Payment Card Industry Data Security Standard). This isn’t just a rulebook—it’s a legal requirement. Non-compliance can result in fines from your processor (starting at $5,000/month), security assessments, and puts customer data at risk.

PCI DSS key requirements for your setup:

1. EMV/Chip card support: Your payment reader must support EMV (chip) cards. Swipe-only is outdated and has higher fraud rates.
2. Encryption in transit: All payment data between your terminal and Shift4’s servers must be encrypted via TLS 1.2 or higher. This happens automatically—you don’t configure it—but your firewall must allow it (usually port 443 HTTPS).
3. No storage of sensitive data: Your POS system should never store credit card numbers, CVV codes, or expiration dates. Shift4 handles this securely; your terminal only stores transaction references and receipt data.
4. Network segmentation: Your payment network (POS terminals, payment reader, merchant server) must be isolated from guest Wi-Fi and office computers. You’ve already done this with VLAN configuration earlier.
5. Regular security updates: Install firmware and software updates as soon as Shift4 releases them. These often contain security patches.
6. Firewalls and access controls: All payment terminals must sit behind a firewall with restrictive inbound/outbound rules. Block all traffic except to known payment gateway IPs.

Tip processing (configure strategically): Configure how tips are handled—this affects both speed and compliance:

• Add tip after payment (customer signs receipt, adds tip amount, staff enters it): common in sit-down restaurants but slower
• Select tip on terminal (customer taps “Yes” or selects 15%/18%/20% on screen): faster for counter service, eliminates paper
• No tip option (tips paid separately or in cash): less common but possible for certain concepts

Settlement schedule: Decide when funds are deposited into your bank account:

• Daily settlement (funds transferred each night): best for cash-flow management
• Rolling settlement (funds available in 24–48 hours): standard for most processors
• Weekly settlement (funds transferred once weekly): less common, not recommended

For detailed payment processing and compliance information, consult Procesamiento de pagos con tarjeta de crédito.

---

SkyTab POS Onboarding Process and Implementation Steps

Installation isn’t just about hardware and software—it’s about training people and building confidence. A poorly trained staff will misuse the system, slow down service, and generate support tickets that could have been prevented.

Follow these 8 steps for a smooth go-live:

Step 1: Confirm Site Readiness and Device Registration (Week 1)

• Network tested and optimized (speed test results documented)
• All hardware physically connected and powered on
• Devices registered in Lighthouse with serial numbers
• Firewall and Wi-Fi configured per security baseline
• Merchant confirmation that site meets all prerequisites

Step 2: Complete Activation Process (Week 1)

• Merchant account synced to POS terminal via Launch Control Wizard
• Test transactions processed successfully
• Settlement account and schedule configured in Lighthouse
• All handhelds and KDS devices activated and communicating with main terminal

Step 3: Import Menu and Configure Routing (Week 1–2)

• All menu items created or imported (50+ items minimum; verify count)
• Modifiers and pricing verified against physical menu
• Kitchen routing configured (which items print to which station)
• Printer and KDS assignments tested with sample tickets
• Menu structure approved by kitchen staff and management

Step 4: Configure Staff Roles and Permissions (Week 2)

• User accounts created for each staff member (min 5 test accounts)
• PINs set and communicated securely
• Role-based permissions verified (servers can’t void, managers can)
• Password policy enforced (strong, unique, 90-day rotation)
• Lighthouse access tested for managers

Step 5: Connect Printers, KDS, and Test Ordering (Week 2)

• All printers mounted and tested with actual tickets
• KDS screens displaying orders correctly with no lag
• Auto-bump rules tested with mock orders (20+ orders in succession)
• Cash drawer tested (opens on receipt printer command)
• Payment reader tested with test card (chip, swipe, tap if supported)

Step 6: Train Front of House and Back of House (Week 2–3)

• FOH training: login, order entry, modifiers, payment processing, tips, voids (2 hours per group)
• BOH training: viewing orders on KDS, marking items ready, handling special requests (1 hour)
• Manager training: Lighthouse access, reports, menu changes, staff scheduling (2 hours)
• Role-based drills with real scenarios (split check, modification, refund) (1 hour)
• Training documented and attendance tracked

Step 7: Conduct Mock Service with Peak-Hour Scenarios (Week 3)

• Simulate a Saturday dinner rush with all staff (2+ hours)
• Process 50+ orders over the mock service period
• Vary orders: simple items, heavily modified items, split checks, refunds
• Review logs and adjust settings based on observed issues
• Collect feedback from servers and kitchen staff
• Document any errors and resolutions

Step 8: Finalize Settings and Schedule Go-Live Support (Week 3–4)

• Lock all configuration (no more menu or permission changes)
• Schedule post-launch hypercare (Shift4 tech on standby for first 48 hours)
• Brief all staff on go-live day procedures
• Assign floor supervisor to monitor POS and resolve issues immediately
• Set escalation contact (usually your Shift4 rep or dedicated support number)
• Print and laminate quick-reference cards for each station

For detailed onboarding timelines and checklists, consult POS Installation Timeline.

---

Essential Restaurant POS Installation Checklist

Use this checklist as your project tracker. Print it, check off items as you complete them, and share it with your team. A checked box means you’re on schedule.

✅ Network & Infrastructure (Pre-Installation Week)

• Internet connection tested: 25+ Mbps download, 5+ Mbps upload, <50ms latency
• Test repeated during peak hours (lunch/dinner rush) to confirm stability
• Network switch installed with VLAN capability (minimum 1 Gbps)
• Wired Ethernet cable runs completed (Cat6, labeled at both ends with facility labels)
• Wi-Fi SSIDs created (Staff 5GHz and 2.4GHz, Guest separate, all WPA3-encrypted)
• Firewall configured: default deny, Shift4 payment gateway IPs whitelisted
• Default router/switch passwords changed to strong credentials (16+ characters)
• Firmware updated on all network equipment to latest version
• UPS unit(s) configured for main POS terminal and critical devices
• UPS battery backup tested (should provide 30–60 minutes runtime)
• Electrical infrastructure reviewed with licensed electrician (dedicated circuits recommended)

✅ Hardware Installation (Installation Week 1)

• All equipment unpacked, serial numbers recorded in spreadsheet
• Physical damage inspection completed; nothing cracked, bent, or loose
• Main POS terminal connected to Ethernet and powered on
• Terminal displays SkyTab login screen (boots successfully)
• Payment reader attached to terminal, test powered on
• Receipt printer(s) connected (Ethernet IPs assigned, static IPs reserved in router)
• KDS screen mounted above kitchen prep line, connected to Ethernet
• Cash drawer connected to receipt printer via RJ12 (cable seated firmly)
• All Ethernet link lights green (indicators on ports showing connection)
• Terminal can ping printer and KDS (latency <50ms)
• UPS unit verified as supplying power to critical devices

✅ Handhelds & Mobile Devices (Installation Week 1–2)

• SkyTab Glass/Mobile devices powered on and Wi-Fi connected
• Devices renamed to descriptive names (e.g., “Glass_Server_1”, “Mobile_Bar”)
• Devices logged into SkyTab app with manager credentials
• Devices assigned to service zones (patio, dining room, bar, etc.)
• Wi-Fi signal strength tested at all service points (minimum 2 bars everywhere)
• No dead zones identified (if found, add mesh extender)
• Handhelds can load menu in <2 seconds from any location

✅ Software & Activation (Installation Week 2)

• Lighthouse account access verified (login successful)
• Merchant account details confirmed (name, address, timezone correct)
• User accounts created for all staff (managers, supervisors, servers)
• Staff PINs set and communicated securely (no plain-text email)
• POS terminal activated via Launch Control Wizard
• Test transaction processed and approved ($0.01 or $1.00)
• Settlement account configured, schedule set (daily, rolling, or weekly)
• Payment methods enabled (credit, debit, mobile wallet, gift card if applicable)
• Shift4 support contact information recorded and accessible

✅ Menu Programming (Installation Week 2)

• Menu items imported or manually entered (all active items present)
• Item count verified (at least 50 items for full restaurant)
• Modifiers configured (size, temperature, special requests) for all applicable items
• Pricing verified against printed menu (spot-check 10 random items)
• Tax rates applied correctly (food vs. beverage vs. alcohol per jurisdiction)
• Kitchen routing configured (item → printer/KDS station mapping)
• Print station assignments verified with sample tickets
• Kitchen staff reviewed menu and approved item names/descriptions
• Modifier combinations tested (no invalid selections possible)

✅ Printer & KDS Configuration (Installation Week 2)

• Receipt printers assigned to stations (counter, kitchen expo, bar)
• Test tickets printed from each printer (clean, legible, proper formatting)
• KDS screen mounted and visible from all kitchen stations
• Order routing tested (entrees → main KDS, appetizers → expo, etc.)
• Auto-bump rules set and tested (orders move off “just received” list on schedule)
• Cash drawer opens on receipt printer command (tested multiple times)
• Printer paper levels verified and restocked
• Printer test buttons functional (if available on hardware)

✅ Security & Compliance (Installation Week 2)

• PCI DSS network segmentation verified (payment network isolated from guest/office)
• EMV/chip card support enabled on terminal
• TLS 1.2+ encryption confirmed for payment transactions
• Staff PIN policies set (unique, 4–6 digits, 90-day rotation)
• Wi-Fi security: WPA3 or WPA2 with strong pre-shared key
• Firewall rules verified: payment gateway IPs whitelisted, unused ports blocked
• Firmware updated on router, switch, and all network equipment
• Default passwords changed on all network devices
• Remote management features disabled on router/switch
• Security audit completed (no default credentials remaining)

✅ Staff Training (Installation Week 2–3)

• FOH staff trained: login, order entry, modifiers, payment/tips (2 hours per group)
• BOH staff trained: KDS viewing, marking items ready, ticket reading (1 hour)
• Managers trained: Lighthouse access, reports, menu changes, refunds (2 hours)
• Role-based permissions tested with realistic scenarios (split check, void, refund)
• Quick reference cards printed and laminated (at each station)
• Training videos or links shared with staff (for review after launch)
• Training attendance documented and signed off

✅ Testing & Go-Live (Installation Week 3–4)

• Mock service conducted: 50+ orders during simulated peak hours (2+ hours)
• All order types tested: simple, modified, split checks, refunds
• Payment processing tested: card, mobile wallet, gift card (if offered)
• Offline mode tested (if applicable; terminal should queue orders)
• Logs reviewed for errors or warnings (Activity Log, System Log)
• Feedback collected from servers and kitchen staff
• Final configuration locked (no more changes to menus, permissions, settings)
• Go-live day support scheduled (Shift4 tech on standby)
• Floor supervisor briefed on escalation procedures
• First 48 hours designated as hypercare monitoring period
• Post-launch check-in scheduled for day 2 and day 7

---

System Testing and Go-Live

The final stretch. This is where you confirm the system works under real conditions before your first paying customer uses it.

POS System Testing and Go Live Process

Testing isn’t just running a few orders through. It’s simulating actual service: busy nights, complex orders, payment mix, and error recovery.

What to test:

1. Order entry accuracy
   • Ring a burger with 5 modifiers (no mayo, extra lettuce, grilled onions, sharp cheddar, toasted bun)
   • Verify the ticket prints in the kitchen with all modifiers clearly shown
   • Confirm the menu doesn’t allow invalid modifier combinations
   • Test quantity changes (change 2 burgers to 1, then back to 3)
2. Procesamiento de pagos
   • Process a card payment: tap, insert, and swipe (test all methods if supported)
   • Add a tip both on the terminal and post-payment (verify both work)
   • Decline a payment (intentionally use a test card marked “declined”) and verify the system handles it gracefully without crashing
   • Test refund workflow (refund a transaction and verify it appears in Lighthouse)
3. Split checks and complex scenarios
   • Ring an order for 6 people, split the check four ways, process payments separately
   • Modify an order after it’s been sent to the kitchen (change temperature, add/remove item)
   • Process a refund on an item or entire check
   • Test void functionality (manager-only action)
4. KDS and kitchen workflow
   • Send 20 orders to the KDS in rapid succession (simulating lunch rush)
   • Verify kitchen staff can see all orders without lag
   • Test auto-bump: orders should automatically move to “cooking” status
   • Test manual bump: kitchen staff taps an item to mark it ready for expo
   • Verify order modifications appear correctly on screen and printed tickets
5. Printer reliability
   • Print 30 consecutive tickets and verify none jam or print incompletely
   • Test with low paper (add paper during a print) and verify no data loss
   • Disconnect the printer mid-print (simulate cable failure) and verify terminal handles it without crashing
6. Handheld devices in high-traffic scenario
   • Deploy 3–4 SkyTab Glass devices simultaneously across the dining room
   • Ring orders from multiple locations at once
   • Verify all orders route to the kitchen correctly (no collisions or dropped orders)
   • Test Wi-Fi handoff as device moves from one access point to another (if mesh network)
7. System stability under load
   • Run the above tests for 2+ hours continuously
   • Monitor CPU usage and memory on the main terminal (should stay below 80%)
   • Check logs for warnings or errors (Manager > Reports > Activity Log)

Expected results:

• All test transactions should process in <3 seconds
• Payment success rate: 100% (for approved test cards)
• Printer queue: no more than 2-second delay between submission and printing
• Handheld connectivity: no disconnections or timeouts during 2-hour test
• KDS: orders visible within 1 second of server submission
• No terminal crashes, freezes, or required restarts
• Staff can complete a full table’s order, payment, and close-out in under 3 minutes (for experienced operators)

If you see issues—slow transactions, printer errors, KDS lag—pause testing, identify the root cause (usually network or configuration), fix it, and restart testing. Don’t proceed to live service until all tests pass cleanly.

---

Mock Service and Go-Live Day Checklist

A mock service is a full dress rehearsal. Real orders, real timing, real pressure. It’s the last chance to catch problems before money is on the line.

Schedule your mock service:

Pick a time when your restaurant would normally be closed (a Monday night, Tuesday afternoon). Invite your entire team: servers, bartenders, hosts, kitchen staff, and a manager to oversee.

Run the mock service for 2+ hours:

• Start slowly: 5–10 orders in the first 15 minutes, allowing kitchen and POS operators to get comfortable
• Gradually increase pace: every 15 minutes, add more orders until you’re simulating your actual peak traffic (e.g., if you do 100 covers on a Friday night, aim for 15+ orders per 15-minute period during mock service)
• Include intentional errors: one server intentionally voids an order, another requests a refund, a third processes a split check. This trains staff on handling mistakes
• Encourage feedback: station a manager or IT person at the host stand, taking notes on what’s confusing or slow
• Run payment processing for all orders (use test cards provided by Shift4)

After the mock service:

1. Review the logs: Go to Manager > Reports > Activity Log and scan for errors or warnings
2. Debrief with staff: What was confusing? What was fast? Did the KDS feel responsive? What would you change?
3. Adjust and re-test: If kitchen staff struggled with order routing, adjust the KDS auto-bump rules or reconfigure which items print where. If servers fumbled payment entry, run a 30-minute refresher training
4. Lock the configuration: Once everything works well, prevent further changes to menus, printer routing, and staff roles

Go-live day:

• Arrive early (2+ hours before service)
• Run a quick end-to-end test: one order from ring-up through payment and kitchen
• Confirm all hardware is powered on and connected
• Verify Shift4 support is on standby (confirm their phone number and chat support URL)
• Assign a floor supervisor to monitor the POS throughout service—their only job is to watch for errors and escalate issues immediately
• For the first 48 hours, don’t make configuration changes. Log every issue, fix it during non-service hours

---

Troubleshooting and Optimization

Even with perfect setup, things go wrong. Here’s how to handle the most common issues.

Common Installation Issues and Resolutions

Printer not found / “No printer detected” error

Root cause: Printer IP not assigned, VLAN isolation blocking communication, or USB cable not seated.

Fix:

1. Power cycle the printer: turn it off, wait 10 seconds, turn on
2. If it’s a network printer, hold the feed button while powering on to print a network config page. Find the IP address printed on the page
3. In SkyTab Manager > Settings > Hardware > Printers, click Add New Printer and enter the IP address manually
4. If the printer is on a different VLAN than the main terminal, adjust the VLAN rules to allow POS traffic to reach it (or move the printer to the same VLAN as the terminal)
5. If it’s a USB printer, disconnect and reconnect the cable, then restart the terminal

Test: Go to Settings > Hardware > Printers, select your printer, and click Test Print. A test ticket should emerge within 5 seconds.

---

Handheld loses Wi-Fi connection / “Not Connected” warning

Root cause: Weak Wi-Fi signal, interference (microwave, cordless phones), or roaming issues between access points.

Fix:

1. Check the Wi-Fi signal strength on the handheld: go to Settings > Wi-Fi and look at the signal bars. Less than 2 bars means the signal is weak
2. Move the access point closer to where handhelds are used, or add a mesh extender
3. Reduce the distance between the terminal and access point (the main terminal should be within 30 feet of the router for stable signal)
4. If multiple access points exist, ensure they’re all on the same SSID with the same password and use non-overlapping channels (2.4GHz: 1, 6, 11; 5GHz: any channel ≥20MHz separation)
5. Check for interference: move the access point away from microwaves, cordless phones, or ovens

Test: Open a menu on the handheld from different areas of the restaurant. Response time should be <2 seconds everywhere.

---

EMV / Payment Reader failures / “Transaction declined” during testing

Root cause: Incorrect payment gateway configuration, firewall blocking payment processing, or expired test card.

Fix:

1. Confirm the payment reader is properly connected (USB or serial, depending on model) and powered on
2. In Manager > Settings > Business > Activation, verify your merchant account number and payment gateway URL are correct
3. Check that your firewall has whitelisted the payment gateway IP addresses and port 443 (HTTPS)
4. Test with a different card: some test cards work only for specific transaction types (e.g., credit only, not debit)
5. If using a real card (not test mode), confirm the card isn’t expired and the cardholder’s bank hasn’t blocked the transaction
6. If using EMV (chip), ensure the terminal is configured for EMV mode. Some readers have a physical switch; others switch in software

Test: Process a small test transaction ($0.01 or $1.00) with an approved test card. You should see “Approved” within 5 seconds.

---

KDS orders showing lag / “Orders appear 5+ seconds after submission”

Root cause: Network latency, Wi-Fi instead of Ethernet for KDS, or too many orders queued.

Fix:

1. Check the network connection: KDS should be on wired Ethernet, not Wi-Fi. Move it if necessary or run a cable
2. Check network latency: open a terminal on the main POS and ping the KDS IP. Response time should be <10ms. If it’s 100+ms, you have a network bottleneck
3. Reduce auto-bump timer: if the KDS is buffering orders, decrease auto-bump from 2 minutes to 1.5 minutes so kitchen staff actively clear orders faster
4. Disable power-saving mode on the KDS: if it’s a monitor, turn off sleep mode in display settings

Test: Send 10 orders rapidly from the main terminal and time how long it takes for all 10 to appear on the KDS. Target: <2 seconds for the last order.

---

Performance Optimization and Hidden Features

Once the system is stable, you can tweak it for speed and staff convenience.

Quick-action modifiers:

Instead of servers selecting “medium temperature, no mayo, extra pickles” from nested menus, create shortcut buttons for common requests:

• Button “No mayo” (applies automatically without selecting from a list)
• Button “Medium-rare” (preset temperature)
• Button “Dairy-free” (applies to any entree with a dairy modifier)

In Lighthouse, under Menu > Modifiers, mark frequently-used modifiers as “Quick Select.” They’ll appear as large buttons at the top of the modifier list instead of buried in dropdowns.

Auto-close tips:

Configure the system to automatically add tips to the check after 2 minutes of payment submission (if the customer doesn’t respond to the “Add tip?” prompt). This speeds up table turnover significantly.

Menu shortcuts and search:

Add a search feature so servers can find items by partial name. Instead of scrolling through “Beverages,” a server can type “Coff” and “Espresso,” “Cappuccino,” and “Coffee Americano” appear instantly.

---

Maintenance Schedule and Monitoring

After launch, POS systems need ongoing care to stay reliable.

Daily tasks:

• Check that the main terminal powered on successfully (green lights on back)
• Confirm Ethernet link lights are green
• Verify Wi-Fi handhelds all connected at morning briefing
• Monitor transaction processing: if transactions are slower than usual, note it and check network latency
• Review any error messages in the Activity Log

Weekly tasks:

• Review activity logs for errors: Manager > Reports > Activity Log, filter for warnings and errors
• Clean printer heads: if print quality degrades, gently wipe the thermal head with a lint-free cloth and isopropyl alcohol
• Check paper levels in all printers and cash drawers; restock as needed
• Verify Wi-Fi coverage by walking the restaurant with a handheld (signal should be 3+ bars everywhere)
• Test a payment transaction to confirm processing is working

Monthly tasks:

• Install any available firmware updates (Shift4 will notify you via email)
• Verify that all transactions are successfully settling (check your bank account for daily deposits)
• Review sales reports and confirm numbers match your actual take
• Test a backup power scenario: temporarily disconnect UPS from wall outlet, verify terminal runs on battery for at least 5 minutes
• Back up your Lighthouse menu and staff configuration (Shift4 does this automatically, but verify the backup date in Lighthouse > Settings)
• Review staff access and remove anyone who’s left the company

Quarterly tasks:

• Security audit: review staff accounts, remove anyone who’s left, reset older passwords (>90 days)
• PCI DSS compliance check: verify payment networks are still isolated, firewall rules haven’t been accidentally disabled, TLS certificates haven’t expired
• Test recovery procedures: simulate a hard drive failure or terminal crash and practice the recovery steps with Shift4 support (do this in off-hours)
• Analyze sales trends and adjust menu pricing if necessary

For detailed maintenance and monitoring guidelines, reference Powerful POS Reports & Analytics.

---

DIY vs. Professional On-Site Setup (Comparison)

Not every restaurant should self-install. Here’s how to decide.

Criterion	DIY (Self-Install)	Professional (Shift4 Technician)	Recommendation
Velocidad	3–5 days with experienced team	1–2 days, often completed same day	Pro: faster, minimizes disruption
Risk	High risk of configuration errors, missed security settings, network failures	Low risk, technician follows proven checklist	Pro: higher compliance and reliability
Costo	Free (staff labor)	$500–$2,000 depending on complexity	DIY if experienced; Pro if first-time
Compliance	Risk of PCI DSS gaps (VLAN, firewall, EMV validation)	Guaranteed PCI-compliant setup	Pro: auditable, certified
Scalability	Works for single terminal, complex for multi-location	Handles single to multi-location seamlessly	Pro: scales efficiently
Ongoing Support	Staff responsible for troubleshooting	Shift4 tech available for post-launch issues	Pro: dedicated support
Capacitación	DIY team must train themselves and staff	Technician can train your team during installation	Pro: more effective training

Best for DIY: Single-terminal, straightforward setup, experienced IT person on staff, non-urgent timeline.

Best for Professional: Multi-location rollout, complex network, first-time POS, urgency to launch, limited internal IT resources.

In my experience, the cost of a professional technician pays for itself within 2–3 weeks through avoided downtime and faster, smoother service. A misconfigured payment network or VLAN can lose you hundreds in transaction failures during peak service.

For professional deployment options and pricing, consult SkyTab Pricing & POS System Pricing or Contactar con SkyTab.

---

Staff Training for Restaurant POS System

Your technology is only as good as your people. The best-configured POS with untrained staff is a liability.

Core Training Curriculum

For all staff (servers, bartenders, hosts):

1. Login and Clock-In (5 minutes)
   • Tap the PIN entry field
   • Enter your unique 4-digit PIN
   • Press Enter
   • Confirm your name appears on screen
2. Order Entry Basics (15 minutes)
   • Tap items on the menu to add them to a check
   • For modifiers (size, temperature), tap the item and then select the modifier before confirming
   • Quantity: tap an item multiple times or enter quantity directly
   • Verify the order preview shows everything correctly before sending to kitchen
   • Tap “Send” to route the order to the kitchen printer/KDS
3. Payments and Tips (10 minutes)
   • When customer is ready to pay, tap “Payment”
   • Select payment method: Card, Mobile Wallet, Cash, Gift Card
   • For card: customer taps/inserts/swipes their card
   • Terminal shows “Approved” (confirm before customer leaves)
   • Ask for tip: customer taps tip amount on screen or you enter it manually
   • Receipt prints: customer signs (if required) and leaves
4. Voids and Discounts (Managers only, 10 minutes)
   • Only managers can void items or apply manual discounts
   • To void: tap the item in the check, tap “Void,” enter manager PIN, confirm reason
   • To apply discount: tap “Discount,” enter amount or percentage, enter manager PIN
   • All voids and discounts appear in the activity log for audit purposes

For kitchen staff (BOH):

1. Reading Tickets (5 minutes)
   • Tickets print automatically when servers ring orders
   • Read the item name and all modifiers printed below
   • Example: “Salmon | No butter | Medium-rare | Capers on side”
   • If a modifier is unclear, ask the expo or manager
2. Marking Items Ready (5 minutes)
   • When an item is cooked, it moves to the “Ready” status on KDS (if using touch KDS)
   • Or, tell the expo the item is ready, and they mark it in the system
   • Don’t leave an item “cooking” if it’s actually done—delays customer delivery

For comprehensive staff training resources, reference Guía completa para la capacitación del personal de punto de venta en restaurantes.

---

Manager Training: Lighthouse and Reporting

Managers need access to Lighthouse, the back-office system, to:

• View sales reports: total revenue, items sold, payment breakdown
• Review staff performance: who voided items, who applied discounts, customer complaints
• Edit menus: prices, modifiers, availability (e.g., “salmon out” during service)
• Manage staff: add new employees, reset forgotten PINs, assign roles
• Handle refunds: process refunds for customer complaints or errors

Lighthouse dashboard walkthrough (for managers):

1. Go to app.skytab.com and log in with manager email/password
2. Click Informes to see daily/weekly/monthly sales, breakdown by category (food/beverage/alcohol), payment methods
3. Click Menú to edit items, prices, modifiers
4. Click Users to manage staff accounts
5. Click Activity Log to review all transactions and staff actions (useful for investigating discrepancies)
6. Click Schedules to view and edit staff shifts

Training managers on refund process:

1. Customer reports a problem (wrong temperature, missing item, overcharged)
2. Verify in activity log that the charge is correct
3. In Lighthouse or on the POS terminal, select the transaction and click Refund
4. Enter the refund amount and reason
5. Process the refund (appear in customer’s bank account within 1–3 business days)
6. Apologize and offer a gesture of goodwill (discount on next visit, complimentary item, etc.)

---

Get Professional SkyTab POS Deployment Support

Many restaurants benefit from professional installation support. Shift4’s technicians can handle the entire setup, train your staff, and stay available for the first few days after launch.

“SkyTab POS has been a heaven sent system for us. The system itself is so user friendly and their staff made the conversion so seamless. I highly recommend SkyTab for anyone looking for a top-notch POS system. They have 24-hour customer service so you have access to getting any issues resolved at any time of the day 7 days a week.” — Restaurant Owner, SkyTab Customer (via testimonials).

What professional deployment includes:

• On-site installation: technician handles all hardware connection, network configuration, and software setup
• Staff training: technician conducts hands-on training for FOH and BOH staff
• Payment activation: technician tests payment processing and confirms merchant account is live
• Go-live support: technician available by phone/chat for first 48 hours to resolve urgent issues
• Documentación: technician provides written setup summary, staff quick-reference cards, and support contact information

Cost estimate: $500–$2,000 depending on complexity (single terminal vs. multi-location, custom network setup, training intensity).

When professional installation is worth it:

• First-time POS implementation (most critical for success)
• Multi-location rollout (efficiency at scale)
• Complex network or kitchen layout (reduces risk of misconfiguration)
• Limited IT experience on staff (ensures proper setup)
• Need to launch on a strict deadline with zero downtime (professional expertise accelerates timeline)

When DIY is sufficient:

• Single, straightforward location
• Experienced IT person on staff
• Comfortable with network and system setup
• Flexible timeline (allows for trial-and-error learning)
• Willing to invest 3–5 days of staff time

Ready to get started? Let our team handle the technical details. We provide on-site installation, merchant account activation, staff training, and 48-hour post-launch support.

📞 Contact Us for Professional Installation

❓ Questions? We’re available 24/7 to support your go-live. Call, email, or chat with our team. For enterprise deployments and multi-location roll-outs, consult our Sistema POS empresarial page.

---

Frequently Asked Questions (FAQ)

---

Conclusion: From Day One to Day 30

Installation is a milestone, not the finish line. Your first 30 days determine whether SkyTab becomes a trusted operational tool or a source of frustration.

Days 1–3 (Launch hypercare):

• Shift4 tech on standby
• Manager monitors every transaction
• Staff errors expected and coached through in real-time
• No configuration changes—only bug fixes

Days 4–7 (Stabilization):

• Monitor transaction success rate (should exceed 99%)
• Collect feedback from servers and kitchen
• Fix minor issues (slow KDS, printer misrouting, unclear menu items)
• Increase transaction volume to normal levels

Days 8–30 (Optimization):

• Fine-tune auto-bump rules based on kitchen feedback
• Optimize menu structure and modifiers
• Create quick-reference guides for recurring situations
• Train replacement staff who missed launch orientation
• Document any remaining issues for Shift4 to address

By day 30, SkyTab should feel less like “that new POS system” and more like how your restaurant operates. Orders flow smoothly, staff make fewer mistakes, and customers experience faster service.

“Max has done a great job from the credit card transition and our SkyTab POS install. Look forward to doing business in the future with Shift4.” — Restaurant Owner (via testimonials).

---

Ready to get started? Contact our team to discuss your SkyTab POS installation timeline and requirements. We’re here to guide you through every step—from network planning through post-launch optimization.

📞 Contact us today at Contactar con SkyTab or explore pricing options at SkyTab Pricing & POS System Pricing.

For third-party integrations and ecosystem partnerships, visit Integraciones de terceros.

---

Information in this guide is general in nature and current as of January 2026. PCI DSS requirements and compliance obligations may evolve. Consult with Shift4, your payment processor, and legal counsel for guidance specific to your business jurisdiction and circumstances.