Skip to main content

POS Not Loading

Cashier Manager Admin

The POS register is a Progressive Web App (PWA). When it fails to load, you may see a blank white screen, a spinning loader that never finishes, or an error message. This page covers the most common causes and how to fix them.

Quick Checklist​

Before diving into detailed troubleshooting, run through this quick checklist:

  1. Is your internet connection working? Try loading another website.
  2. Can you access the admin panel at storename.brotherpos.ca/admin?
  3. Have you tried refreshing the page with a hard refresh (Ctrl+Shift+R or Cmd+Shift+R)?
  4. Have you tried a different browser?
  5. Is the POS URL correct? It should be storename.brotherpos.ca/pos.

If the admin panel loads but the POS does not, the issue is almost certainly browser-side (cache, service worker, or JavaScript error).

Blank White Screen​

Problem​

Navigating to /pos shows a completely blank white page. No header, no buttons, no loading indicator.

Solutions​

  1. Hard refresh the page.

    • Windows/Linux: Press Ctrl+Shift+R
    • Mac: Press Cmd+Shift+R
    • This forces the browser to bypass the cache and reload all assets from the server.

  2. Clear the browser cache.

    • In Chrome: Ctrl+Shift+Delete > select "Cached images and files" > Clear.
    • Close and reopen the browser after clearing.

  3. Check for JavaScript errors.

    • Open the browser developer tools: F12 or Ctrl+Shift+I (Windows/Linux) or Cmd+Option+I (Mac).
    • Click the Console tab.
    • Look for red error messages. Common errors include:
      • ChunkLoadError -- a JavaScript file failed to download.
      • SyntaxError -- a corrupted cached file is being loaded.
      • TypeError -- a code error (report this to support).

  4. Try incognito/private mode. Open a new incognito window and navigate to the POS URL. If it loads in incognito but not in a regular window, the problem is cached data or a browser extension.

  5. Disable browser extensions. Ad blockers, privacy extensions, and security plugins can sometimes interfere with the POS. Try disabling all extensions temporarily.

Ad blockers

Some ad blockers (such as uBlock Origin) can block API requests that look like tracking calls. If the POS loads but products do not appear, try disabling your ad blocker for the Brother POS domain.

Infinite Loading Spinner​

Problem​

The POS shows a loading indicator that spins indefinitely and never reaches the main interface.

Solutions​

  1. Check your network connection. The POS needs to contact the server during initial load to authenticate and fetch store settings. If the server is unreachable, loading will stall.

  2. Verify your session is valid. Your login session may have expired.

    • Try navigating directly to storename.brotherpos.ca/pos (not from a bookmark).
    • If prompted to log in, log in with your credentials or PIN.

  3. Clear application storage.

    • Open developer tools (F12).
    • Go to Application tab (Chrome) or Storage tab (Firefox).
    • Click Clear site data or manually clear:
      • Local Storage
      • Session Storage
      • Local databases
      • Service Workers
    • Refresh the page.

  4. Check if a cash drawer session is required. The POS may be waiting for a manager to open a cash drawer session. Look for a message or prompt behind the loading spinner. Ask a manager to open the drawer.

Service Worker Problems​

Problem​

The POS loads an outdated version, shows stale data, or behaves inconsistently. You may see features that were recently updated not reflecting properly.

Explanation​

The POS uses a service worker to enable offline capabilities. Service workers cache the app's files locally so it can load quickly and work without a network connection. Sometimes the service worker holds onto outdated files.

Solutions​

  1. Force an update.

    • Hard refresh: Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (Mac).
    • If the app shows an "Update Available" prompt or banner, tap it to apply the update.

  2. Unregister the service worker manually.

    • Open developer tools (F12).
    • Go to Application > Service Workers.
    • Click Unregister next to the Brother POS service worker.
    • Refresh the page. A new service worker will be installed automatically.

  3. Clear all site data.

    • In Chrome: developer tools > Application > Storage > Clear site data.
    • Check all boxes (including "Unregister service workers").
    • Click Clear site data, then refresh.
Service worker updates

When a new version of the POS is deployed, the service worker detects the change and downloads the updated files in the background. On the next page load, you will get the new version. If you need the update immediately, a hard refresh forces it.

Local Database / Local Storage Issues​

Problem​

The POS loads but behaves strangely -- products are missing, settings seem wrong, or the offline queue shows phantom transactions.

Solutions​

  1. Clear local database data.

    • Open developer tools > Application > Storage.
    • Expand the Brother POS database entries.
    • Right-click each database and select Delete database.
    • Refresh the page. The POS will rebuild its local database from the server.

  2. Clear Local Storage.

    • Open developer tools > Application > Local Storage.
    • Right-click the entry for your Brother POS domain and select Clear.
    • Refresh the page.
Check your offline queue first

Before clearing local database data, check if you have any pending offline sales that have not synced yet. Clearing the local database will delete those queued transactions permanently. See Offline Issues for how to check.

PWA Installation Issues​

Problem​

The POS was installed as a PWA (pinned to the home screen or taskbar) and now it will not open, opens to a blank screen, or shows an outdated version.

Solutions​

  1. Open the POS in a regular browser first. Navigate to storename.brotherpos.ca/pos in Chrome or Edge. If it loads fine in the browser, the problem is with the PWA installation.

  2. Uninstall and reinstall the PWA.

    • Windows/Chrome: Click the three-dot menu > "Uninstall Brother POS" or right-click the taskbar shortcut.
    • Android: Long-press the app icon > "App info" > "Uninstall".
    • iPad/iPhone: Long-press the icon > "Remove App" > "Delete App".
    • After uninstalling, navigate to the POS URL in the browser and reinstall by clicking the install prompt in the address bar.

  3. Clear PWA cache. On some platforms, PWAs maintain their own separate cache that persists even after clearing the browser cache.

    • Android: Settings > Apps > Brother POS > Storage > Clear Cache.
    • Windows: The uninstall/reinstall process clears the cache.

Browser Compatibility​

Problem​

The POS does not load or has visual glitches in your browser.

Supported Browsers​

BrowserSupportedNotes
Chrome 90+YesRecommended. Full feature support.
Edge 90+YesChromium-based Edge works identically to Chrome.
Firefox 100+YesSupported but PWA installation not available.
Safari 15+PartialWorks but some features (Web Serial for scales) may not be available.
Internet ExplorerNoNot supported. Do not use.

If you are using an unsupported or outdated browser, update to the latest version of Chrome or Edge.

Mobile Device Issues​

Problem​

The POS does not load or is unresponsive on a tablet or phone.

Solutions​

  1. Check available storage. If the device is very low on storage, the browser may be unable to cache the POS files. Free up space by removing unused apps or files.

  2. Check available memory. Close other apps running in the background. The POS needs adequate RAM to run smoothly.

  3. Restart the device. A full restart clears temporary memory and can resolve many issues.

  4. Update the browser. Ensure the browser app is updated to the latest version from the App Store or Play Store.

  5. Check screen rotation lock. If the POS layout looks broken, the display may be in portrait mode when it is designed for landscape, or vice versa.

When Nothing Works​

If none of the solutions above resolve the problem:

  1. Note the exact error message (if any) from the browser console (F12 > Console tab).
  2. Take a screenshot of the console errors.
  3. Note which browser and device you are using (e.g., Chrome 120 on Windows 11).
  4. Try a completely different device to confirm whether the problem is device-specific or server-side.
  5. Contact your admin with the above information. They can submit a support ticket by clicking their name in the top-right corner and selecting Get Support.