Building a Multi-Terminal Restaurant POS with C# .NET — Architecture & Lessons

Ahsan Mehmood — Mon, 09 Mar 2026 03:33:29 +0000

Building a Point-of-Sale system sounds straightforward until you realize it needs to handle multiple terminals, thermal printers, kitchen displays, real-time table tracking, and never lose a transaction — even when the network drops.

I built RestoCare+ — a multi-terminal restaurant POS system — and in this post, I'll walk through the architecture decisions, the problems I ran into, and what I'd do differently.

Background

I spent 4+ years working as a supervisor at a restaurant in Islamabad. I saw firsthand how terrible most POS systems were — slow, unreliable, confusing for staff, and impossible to maintain.

When I transitioned into software development, this was the first real product I wanted to build. Not because it was technically exciting, but because I deeply understood the problem.

Tech Stack

Language: C#
Framework: .NET Framework (WinForms for UI)
Database: SQL Server
Printing: ESC/POS commands via Windows Services
Architecture: Client-Server with centralized SQL database

High-Level Architecture

┌──────────────┐    ┌──────────────┐    ┌──────────────┐
│  Terminal 1   │    │  Terminal 2   │    │  Terminal 3   │
│  (Cashier)    │    │  (Cashier)    │    │  (Manager)    │
└──────┬───────┘    └──────┬───────┘    └──────┬───────┘
       │                   │                   │
       └───────────┬───────┴───────────────────┘
                   │
           ┌───────┴───────┐
           │   SQL Server   │
           │   (Central DB) │
           └───────┬───────┘
                   │
       ┌───────────┼───────────┐
       │           │           │
┌──────┴──┐  ┌────┴────┐  ┌───┴──────┐
│ Thermal  │  │ Kitchen  │  │ Receipt  │
│ Printer 1│  │ Display  │  │ Printer  │
└─────────┘  └─────────┘  └──────────┘

Key Design Decisions

1. Centralized Database, Not Peer-to-Peer

Every terminal connects to a single SQL Server instance. I considered SQLite per terminal with sync, but restaurants can't tolerate eventual consistency — if Terminal 1 marks Table 5 as occupied, Terminal 2 needs to see that immediately.

// Connection string points to central SQL Server
string connectionString = ConfigurationManager
    .ConnectionStrings["RestoCareDB"].ConnectionString;

2. Real-Time Table Management

The table management system uses a polling approach to keep all terminals in sync. Every terminal refreshes the floor plan every few seconds.

// Table status refresh timer
private Timer _tableRefreshTimer;

private void InitializeTableSync()
{
    _tableRefreshTimer = new Timer(3000); // 3-second interval
    _tableRefreshTimer.Elapsed += RefreshTableStatuses;
    _tableRefreshTimer.Start();
}

private void RefreshTableStatuses(object sender, ElapsedEventArgs e)
{
    var tables = _tableRepository.GetAllWithStatus();
    UpdateTableUI(tables);
}

Why polling instead of SignalR/WebSockets? Simplicity. In a restaurant with 3-5 terminals on a local network, a 3-second poll is good enough and dramatically simpler to debug when something goes wrong at 9 PM on a Friday night.

3. Thermal Printing via Windows Service

Thermal receipt printers speak ESC/POS — a binary command language. I built a dedicated Windows Service (IMS Print Service) that handles all print jobs:

// ESC/POS command to print bold text
byte[] boldOn = new byte[] { 0x1B, 0x45, 0x01 };
byte[] boldOff = new byte[] { 0x1B, 0x45, 0x00 };
byte[] centerAlign = new byte[] { 0x1B, 0x61, 0x01 };

public void PrintReceipt(Order order)
{
    var printer = new RawPrinter(_printerName);

    printer.Write(centerAlign);
    printer.Write(boldOn);
    printer.WriteText("RESTAURANT NAME\n");
    printer.Write(boldOff);

    foreach (var item in order.Items)
    {
        printer.WriteText(
            $"{item.Name,-20} x{item.Qty,3} {item.Total,8:C}\n"
        );
    }

    printer.WriteText($"\nTOTAL: {order.Total:C}\n");
    printer.CutPaper();
}

Why a Windows Service? Two reasons:

The print service runs independently — even if the POS UI crashes, queued prints still go through.
Multiple terminals can send print jobs to the same service, which queues them to avoid conflicts.

4. Kitchen Display Integration

When a waiter submits an order, it needs to appear on the kitchen display instantly. The kitchen display is a separate WinForms app running on a screen in the kitchen:

// Kitchen display polls for new orders
public List<KitchenOrder> GetPendingOrders()
{
    using (var context = new RestoCareContext())
    {
        return context.Orders
            .Where(o => o.Status == OrderStatus.Pending 
                     || o.Status == OrderStatus.InProgress)
            .OrderBy(o => o.CreatedAt)
            .Include(o => o.Items)
            .ToList();
    }
}

Kitchen staff tap items as they're prepared, and the waiter's terminal updates in real-time showing which items are ready.

