Hilfe - Alle Produkte & Anleitungen

Wireless Ordering on Sub-Terminals

When a location runs one or more Sub-Terminals alongside the Main Sales Point, several Sales Points and terminals become selectable after signing in to the Sales Point app. Sub-Terminals work the same way as Main Sales Points, but they do not talk to the bessa cloud over the internet — instead they communicate locally with the Main Sales Point on the same network. The Main Sales Point then aggregates the bookings of every Sub-Terminal and synchronises them with the cloud.

This page covers the sign-in order, the fixed IP allocation for the Main Sales Point, the network requirements for trouble-free wireless ordering, and how printers are resolved on Sub-Terminals.

Sign-in order

Because Sub-Terminals only communicate with the Main Sales Point, you must always connect the Main Sales Point first at commissioning — only afterwards are the individual Sub-Terminals signed in. Otherwise the Sub-Terminals would lack their communication partner and could not pull the initial master data.

Fixed IP for the Main Sales Point

Strongly recommended: give the Main Sales Point a fixed IP address on the local network (e.g. via DHCP reservation on the router) and configure that IP address in the bessa Manager for the Main Sales Point.

Benefits:

  • Sub-Terminals do not have to rediscover the Main Sales Point every time.

  • Local communication is noticeably faster.

  • No disconnects when the DHCP lease changes.

If the configured IP address of a Main Sales Point needs to change, the change must be made in the Manager first, before being switched physically on the network. Then synchronise the Main Sales Point and, in turn, all Sub-Terminals. Sub-Terminals only ever communicate with the stored IP address — if that address is changed without updating the Manager first, the Sub-Terminals have no way of learning the new address themselves.

Emergency fallback: sign out the Sub-Terminals, change the IP, then sign them back in.

Security and network segmentation

For performance reasons the Main Sales Point and Sub-Terminals communicate on the local network unencrypted. Consequences:

  • The Sales Points should live in their own network — separated from guests, IoT devices, or general office traffic.

  • Never on the same network as a customer or guest Wi-Fi.

Network requirements

For trouble-free wireless ordering we recommend ensuring the following points:

  • Time synchronisation — every Sales Point must run automatic time sync and the same time zone.

  • Fixed IP addresses for every network component: Main Sales Point, printers, card terminals, and ideally also the Sub-Terminals.

  • Open ports on the local network — see the table below.

Port

Purpose

48858 / TCP

Discovery — the Main Sales Point becomes findable on the network

48880 / TCP

Sync — the actual data exchange

Wi-Fi recommendations

Wi-Fi networks are the most common cause of sporadic disconnects between Main Sales Point and Sub-Terminals. Several points deserve attention:

  • Multiple access points → Managed Network System If you need several access points for full coverage, a Managed Network System is required to make sure every AP uses the same BSSID/ESSID (depending on the system) and that channels and frequency bands are optimally distributed. Otherwise devices keep hopping between BSSIDs — the result is constant disconnects and synchronisation issues. We recommend UniFi components by Ubiquiti.

  • Never use Wi-Fi repeaters Most repeaters use different BSSIDs for the same Wi-Fi name, which causes the same problems described above.

  • Separate 2.4 GHz and 5 GHz If you run both a 2.4 GHz and a 5 GHz Wi-Fi, make sure they have different SSID names and attach the Sales Points explicitly to only one of them. When in doubt, prefer 2.4 GHz because of its greater range. Some devices cannot distinguish networks sharing the same SSID name and switch between frequency bands on weak signal — also causing disconnects.

Printer assignment on Sub-Terminals

A Sub-Terminal no longer has to replicate every printer slot of the Main Sales Point. When a Sub-Terminal leaves a printer role empty, the print job is delegated to the Main Sales Point automatically and resolved against its own printer settings. A printer explicitly assigned on the Sub-Terminal always takes precedence — the fallback only applies to roles that are left unset.

This fallback behaviour requires bessa Kassa version 6.0 or later on both the Main Sales Point and the Sub-Terminal. If either device runs an older version, the previous behaviour applies: every printer role must be configured locally on the Sub-Terminal.

Which printer is used for an unset role depends on the role:

Printer role

Behaviour when unset on the Sub-Terminal

Invoice Printer, Cash Drawer, Report Printer

Uses the device's built-in printer (e.g. on Sunmi/iMin devices) if present — otherwise the Main Sales Point.

Order Ticket Printer, Printing Group Printers, Expediter Printer

The job goes straight to the Main Sales Point — it no longer falls back onto the Sub-Terminal's invoice printer.

So each Sub-Terminal still prints its own invoices locally and opens its own cash drawer, while order tickets, printing groups and expediter tickets run through the Main Sales Point without having to be maintained twice.

Force local printing: to keep a role printing on the Sub-Terminal itself, assign the corresponding printer explicitly on the Sub-Terminal. That removes the fallback for this role.

Changed behaviour: previously, an unconfigured order ticket, printing group or expediter printer on a Sub-Terminal printed on that Sub-Terminal's own invoice printer. From version 6.0 onwards, such a job goes to the Main Sales Point instead. If you relied on this fallback onto the invoice printer, assign the affected roles explicitly on the Sub-Terminal so they keep printing locally.