POS Terminal for SambaPOS: Specifying the Hardware

Quick answer: SambaPOS is a Windows .NET application backed by Microsoft SQL, so the terminal must be Windows — Android POS hardware is not an option. The decision that matters most is not the processor: it is whether you choose SQL LocalDB or SQL Server Express at installation, because that determines whether you can ever add a second till without rebuilding.

For a single restaurant till, the NB-POS750 (15.6″ 1920×1080, Intel Core i3/i5/i7, 4–8GB, SSD, Windows 10/11) is the straightforward choice. If it will also act as the SQL server for other tills, specify i5 and 8GB.

What SambaPOS requires

The prerequisites are short, and each one has a hardware consequence:

  • Windows 10 or higher. Not negotiable — this is a .NET desktop application. An Android terminal cannot run it.
  • .NET Framework 4.6.2, installed automatically by the SambaPOS setup if it is not already present.
  • Microsoft SQL. SQL LocalDB for a simple single-machine setup, or SQL Server Express where more than one computer is involved.

That third point deserves the rest of this section, because it is the decision people get wrong.

LocalDB or SQL Express: decide once, at the start

SQL LocalDB is a lightweight database that runs on demand for the application on that machine. It is the easy path: nothing to configure, no service running in the background, no network exposure. For a single till that will always be a single till, it is entirely adequate.

SQL Server Express is a proper database service. It runs continuously and accepts connections over the network, which is what a second terminal needs in order to see the same tables.

The trap is that the easy path is a dead end for growth:

You install Then you add a second till
LocalDB It cannot connect. You migrate the database to SQL Express and reconfigure — usually on the evening you wanted the second till working.
SQL Express Point the new terminal at the server. Done.

If there is any prospect of a second terminal — a bar station, a takeaway counter, a second floor — install SQL Express from day one. It costs nothing and takes a little longer once, instead of a lot longer later.

This affects the hardware order too. The machine hosting SQL Express is doing more work than the others and should be specified accordingly: i5 rather than i3, 8GB rather than 4GB, and an SSD. The satellite terminals can be lighter.

Restaurant realities that decide the specification

SambaPOS is a hospitality POS, and a restaurant is a harder environment than a retail counter.

  • Heat and grease. A terminal near a service pass runs hotter and collects an oily film that ordinary dust does not. A metal chassis dissipates heat better than plastic, and a sealed capacitive glass front wipes clean — a resistive touch film does not survive repeated wiping as well.
  • Wet hands, fast taps. Projected capacitive multi-touch responds to a light touch. Staff in service do not press carefully.
  • Ticket printing is time-critical. The kitchen printer is usually on the network, so the terminal needs reliable Ethernet — wire it. See the SambaPOS receipt printer guide.
  • Service does not pause for a reboot. An SSD, adequate memory and a machine that is not running at its limit during the dinner rush are operational decisions, not luxury ones.
  • Power. Put the terminal, the router and the kitchen printer on the same UPS. A terminal that survives a brownout while the router dies has solved nothing — the kitchen still stops receiving tickets.

Screen size and layout

SambaPOS is a dense desktop interface: ticket list, menu categories, item grid, modifiers, table plan. Two points follow.

Resolution matters more than diagonal. At 1920×1080 a full menu grid with modifiers fits without paging. At 1366×768 staff page through categories on every order, which costs seconds per ticket and adds up across a service.

Consider the customer-facing side. A second display or a VFD customer display is worth specifying up front — retrofitting is awkward. In many markets showing the running total to the customer is expected, and in some it is regulated.

NETBYE terminals for SambaPOS

Model Screen Platform Memory Storage Best for
NB-POS750 15.6″ 1920×1080 Intel Core i3/i5/i7, Windows 10/11 4GB / 8GB mSATA SSD 64GB–512GB Main till, or the SQL Express host
NB-POS750D 15.6″ 1920×1080 + second screen Intel Core i3/i5/i7, Windows 10/11 4GB / 8GB / 16GB mSATA SSD 64GB–512GB Where a customer-facing second screen is wanted

The NB-POS750 has projected capacitive multi-touch on an aluminium alloy and ABS housing, rated for 0–50°C operation, with optional 3-track MSR card reader, Wi-Fi, integrated receipt printer and scanner. Browse the full range of all-in-one POS terminals.

Ordering advice for SambaPOS: if this terminal hosts SQL Express for other tills, specify i5 and 8GB. If it is a satellite terminal, i3 with 4GB is sufficient. Specify Ethernet use over Wi-Fi for any fixed station — kitchen ticket delivery should not depend on wireless.

The rest of the till

Frequently asked questions

Can SambaPOS run on an Android POS terminal?

No. SambaPOS is a Windows .NET application. If you are being offered Android hardware for a SambaPOS installation, something has been misunderstood.

What specification do I need?

SambaPOS documents software prerequisites — Windows 10 or higher, .NET Framework 4.6.2 and Microsoft SQL — rather than hardware minimums. From the workload our guidance is: i5 and 8GB for the machine hosting SQL Express, i3 and 4GB for satellite terminals, SSD in both cases. Confirm current requirements with SambaPOS.

Should I use LocalDB or SQL Express?

LocalDB only if you are certain there will never be a second terminal. Otherwise SQL Express from the beginning — migrating later is avoidable work at a bad moment.

Can two terminals share one database?

Yes, with SQL Express on one machine and the others connecting over the network. Wire them, and give the host a fixed IP address so the connection does not break after a router reboot.

Do I need a touchscreen, or will a monitor and mouse do?

It will work, but in hospitality a touchscreen pays for itself quickly. Order entry during service is a touch workflow; a mouse slows every ticket.

Is an integrated printer a good idea for a restaurant?

Usually not for the main till. A separate printer can be positioned where the customer receipt is handed over, is easier to replace mid-service, and leaves you free to choose speed and interface. The kitchen printer is separate regardless.

A note on this guide. The hardware side above — specifying for a database host versus a satellite till, screen resolution for a dense hospitality interface, touch technology, heat and power planning — is what we know from the products we supply and from supplying terminals into restaurant environments. The SambaPOS prerequisites are drawn from SambaPOS's published documentation; versions and requirements change, so confirm current details with SambaPOS. If something here did not match your installation, tell us and we will correct this page. We would rather publish something accurate than something impressive.

Get pricing

NETBYE supplies distributors, system integrators and retailers worldwide. Our terminals are built by our partner factories in Shenzhen and sold under our own model range — we handle specification, quality control and support, so you deal with one supplier rather than several factories. Direct wholesale pricing, low MOQ on first orders, and OEM/ODM covering branding, memory and storage configuration, and pre-installed system images.

Tell us how many stations, which one hosts the database, whether a customer display is needed and which country, and you will get an accurate quote in one reply — specified for the role each machine plays rather than identically across the order. Request a quote.

Related guides

These guides form a set. The rest of the hardware for SambaPOS:

And if you are comparing across POS software, terminals for other systems:

Back to blog