POS errors
Overview
Occasionally, if the POS becomes out of sync with the backend, you may notice issues. Most of these can be easily resolved by setting up the POS again.
Solutions
To solve your POS errors, try the following steps:
If your issue still exists after trying all of the below steps, please contact our support team.
1. Check your browser is correct
The POS works and has been fully tested with Google Chrome.
We would not recommend other browsers like Internet Explorer, Safari, Opera, Edge, or Firefox.
2. Sync the POS and Cin7 Omni
Most issues are usually resolved by syncing your POS with Cin7 Omni.
After logging in to your POS, click on the Sync button.
3. Refresh the page
Press CTRL+F5 on your keyboard (Command+Shift+R for Mac users).
4. Check your browser extensions or anti-virus
Sometimes anti-virus software can get in the way of syncing. Try temporarily switching off programs such as Norton or McAfee to see if this resolves the issue.
Don't forget to switch it back on if this does not solve the issue.
5. Check for offline orders
You may have old offline orders. If these have already been exported, you can clear these by syncing your POS.
Log out, close browser, re-open and then sync settings from the login screen.
Log out by clicking Logout at the top right of the screen.
Close the browser.
Re-open the browser again and load the login page.
6. Clear the cache
We recommend that you clear your cache and cookies periodically to prevent any issues. Do not clear the cache if you haven't exported your Offline Orders. Clearing your cache will delete these orders.
You will have different steps for clearing your cache depending on your web browser. Google Chrome provides instructions on clearing your cache and cookies.
7. Reset Chrome
This will remove all settings in Chrome, so should only be used as a last resort. Google Chrome provides instructions on how to reset Chrome settings to default.
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB
- Zendesk publishing.4.log-2014405138.zip30 KB