Error Codes
When WCPOS encounters an issue, it displays an error code that helps identify the problem. From v1.10.0, codes follow the format domain + three digits — for example SYNC131 or AUTH311. The domain names the area of the POS; the number identifies the specific condition. Every code has its own page with what it means, what to do, and what it means for your data.
In the POS, error codes appear in Store health → Logs: expand a row and use the Help link to jump straight to the code's page here.
Error Domains (v1.10.0+)
| Domain | Area | Examples |
|---|---|---|
AUTH | Login, sessions, and tokens | AUTH101, AUTH311 |
CHECKOUT | Completing orders at the till | CHECKOUT101, CHECKOUT201 |
CLIENT | The POS app itself and local storage | CLIENT101, CLIENT201 |
LICENSE | Pro licence activation and validation | LICENSE101 |
PAYMENT | Payment gateways and terminals | PAYMENT101, PAYMENT301 |
PRINT | Receipt printing | PRINT101, PRINT301 |
PRODUCT | Product data and catalogue operations | PRODUCT101, PRODUCT401 |
SYNC | Synchronisation between the POS and your store | SYNC101, SYNC121, SYNC311 |
Use the sidebar to browse every code in a domain, or search for the code directly.
Codes ending in 999 are the domain's catch-all for conditions that don't yet have a specific code.
Legacy Codes (before v1.10.0)
Versions before v1.10.0 used a different scheme: [DOMAIN][CATEGORY][SPECIFIC_CODE], e.g. API04001 = API (domain) + 04 (response errors) + 001 (invalid response format). If you're running an older version, or reading an old log entry or support thread, these pages still apply:
| Domain | Total Codes | Covers |
|---|---|---|
| API | 39 codes | Server communication, authentication, plugin issues |
| DB | 9 codes | Local data storage and retrieval |
| PY | 6 codes | Payment processing |
| SY | 5 codes | Device resources and configuration |
A v1.10.0+ client never emits these codes — if you see one on an up-to-date POS, it's from an old retained log entry or a server-side message.
Need More Help?
If you're still experiencing issues after following the troubleshooting steps:
- Check the Troubleshooting section for more detailed guides
- Join our Discord community for support
- Report issues on GitHub