POS Terminal for KORONA POS: Standardise the Build

Quick answer: KORONA is a cloud POS with a local client, so the terminal is an ordinary well-specified Windows machine — 8GB, SSD, 1920×1080. The NB-POS750 covers it.

The part worth planning is not the terminal spec but how you build the terminals. KORONA addresses the receipt printer by its name in Windows — so if every till is imaged the same way, with the printer installed under the same name, a single POS profile covers the whole estate and commissioning becomes copy-paste. Get that wrong and every site needs its own configuration.

The terminal itself is the easy part

KORONA runs a local client against a cloud back office. That is the most conventional arrangement in this category, and it means the hardware conversation is short:

Component Specify Reason
Memory 8GB 4GB runs it. 8GB is what keeps it comfortable alongside Windows and a browser someone will inevitably open.
Storage SSD, 128GB+ Not eMMC. Windows feature updates need staging space across the terminal's life.
CPU i3 or better Sufficient for a POS client.
Screen 1920×1080 More items visible, less scrolling at the counter.
Network Wired where possible Cloud back office. The connection is part of the system.

Nothing here is unusual. Which is why the interesting part of specifying KORONA terminals is not the specification.

The part that actually saves you money: standardise the build

KORONA does not scan for the printer. It looks for a name — the printer's name in Windows, entered as a port parameter in the POS profile. We covered the failure mode this creates in the KORONA receipt printer guide: a duplicate Windows installation ending in (2) produces a printer that tests fine in Windows and prints nothing in KORONA.

At one till that is a curiosity. Across twenty tills it is an operating model, and KORONA gives you two ways to handle it.

Option 1: make every terminal identical

Same terminal model, same Windows image, printer installed under the same name at every site. Then one POS profile works everywhere with no per-site values at all, and a replacement terminal is a swap rather than a configuration job.

This is the approach we would recommend to a distributor or integrator, and it is the reason to buy terminals in one specification rather than whatever is cheapest each quarter.

Option 2: device configuration variables

KORONA supports device configuration variables: you define a variable in the POS profile and give each point of sale its own value. In KORONA's own words, a single POS profile can be used on all of the points of sale even if the printers all have different names.

This is the right tool when you inherit an estate you did not build — mixed hardware, printers named by whoever installed them. It is not a reason to skip standardising when you are building the estate.

Ordering terminals for a rollout

Three things worth asking for when the order is more than a couple of units:

  • One configuration across the order. Same memory, same storage, same screen. Spares become interchangeable.
  • Consistent pre-configuration. We can ship terminals prepared identically so the imaging step is the same at every site — which is what makes Option 1 above practical.
  • One spare on the shelf. With a standardised build, a single spare covers the estate. With mixed hardware it covers nothing reliably.

Built-in printer or separate?

For KORONA, specify a separate printer. The integration is built around a named Windows printer, and a standard external unit is the most ordinary version of that — easier to install predictably, easier to name consistently, and swappable on its own when it fails. Our built-in-printer terminals are also the lower-specified models, below what we would put under a Windows POS client.

NETBYE terminals for KORONA

Model Screen Memory Storage Best for
NB-POS750 15.6″ 1920×1080 4GB / 8GB mSATA SSD 64–512GB The default across an estate
NB-POS750D 15.6″ 1920×1080 4GB / 8GB mSATA SSD 64–512GB Same, with a 15.6″ customer-facing second display
NB-POS420 15.1″ 1024×768 SO-DIMM DDR4, 4 / 8 / 16GB mSATA SSD 64–512GB Upgradeable memory slot

Browse all-in-one POS terminals.

Ordering advice for KORONA: pick one model and stay on it across the estate. Tell us the site count and we will quote them identically configured — that consistency is worth more on a KORONA rollout than a few dollars of per-unit spec, because it is what lets one POS profile cover every till.

The rest of the till

Frequently asked questions

What hardware does KORONA POS need?

A conventional Windows terminal: 8GB memory, SSD storage, i3-class processor, 1920×1080 touchscreen. KORONA runs a local client against a cloud back office, so there is nothing unusual to accommodate.

Is 4GB enough?

It runs. 8GB is what we would ship for a till expected to stay in service for years alongside Windows updates and whatever else ends up on the machine.

Why does standardising the build matter so much for KORONA?

Because KORONA addresses the printer by its Windows name. Identical images with identically-named printers mean one POS profile covers every till, and a replacement terminal is a swap rather than a configuration exercise.

What if the sites already have different printers and names?

Use device configuration variables, which let one profile carry per-site values. That is the intended solution for a mixed estate.

Should the printer be built into the terminal?

For KORONA, no. A separate printer installs and names more predictably, and can be swapped on its own.

Wired or Wi-Fi?

Wired where the layout allows. The back office is in the cloud.

A note on this guide. The terminal side above — memory and storage behaviour, eMMC versus SSD, the operational case for standardised builds and interchangeable spares — is what we know from the products we supply. The KORONA-specific parts, including printer name addressing and device configuration variables, are drawn from KORONA's published support manual. The sizing recommendations are our engineering judgement rather than published KORONA minimums. 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, packaging and pre-configuration.

Tell us how many sites, what configuration, what quantity and which country, and you will get an accurate quote in one reply. For a multi-site KORONA rollout, ask about consistent pre-configuration — it is what makes one POS profile cover the whole estate. Request a quote.

Related guides

These guides form a set. If you are specifying a complete till, the other hardware for KORONA POS is covered here:

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

Back to blog