Robot wash network portal: how to automate your car wash business from scratch

Automation of processes in car services and car washes has become not just a trend, but a necessity for competitiveness. Robot car washes is a revolutionary solution that reduces personnel costs, increases service speed and guarantees consistent quality. However, simply buying equipment is not enough: for the system to work as a single organism, integration into network portal — a centralized platform for managing all devices, finances and client flow.

In this article we will look at how it works network infrastructure of robot washes, what technical and organizational nuances need to be taken into account when connecting, as well as how to avoid common mistakes that lead to downtime and financial losses. The material will be useful to car service owners, investors in car washes and IT specialists involved in business automation.

What is a robot car wash network portal and why is it needed?

The portal of the robot car wash network is hardware and software complex, which unites all automatic washes into a single control system. It performs several key functions:

• 📊 Equipment operation monitoring Real-time monitoring of each robot's status, detergent levels, errors and warnings.
• 💰 Financial control: automated income accounting, integration with payment systems (SBP, Apple Pay, bank terminals).
• 🔧 Remote control: the ability to reboot the robot, update the firmware or change the washing program without being physically present.
• 📱 Customer service: mobile application for booking, payment via QR code, order history and loyalty (discounts, bonuses).

Without a portal, each car wash operates in isolation, which leads to chaos in accounting, difficulties with technical support and loss of customers. For example, if one of the sinks runs out of wax, the system should automatically notify the supplier and redirect customers to free boxes - and this is only possible with centralized management.

⚠️ Attention: Not all robot car wash manufacturers support integration with third-party portals. Before purchasing equipment, check whether there is an API for connecting to your IT infrastructure. For example, robots WashTec and PDQ LaserWash have closed protocols, and AutoBell and Sonny’s offer open solutions.

Types of robot washers and their compatibility with network portals

Robot car washes are divided into three main types, each of which requires a different approach to integration:

Robot type	Examples of models	Difficulty of integration	Connection features
Portal	WashTec SoftCare, PDQ LaserWash 360	Average	Requires PLC controller and protocol settings Modbus TCP.
Tunnel	Sonny’s The Wave, AutoBell Tunnel	High	Synchronization with the conveyor system and position sensors is required.
Contactless	Kärcher RM 899, Nilfisk Alto	Low	Connected through the manufacturer’s cloud services (for example, Kärcher Fleet).

The most universal are considered portal robots: They are suitable for self-service and full-service car washes, and their software most often supports external APIs. Tunnel systems, despite their high performance, require complex setup due to the large number of sensors and moving parts. Contactless robots are usually easier to integrate, but are limited in functionality (for example, they cannot apply wax or polish).

Technical requirements for the network portal

For the robot car wash network portal to work stably, it must meet the following criteria:

• 🖥️ Server equipment: minimum requirements - processor Intel Xeon E5, 16 GB RAM, 500 GB SSD drive. For a network of 10+ car washes, a cloud server with redundancy is recommended.
• 🌐 Network infrastructure: wired connection with a speed of at least 100 Mbit/s and a backup channel (for example, 4G/LTE). Wi-Fi is not suitable due to signal delays.
• 🔒 Security: VPN for remote access, two-factor authentication and protocol traffic encryption are required TLS 1.3.
• 📡 IoT gateways: to communicate with robots, industrial routers are needed (for example, Cisco IR829 or Huawei AR502), supporting MQTT or OPC UA.

One of the most common mistakes is saving on server hardware. For example, if the portal is deployed on virtual hosting with shared resources, during peak load (for example, on weekends) the system will freeze, which will lead to failures in the work of car washes and loss of customers. The minimum delay in processing commands by robots should not exceed 200 ms - otherwise the brushes may collide with the car body.

Step-by-step instructions for connecting the robot wash to the portal

The integration process consists of several stages. Let's consider it using the example of a portal robot WashTec SoftCare 2.0:

1. Setting up network equipment

   Connect the robot to the local network via cable Cat6. Assign a static IP address in a range not used by DHCP (for example, 192.168.1.100).

2. Installing portal software

   Deploy server software (for example, WashPortal Pro or CarWash Manager) on a dedicated server. Follow the manufacturer's instructions to configure the database (MySQL 8.0+ or PostgreSQL 13+).

3. Synchronization with the robot

   In the portal web interface, add a new device by specifying its IP address, model and serial number. Use the protocol Modbus TCP (port 502) for data exchange.

4. Testing

   Run a test wash manually through the portal. Check that the data on water consumption, detergent consumption and cycle time is transmitted correctly.

If the robot does not respond to portal commands, check:

• 🔌 Correct cable connections (use a tester Fluke Networks).
• 🔄 Firewall settings (allow traffic to ports 502 and 8080).
• 📋 Error logs in the portal software (most often the problem is an incorrect serial number or robot firmware version).

Legal and financial aspects

Connecting robot washes to a network portal requires taking into account several legal nuances:

