Warm, controlled water
Comfortable washing with final temperature limits verified against the selected equipment.
The station
One useful product.
Two connected systems.
A well-designed physical wash for dog owners, supported by an operating layer that helps us run every location consistently.
Get pilot updatesAt the siteWash · Rinse · DryCustomer experience
↕Across the networkMonitor · Respond · LearnDog Wash Stop OS
Pilot procurement brief
What we intend every station to have.
These are selection requirements, not claims about equipment already purchased. The final specification will follow supplier due diligence, site survey and dog-welfare review.
Measured dog products
Integrated dispensing intended to make dosing simple and consistent.
Wash and rinse control
A handheld system with clear modes, visible time remaining and an immediate stop control.
Adjustable drying
Owner-controlled drying designed to remove much of the water without promising a fully dry coat.
Secure footing
Non-slip surfaces plus restraint and access features appropriate to the final machine design.
Owner comfort
A raised working height intended to reduce lifting, kneeling and bending.
Contactless payment
A simple card and digital-wallet journey, subject to payment-terminal selection.
Reset for the next dog
A clear end-of-cycle clean-down process, supported by planned operator checks.
Dog Wash Stop OS
The operating system is more than software.
It is the combination of machine data, service rules and people that turns unattended equipment into a managed network. Initially, the “OS” will be a disciplined operating model using supplier tools. We should only build proprietary software where it removes a repeated constraint or creates defensible network value.
Customer layer
Simple on-station guidance, price and time visibility, pause or stop controls, help and fault reporting.
Machine layer
The supplier controller manages water, product dosing, timing and safe operating limits. We do not plan to rewrite proven machine firmware for the pilot.
Network layer
Remote status, payments, session counts, error codes and consumable signals brought into one operational view where integrations permit.
Operations layer
Alerts become real work: triage, cleaning visits, refill routes, maintenance tickets, response targets and an auditable service history.
Build in stages
Prove it before we platform it.
Use proven supplier systems
Validate payment reliability, uptime, error visibility, data export and the daily service routine at one location.
Buy nowCreate one operational view
Normalise data across compatible hardware and connect alerts, support cases, refills and maintenance activity.
Build when repeatedOptimise with real data
Predict faults, plan service routes, understand demand and test customer products or pricing responsibly.
Differentiate laterSupplier decision gates
Data access is part of the machine specification.
- 01Can we access live status and meaningful error codes?
- 02Can we export session, payment and uptime data?
- 03Who owns the data, and can it be used across our network?
- 04Is there a documented integration route or API?
- 05Can branding and the customer interface belong to us?
- 06What still works safely if connectivity is lost?