Offline Transactions:

Offline Transactions are the transactions that occur when your device is offline. In the event that your POS goes offline, ACME Sales will still function normally. It will just store all transactions until your device is back online, and will send them through to the Back Office. You can find all transactions that occured offline in the "orders" section in Backoffice.

In general, offline transactions are not something the POS operator needs to worry about. However, if the network does go down anytime during the day, a supervisor (or someone with appropriate permissions) should go to the Back Office and confirm that all Offline Transactions went through.


Offline Notification:

If you are offline, you'll see a red circle with white line through it at the top of the screen. You may also get the following notification: "Connectivity Error: No response received from the ACME servers. Please check your Internet connectivity and try again."

NOTE: If you log out of the ACME Sales POS while in Offline Mode and need to log back in, you will NOT use your usual login credentials. To log into ACME Sales POS once offline, use the username "offline" and your designated offline PIN (setup by your local admin) as the password. 


Working while Offline:
If your device is offline and you are processing an order, you can add items as you normally would. 

  1. Proceed the "CHECKOUT" screen. 
  2. Select the form of payment (cash, credit card, check, etc.).
  3. Click "COMPLETE". A WARNING message will pop up, alerting you that your device is having trouble connecting to ACME Cloud. From here, you have three options:
    • CANCEL: cancel the transaction entirely. This choice is not generally recommended.
    • RETRY: retry the transaction, in case this is a brief network hiccup. If you were not expecting to be offline, you should try this option once or twice, in case connectivity has been restored.
    • QUEUE (RECOMMENDED): place this transaction in the offline queue. If you've Retried the transaction a few times, or you're still offline, choose this option.
  4. If you select "QUEUE", a message will pop up letting you know that your transaction has been cached (saved in Queued Transactions).

Once you're back online, the POS should automatically send all stored transactions to the Back Office.



Confirming Offline Transactions:

If your device has gone offline at any point during the day, you should check to make sure that all transactions were sent through once the device came back online. To do this, you go to "Offline Transactions" in the Back Office.


NOTE: Confirming Offline Transactions is not generally something the POS operator should worry about. We do, however, recommend that a supervisor (or someone with appropriate permissions) confirm that all transactions have gone through.


To check offline transactions:

  1. Log into Backoffice

  2. Click on "Orders" in the left navigation panel.
  3. Select "Offline Transactions" from the expanded Events menu.
  4. If any transactions show up as Failed, click "Run Failed Transactions" in the upper right corner.


Things to Remember:

  1. If a user is logged in when offline mode starts, we recommend staying logged in. That way, they can queue any transactions they complete while offline and then those orders will be pushed through as soon as service is restored. 
  2. If a user is not logged in while the network connection is down and needs to log in, they can do so with the username "offline" and the offline pin as the password. We also recommend that as soon as service is restored, that they log out and back in with their normal user credentials. This queuing process will also occur for users logged in as "offline" but they will not be automatically reconnected to online mode once service is restored as they are in the special offline profile, hence needing to log out and back in with their regular user credentials.
  3. Note that in order for the offline PIN to work as expected, a normal login needs to occur at least once earlier that day on that same sales terminal . This allows the Sales application to verify the current PIN as it is programmed in Back Office. The PIN is then saved as a temporary file for the rest of the day.