Organisations
| Name | PowerEPOS code | Account | Outlets | Handhelds | Status |
|---|
An organisation is a customer. Both PowerEPOS values here are issued by
PowerEPOS rather than chosen by us, and both can be blank until they are: the
code is what ROS puts on a notification, so it has to be exactly what they send
— an outlet ID on its own does not say which venue a notification is
about. Edit fills either in later.
Customer
Outlets
| Name | ROS outlet ID | Handhelds | Menu | Onsite server | Status |
|---|
Accounts
| Name | Role | Last signed in |
|---|
Outlet
Licence
Green is registered, amber has a code waiting, dashed is free.
Getting a number back
Deleting a handheld returns its number to the pool, so the numbers stay the ones actually in use rather than a count that only ever goes up.Menu
Venue logo
Handhelds run dark, so a logo wants to be light or carry its own background.
Formats, and why it is shown on black
PNG, JPEG, WebP or GIF, under 1MB. It is shown above the way a handheld shows it, which is the only way somebody finds out at upload time that a dark-on-transparent logo will vanish on every screen in the building.Codes waiting to be used
Registered handhelds
| No. | Name | Device | Registered | Last seen |
|---|
Onsite server
Registration
The onsite server redeems this once, on its own admin page, and pulls the rest
down with it.
What that saves
Nothing on this screen has to be typed into a machine in a back office, which is where a mistyped key normally comes from. Issuing a new code withdraws any code still waiting.PowerEPOS
Order N Pay runs the other way round from everything else: PowerEPOS is the
client, and connects into this venue's own broker.
What that means for these values
Their POS server sits in the venue on the same network as the broker, so nothing here is waiting on them to open a port for us, and the address we give them is a LAN address rather than a public one. They present the auth secret to the broker before opening the WebSocket. Everything set here reaches the broker on its next refresh, so a correction is an edit rather than a visit to the venue.What we give them
What they give us
The service mode IDs are theirs and cannot be invented — a wrong one
produces an outlet that looks installed and sends its orders to the wrong
service mode.
Overrides — normally nothing to set
Where PowerEPOS reach the broker. The address comes from
Onsite server, or from the broker reporting itself when it
registers. The port is the broker's POS listener — the same machine
the handhelds talk to, a different port from theirs above.
Identity. POSRemoteID builds itself from the
customer's PowerEPOS code and this outlet's ROS outlet ID, shown below, so
leave it blank — what is typed here stops following a later correction
to the code. Paste an auth secret only if PowerEPOS issued one themselves;
otherwise generate one above.
Portal accounts
| Name | Role | Scope | Last sign-in | Status |
|---|
A password is shown once, when the account is made or reset. Only a hash is
kept, so it cannot be read back — and the person is asked to change it at
their first sign-in.