Quick answer: uniCenta oPOS is a Java application that needs a MySQL database alongside it — and that, not the POS software itself, is what should drive your hardware choice. Specify memory before CPU. A terminal running the JVM and MySQL together is far happier with 8GB and an i3 than with 4GB and an i7.
The NB-POS750 (15.6″ 1920×1080, Intel Core i3/i5/i7, 4–8GB, mSATA SSD, Windows 10/11) covers a single-till shop comfortably. Because uniCenta also runs on Linux, the NB-POS420 is worth a look if you would rather not pay for Windows licences across several tills.
What uniCenta actually asks of the hardware
Before specifying anything, it is worth being precise about what gets installed. uniCenta oPOS is not a self-contained program that you run and forget:
- Java JRE 1.8 or later. On a 64-bit machine, install the 64-bit Java — a mismatch here is a classic cause of a POS that runs but feels sluggish.
- A MySQL database (5.5 minimum, 5.6 or 5.7 preferred). This is the part people miss. uniCenta no longer ships with an embedded database, so MySQL is a separate installation that has to live somewhere.
So on a single-till setup, your terminal is running a Java application and a database server at the same time. That is a genuinely different load profile from a lightweight cloud POS that only draws a screen and talks to a server elsewhere.
The practical consequence: memory is the constraint, not raw processor speed. The JVM reserves a heap, MySQL wants its buffer pool, Windows wants the rest. On 4GB with both running you will see the machine start swapping during a busy period — which feels exactly like “the POS is slow” and gets blamed on the software.
Where does the database live?
This decides your whole hardware plan, and it is worth answering deliberately rather than by accident.
| Setup | Arrangement | What to specify |
|---|---|---|
| Single till | MySQL and uniCenta on the same terminal | 8GB. i3 is plenty. SSD, not a mechanical drive. |
| Two or three tills | One terminal hosts MySQL, others connect over the LAN | The host machine: i5, 8GB. The others can be lighter. |
| Several tills, or a busy site | MySQL on a separate small server or NAS | All terminals become clients — i3, 4GB each is fine. |
Two things worth planning for in the multi-till cases, because they are easy to get wrong on installation day:
- Wire the terminals. A database connection over Wi-Fi is a bad idea in a shop full of people and metal shelving. Use Ethernet where the till is fixed.
- Give the database host a fixed IP address. If it moves, every other till loses its connection at once. Same principle as with network printers — DHCP reservation in the router, or a static address outside the DHCP pool.
And back up the database. It is not glamorous advice, but with uniCenta your entire sales and inventory history is in that MySQL instance. A terminal is replaceable in a day; the database is not.
Windows or Linux?
uniCenta runs on both, which is a genuine advantage of an open-source, Java-based POS and worth considering seriously if you are buying more than one till.
| Windows | Linux | |
|---|---|---|
| Licence cost | Per machine | None |
| Peripheral drivers | Widest support, least effort | Usually fine for ESC/POS printers and HID scanners; occasionally more work |
| Java | Straightforward | uniCenta's documentation recommends the Oracle JRE; OpenJDK has caused problems |
| Right for | Most shops, especially one or two tills | Multi-site rollouts where licence cost multiplies, with someone technical available |
Our NB-POS420 lists Linux among its supported systems alongside Windows 7/8/10 and embedded variants. If the Linux route interests you, tell us before ordering — we would rather confirm the specific configuration than have you discover a driver gap after delivery.
For most single-shop buyers, the honest answer is Windows. The licence is a small part of the total, and everything else is one step simpler.
What actually matters in the terminal itself
Beyond the compute specification, these are the things that determine whether a till is still pleasant to use in year three:
- Screen resolution. uniCenta's interface is a desktop application with buttons, grids and dialogs. At 1920×1080 you can see a full product grid without scrolling; at 1366×768 you spend the day paging. For a Java desktop POS this matters more than it does for a simplified tablet app.
- Projected capacitive touch, not resistive. Capacitive responds to a light touch and survives millions of them. Resistive needs pressure and wears at the points people press most.
- SSD, always. With MySQL on the same machine, a mechanical drive is the difference between an instant sale lookup and a visible pause.
- Housing and thermals. A metal chassis dissipates heat better than plastic, which matters in a shop without air conditioning.
- Ports you will actually use. Count them before ordering: receipt printer, scanner, cash drawer via the printer, customer display, network.
NETBYE terminals for uniCenta
| 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 | Single till, or the database host in a multi-till shop |
| NB-POS420 | 15.1″ 1024×768 | Celeron J1800/J1900 or Core i3/i5/i7, Windows 7/8/10, embedded, WEPOS, Linux | DDR4 4GB / 8GB / 16GB | mSATA SSD 64GB–512GB | Linux deployments, licence-conscious rollouts |
One trade-off to be explicit about: the NB-POS420 runs Linux, but its screen is 15.1″ at 1024×768. Having just argued that resolution matters for a desktop POS interface, we are not going to pretend that is a detail. On uniCenta's product grid you will page more than you would at 1920×1080. If the Linux licence saving across many tills is the point, that is a reasonable trade; if you are buying one or two, take the higher-resolution Windows machine.
The NB-POS750 is 1920×1080 with projected capacitive multi-touch, an aluminium alloy and ABS housing, and options for a 3-track MSR card reader, Wi-Fi, an integrated receipt printer and a scanner. Browse the full range of all-in-one POS terminals.
Ordering advice for uniCenta: specify 8GB if the terminal will also host MySQL — this is the single specification most worth spending on. An i3 with 8GB will outperform an i5 with 4GB for this workload. Ask for the SSD size that suits your history retention; 128GB is ample for most shops.
The rest of the till
A terminal is one part of a working counter. The other hardware for uniCenta is covered in detail here:
- Receipt printer — uniCenta can drive a printer directly over a virtual COM port, which is a real advantage of this software.
- Barcode scanner — USB-HID, no driver.
- Cash drawer — wired to the printer, not the terminal.
- Label printer — if you need to code your own stock.
Frequently asked questions
What are the minimum specifications for a uniCenta terminal?
uniCenta's documentation states software prerequisites — Java JRE 1.8 or later and MySQL 5.5 or later — rather than hardware minimums. From the workload, our guidance is 8GB of memory where the terminal also runs MySQL, an SSD, and any current Intel Core processor. Confirm current requirements with uniCenta, as versions change.
Can one terminal run both uniCenta and the database?
Yes, and that is the normal single-till arrangement. Specify 8GB rather than 4GB.
Can I run uniCenta on an Android POS terminal?
No. uniCenta is a Java desktop application for Windows or Linux. An Android terminal is the wrong platform for it — if you have been offered one for this purpose, that is a reason to ask more questions.
Do I need Windows, or will Linux do?
Both are supported. Linux removes licence cost and is worth considering for a multi-site rollout with technical support available. For one or two tills, Windows is simpler.
How many tills can share one database?
That is a MySQL and network question rather than a terminal question. Small shops routinely run several tills against one host; beyond that, move the database to a dedicated machine. Wire the terminals rather than using Wi-Fi.
Does the terminal need an integrated printer?
It is an option on the NB-POS750, and it saves counter space. A separate printer is easier to replace if it fails and gives you a wider choice of print speed and interfaces. For a busy counter we would generally specify a separate printer.
A note on this guide. The hardware side above — memory versus processor for a JVM-plus-database workload, screen resolution for a desktop POS interface, touch technology, database host planning — is what we know from the products we supply and from supplying terminals into this kind of deployment. The uniCenta software prerequisites are drawn from uniCenta's published installation documentation; versions and requirements change, so confirm current details with uniCenta. 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 tills, whether one of them hosts the database, Windows or Linux and which country, and you will get an accurate quote in one reply — specified for the workload rather than for the highest number on the datasheet. Request a quote.
Related guides
These guides form a set. The rest of the hardware for uniCenta oPOS:
- Receipt printer for uniCenta oPOS
- Barcode scanner for uniCenta oPOS
- Cash drawer for uniCenta oPOS
- Label printer for uniCenta oPOS
And if you are comparing across POS software, terminals for other systems: