Troubleshooting

Each entry below is a message the module actually shows, or a symptom that has a definite cause. Work down the checks in order.

The module has no effect at all

Symptom. After activation there is no Kitchen & Customer Screen settings tab, no Customer Screen column on the outlet list, and the kitchen address returns a "not found" page.

You will also see an admin notice: "RESPOS Kitchen And Customer Screen is activated but not effective. It requires Point of Sale and Restaurant Point of Sale (optional) in order to work at Point of Sale end."

Cause. WooCommerce Point of Sale is not active. The module loads nothing without it.

Fix. Activate WooCommerce Point of Sale, then deactivate and reactivate this module so that activation can create the role, the tables and the app files.

"Webkul Module License Activation Required" notice

Symptom. A standing notice in the WordPress admin says one or more active Webkul modules are missing valid purchase codes. Customers may also be unable to complete checkout, and an activation notice appears in the site footer.

Cause. A Webkul module — possibly this one, possibly the Point of Sale plugin itself — has not been activated with its purchase code.

Fix. Go to Restaurant POS → License, find any row whose Status column shows an Activate button, and enter the purchase code from that module's order. A row reading Approved is already fine. See Licence and Updates.

If you are not an administrator the same notice asks you to contact the administrator instead, because only an administrator can enter a purchase code.

"Purchase Code is not Correct"

Cause. The code entered does not match the module it was entered against, or does not match the order.

Fix. Check that you are pasting the code for this module and from the right store. A code bought on CodeCanyon does not activate a Webkul Store licence and the other way round. The Purchase From column on the Module License screen tells you which one the module expects.

A module shows Extend Support instead of Approved

Cause. The support period on that licence has ended. The module keeps working; renewing restores support.

Fix. Select Extend Support and renew, then use Sync Support to pull the new date in. Sync stays disabled for a few minutes after renewing while the store catches up — hover it to see how long is left.

The kitchen board is empty

Work through these in order.

Has a ticket actually been sent? Check Dining Tables → Kitchen Orders in the POS. If it is empty there too, nothing has been sent yet.
Is the live channel configured? Go to Restaurant POS → Settings → Kitchen & Customer Screen and confirm that either the Firebase details are filled in or Select App Access Type is set to Socket with the Node server running. See Real Time Connection.
Is the Node server running? On the Socket channel only, open Restaurant POS → Settings → Node Server and check that Start/Stop Server offers Stop Server rather than Start Server, and that every item in the Env Variables Require Keys Included checklist is ticked. If any is not, change a field and save again so the environment file is rewritten.
Is the signed in account mapped to an outlet? Open Restaurant POS → Users and check the Outlet column for that account. A Kitchen User with no outlet always sees an empty board.
Is it the same outlet the cashier is on? The cashier and the kitchen must be on the same outlet.
Is it a new day? On the Firebase channel the board holds the current day only, so yesterday's tickets are gone by design. See Order Lifecycle.

Old tickets are still on the board the next day

Cause. The store uses the Socket channel. On Socket, tickets are kept in your WordPress database and are never cleared by date, so anything left in On Hold, Preparing or Completed is still there the next morning, and every sent ticket stays on the POS Sent Orders tab. Firebase is the only channel that clears the previous day automatically.

Fix. Close each service with an empty board: send the tickets that were served, and delete the ones that were not with Delete on the POS Kitchen Orders tab. A ticket that is already on the Sent Orders tab can be removed by selecting Back to Hold and then Delete. See Order Lifecycle.

Start Server shows an error on the Node Server tab

These messages come from Restaurant POS → Settings → Node Server when Start Server is selected, and only matter on the Socket channel.

Message	Cause and fix
Please install Node.js on your server or contact your hosting provider!	Node.js is not installed on the web server. Install it, or ask your host to
Your Node.js version is too low. Please upgrade to version 14 or higher!	Upgrade Node.js to version 14 or newer
Please enable shell_exec or exec function in your PHP configuration.	The host has disabled both functions. Ask your host to enable one of them
Server connection refused!	The server did not answer on the address and port entered. Check Node Server ( Domain / IP ) Address and Node Server PORT, and that the port is open in the firewall

If your host cannot run Node.js at all, use the Firebase channel instead. See Real Time Connection.

"Firebase configuration not setup properly kindly check your firebase connection"

Cause. One or more Firebase fields is missing, mistyped, or belongs to a different project.

Fix. Open your Firebase project, go to Project settings → General, open the web app configuration and copy all eight values again into Restaurant POS → Settings → Kitchen & Customer Screen. The Database Url and the API Key are the two the module checks first, so start there. Save, then reload the kitchen board.

"You can not operate this in offline mode"

Cause. The till has lost its internet connection. Kitchen tickets cannot be queued offline.

Fix. Restore the connection and send the order again. Nothing was sent, so nothing is duplicated.

"You are not allowed to access this page." on the kitchen screen

Cause. Somebody is signed in to the site, but with an account that does not hold the Kitchen User role — often the store owner's own administrator account.

Fix. Sign out and sign in with a Kitchen User account. To give an existing account access, open it under Restaurant POS → Users and set User Role to Kitchen User. See Kitchen Users.

"Error : Invalid username and password."

Cause. Wrong credentials on the kitchen sign in card.

Fix. Check the username and password. If the password is lost, reset it from Restaurant POS → Users or from the WordPress user profile.

The cart has no Add To Prepare button

Cause. The button is only rendered when Restaurant Point of Sale is active, because it belongs to the dine in workflow.

Fix. Either activate Restaurant Point of Sale, or send take away orders using the Add To Prepare checkbox on the payment page, which works either way. See Sending Orders From The POS.

"Please select booking table from booking tab first."

Cause. Add To Prepare was used with no table open, so the module does not know which table the food is for.

Fix. Go to Dining Tables, book or open the table, select Add Product, then build the cart and send it.

"You can not send order for preapare in take away mode."

Cause. The cart is a take away cart, and the cart button is for dine in only.

Fix. Select Pay and tick Add To Prepare on the payment page instead.

"Your cart has some products first empty the cart."

Cause. ADD MORE or Create Bill was used while another cart is already open. Both actions replace the cart, so the POS refuses rather than lose what is in it.

Fix. Complete, park or clear the current cart, then try again.

"You can not add more products for take away orders."

Cause. ADD MORE was used on a take away ticket. Take away tickets are already paid for, so items cannot be added to them.

Fix. Send a second ticket for the extra items.

The customer screen shows a plain welcome message

Cause. The address has no outlet in it, so the screen has no configuration to load.

Fix. Open it from Restaurant POS → Outlets using the Open button in the Customer Screen column, which includes the outlet. See Endpoints and URLs.

The customer screen ignores a setting I just changed

Cause. The display loads its configuration once, when the page is opened.

Fix. Reload the display. If it still looks stale, reload it again bypassing the browser cache, with Ctrl + F5 on Windows or Cmd + Shift + R on a Mac.

The customer screen never shows orders

Cause. Customer Screen Visible Status is unticked for that outlet, which is the setting that puts the display in slideshow only mode.

Fix. Tick it on the outlet's Customer Screen tab and save. See Customer Screen Setup.

The outlet Customer Screen tab will not save

The form checks the artwork before saving and reports exactly what is missing at the top of the page.

Message	Fix
Please select side image.	Upload at least one side image.
Please select minimum 4 slider images.	With video off, upload four or more slideshow images.
Please select minimum 4 slider card images.	With video on, upload four or more card images.
Please select minimum 4 bottom slider images.	Upload four or more bottom images.
Please select a video.	Video is enabled but no file is chosen. Choose one, or untick video.
Nonce does not varify.	The page was open too long. Reload it and make the change again.

The kitchen address returns a "not found" page

Cause. The rewrite rules have not been refreshed since the endpoint was created or renamed.

Fix. Go to Settings → Permalinks and select Save Changes once. Nothing else on that screen needs to change.

Also check that no page, post or product uses the same slug as the endpoint. If one does, rename the endpoint under Restaurant POS → Settings → Endpoints.