Skip to content
NOOLERP

Deployment

Your server. Your network. Your data.

Nool is installed in the shop rather than rented from a data centre. That one decision is why the counter survives an outage, why nobody else holds your trading figures, and why there is no monthly bill.

01

On your own server

The database sits in your shop, on a machine you own.

Nool is not rented from a data centre. The server runs in the shop — on a dedicated machine for a busy store, or on the office computer for a small one — as a Windows service that starts with the machine and comes back after a power cut without anyone logging in.

  • Your trading data stays on your premises
  • Runs as a Windows service behind a reverse proxy
  • Schema changes are migration-managed, so an update cannot half-apply
  • Automated backups on a schedule, with the restore tested at handover

02

Every device in the shop

Tills, the back office and staff phones, all on the shop's own network.

Anything on the shop's Wi-Fi or cable reaches the server: the counter terminal, a second till at the busy end of the week, the office computer doing purchases, and a phone in someone's hand checking whether a size is on the shelf. The interface adapts to the screen it is on.

  • Multiple tills, each with its own session, cash close and variance
  • Back office on the same data, at the same moment
  • Phones and tablets for stock checks on the shop floor
  • Roles decide what each device's user may see

03

More than one shop, over VPN

We recommend this

The setup we recommend once there is a second location.

Branches, and your own phone when you are not in the shop, reach the same server through a VPN — an encrypted private link, rather than opening the shop's server to the public internet. One set of books across locations, stock and sales readable per branch, and no third party holding the data.

  • One server, several locations
  • Location-wise stock, sales and closing figures
  • The owner can see the shop from anywhere with a connection
  • Encrypted link; the server is never exposed publicly

04

When the internet goes

The counter keeps selling, because the internet was never in its path.

A till talks to the server over the shop's own network. If the broadband drops, the counter does not notice: bills are rung up, stock moves, the ledger posts. What does need a connection is anything coming from outside — a branch over the VPN, or you looking at the day's takings from home. We tell customers that plainly rather than promising the impossible.

  • Selling, printing and posting continue through an outage
  • Local thermal printing through an agent — no cloud print service
  • Remote and multi-branch access resume when the line comes back

What we do so you do not have to think about it

A shop server is a machine nobody looks at until the day it matters. These are the things running quietly on it.

Backups
Automated database backups on a schedule, and the restore verified rather than assumed.
Health checks
Scheduled checks and log rotation, so a machine left alone for a month is still a machine you can trust.
Services
Runs as Windows services behind a reverse proxy; survives reboots and power cuts.
Migrations
Schema changes are versioned and applied in order, so an update either lands or does not.
Tests
A regression suite of roughly 55 test files covering pricing, tax, stock direction, ledger posting and label geometry.
Printing
Thermal invoices and labels go straight to the printer through a local agent, with no browser dialog.

Not sure what your shop needs?

Tell us how many counters you run and whether there is a second branch, and we will tell you what to buy — including when the answer is the computer you already have.