Car Wash Equipment Website vs Field Service and Inventory Software: What Should Own What?

Overview

A car wash equipment company can sell through a website and operate through field-service software.

The two systems should cooperate without becoming duplicate equipment databases.

The public front office should answer:

The operational stack should answer:

• Which operator?
• Which site?
• Which equipment type?
• What does the operator need?
• How urgent?
• Who should respond?
• Which exact equipment asset?
• Which technician?
• Which work order?
• Which part?
• What diagnosis?
• What repair happened?
• What PM is due next?

What the public website should own

Usually:

Current OneStudio features fit this layer.

• service/equipment pages;
• brand pages;
• territory;
• project proof;
• public service/quote request;
• ordinary client/contact history;
• marketing analytics.

What field-service software should own

Usually:

• operator sites;
• equipment assets;
• work orders;
• technician assignment;
• dispatch;
• job status;
• field notes;
• photos;
• service history;
• operational invoice.

What car-wash operations / CMMS software should own

Current car-wash operations products manage combinations of:

That is operational data.

• preventive maintenance;
• equipment maintenance history;
• inspections/checklists;
• chemical levels;
• inventory;
• parts;
• tasks;
• site operations.

Keep client and site separate

One operator may own:

The front-office CRM can own the operator relationship.

The field system should own each site.

• one wash;
• a regional chain;
• dozens of locations.

Keep site and equipment separate

A site may contain:

Each asset can have its own service history.

Do not put all machine history into one free-text client note.

• conveyor;
• brushes;
• pumps;
• arches;
• dryers;
• water reclaim;
• pay stations;
• vacuums.

Keep the public request separate from the work order

Operator:

In-bay automatic intermittently stops during wash cycle.

Accepted field job may later contain:

Keep both.

The request preserves the operator’s observation.

The work order controls what was diagnosed and repaired.

• exact model/serial;
• control fault;
• failed sensor;
• replacement part;
• technician;
• labor;
• test result.

Keep preventive maintenance specialist

WashWerk, WashConsole and WashPro.AI currently treat maintenance/work orders/equipment as core operations.

PM can depend on:

That should live in the specialist system.

• calendar;
• machine hours;
• wash counts;
• site history;
• manufacturer guidance.

Keep parts inventory specialist

A service company may have:

OneStudio should not be positioned as parts inventory.

• central warehouse;
• multiple depots;
• truck stock;
• serialized/compatible parts;
• reorder points.

Keep technician dispatch specialist

Dispatch can depend on:

Do not turn online booking into a technician-routing promise.

• skill;
• geography;
• job priority;
• current workload;
• parts;
• vehicle.

Keep field evidence attached to the work order

Useful service records can include:

Keep them with the job.

• diagnosis;
• photos/video;
• part used;
• labor;
• calibration/tune-up;
• test;
• customer sign-off;
• follow-up.

Keep operator-site status specialist

If a provider or operator wants dashboards for:

use the operations platform that owns those records.

• equipment uptime;
• open work orders;
• PM compliance;
• inventory;
• daily checklists;

Use one explicit handoff

Choose:

Car wash equipment request accepted into field operations

Before handoff:

After handoff:

• website;
• service/quote request;
• ordinary client/contact;
• marketing source.
• site;
• equipment asset;
• work order;
• technician;
• PM;
• parts;
• field service;
• invoice.

Source-of-truth matrix

A 28-point buyer test

1. Website and field systems have explicit roles.
2. Request and work order are separate.
3. Client and site are separate.
4. Site and equipment asset are separate.
5. Customer issue description remains historical.
6. Handoff has one explicit trigger.
7. Site ID has one owner.
8. Equipment ID has one owner.
9. Brand/model/serial truth has one owner.
10. Work order has one owner.
11. Priority has one operational owner.
12. Technician has one owner.
13. Dispatch status has one owner.
14. Diagnosis has one owner.
15. Repair action has one owner.
16. Field photo/video has one owner.
17. Part used has one owner.
18. Inventory has one owner.
19. PM schedule has one owner.
20. PM completion has one owner.
21. Equipment service history has one owner.
22. Site checklist has one owner.
23. Operational invoice has one owner.
24. Public CRM excludes live dispatch data.
25. Public CRM excludes equipment PM truth.
26. Website can survive operations-software changes.
27. Public analytics exclude operator technical records.
28. Staff can explain the boundary in one sentence.

Give the website the service opportunity and the field system the equipment truth

The public layer should make the provider easy to find and contact.

The specialist layer should make every machine, technician, part and maintenance event traceable.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask