Which POS
HospoView for NeoPOS
NeoPOS is connected today. This page says exactly what the agent reads, what it writes, and what it needs.
NeoPOS keeps its data in a database on the POS machine. HospoView’s agent is a small Windows service that sits on that machine, reads the database, and sends what it reads to the cloud. NeoPOS itself is not changed, and your staff don’t see anything different at the till.
What the agent reads
| From NeoPOS | Used for |
|---|---|
| Sales and their line items | Live takings, top products, patterns, comparisons |
| Products, prices and categories | Menu boards, reporting by category |
| Customers and reward transactions | Members, points |
| Staff list | Reports by operator |
Reading is done with a read-only login. The agent cannot change a price, void a sale or touch a transaction, because the login it uses isn’t allowed to.
What the agent writes
One thing: members. When someone joins through Regular, their record is written into the NeoPOS customer list, so the till recognises them and applies whatever member pricing and points you’ve set up. Nothing else is written. If you don’t run Regular, nothing is written at all.
What it needs
- NeoPOS running on a Windows machine in the venue, with its database on that machine or on the venue network.
- The agent installed on that machine. It installs as a Windows service and starts with the machine. We do this with you, in a remote session, and it takes well under an hour.
- An internet connection. Not a fast one; the agent sends small batches, about once a minute.
- The printers you want Docket to use on the same network, if you use it.
When things go wrong
- Internet drops. The agent keeps its place. When the connection returns it sends what it missed, in order, once. Nothing is lost and nothing is counted twice.
- The POS machine restarts. The service starts with Windows and carries on from where it was.
- We can see the agent’s health, version, uptime and free disk, so if a POS machine is running out of room we know before it becomes a problem on a Saturday night.
Multiple terminals
If a venue runs several terminals sharing one NeoPOS database, the agent goes on the machine that holds the database, once. Each additional venue is its own agent on its own machine.
Run something else?
The agent is built to be pointed at a POS database on a Windows machine. NeoPOS is the integration that is done and running in venues, and it’s the only one we’ll call supported until another one is. If you run something else, tell us what and we’ll tell you honestly where it sits.