🖥️ Local Server Setup

What Is the Local Server?

The CoreAxis ePOS Local Server is a standalone Windows application that runs the entire CoreAxis ePOS backend on one shop PC. All other terminals (phones, tablets, other PCs) connect to it over your local network (WiFi/LAN) — no internet required for day-to-day billing, inventory, and sales.

Think of it as your own private CoreAxis server, running right inside your shop. It includes everything: the backend API, the database, and the web interface — all bundled into a single installer.

Cloud Mode vs Local Server Mode

CoreAxis ePOS supports two operating modes. You can switch between them at any time from Settings → Server Address.

Key Features

• One-click installer — NSIS installer sets up everything: PHP runtime, Laravel API, SQLite database, web UI. No manual configuration needed.
• System tray app — Runs quietly in the background. Right-click the tray icon for quick access to dashboard, server info, and quit.
• Auto-migration — Database tables are created automatically on first launch. Updates run migrations automatically too.
• APP_KEY auto-generation — Security key is generated on first run, unique to each installation.
• Cloud Sync — Pushes completed sales to the cloud every 3 minutes via sync:push. Works in background.
• WAL mode SQLite — Write-Ahead Logging enables concurrent reads from multiple terminals without locking.
• Multi-worker PHP server — 2–6 PHP worker processes handle concurrent terminal requests.
• Window close = minimize — Closing the window hides it to system tray. The server keeps running.

System Requirements

Server PC (the PC that runs the Local Server)

Terminal Devices (phones, tablets, other PCs that connect to the server)

Setup Steps

Step 1: Download & Install

Download

1. Go to the Downloads page on coreaxis.cloud
2. Under "Local Server", click Download for Windows
3. The file is named CoreAxis-Local-Server-Setup-1.1.0.exe (~110 MB)
4. Alternatively, get the installer from your CoreAxis dealer or support team

Install

1. Double-click the downloaded .exe file
2. If Windows SmartScreen appears, click "More info" → "Run anyway"
3. Choose installation language (English)
4. Accept the License Agreement
5. Choose installation directory (default: C:\Users\<you>\AppData\Local\Programs\CoreAxis Local Server)
6. Click Install and wait for completion (~30 seconds)
7. Check "Run CoreAxis Local Server" and click Finish

Step 2: First Launch & Cloud Account Setup

When you launch CoreAxis Local Server for the first time, it performs automatic setup and then opens the Cloud Account Setup wizard:

Automatic Setup (background)

1. Copies backend files — The bundled API code is copied to AppData so it can write database and log files
2. Creates the database — An empty SQLite database is created at AppData\coreaxis-local-server\api\database\database.sqlite
3. Generates APP_KEY — A unique encryption key is generated for your installation (this secures session tokens and encrypted data)
4. Runs migrations — All database tables are created automatically (products, sales, customers, inventory, etc.)
5. Starts PHP server — The built-in PHP server starts on port 8000, listening on all network interfaces (0.0.0.0:8000)

Cloud Account Setup Wizard

After the server starts, the app detects this is a fresh installation (no users exist) and opens the Local Server Setup page instead of the login screen:

1. Enter Cloud Credentials — Sign in with the same email and password you use on coreaxis.cloud. This connects your Local Server to your existing Cloud account.
2. Verify OTP — A 6-digit OTP is sent to your Cloud email for identity verification. Enter it to proceed.
3. Setup Complete — The wizard automatically creates your business (tenant), branch, roles, owner account, chart of accounts, and expense categories on the Local Server — all pulled from your Cloud account.

This entire first-launch process takes about 1–2 minutes. Subsequent launches are much faster (~5–10 seconds) and go straight to the login screen.

What You'll See

• Setup wizard — "Local Server Setup — Connect your Cloud account to get started" with email and password fields
• System tray icon — A CoreAxis icon appears in the Windows taskbar system tray (bottom-right corner, near the clock)
• After setup — "Local Server Ready!" confirmation with your business name and account email, and a "Go to Login" button

