Go to the Menu section and click Sync with Cash Register—the Cash Register set will appear


If the set did not appeared or there were no changes to the dishes, then

  1. Go to the WhiteServer admin panel
  2. Find the task GetMenuByParams

  3. Check the request log. Access to the XML interface may not be configured or there may be an error in the menu.
  4. Correct the error and update the menu using the Sync with Cash Register button in Delivery

  5. If information appears for a restaurant chain, but dishes are displayed with a zero cost:

    1. Go to the r_k Delivery admin panel
    2. Go to the menu section Establishments
    3. Fill in the order category in the Menu Synchronization section in all establishments' cards.
    4. Save the changes.

Issues with order transfer to cash register

  1. Check if WhiteServer Agent v2 is running
  2. Check the agent configuration
  3. Check the server and task agent logs for CreateOrder tasks. The procedure is described in the restaurant card article.
Error messageError nameDescriptionSolution
Errors when creating and editing an order

The Phone field is not a valid phone number.

The phone value cannot be empty.

An attempt was made to create an order without the customer's phone number, or the number was entered incorrectly.Fill in the number field or check its correctness.
Invalid paymentTypeID specified.When creating an order, the payment method was not specified.Select a payment method for your order.
The order fulfillment time is less than the actual cooking time.When creating an order, insufficient time is specified for its completion.

If you are creating an order By time, please increase the delivery time.

If you are creating an ASAP order, increase the order delivery time in the settings. Read more in the Settings article.

An empty dishList order cannot be created.Attempting to delete all dishes from the created order.Cancel the order if you don't need it.
The order cannot be transferred to the specified status.An attempt to transfer an order to the status Picked up by the courier, without assigning a courier.Assign a courier.

RKInternal: The order cannot be closed, it is not paid in fullAttempt to close an order without accepting payment.Pay for the order and change the status back to Completed.
Order have FINAL 11 statusAttempting to make changes to a closed order.Once an order is closed or cancelled, changes cannot be made.

You must specify the cash register ID to work with the shiftError when pressing the Open shift key

You need to fill in the ID of the cash register in the administrative panel. To do this:

  1. In the Administrative Panel, go to the Establishments section 
  2. Choose your establishment
  3. In the Order Parameters section, specify the ID of the cash register
Payment on receipt is not availablePayment on receipt is not available

The error occurs when trying to create an order with integration with Yandex.Delivery.

There is a ban on accepting card payments by couriers from Yandex.Delivery for your Yandex.Delivery account.

Contact Yandex.Delivery and change the conditions or use the All online paid setting. In this case, the restaurant manager will have to control the fact of payment themselves.
To set the All online paid option or remove it if necessary, contact ServiceDesk

The courier can be changed before the status of Sending to the kitchenAttempting to assign a courier after the order status was changed to Sent to kitchen.The courier can be assigned at any time. Ignore this message.

The delivery address can be changed before the status Accepted at restaurantAttempting to change delivery address after order status has changed to Accepted at restaurant.You can edit the delivery address before you send the order to the kitchen.
The correct price must be passed for the dish or it should not be passed at all.
In the r_k Delivery admin panel, republish the menu set.

Cannot find guest, loyalty error code: 3007.

r_k Loyalty cannot find a guest with the given phone number.


Do nothing, the order can be created.
Order validation error in r_keeper (One or more errors occurred. (Failed to determine the Delivery enumeration))An order is created, but it does not reach the cash register.

There are 3 ways to solve this problem:

  1. Apply three XML queries sequentially to the r_keeper ref (importantly, to the ref namely) via the XML API.
    It is important to apply them sequentially:

2. Update WSA to the latest recommended version.
There will be no more errors after the update, but it is still recommended to use the method in point 1 over time if you will not be updating r_keeper itself in the near future.
This application (point 1) is necessary if r_k Loyalty is applied to an object.

Call Center Related Errors
No error body was created on the server sideAttempt to log into the call center and the establishment's interface from the same browser.Open one of the interfaces in incognito mode or set up different logins for employees with different roles. For more information, see the article Login Issues.
The order has been blocked by one of the employees.Attempt to edit an order that was opened by a call center employee.Close the order card in the call center. 
WSA Errors
WSADuplicateOrder: An attempt to recreate the orderAn attempt to create or transfer an order to the same status. An attempt to pay for an order in the establishment's interface when the cash register application is turned off.Refresh the page. 
If you have a confirmation of order receiving at the cash register, make sure that the order is confirmed.

WsaOrderError: MidServ Errors: Printer Computer Not ConnectedAttempt to pay for an order in the establishment's interface when the cash register application is turned off.Launch the cash register application and pay for the order again.

WSAFillingOrderError. Data at the root level is invalidThe system does not recognize the order data.Wait a bit and then repeat the action.
WsaRkSystemNotAvaliable: R-Keeper cash server information system is not availableThe cash server (MID) is not running.Start the cash server.
WsaOrderError. RkInternal: The common shift was opened too long agoThe common shift is open for more than 24 hours.

Close and reopen the shift. This can be done:

RK7Error: The shift cannot be closed because there is an unpaid order.An attempt to close a shift via the Establishment Interface when the order has not been closed in the cash register application.Go to the cash register application and click on the Edit order button. Close all orders. Close the common shift. Return to the Establishment Interface.

WsaOrderError. RkInternal: Cash register [xxx] Unable to close the receipt because there is an imbalance for currency

WsaOrderError. RkInternal: Cash register [xxx] Not enough money to pay for the order in full