• 📄 Software Licensing: most portals operate on a subscription basis (from 5,000 ₽/month for 1 wash). For example, CarWash Manager takes 1% from each client payment.
• 🔐 Personal data protection: if the portal stores customer data (phone numbers, payment history), it is necessary to notify Roskomnadzor and ensure encryption by FZ-152.
• 💸 Taxation: automated car washes refer to “services using machines” (Article 346.29 of the Tax Code of the Russian Federation), which implies a simplified taxation system (STS 6%).

One of the pitfalls is responsibility for failures. If, due to a portal error, the robot damages a customer's car, the blame will fall on the owner of the car wash, not on the equipment manufacturer. To minimize risks, enter into an agreement with the IT contractor who will service the portal, and include in it a clause on guaranteed response to incidents (response time no more than 2 hours).

⚠️ Attention: When integrating payment systems (for example, SBP or Tinkoff Acquiring) make sure that the portal is certified according to the standard PCI DSS. Otherwise, banks may block accepting payments.

System maintenance and upgrades

The robot car wash network portal requires regular maintenance. Here are the key procedures:

Procedure	Frequency	Responsible	Tools
Robot firmware update	1 time per quarter	IT specialist	WashTec Service Tool, FTP client
Database backup	Daily	Automatically (cron)	mysqldump, Cloud Backup
Checking network equipment	1 time per month	System Administrator	Wireshark, PingPlotter

Robot firmware updates should be installed during non-business hours (for example, 2:00 to 5:00) as the process can take up to 30 minutes per device. Before updating, be sure to:

1. Create a backup copy of the robot's current settings.
2. Check the compatibility of the new version with your portal (information is in the manufacturer's documentation).
3. Make sure there are no customers at the car wash (lock the box in the booking system).

What happens if you interrupt the firmware update?

Interrupting the update process may result in the robot controller becoming bricked. In this case, the physical intervention of a service engineer will be required to reflash it via the JTAG port, which will cost 15-30 thousand rubles plus a simple wash for 1-2 days.

To monitor the status of the portal, it is recommended to use systems like Zabbix or Nagios. They allow you to configure notifications about critical events (for example, a loss of communication with the robot or low detergent level) via SMS or Telegram.

Common mistakes and how to avoid them

Even experienced car service owners make mistakes when integrating robot washes into the network. Here are the most common:

• 🚫 Ignoring the backup communication channel: If the Internet provider turns off the services, the sink will stop. The solution is a backup 4G modem with automatic switching.
• 🔌 Incorrect cabling: Using cheap twisted pair cables or laying cables near noise sources (such as welding machines) results in lost data packets.
• 💻 Lack of test bench: updates to the portal or robot firmware should first be checked on one device, and not deployed to the entire network at once.
• 📉 Unaccounted for maintenance costs: many people forget to budget for the cost of software licenses (from 300 thousand rubles/year) and the salary of an IT specialist (from 80 thousand rubles/month).

One of the most costly mistakes is equipment incompatibility. For example, if you buy a robot PDQ LaserWash with a proprietary protocol, and your portal only supports Modbus, you will need to buy an additional protocol converter (cost from 150 thousand rubles). Always check with the portal manufacturer for a list of supported devices.

FAQ: Frequently asked questions about robot car wash network portals

Is it possible to connect robots from different manufacturers to one portal?

Yes, but for this the portal must support universal protocols like Modbus TCP or OPC UA. In some cases, it will be necessary to install intermediate gateways (for example, KEPServerEX). The cost of integrating robots from different brands can increase by 30–50%.

How much does it cost to deploy a portal for a network of 5 car washes?

One-time costs:

• Server equipment: 200–300 thousand ₽;
• Portal software license: 150–250 thousand rubles;
• Network equipment (routers, switches): 100–150 thousand ₽;
• Setup and testing: 50–100 thousand rubles.

Monthly expenses: from 10 thousand ₽ for hosting and technical support.

How to ensure portal cybersecurity?

Minimum measures:

• Install a firewall (FortiGate or Cisco ASA);
• Set up a VPN for remote access (OpenVPN or WireGuard);
• Update the firmware of all network devices;
• Organize separate networks for robots and client terminals.

A quarterly security audit is recommended (cost from RUB 50,000).

What to do if the portal no longer sees the robot?

Sequence of actions:

1. Check the physical connection of the cables;
2. Reboot the robot via the button on the body;
3. Ping the robot's IP address from the portal server (ping 192.168.1.100);
4. Check the portal logs for connection errors;
5. Update the robot's firmware to the latest version.

If the problem is not resolved, contact the manufacturer's support with error logs.

Can I use a cloud portal instead of a local server?

Yes, but with reservations:

• ✅ Pros: no hardware costs, automatic backup, access from anywhere in the world.
• ❌ Cons: dependence on Internet speed, monthly subscription fee (from 15 thousand ₽/month), risks of data leakage.

Cloud solutions are suitable for small networks (up to 5 sinks). For large networks, a hybrid option is better: local server + cloud backup.