Step 3: Find Your Server IP Address

You need the server PC's local IP address so other devices on the network can connect to it. There are two ways to find it:

Method A — From the Server App (Easiest)

1. Right-click the CoreAxis tray icon in the system tray (bottom-right of taskbar)
2. Click "Server Info"
3. A popup shows your Server Address, e.g., http://192.168.1.100:8000
4. Note down this address — you'll need it for connecting terminals

Method B — Using Command Prompt

1. Press Win + R, type cmd, press Enter
2. Type ipconfig and press Enter
3. Look for your active network adapter:
   • WiFi: Under "Wireless LAN adapter Wi-Fi" → IPv4 Address
   • Ethernet: Under "Ethernet adapter Ethernet" → IPv4 Address
4. The IPv4 Address is typically something like 192.168.1.100 or 192.168.0.105

Method C — From Windows Settings

1. Open Settings → Network & Internet → WiFi (or Ethernet)
2. Click your connected network name
3. Scroll down to find IPv4 address

Step 4: Connect Terminals

Any device on the same WiFi/LAN network can connect to your Local Server. There are two methods:

Method A — Browser (Works on Any Device)

The simplest way — no app installation needed.

1. Open Chrome, Edge, Safari, or Firefox on the terminal device
2. In the address bar, type your server address:
   http://192.168.1.100:8000/app
   (Replace 192.168.1.100 with your actual server IP from Step 3)
3. The CoreAxis ePOS login page appears
4. Bookmark the page for quick access — tap the star icon in the browser, or add to home screen on mobile

Method B — CoreAxis App (Mobile or Desktop)

If you have the CoreAxis ePOS mobile app or desktop app installed:

1. Open the CoreAxis ePOS app
2. Go to Settings → Server Address
3. You'll see two options:
   • ☁️ Cloud Server (default) — connects to coreaxis.cloud
   • 🖥️ Local Server — connects to your own server
4. Select "Local Server"
5. Enter the server address: http://192.168.1.100:8000
   (Replace with your actual server IP — do NOT include /app here)
6. Tap "Save & Connect"
7. The app restarts and connects to your Local Server

Step 5: Login & Getting Started

After the Cloud Account Setup wizard completes (Step 2), you can log in immediately.

Owner Login

1. Click "Go to Login" on the setup complete screen (or navigate to the server URL)
2. Enter the same email and password you use on CoreAxis Cloud
3. Click Sign In — you're logged in instantly, no email OTP required

Banking-Style Device Trust

For security, both Local Server and Cloud use banking-style device trust:

• One user, one device — Each user can only be logged in on one device at a time, just like a banking app.
• New login kicks old session — If you log in on a new phone/PC, your session on the previous device is automatically terminated.
• All platforms — This applies across web browsers, mobile apps, and desktop apps. Logging in on any device revokes all other active sessions.
• Registered devices — Each login registers the device (browser/app) with a unique ID. The server tracks which device is currently active.

Creating Staff Accounts

1. After the owner logs in, go to Settings → Users
2. Click "Add User" to create staff accounts
3. Assign roles: Staff, Accountant, or custom roles with specific permissions
4. Each staff member logs in with their own email and password on their own terminal

Onboarding Checklist

The dashboard shows a "Get Started" checklist to help you configure your business:

• Complete your Business Profile (address, phone, logo, GSTIN)
• Add your first Product
• Make your first Sale
• Set up an Offline PIN (for extra security when internet is unavailable)

Step 6: Cloud Sync Configuration

The Local Server can automatically sync your sales data to your CoreAxis Cloud account. This gives you:

• Cloud backup — Your data is safe even if the server PC is damaged
• Remote reports — View sales, inventory, and financial reports from anywhere via coreaxis.cloud
• Multi-branch consolidation — If you have multiple shops, each syncs to the same cloud account for combined reporting