The system is unable to close the receipt as it detects a currency imbalance.. 

It is necessary to change the currency rounding rule in the r_keeper settings. To do this:

  1. Go to r_keeper menu Money > Currencies
  2. Select the currency you tried to pay for the order with and open its properties
  3. Expand the Main section and find the Rounding Rule field. Set the value to 1.00 and save the changes.
  4. Return to the Establishment Interface and pay for the order.

You can also pay for the order without changing the rounding rules. To do this:

  1. Open the cash register application and click on the Edit order button
  2. Select the desired order and confirm that you want to edit it.
  3. Complete the payment for the order
  4. Return to the Establishment Interface and bring the order to the Completed status.
WsaOrderError RkInternal: Cannot lock orderAn attempt to accept payment for an order that has already been accepted in the cash register application.Since the order was paid for using the cash register app, there is no need to pay for the order in the Establishment Interface. The order can be marked as Completed.
WsaOrderError RkInternal: Order closedAttempt to change the order contents after it has been paid.

If you need to reduce the number of servings or remove a dish from your order, cancel the order and create a new one.

If you need to add something, create a new order.

WsaOrderError. RkInternal: The user does not have the permission to Close receiptAttempting to close an order without permission.

It is necessary to grant rights to the employee who works in the Establishment Interface. Usually this is a WSA employee. To do this:

  1. Go to r_keeper menu Personnel > Empoloyees.
  2. Select the required employee and go to his properties.
    If you set everything up by default, then expand the Central office group and select the WSA role. Select the WSA employee and go to his properties.
  3. Expand the Cashier Restrictions section and find the Close Receipt field. Activate the setting.
  4. Save the changes.
  5. Return to the Establishment Interface and close the order.
WsaOrderError. RkInternal: The price of the dish differs from the price in the price listWhite Server Agent has stopped accurately transmitting menu item prices, causing the system to detect discrepancies. 

Verify that WSA processes tasks without errors.
To do this, go to your establishment in the White Server administrative panel and open the Tasks tab. Check that the TaskTypeV2 column contains the GetMenu and GetMenuByParams tasks and that they respond correctly: there is a green check mark  in the Task Status column

If there are no errors in WSA, to fix the issue, you need to create a new menu set.

WsaOrderError. RkInternal: Errors MidServ [2219] Unable to block. The order is blocked by another blocking key (Cash register station, Admin operator).An attempt to make changes to an order that is open at a cash register. The name of the cash register and the operator's full name are shown in brackets.Close the order at the cash register station.
WS Error: Error code: WsaOrderError. RkInternal: Cash register [3813] Plazius (PDS): Error "Error processing loyalty program: unexpected" (-1)

"agentError":{ "code":"WsaOrderingPreferencesError", "desc":"WebException: The connection was not established because the destination computer rejected the connection request..." }

WsaOrderingPreferencesError

The connection was not established because the destination computer rejected the connection request..."

The configured website address with the order acceptance confirmation form at the cash register is not available.

Please note the OrderConfirmationHost setting

The error means that your order acceptance form at the cash register is not configured correctly.
What you can do: Go to the browser on the computer where the agent is installed.
open the page with the IP from the OrderConfirmationHost setting and the port from the Kestrel.EndPoints setting

If the page does not open, check if the IP and port are specified correctly. The port must be free.

"wsError": { "code": "Timeout", "desc": "Agent is offline or has been unresponsive" } }

wsError

Timeout. Agent is offline or has been unresponsive

The agent is not running.Check your internet connection if it is faulty - for WhiteServer the agent is offline
"error": { "agentError": { "code": "WsaOrderError", "desc": "WsaOrderError: Additional order properties are not added to R-Keeper" } }


WsaOrderError: Additional order properties are not added to R-Keeper

When trying to place an order, an error occurs.At the point, grant the "Advanced Properties" right to the Xml-editing user.
"error": {     "wsError": { "code": "License", "desc": "WsProduct"      } }

wsError code: License

When working with delivery, an error with the license occurs.

It is necessary to check whether there are the necessary licenses for the connection between WS and r_k Delivery and for the connection between WSA and r_keeper:

  • R-Keeper Interface to r_keeper Delivery module
  • R-Keeper module XML interface for WSA software—please note: this license must be in a single copy at the facility. Otherwise, the delivery system may not work correctly.

For more information about licenses, see the articles Licensing and Licensing Integrations.

WsaOrderError Rknternal: MidServ Errors [2205] Order with guid"The order was created in the call center, sent to the restaurant. When trying to transfer the order to the status In the kitchen—error: the order is blocked by the cash server, when trying to transfer the order again—error: The order already exists.Update WSA agent to version 2.7.3.26.

WsaOrderError RkInternal: Cash register
[3140] The order type "Restaurant delivery" does not match the selected order category "Main"		When trying to place an order, an error occurs.

You need to add the Order Type Restaurant Delivery to the Main category. To do this, in the r_keeper settings:

  1. Go to the Order section, then Order categories.
  2. Select category Main
  3. In the properties of the Main category, go to the Use order types section
  4. Check the box next to Restaurant Delivery

Errors in WSA v2 logs and their decoding

Block

Description

RKeeper.OrderCreationPreferencessettings for creating an order at the cash register and receiving a menu
RKeeper.RefServer.TcpConnetionconnection to ref server. Required to record additional order properties, such as courier phone number and guest data
Kestrelis responsible for the order acceptance form at the cash register. By default, it is configured for port 5050. The host is specified in the OrderConfirmationHost parameter of the RKeeper.OrderCreationPreferences block.