---
title: "GoSufra Edge: the small service that keeps the restaurant talking to itself | GoSufra"
description: "Offline mode usually means one till limping alone. Edge is a service on the till machine that keeps the POS, kitchen screen and waiter tablets talking over your own network, then syncs to the platform when the line returns."
url: "https://gosufra.com/en/blog/what-gosufra-edge-is/"
language: "en"
source: "https://gosufra.com"
---
# GoSufra Edge: the small service that keeps the restaurant talking to itself

Offline mode usually means one till limping alone. Edge is a service on the till machine that keeps the POS, kitchen screen and waiter tablets talking over your own network, then syncs to the platform when the line returns.

2026-09-23 · 7 min read

![Illustration of a till, a kitchen screen and a tablet connected in a building with the cloud disconnected](https://gosufra.com/blog/what-gosufra-edge-is.svg)

## Key points

- The hard part of an outage is not one till working alone — it is the till, the kitchen and the waiters still hearing each other.
- Edge is a Windows service, not part of the POS, so closing the till does not take the kitchen screen down with it.
- Orders travel as events, not as final state, which is why two tills selling the same stock do not erase each other.
- Customer orders are deliberately refused while a branch is offline: an order nobody in the kitchen can see is worse than a rejected one.

Most offline modes solve the wrong half of the problem. They make sure the cashier can still ring up a sandwich when the internet dies — which is necessary, and is also the easy part.

The hard part is that a restaurant is not one device. It is a till, a kitchen screen, two waiter tablets and a printer, and they normally talk to each other *through the internet*. Kill the line and the cashier can still take an order, but the kitchen never hears about it. You are back to shouting through a hatch, with a very expensive screen watching you do it.

**GoSufra Edge** exists for that half.

## What it actually is

A small Windows service that runs on the till machine. It starts with Windows, keeps its own database on that machine, and offers the restaurant’s own devices two things the internet was previously providing:

- a **message bus**, so the POS, the kitchen screen and the waiter tablets keep hearing each other over your own network, and

- a **queue**, holding everything that happened while the line was down, to be sent up when it returns.

It is for Cloud Edition restaurants. If you run the Local Edition — the platform installed on your own machine — you already have all of this and need no Edge.

## Why a service, and not part of the POS app

This sounds like an implementation detail. It is not; it is the difference between a feature that works and one that works on the demo.

The cashier closes the till at the end of a shift. If the Edge lived inside the POS application, the kitchen screen would go dark the moment they did — and after a Windows restart somebody would have to log in before the restaurant could take another order. A service starts with the machine and keeps running whether or not anybody is signed in.

## What keeps working, and what honestly does not

|   | Internet up | Internet down |
| --- | --- | --- |
| Cashier takes an order | yes | **yes** |
| Kitchen sees the ticket | yes | **yes**, over your network |
| Waiter marks it served | yes | **yes**, over your network |
| Receipt prints | yes | **yes** |
| Cashier stays signed in | yes | **yes**, for a few days |
| A customer orders from their phone | yes | **no** — refused on purpose |
| A password or a permission is changed | yes | **no** |

The last two are the honest part, and both refusals are deliberate.

**Customer orders are refused** because an order accepted while the kitchen is unreachable is an order the customer waits for and nobody ever sees. A clear “we cannot take orders right now” is a far better experience than silence and a cold kitchen. Note that this applies to guests ordering remotely — **staff in the building are exempt**, because a cashier standing in your restaurant is precisely the person for whom “the restaurant is offline” means nothing.

**Permissions cannot change** because only the platform can decide who may do what. The Edge has no password to check anything against, and that is by design rather than by omission — a machine sitting in a public room should not be holding the keys to your accounts.

## Orders travel as events, not as state

This is the part that decides whether the sync is trustworthy, and it is worth understanding even if you never touch a server.

When the line comes back, the till does not send the kitchen “here is what this order looks like now”. It sends the sequence of things that happened:

> created → status changed → payment added → stock adjusted

Sending the final picture instead would mean the last device to speak wins. A cancelled item would come back to life because one till’s copy still listed it. Two tills that each sold the last five portions would each erase the other’s deduction, and your stock count would be wrong in a way nobody could trace.

Stock in particular moves as a **change** — minus half a kilo — never as a new total. Two changes add up. Two totals overwrite each other.

## Nothing gets counted twice

Every event carries an identifier generated on the device, and the platform keeps a receipt for each one it has already settled. If an acknowledgement is lost on the way back — which happens constantly on bad connections — the device asks again and the platform answers from the receipt instead of applying it a second time.

The practical promise: **a lost acknowledgement costs a repeated request, never a repeated order.** You will not open the reports on Monday to find Saturday’s rush counted twice.

Retries also back off — seconds, then a minute, then five — and the backoff survives a restart, so a service that comes back up does not hammer the platform with everything at once.

## Nobody types an IP address

A paired screen remembers the Edge by a name it can look up on your own network, not by an address. So when the router reboots and hands out different addresses, nothing has to be retyped and nobody has to phone anybody.

Being on the WiFi is not enough to join, either. A restaurant’s network carries the owner’s laptop, a supplier’s tablet and whatever a guest connected to. A screen earns access by redeeming a single-use code that a member of staff generates on the till — short-lived and rate-limited — and then proves its own identity on every later request. A screen in a shared food court cannot end up pointed at the restaurant next door.

Setup is three steps on the till: register the machine once (this needs the internet), pair the till itself, then pair each other screen with a QR code.

## What is kept on the machine, and what is not

Only what a till needs to sell: the menu, prices, taxes, tables, the branch settings, the staff and customers it must be able to name, and the printers.

Not reports. Not accounting. Not payroll. Not any other branch. Not password hashes. None of it is needed to sell a sandwich, and all of it would be sitting on a computer in a room the public walks through.

The database also lives outside the program folder, so an app update cannot replace it. And the uninstaller asks before deleting it, defaulting to **No** — because it may still be holding orders you have not been paid for.

## What to ask a vendor

If you are comparing systems, these four questions separate a real offline story from a marketing one:

1. When the internet dies, does the **kitchen screen** still receive tickets — or only the till keep working?
2. If two tills each sell the last portions of something, what does the stock count say afterwards?
3. If the connection drops during sync, can the same order be recorded twice?
4. Can a customer place an online order that nobody in the kitchen will ever see?

The fourth one catches most systems out. A vendor who has thought about outages will have an opinion about refusing those orders. A vendor who has not will tell you it never happens.

## The short version

An outage is not a device problem, it is a coordination problem. Edge keeps the restaurant’s own devices coordinated on your own network, queues what the platform needs to hear, and replays it in order and exactly once when the line comes back — while being honest about the two things that genuinely cannot work without the internet.

- restaurant offline mode
- POS without internet
- kitchen display offline
- restaurant network

## In the product

### [Point of Sale & Orders](https://gosufra.com/en/features/restaurant-pos/)

Explore

### [Kitchen Display System](https://gosufra.com/en/features/kitchen-display-system/)

Explore

## Run all of this from one system

POS, kitchen, inventory, recipe costing, staff and accounting — connected, and free to start.

[Create your free account](https://app.gosufra.com/register?lang=en)

## Related articles

![Illustration of a till still selling while the cloud link is cut](https://gosufra.com/blog/how-offline-mode-works.svg)

How it works 2026-08-30 · 7 min read

### [What "works offline" actually means for a restaurant POS](https://gosufra.com/en/blog/how-offline-mode-works/)

Offline mode is easy to claim and hard to build. Here is what a till must keep doing without internet, what it cannot do, and how the queue catches up safely afterwards.

Read article

![Illustration of a till serving a kitchen screen and a phone over WiFi, with an unplugged cable](https://gosufra.com/blog/run-a-restaurant-with-no-internet.svg)

Setup & hardware 2026-09-10 · 9 min read

### [Running a whole restaurant on one PC, with the internet unplugged](https://gosufra.com/en/blog/run-a-restaurant-with-no-internet/)

The cashier machine becomes the server, the tablets become browsers, and the router stops mattering. What that shape needs, the firewall trap that breaks it, and what you give up.

Read article

![Illustration of two paths from one restaurant — one to a shop PC, one to a cloud](https://gosufra.com/blog/local-or-cloud-for-a-restaurant.svg)

Growth 2026-09-10 · 8 min read

### [Local or cloud: choosing without regretting it in a year](https://gosufra.com/en/blog/local-or-cloud-for-a-restaurant/)

Five questions that decide it, the second-branch problem that catches most people, what each side costs you in work rather than money, and why the choice is reversible in both directions.

Read article

[← All articles](https://gosufra.com/en/blog/)

[Contact us](https://t.me/GoSufraSupport)