3.51.15
Release Date: April 1, 2026
Store Manager and Central Manager
Changes to licensing grace period
Starting with release 3.51.15, if the computer loses internet connectivity or the cloud licensing service is unavailable, the Store Manager and Central Manager apps will retain their seats and continue to operate normally without interruption for up to 2 weeks (14 days). This ensures that the apps will continue to operate even if connectivity is lost for an extended period of time. The POS app also has a grace period of 2 weeks (14 days).
Changes to item cost in received purchase orders
Starting with release 3.51.15, if the supplier's item cost changes after the store releases a purchase order, the store can enter the new item cost when they receive the purchase order, and use this new item cost to update the item's price.
A new option, Cost (PO Cost). is available in the Formula dialog under Set New Price To. Stores can use this option to update the item's price based on the new item cost entered into the Cost column on the Receive Purchase Order screen.

The new workflow is as follows:
Open the purchase order.
Click Receive.
Go to the Items tab.
Enter the new item cost in the Cost column.
(Optional) Use the new item cost to update the item's price:
Click in the New Price column.
Click the Formula button.
Under Set New Price To, select Cost (PO Cost) and enter the desired formula.
Select either Apply formula to this selection or Apply formula to all rows in this column.
Click OK.
Enter the quantity received in the Qty. Rcv column.
Click Commit.
Central Manager
Changes to the Consistency Checker
Starting with release 3.51.15, in the RMH Central Client, there is a new option Update existing data on the Consistency Checker tab. If you select this option, the Consistency Checker process will update existing values in the store database, in addition to inserting missing values. If you run the Consistency Checker manually from Command Prompt or PowerShell, you can use -u to update existing data.
Selecting the Update existing data option (or using -u) slows down the Consistency Checker process, because it is both updating and inserting values into the store database.

Last updated