How Sync Works

• The server checks for internet connectivity automatically
• When internet is available, it pushes completed sales to the cloud every 3 minutes
• If internet goes down, sales continue normally — they queue up and sync when connection returns
• Sync runs in the background — it never interrupts billing

Sync Status

• Dashboard — Shows "Last Synced: [time]" and "Pending Items: [count]"
• System tray — Right-click → Server Info shows sync status
• Cloud dashboard — Login to coreaxis.cloud to see synced data in real-time

Advanced Configuration

Architecture & Technical Details

Understanding the Local Server architecture helps with troubleshooting and optimization.

Components

Data Flow

File Locations

Firewall Configuration

The installer usually configures Windows Firewall automatically. If terminals can't connect, check and configure the firewall manually:

Windows Defender Firewall

1. Press Win, type "Windows Defender Firewall", open it
2. Click "Advanced settings" on the left panel
3. Click "Inbound Rules" in the left panel
4. Click "New Rule..." in the right panel
5. Select "Port" → Next
6. Select "TCP" → "Specific local ports" → Enter 8000 → Next
7. Select "Allow the connection" → Next
8. Check all profiles: Domain, Private, Public → Next
9. Name the rule: "CoreAxis Local Server" → Finish

Third-Party Firewall / Antivirus

If you use a third-party firewall (Norton, Kaspersky, Avast, etc.), you also need to:

• Allow php.exe through the firewall (located in the installation folder under resources\php\)
• Allow inbound TCP connections on port 8000
• Add the CoreAxis installation folder to the antivirus exclusion list

Quick Firewall Test

From a terminal device, open Command Prompt (or Terminal on Mac) and run:

ping 192.168.1.100 (replace with your server IP)

• Reply from ... → Network connectivity is fine. If still can't connect, it's a firewall issue on port 8000.
• Request timed out → The devices are not on the same network, or the server PC's firewall is blocking ICMP.

Static IP Setup

By default, your router assigns IP addresses dynamically (DHCP). This means the server PC's IP can change after a router restart, breaking terminal connections. Setting a static IP prevents this.

Set Static IP on Windows

