Skip to main content
Version: 1.x

DB03001: Query Syntax Error

What This Means​

The database query has syntax errors. This typically indicates a bug in the application rather than a user error.

Common Causes​

  • Software bug — An issue in the POS application
  • Version mismatch — Incompatible data schema
  • Corrupted data — Data contains unexpected characters
  • Encoding issues — Character encoding problems

How to Fix​

1. Update the Application​

Ensure you're running the latest version:

  • Check for POS app updates
  • Update the WCPOS WordPress plugin
  • Restart after updating

2. Clear Application Data​

Check for unsaved work first

Clearing local data or reinstalling the app deletes anything on this device that hasn't reached your store — including sales taken while offline, open carts, and edits that didn't save. Before you clear anything, open Store health → Database and check nothing is listed as held or as never having reached your server, then Store health → Logs for 0 stuck records and 0 changes waiting to send; then finish or note every open cart. If your WCPOS has no Store health page, update WCPOS first, then check. If anything is listed or waiting, or you can't check, don't clear — ask your store owner or contact support.

Only if the other steps on this page didn't help, and only after the check above, reset to a clean state:

  • Clear local data/cache
  • Login again
  • Re-sync data

3. Check for Special Characters​

If the error occurs with specific data:

  • Check for unusual characters in product names
  • Look for emojis or special symbols
  • Try with simpler data

4. Report the Bug​

If the issue persists:

  1. Note what action causes the error
  2. Capture any error details
  3. Report on GitHub

This is Usually a Bug​

Query syntax errors are typically bugs in the software, not user errors. If you encounter this:

  • You're not doing anything wrong
  • The development team needs to know
  • A fix will be released in an update

Workaround​

Until a fix is available:

  • Try alternative approaches to accomplish your task
  • Use WooCommerce admin for affected operations
  • Check for updates regularly