# AUTH331: WCPOS plugin outdated

## What this means[​](#what-this-means "Direct link to What this means")

This store's WCPOS plugin is too old for this version of the app.

The app has been updated but the WCPOS plugin on the store has not, and the two versions no longer work together. Ask whoever manages the site to update the WCPOS plugin in WP Admin, then connect again. Nothing needs to change on the till.

## What to do[​](#what-to-do "Direct link to What to do")

A settings change is needed before this will work. Retry after making the change above; retrying without it will fail the same way.

## Your data[​](#your-data "Direct link to Your data")

No order or product data is affected. If this persists, ask the person who manages your WordPress site.

## Troubleshoot[​](#troubleshoot "Direct link to Troubleshoot")

1. Update WCPOS on the store: WP Admin → Plugins → update WCPOS to 1.10.0 or later. If WCPOS Pro is installed, update it to a matching version at the same time.
2. If no update is offered, check WP Admin → Dashboard → Updates; for Pro, an unauthorized updater blocks updates (see LICENSE301) — fix that first.
3. After updating, reconnect from the till — you do not need to type the store address again.
4. If the store cannot be updated yet, contact support: the till needs an app version that matches the plugin, and support can tell you which one.

## Where to look[​](#where-to-look "Direct link to Where to look")

When WCPOS can save this error, it is recorded on the device that raised it. Open **Store health → Logs** (the heart-pulse icon at the bottom of the navigation drawer), find the entry marked with this code and expand it: the expanded row shows the plain-language reason and the context captured at the moment of failure. For a store request, that context may include the server’s own error code (`serverCode`), the HTTP `status` or the `endpoint`; the fields shown depend on where the failure occurred. When reporting a problem, use **Copy debug info** at the top of the Logs screen (**Share debug info** on phones and tablets) rather than screenshots: it bundles the app version, connection state and the most recent errors. Logs are kept for at most 30 days, so collect them while the problem is fresh. Also copy any browser-console error that appeared before the POS was able to write its own log entry.

Beyond the in-app log, this failure can leave evidence in:

* **Network inspector** (web and desktop): open the developer tools — press F12 in the browser, or **Advanced → Toggle Developer Tools** in the desktop app’s menu — and select the **Network** tab. Follow this page’s retry guidance first; reproduce the action only when those steps say it is safe. A failing request shows the HTTP status and the raw response body, including error pages that never reach the POS log.
* **Server-side POS logs**: in WP Admin, open **POS → Settings → Tools → Logs**. This page records POS-related warnings and errors raised on the server itself, which may never appear inside the app. A red badge on the menu means unread server-side errors.

## Details[​](#details "Direct link to Details")

* **Code:** `AUTH331` (`WCPOS_PLUGIN_OUTDATED`)
* **Severity:** error
* **Introduced in:** WCPOS 1.10.0