1. Open Settings → Network & Internet → WiFi (or Ethernet)
2. Click your connected network → click "Edit" next to IP assignment
3. Change from "Automatic (DHCP)" to "Manual"
4. Enable IPv4 and enter:
   • IP address: 192.168.1.100 (or your preferred IP — use a number above 100 to avoid conflicts with DHCP)
   • Subnet mask: 255.255.255.0
   • Gateway: 192.168.1.1 (your router's IP — check with ipconfig)
   • Preferred DNS: 8.8.8.8
   • Alternate DNS: 8.8.4.4
5. Click Save

Alternative: Reserve IP on Router

Most routers support DHCP reservation — this assigns the same IP to a specific device every time, without changing Windows settings.

1. Open your router's admin page (usually 192.168.1.1 or 192.168.0.1 in a browser)
2. Find DHCP Reservation or Address Reservation (usually under LAN/DHCP settings)
3. Add a reservation: enter the server PC's MAC address and your desired IP address
4. Save and restart the router

Performance Tuning

The Local Server works well out of the box for most shops. For high-traffic scenarios, these tips help:

Server PC Optimization

• Close unnecessary programs — Each open app consumes RAM. Close Chrome tabs, games, and heavy apps on the server PC.
• Disable sleep/hibernate — Go to Settings → System → Power → set "Screen and sleep" to Never when plugged in. The server must stay awake for terminals to work.
• Use Ethernet if possible — A wired connection to the router is more stable and faster than WiFi for the server PC.
• SSD recommended — An SSD makes database reads/writes significantly faster than a traditional hard drive.

Network Optimization

• Use 5 GHz WiFi — If your router supports dual-band, connect terminals to the 5 GHz band for faster, less congested connections.
• Reduce WiFi interference — Place the WiFi router centrally in the shop, away from microwaves, thick walls, and other electronics.
• Limit concurrent terminals — The server supports 2–6 terminals. For best performance, keep it under 4 active billing stations.

Database Maintenance

• The SQLite database grows over time as you add products, sales, and transactions
• For shops with 50,000+ transactions, database operations may slow slightly
• Cloud sync helps — once data is synced, old transactions can be archived
• Regular backups (see Backup & Restore) keep the database healthy

Backup & Restore

Your data is valuable. While cloud sync provides one layer of backup, we recommend regular local backups too.

What to Back Up

The entire api folder contains everything:

C:\Users\<you>\AppData\Roaming\coreaxis-local-server\api\

This includes:

• database\database.sqlite — All your business data (products, sales, customers, inventory, accounts)
• .env — Configuration and security keys
• storage\app\ — Uploaded files (logos, documents, product images)

Manual Backup

1. Stop the Local Server — Right-click tray icon → Quit (important: don't backup while server is running)
2. Navigate to C:\Users\<you>\AppData\Roaming\coreaxis-local-server\
3. Copy the entire api folder to a USB drive, external hard drive, or cloud storage (Google Drive, OneDrive)
4. Name the backup with the date: e.g., api-backup-2024-09-13
5. Restart the Local Server

Restore from Backup

1. Stop the Local Server
2. Navigate to C:\Users\<you>\AppData\Roaming\coreaxis-local-server\
3. Rename the current api folder to api-old
4. Copy your backup api folder to this location
5. Start the Local Server — it will use the restored data

Switch Back to Cloud

You can switch any terminal back to cloud mode at any time:

Using the App

1. Open CoreAxis ePOS app on the terminal
2. Go to Settings → Server Address
3. Select "☁️ Cloud Server"
4. Tap "Save & Connect"
5. The app reconnects to coreaxis.cloud

Using Browser

1. Simply navigate to coreaxis.cloud/app in your browser
2. Login with your cloud account credentials

Switching back to cloud mode does NOT delete any data from the Local Server. Your local data remains on the server PC. If you switch back to Local Server mode later, all your data is still there.

Updating the Local Server

When a new version of CoreAxis Local Server is available:

1. Download the latest installer from the Downloads page or from your dealer
2. Stop the running Local Server — Right-click tray icon → Quit
3. Run the new installer — it installs over the existing version
4. Launch the new version — it automatically runs any new database migrations
5. Verify all terminals can connect — they should work without any changes

Troubleshooting

Server Won't Start

Symptom: App opens but shows "Server failed to start" or stays on loading screen

• Port 8000 in use: Another application is using port 8000. Open Command Prompt and run: netstat -ano | findstr :8000. If a process is listed, close that application or change its port.
• Antivirus blocking PHP: Your antivirus may be blocking php.exe. Add the CoreAxis installation folder to your antivirus exclusion list.
• Run as Administrator: Right-click the CoreAxis Local Server shortcut → "Run as administrator".
• Corrupted installation: Uninstall via Settings → Apps, then re-download and install fresh. Your data in AppData is preserved.

Symptom: App crashes immediately on launch

• Missing Visual C++ Redistributable: Download and install Visual C++ Redistributable 2015-2022 (x64) from Microsoft.
• Windows version too old: Requires Windows 10 (64-bit) or later. Check with winver in Run dialog.

Terminal Can't Connect

Symptom: Browser shows "This site can't be reached" or "Connection refused"

1. Check server is running: Look for the CoreAxis icon in the system tray. If not there, launch the app.
2. Verify same network: Both the server PC and the terminal must be on the same WiFi/LAN. Check WiFi name on both devices.
3. Check IP address: The server IP may have changed. Re-check using Step 3.
4. Try ping: From the terminal device, ping the server: ping 192.168.1.100. If it fails, it's a network issue.
5. Check firewall: See Firewall Configuration.
6. Check the URL: Ensure you're using http:// (not https://) and port 8000.

Symptom: Some terminals connect but others don't

• The non-connecting device may be on a different WiFi network (e.g., guest WiFi vs main WiFi)
• Some routers have AP isolation enabled — this prevents devices on WiFi from seeing each other. Disable it in router settings under WiFi → Advanced.
• The device may be using a VPN that routes traffic outside the LAN. Disconnect the VPN.

Slow Performance

Symptom: POS is laggy, pages load slowly, transactions take long

• Check server PC resources: Open Task Manager (Ctrl+Shift+Esc). If CPU or RAM is above 90%, close other applications.
• Too many terminals: Reduce active terminals to 3–4. Each terminal creates concurrent connections.
• WiFi signal strength: Weak WiFi causes latency. Move the terminal closer to the router, or use 5 GHz band.
• Large database: If you have 100,000+ transactions, some queries may slow down. Ensure cloud sync is active and consider archiving old data.
• Server PC disk: If the server PC has a traditional hard drive (HDD), consider upgrading to an SSD. Database operations are 5–10x faster on SSD.

Sync Issues

Symptom: Data not appearing on cloud dashboard

• Check internet: Open a browser on the server PC and try loading any website. If no internet, sync can't work.
• Check sync status: Open the Local Server dashboard — look at "Last Synced" timestamp and "Pending Items" count.
• Verify cloud credentials: Go to Settings in the POS → verify that your cloud account email and API key are correct.
• Firewall blocking outbound: The server needs to make HTTPS requests to coreaxis.cloud. Ensure your firewall allows outbound HTTPS (port 443).

Symptom: Sync is slow or takes a long time

• Large backlog: If the server was offline for a long time, there may be thousands of pending transactions. Give it time to catch up.
• Slow internet: Sync speed depends on your upload bandwidth. A 1 Mbps upload connection may take longer for large batches.

Server IP Changed

Symptom: Terminals suddenly can't connect, but server is running

This usually happens after a router restart, power outage, or network change. The router assigned a new IP to the server PC.

1. On the server PC, re-check the IP using Step 3: Find Server IP
2. Update the server address on each terminal:
   • Browser: Change the URL to the new IP
   • App: Settings → Server Address → update the IP
3. To prevent this from happening again, set a Static IP

Printer Not Working

Symptom: Thermal receipt printer doesn't print from the Local Server

• Browser printing: When using the POS via browser, the print command opens the browser's print dialog. Select your thermal printer and configure paper size (typically 80mm or 58mm width).
• Printer connected to different PC: If the printer is connected to a terminal PC (not the server PC), printing works from that terminal's browser. Printers don't need to be connected to the server PC.
• USB printer: Ensure the thermal printer is connected via USB to the billing terminal PC and the printer driver is installed.
• Network printer: If using a network/WiFi thermal printer, ensure it's on the same network and its IP is reachable.

Print Settings

1. In the POS, go to Settings → Printer Setup
2. Select your printer type: Thermal (80mm) or Thermal (58mm)
3. Test print by clicking "Print Test Receipt"
4. Configure receipt layout: header, footer, columns, logo, QR code

Frequently Asked Questions

General

Q: Does the server PC need to stay on all the time?

Yes. The server PC must be running with the Local Server app open for other terminals to work. If the server PC shuts down, sleeps, or hibernates, all terminals lose connection and can't bill until it's back. We recommend disabling sleep mode (Settings → System → Power → Never) and using a UPS (Uninterruptible Power Supply) to protect against power outages.

Q: Can I use the server PC as a billing terminal too?

Yes! Open http://localhost:8000/app in a browser on the same PC. This connects directly without going through the network, so it's the fastest terminal. Many shops use the server PC as both the server and the main billing counter.

Q: What happens if the server PC crashes or loses power?

The SQLite database uses WAL (Write-Ahead Logging) mode, which provides crash protection. Completed transactions are safely written to disk. In-progress sales (items added to cart but not yet completed) on terminals will be lost. After a crash, simply restart the PC and launch the Local Server — it recovers automatically.

Q: Can multiple shops use one Local Server?

No. Each shop needs its own Local Server on its own local network. However, each shop's Local Server syncs to the same cloud account, so you see consolidated reports from all branches on coreaxis.cloud.

Q: Why doesn't the Local Server ask for OTP during login?

The Local Server skips email/phone OTP because it runs on your own LAN inside your shop — only people physically present in the shop can access it. Instead, banking-style device trust provides security: each user can only be logged in on one device at a time. Logging in on a new device automatically logs you out of all other devices.

Q: What is "device trust" and how does it work?

Device trust works like a banking app. When you log in, the server registers your device and revokes all other active sessions for your account — both on Local Server and Cloud. This means only one device per user can be active at any time. If someone else tries to use your credentials on another device, your session is terminated. This applies to web browsers, mobile apps, and desktop apps equally.

Q: Do I need a Cloud account to use the Local Server?

Yes. During first-time setup, the Local Server connects to your CoreAxis Cloud account to verify your identity and pull your business details (name, currency, settings). After setup, the Local Server works independently — no internet needed for billing. Your Cloud email and password become your Local Server login credentials.

Network & Connectivity

Q: What happens if the WiFi router restarts?

Terminals will briefly disconnect. Once WiFi is back, terminals automatically reconnect when you refresh the page or the app retries. No data is lost — all completed transactions are stored on the server PC.

Q: Can I use mobile data (hotspot) instead of a router?

Yes, but it's not recommended for production use. A phone hotspot works for connecting a few devices, but the IP address changes frequently, and hotspot performance varies. Use a dedicated WiFi router for reliability.

Q: Can I access the Local Server from outside my shop (remotely)?

Not directly — the Local Server is only accessible on the local network by design (for security). For remote access, use your CoreAxis Cloud account at coreaxis.cloud, which has all your synced data. If you need direct remote access, you'd need to set up port forwarding on your router and a dynamic DNS service, but this is not recommended due to security concerns.

Q: Does Local Server work with 4G/5G mobile data on terminals?

No. Terminal devices must be connected to the same WiFi/LAN network as the server PC. If a phone is using mobile data instead of WiFi, it can't reach the local server. Make sure WiFi is enabled and connected to the shop's router on all terminal devices.

Data & Sync

Q: What data syncs to the cloud?

Completed sales, customer records, product changes, inventory adjustments, and financial transactions. Draft bills, parked bills, and in-progress sessions sync only after they're completed or finalized.

Q: Can I import data from cloud to Local Server?

Currently, sync is one-way: Local Server → Cloud. If you've been using cloud mode and want to switch to Local Server, you start fresh locally. We recommend using the Data Import feature (Settings → Import/Export → Import Products from CSV/Excel) to quickly set up your product catalog on the Local Server.

Q: Is my data safe if the PC's hard drive fails?

If cloud sync is active and up-to-date, all your synced data is safe on CoreAxis cloud servers. For local-only data (not yet synced), regular backups to a USB drive or external disk are essential. See Backup & Restore.

Updates & Compatibility

Q: How do I update the Local Server?

Download the latest installer and run it over the existing installation. Your data is preserved — the database lives in AppData, not the install folder. See Updating the Local Server for step-by-step instructions.

Q: Is the Local Server compatible with all ePOS features?

Yes. The Local Server runs the same Laravel API and React UI as the cloud version. All features work: POS, inventory, GST, CRM, HR, reports, industry modules — everything. The only difference is that some cloud-only features (like real-time remote access) require internet/sync.

Q: Can I run Local Server on Linux or Mac?

Currently, the Local Server installer is available only for Windows (64-bit). Linux and macOS support is planned for a future release.