Skip to main content
FIRE POS is a web application (PWA) served from the cloud: the terminal does not run the application, it only opens it in a browser. There is no executable or installer to download — you reach it at a URL. The only component installed locally is Fire Agent, required to print receipts and open the cash drawer.

​
Addresses

Staging is the test environment: use it for training, validation and integration testing, never to run a real store.
The two environments are completely separate. A linking code generated in the production backoffice does not work on the staging POS, and vice versa. Terminals, cashiers, sales and register closes are not shared between environments either.Before linking a terminal, check that the backoffice and the POS are on the same environment.

​
Summary

FIRE POS requires a permanent internet connection. There is no offline mode today: without network the terminal cannot authenticate cashiers, load the catalog or record sales.

​
What runs on the terminal

FIRE POS can be installed as an app from the browser (PWA) so it opens full screen, without an address bar. The Fire backoffice, where terminals, cashiers and authorization codes are managed, is a separate application and is not opened from the point-of-sale terminal. See Addresses for the URL of each environment.

​
Operating system

FIRE POS runs on Windows 10 or Windows 11, 64-bit. It is the only supported platform, and the only one where thermal printing and the cash drawer work. The terminal also needs:
  • Administrator rights during Fire Agent installation or uninstallation only.
  • PowerShell 5.1 or later (already included in Windows 10/11).
  • The thermal printer driver already installed in Windows.
Fire Agent listens locally only, so there is no need to open ports or create Windows Firewall rules. See the Fire Agent installation guide.

​
Processor, memory and storage

FIRE POS takes no space of its own — it uses the browser cache. Fire Agent takes under 100 MB. Disk type is what shows most in terminal and browser startup:
The browser must be allowed to keep site data across sessions. If a store policy clears it on close, or if the terminal runs in incognito/private mode, the terminal loses its link and must be registered again with a new code.

​
Ports and connectivity

Free USB ports are counted in addition to those already taken by the thermal printer and the keyboard. They are needed to add a barcode scanner, scale, numeric keypad, second printer or a network adapter without relying on an external hub.
A powered USB hub solves a shortage of ports, but adds one more point of failure at the counter. Choosing a terminal with enough ports from the start is preferable.

​
Display and resolution

FIRE POS uses a full-screen, landscape layout with no page scrolling. The product grid adds columns according to the available width.
  • Landscape orientation. The layout assumes more width than height.
  • Minimum height of 768 px.
  • Windows scaling at 100 %. A higher scale reduces usable space.
  • Browser zoom at 100 %. FIRE POS pins the zoom level and disables pinch gestures.

​
Input

FIRE POS is operated with a touchscreen or with keyboard and mouse. Controls are sized with a 56 px touch target, designed for finger operation. A capacitive touchscreen is recommended (resistive works, but is less precise), along with a numeric keypad for cashier PIN entry and authorization codes.

​
Browser

Chrome or Edge on their latest stable version is recommended. These are the browsers FIRE POS is tested on, and the ones that automatically trust the Fire Agent certificate.

​
Minimum versions

These are the first versions that support the web features FIRE POS needs. On earlier versions the application does not load correctly.
Internet Explorer and Edge Legacy are not supported. Neither are older embedded browsers shipped with POS terminals: if the device comes with a built-in browser that cannot be updated, install Chrome or Edge.

​
Required browser configuration

​
Network and bandwidth

​
Usage

For FIRE POS, stability and latency matter more than bandwidth. Wired Ethernet is recommended over Wi-Fi, along with a backup link (4G/5G) with automatic failover.

​
Corporate network

If the store operates behind a corporate proxy or firewall, allow:
  • HTTPS (443) to the FIRE POS and Fire backend domains.
  • Local traffic for Fire Agent. It never leaves the machine, but some security suites intercept it.
  • NTP to keep the terminal clock synchronized.
Ask the Fire team for the domain list for your country and environment — they vary by deployment region.

​
Peripherals

​
Deployment recommendations

1

Install FIRE POS as an app (PWA)

Open the environment URL (pos.fire.rest in production) in Chrome or Edge and install it from the browser so it opens full screen, without an address bar.
2

Set Windows scaling to 100 %

Check Settings → System → Display → Scale on every terminal.
3

Synchronize the clock over NTP

The terminal clock affects credential validity and sales timestamps.
4

Exclude Fire Agent from antivirus

Add exclusions for C:\Program Files\FireAgent and %APPDATA%\FireAgent. Packaged Node executables trigger false positives.

​
Next step

Link the terminal

Register the terminal against a store with a single-use code.

Install Fire Agent

Enable thermal printing and the cash drawer on the terminal.