5. Handling the Offline Scenario

What happens when the network drops? This is critical in restaurants — you can't stop taking orders because WiFi went down.

My approach: local queue with retry.

// If SQL Server is unreachable, queue locally
public void SubmitOrder(Order order)
{
    try
    {
        _orderRepository.Save(order);
        _kitchenService.NotifyNewOrder(order);
    }
    catch (SqlException)
    {
        _localQueue.Enqueue(order);
        _logger.Warn("DB unreachable — order queued locally");
        // Background task retries every 10 seconds
    }
}

Mistakes I Made

1. Not planning for menu changes

My initial schema had menu items tightly coupled to orders. When the restaurant changed prices or renamed dishes, it broke historical reports. Fix: I added a snapshot of the item at order time — OrderItem stores its own PriceAtTime and NameAtTime.

2. Underestimating receipt formatting

Thermal printers have 42-character line width (for 80mm paper). I spent more time formatting receipts than I expected. Arabic/Urdu text support was a whole adventure.

3. Not building user management from day one

I added multi-user roles (cashier, manager, admin) later, and retrofitting permissions into an existing system is painful. Always plan roles early.

What I'd Do Differently

Use .NET 8 instead of .NET Framework — better performance, cross-platform
Add offline-first architecture from the start, not as an afterthought
Build a web dashboard alongside the desktop app for owners to check reports remotely
Use message queues (RabbitMQ or even a simple one) instead of polling for kitchen display

Results

RestoCare+ is running in production at real restaurants. It handles:

✅ 3-5 terminals simultaneously
✅ Thermal receipt printing with proper formatting
✅ Kitchen display with real-time order updates
✅ Table management with status tracking
✅ Daily sales reports and analytics
✅ Menu management with category organization

Key Takeaways

Domain knowledge is your unfair advantage. My 4 years in a restaurant made me a better POS developer than someone with 10 years of pure coding.
Polling is fine for local networks. Don't over-engineer with WebSockets when 3-second polling works perfectly.
Thermal printing is harder than it looks. Budget extra time for this.
Build the boring stuff well. Boring features like user roles, audit logs, and error handling are what separate a demo from a product.

I'm Ahsan Mehmood — a Full-Stack Developer and Co-Founder of XechTech. I share what I learn from building real-world software. Follow for more .NET, Flutter, and AI content.

Connect: LinkedIn · GitHub · XechTech

From Restaurant Supervisor to Technical Founder: Shipping 38+ Projects in 5 Years

Ahsan Mehmood — Mon, 09 Mar 2026 03:25:50 +0000

Hey Dev.to 👋 I'm Ahsan Mehmood — a Full-Stack Developer and Co-Founder of XechTech, based in Islamabad, Pakistan.

My Journey

In 2017, I was working as a restaurant supervisor. By 2021, I had pivoted into software development full-time. Today, I've shipped 38+ production projects across 8+ organizations, serving clients in Pakistan, the US, and Australia.

What I Build

My core stack is .NET/C#, but I work across the full spectrum:

🖥️ Desktop: Multi-terminal POS systems, payroll, accounting tools (C#, .NET, SQL Server)
📱 Mobile: Cross-platform apps with Flutter (Booktionary, EstiMate Pro, DLP App)
🌐 Web: React, Laravel, Node.js, TypeScript (pal.gov.pk, xechtech.com)
🤖 AI: AutoCAD AI Agent, Gemini PC-Commander, LLM-powered workflows
🏗️ Engineering: 7+ structural tools for RPEQ-certified projects in Australia

My Company: XechTech

I co-founded XechTech in 2021 with my partner Aaqib Saleem. We build high-end software solutions — from RestoCare+ (a restaurant POS system with thermal printing and kitchen displays) to AI-powered PDF automation tools.

Key Projects

Project	What It Does	Tech
RestoCare+ POS	Multi-terminal restaurant POS	C#, .NET, SQL Server
EstiMate Pro	AI-powered PDF automation	Flutter, Dart
Engineering Suite	7+ structural analysis tools	C#, .NET, AutoCAD
PAL Website	Government website	PHP, Laravel, Flutter
Booktionary	Dictionary & book app	Flutter, SQLite
AutoCAD AI Agent	AI-generated floor plans	Python, Gemini API

What I've Learned

The biggest lesson from shipping 38+ projects: Solve real problems for real people. The fanciest tech stack means nothing if it doesn't solve a pain point.

I built RestoCare+ because I spent 4 years in a restaurant and knew exactly what was broken. I built engineering tools because construction firms in Australia needed calculations done faster. Every successful project started with understanding the problem deeply.

What's Next

I'm currently focused on:

AI integration into traditional business software
Growing XechTech's client base internationally
Sharing what I've learned through writing here on Dev.to

If you're a developer in Pakistan building your career, or if you're transitioning into tech from another field — I'd love to connect. Drop a comment or find me on LinkedIn 🤝

Follow me for posts about .NET, Flutter, AI integration, and building software businesses from Pakistan.

DEV Community: Ahsan Mehmood