Contents
On this page

Troubleshooting - Plugixa POS for WooCommerce

Each heading below is a symptom, with the message you see when there is one.

The register page shows “Page not found”

The register lives at /pos. Its address is a WordPress rewrite rule, written when the plugin is activated. If /pos answers with your theme’s “not found” page:

  1. Open Settings > Permalinks in WordPress and click Save Changes without changing anything. This rewrites the rules.
  2. Check that no page or post uses the slug pos.

If a developer moved the register with the plugixa_pos_register_slug filter, use that address instead. See Hooks.

“You do not have access to the register. Ask a store manager to give you access.”

The signed-in user holds none of the Plugixa POS capabilities. Give them at least plugixa_pos_sell. Shop managers do not get it automatically. See Staff access.

The Plugixa POS menu is missing in WordPress

Same cause: the menu is only shown to users who hold at least one Plugixa POS capability. Administrators always have them.

“Plugixa POS needs WooCommerce 9.6 or newer.”

Install and activate WooCommerce 9.6 or newer. The register, orders and stock all need it.

“Plugixa POS could not finish setting up its database, so parts of it will not work.”

An administrator sees this notice when the plugin could not create or update one of its tables. The notice names the table and, when it can, what the database said. The usual cause is a database user that is not allowed to create tables. Fix the permission with your host, then click Try again in the notice.

A screen of the back office stays empty or shows an error

Each screen checks its own capability on the server: the Dashboard and Cash sessions need plugixa_pos_view_reports, the Fiscal journal needs plugixa_pos_fiscal_audit, Store & registers needs plugixa_pos_manage_settings, and so on. A user can open every screen from the menu but only sees the data they are allowed to see. See Staff access.

“Ask a manager to open the register.”

The cashier may sell but may not open the cash session. Someone with plugixa_pos_manage_sessions opens it, or you give the cashier that capability. See Cash sessions.

“This register already has an open session.”

Somebody opened the same register from another device a moment before. Each register has one open session at a time. If two devices sell at the same time, give each its own register; see Stores and registers.

“Open a cash session before selling.” or “There is no open cash session on this register.”

The register’s session was closed, perhaps from another device sharing the register. Open it again from the opening screen.

The Close register (Z) button stays grey

Every field of the closing dialog must hold an amount, card fields included. Type 0 for a payment method that took nothing. With Offline mode PRO, the button also stays grey while Some sales have not reached the server yet. Sync them before closing the register.

The Z report shows a difference

The difference is what you counted minus what was expected, over all payment methods. Check, in this order:

  • the opening float typed at the start of the shift;
  • cash in and out that was not recorded with Cash in / out;
  • change given from the wrong drawer, or a cash sale rung up as card (or the other way round);
  • the card total: type the terminal’s own end-of-day total.

A closed session cannot be reopened or corrected. The difference stays on the Z report and on the Cash sessions screen.

A sale is refused

Message What to do
Not enough stock for a product WooCommerce has fewer in stock than the cart holds. Correct the stock in WooCommerce or change the quantity.
Prices changed since the cart was built. Check the new total and pay again. A price changed in WooCommerce while the sale was open. Check the new total and take payment again.
A product in the cart is no longer for sale. The product was unpublished or deleted. Remove it from the cart.
You are not allowed to give discounts. or You are not allowed to sell custom items. The cashier lacks plugixa_pos_discount.
A coupon cannot be combined with a register discount. Remove one of them. Use either a WooCommerce coupon or a register discount on one sale.
The payments do not cover the total. Add a payment for the rest.
A card payment cannot be more than the amount due. Only cash can give change.
Cannot reach the server. Check the connection and try again. The device lost its connection. When the register says No connection. Press Complete again: the sale will not be charged twice., do exactly that once the connection is back.

“The register sells in …, the shop currency, but a currency switcher changed it to …”

A currency switcher plugin changed the currency during a register sale. The register always sells in your shop’s base currency, so the sale is refused. Turn the switcher off for the register requests, or ask its author how to exclude the /pos page and the plugixa-pos/v1 REST routes.

A POS order cannot be edited in WooCommerce

That is intended. This register sale is in the fiscal journal and cannot be changed or deleted. Make a refund instead. See Orders and Refunds.

“Only a paid sale can be invoiced.”

Only a sale whose order is Completed or Refunded can have an invoice. Invoices are a Pro feature. See Invoices.

The invoice PDF does not open

This applies to A4 invoices in Pro. The PDF opens in a new tab. When the browser blocks pop-ups for your site, it is downloaded instead; look in your downloads, or allow pop-ups for your site.

Day and month closings are missing

They are written by a WordPress scheduled task that runs every hour and needs your site to have visits (WordPress cron). On a quiet site, or with DISABLE_WP_CRON set, run cron from the server. The task catches up on its next run, and a day without sales has no closing.

“The journal has been altered at entry …”

Verify journal found an entry that does not match. The message gives the first failing entry number and the reason:

  • gap: an entry number is missing, so an entry was deleted;
  • prev_hash: an entry’s link to the previous one is wrong, so an entry was inserted, deleted or edited;
  • hash: the entry’s content no longer matches its hash, so it was edited.

Nothing in the plugin edits or deletes journal entries, so a failing check means the database was changed from outside the plugin (a database tool, a restored backup of part of a table, a cleanup plugin). Restore the table from a backup taken before the change and run the check again. The check also covers the audit log. See Fiscal journal.

Online orders are not on the Dashboard

The Dashboard only counts register sales, read from the fiscal journal. Online orders are in WooCommerce’s own reports. See Dashboard.

Quick Links

Share