Car Wash Forecourt Controller Integration: Setup, Protocols, and Configuration
Car wash services can add $40,000 to $100,000 in annual revenue per fuel site, yet the controller link between the wash and the forecourt is still the least documented part of the stack.
That gap matters because standards documents are not written for operators on a forecourt at 6 a.m. This guide explains the ecosystem, the code workflow, serial vs Ethernet protocols, bundled promotions, and the setup problems that usually surface first. See What Is a Forecourt Controller for broader context.
Table of Contents
- TLDR
- What Are the Components of a Car Wash Integration at a Fuel Site?
- How Do Car Wash Codes Work at a Fuel Site?
- What Is the FDC Specification for Car Wash Integration?
- How Does Serial vs Ethernet Car Wash Integration Compare?
- How Do Fuel and Car Wash Bundled Promotions Work?
- What Are the Most Common Car Wash Integration Challenges?
- Frequently Asked Questions About Car Wash Forecourt Controller Integration
- Conclusion
TL;DR
- Car wash forecourt controller integration can add $40,000 to $100,000 in annual revenue per site, but the controller layer decides how much of that is easy to capture.
- Four connected systems make up the setup: the car wash controller, forecourt controller, POS, and outdoor card reader.
- The code workflow has five steps: purchase, generation, delivery, redemption, reconciliation.
- Conexxus defines the messaging standards for forecourt control and wash code generation.
- Serial handles basic control; Ethernet adds real-time status, queue management, diagnostics, and automated promotions.
- Bundled fuel and car wash offers can lift attach rates by 15% to 25%.
- Allied supports 52,000+ interface devices worldwide and stocks 57,455+ parts.
What Are the Components of a Car Wash Integration at a Fuel Site?
A car wash integration at a fuel site involves four connected systems: the car wash controller, the forecourt controller, the POS, and the outdoor card reader.
The car wash controller runs the wash equipment, including the conveyor, chemical dispensers, dryers, and bay doors. It receives commands and reports status back to the site. Allied lists car wash controller parts for operators that need spares or replacement components.
The forecourt controller sits in the middle. It manages dispensers, card readers, tank gauges, car wash controllers, and price signs, then routes data between those devices and the POS. Allied's NeXGen PRIME and AEGIS both list car wash controllers among the device types they manage.
The POS handles transactions and payment processing. In most configurations, it does not talk directly to the car wash controller. The outdoor card reader is where the customer usually sees the wash offer after fueling.
Understanding the ecosystem raises the next operational question: how does a customer actually buy and redeem a wash at the site?
How Do Car Wash Codes Work at a Fuel Site?
A car wash code is a unique alphanumeric string tied to a purchased wash package, then validated at the terminal before the wash cycle starts.
Conexxus Car Wash Specification v1.0, published in September 2021, standardized the API for generating these codes and exchanging transaction details between systems. For the standards themselves, see the Conexxus Car Wash Working Group and the FDC Specification.
- Purchase at the pump. The customer buys a wash through the outdoor card reader after fuel authorization.
- Purchase at the POS register. A cashier rings up the wash as part of the sale.
- Purchase at a standalone kiosk. The customer selects a wash without using the fuel lane.
After purchase, the system generates a code tied to a specific wash level, such as basic, deluxe, or premium. The forecourt controller or the POS creates that code, depending on the configuration.
The code then reaches the customer in one of three ways. It can print on the fuel receipt. It can display on the card reader screen. Or it can appear on a standalone receipt from the kiosk or cashier.
At redemption, the customer enters the code on the keypad or scans the barcode. The car wash controller validates the code against the issuing system, checks that it has not already been used, and activates the selected wash cycle. The site then logs the fuel sale and the car wash sale together. Codes can expire after 24 hours, 7 days, or 30 days.
What Is the FDC Specification for Car Wash Integration?
The Conexxus Forecourt Device Controller specification defines standardized XML messaging between the forecourt controller and the POS, including car wash device control and code generation.
In practical terms, FDC gives the site a common language. It covers dispensers, tank gauges, price signs, and car wash controllers as supported device types, so car wash stays inside the core forecourt model.
That matters because interoperability stops being a custom project. A car wash system that supports Conexxus messaging can integrate with an FDC-compliant forecourt controller without a one-off translation layer. The Car Wash Working Group published the wash spec in September 2021, and the FDC Specification defines the broader XML structure.
How Does Serial vs Ethernet Car Wash Integration Compare?
Serial integration provides basic control and validation, while Ethernet integration adds real-time visibility, queue handling, diagnostics, and automated promotional workflows.
Legacy car wash controllers often connect to the forecourt controller over RS-232 serial bus. That setup can start and stop washes, validate codes, and select the wash cycle. Status reporting is limited.
Modern controllers connect over Ethernet using REST API or XML messaging aligned with the FDC specification. That opens up more operational data and more automation. The main gains are:
- Real-time wash status
- Queue management
- Remote diagnostics
- Automated fuel and car wash promotions
The difference shows up fast at busy sites. Serial can cover the transaction. Ethernet can manage the transaction and the operational layer around it.
How Do Fuel and Car Wash Bundled Promotions Work?
Bundled promotions offer discounted washes when a customer buys qualifying fuel, and the forecourt controller generates the discount code automatically.
The operator sets a rule in the forecourt controller or POS. A simple example: buy 8 or more gallons and get $2 off a Premium wash. The controller watches the fuel sale in real time and checks whether the threshold has been met.
If the purchase qualifies, the outdoor card reader displays the wash offer. If the customer accepts, the controller issues the discounted wash code without cashier intervention.
Payment flow can vary by site. Some operators want the promotion attached to a fuel receipt. Others want it triggered from the POS. Others still use a kiosk for wash-only purchases. NACS publishes the Convenience Industry Factbook at convenience.org.
Industry data from petroleum retail trade publications commonly places attach-rate lift from bundled promotions at 15% to 25% versus standalone pricing.
Operators can also set time-of-day discounts, loyalty-tier pricing, and seasonal campaigns. Off-peak offers can fill slow periods. Loyalty pricing can reward repeat customers. Seasonal campaigns can push traffic during weather-driven demand swings.
What Are the Most Common Car Wash Integration Challenges?
The biggest problems are protocol mismatches, code generation failures during outages, reconciliation gaps, and wash package mapping errors.
Different vendors do not always speak the same language. A car wash controller and a forecourt controller may both work, but not together, if their protocols do not match. Choosing a controller that supports both serial and Ethernet reduces that risk. Allied's open POS approach also helps; any POS vendor can request the software specification document to interface with NeXGen PRIME or AEGIS.
If the network connection between the forecourt controller and the car wash controller drops, the site cannot generate or validate codes. The fallback is manual code issuance from the POS register.
Reconciliation issues usually show up when fuel and wash transactions use different timestamps, transaction IDs, or settlement cycles. The fix is a unified report from the forecourt controller that logs both transaction types together. Wash package mapping is another common mismatch; the POS may list different wash levels than the car wash controller supports, and mismatched package IDs cause the wrong wash to activate. Configuration alignment during installation prevents this.
For sites that need help planning the car wash forecourt controller integration path, contact Allied for support.
Frequently Asked Questions About Car Wash Forecourt Controller Integration
Operators and dealers frequently ask these questions when planning or troubleshooting car wash integration at fuel sites.
Conclusion
Car wash forecourt controller integration works best when the controller layer is treated as part of the revenue model, not just a wiring project.
- The four-device ecosystem is the foundation of the setup.
- The code workflow is the operational core.
- Serial and Ethernet determine how much automation the site can support.
- Bundled promotions are the highest-value commercial outcome for many operators.
NeXGen PRIME and AEGIS both support car wash controller integration through serial and Ethernet connectivity. Allied also stocks car wash controller parts through a parts superstore with 57,455+ SKUs, backed by 52,000+ interface devices deployed worldwide.
Ready to Add Car Wash Revenue to Your Forecourt?
Allied's NeXGen PRIME and AEGIS support both serial and Ethernet car wash controller integration. Talk to a specialist about protocol compatibility, bundled promotion setup, and parts availability for your site.
Talk to a Specialist →