This topic describes the best practices for configuring and managing an offline database, which stores can use to process sales transactions if POS loses its connection to the store database.
You can configure an offline database for each POS register that allows cashiers and salespeople to continue processing sales transactions if POS loses its connection to the store database.
The offline database cannot be connected to the same SQL Server instance as the store database. It is recommended that you install Microsoft SQL Server Express on the same computer as POS, create a unique SQL Server instance for the offline database, and then connect the offline database to that SQL Server instance. An empty store database, rmhdb.bck, is shipped with RMH that you can use for the offline database. It is usually available under C:\Program Files (x86)\Retail Hero\RMH Store Manager\DBFiles.
When POS loses its connection to the store database, a warning message displays in POS and the cashier or salesperson is offered two options: try to reconnect to the store database or close the POS app. If attempts to reconnect to the store database fail, the cashier or salesperson should close and restart the POS app. When POS restarts, it connects to the offline database and a message displays to indicate that POS is operating in offline mode.
In offline mode, cashiers or salespeople can continue to process sales transactions. However, it is not possible to process more complicated transactions such as quotes, layaways, or work orders. In addition, integrated payment processing may be impacted. Stores should have a failover solution in place for payment processing to ensure they are able to continue processing payments if POS loses its connection to SQL Server and the store database.
Last updated