Crunchtime Kitchen (QSR Automations) Setup – NX Restaurant

⚙️ Setting Up Crunchtime (QSR Automations) ConnectSmart Kitchen Integration in NX

The Crunchtime ConnectSmart Kitchen (CSK) Integration allows NX to communicate directly with CSK Kitchen Display System (KDS), ensuring real-time kitchen order routing and updates.

This guide walks you through setting up your integration correctly so that NX sends orders to your kitchen seamlessly.

🚀 Getting Started

To create a new integration for QSR Automations:

Go to Venue → Integrations
Select New
From the Integration Partner dropdown, choose QSR Automations

Once selected, the QSR Automations Configuration fields will appear.

⚙️ Configuration Fields

Field	Description	Required
Primary Server Host	The IP address or hostname of your primary QSR ConnectSmart Kitchen server. Do not include http:// or https://.	✅ Yes
Secondary Server Host	The IP address or hostname of your secondary server, if one exists. Leave blank if not applicable.	⚙️ Optional
Server Port	The port used for communication with QSR Automations. The default is 32768 and should only be changed if directed by QSR.	✅ Yes
Site ID	The site identifier for your venue. Set to 0 unless using the QSR Cloud Kitchen platform, in which case enter the assigned Site Code.	✅ Yes
Order Interface Method	Determines when NX sends order data to the kitchen. Options are: 🔹 On The Fly – sends orders immediately as items are added. 🔹 On Save – sends orders when the check is saved. (Default) 🔹 On Tender – sends orders only once payment is initiated.	✅ Yes
Cloud Logging	Enables cloud logging for third-party kitchen interface support. Typically disabled unless required for troubleshooting or advanced integrations.	⚙️ Optional

🧩 Example Configuration

Setting	Example Value
Integration Partner	QSR Automations
Primary Server Host	192.168.101.250
Secondary Server Host	192.168.101.251
Server Port	32768
Site ID	0
Order Interface Method	On Save

💡 Choosing the Right Order Interface Method

Option	Best Used When…
On The Fly	You want the kitchen to see updates as servers build the order — ideal for fast-paced environments where cooks start prep immediately.
On Save	You prefer the kitchen to receive orders once the server confirms them — ideal for traditional table service. (Default)
On Tender	You only want the kitchen to receive orders when payment begins — useful for pre-paid or quick-service concepts.

🔁 Data Flow Overview

An order is created in NX.
Based on the Order Interface Method, NX sends the data to both the Primary Server Host and Secondary Server Host simultaneously QSR CSK via your configured server.
CSK displays the order on kitchen screens according to its routing rules.
Optional: NX can log these communications if Cloud Logging is enabled.

🧠 Best Practices

Keep Server Port at 32768 unless specifically instructed otherwise by QSR.
Verify network connectivity between NX and your CSK server(s).
Always test with a sample order to confirm that items appear correctly on the KDS.
If your venue migrates to CSK Cloud, update the Site ID to your assigned code.

🆘 Troubleshooting

Issue	Possible Cause	Resolution
Orders not appearing on the KDS	Incorrect server host or port	Verify Primary Server Host and Port configuration.
Duplicate or missing orders	Order Interface Method mismatch	Check that the selected method aligns with your workflow.
Site ID error	Invalid or missing Site ID	Confirm with QSR Automations whether you’re using a Cloud or local setup.

✅ Summary

NX communicates directly with CSK to deliver real-time kitchen data.
Primary Server Host, Site ID, Server Port, and Order Interface Method are required.
The default configuration (32768 port, Site ID 0, and On Save interface) works for most setups.
NX transmits order data based on your chosen integration mode to keep your kitchen operations flowing smoothly.