POS pushes KOTs to the Web KDS service

The POS can now push KOTs to the Web KDS by calling a specific Endpoint (ReceiveKot). This reduces network traffic, which is good in the SaaS environment.

To enable this, the connections need to be defined in the Kitchen Service Configuration. And each Restaurant needs to be linked to the appropriate Kitchen Service Connection.

Note: It is possible, to have for example, one Restaurant use the Standard KDS and another can use the Web KDS. This can come in handy if there are many restaurants, within the company, migrating from the Standard KDS to the Web KDS and the customer wants to migrate one by one.

Connections Configuration

Define the Kitchen Connections in the How to: Set the Kitchen Service Configuration card.

In the Web KDS WebService Connections FastTab, enter the connection information for the Kitchen Service which is available. There can be more than one services defined.

Field	Description
ID	The ID of the connection, defined by the user.
Description	Description of the role of the Kitchen Service.
Web KDS URL	Enter the hostname and port number where the Kitchen Service is running. After the port number should be the fixed text '/api/Kot' Example: localhost:8052/api/Kot If missing, this should be automatically added when leaving the field.
Use SSL (https)	Enable this if the Web Kitchen Service runs in SSL with a certificate. When the Web KDS is configured for SSL it usually listens on a different port. It can be configured in the Kitchen Service Settings Admin page. See Web KDS configurations for more information.
ID for the BC Service Tier	Enter the name of the BC Service instance name. In OnPrem this is the Service Tier instance name. In SaaS this is the Service Name in the Web Services setup card.
API Key for Web KDS Endpoint	This pass-code is used for authenticating the call from the POS to the KDS. It is acquired in the Admin page of the Kitchen Service. Each Connection has its own API key.

An Endpoint is a web service functionality in the Kitchen Service, which can be called from external clients. In this case the client is the Business Central POS.

Command action buttons

There are four command actions on this FastTab:

Where Used	Shows a list of all restaurants which use the selected connection.
Open Restaurant List	Opens the Restaurant list.
Test Connection to Web KDS Service	Sends a test KOT to the connection. If the test is successful. If an error occurs a Messagebox is shown with the error message. The message is also logged in the Web KDS Log

KDS Fields in Restaurant Card

There are three fields on the Restaurant Card which relate to the Kitchen service:

Field	Description
Kitchen Prod. System in Use	Set if a Kitchen Service in use. Set it to Yes if it is not already set.
KDS in use	Choose Web KDS to use the Web Kitchen Service. Or Standard KDS to use the Standard KDS
KDS Service Usage	Sets what activity is used by the Kitchen Service. For the Web KDS there are two options: Push or Pull. Choose Push for the POS to push KOTs to the Web KDS. Choose Pull for the Web KDS or Standard KDS - Remember to enable the Receive Kots setting in the Web Kitchen Service Admin tool (not part of the BC environment).

Link Web KDS Connections to Restaurant

To link a Web KDS Connection to a Restaurant, open up the Restaurant Card. Choose Web KDS from the Action ribbon, and click Kitchen Connection which opens the Web Kitchen Connection list.