Car Wash Loyalty Rules for Commercial Customers and Multiple Vehicles

A car wash loyalty programme is a way to encourage a continuing customer relationship. However, people bring vehicles for different reasons. Someone washing their own car a few times a month is not in the same position as a repair business sending ten different vehicles in a day. Applying one rule to both can change the purpose and cost of the reward. Commercial customers, multiple registration plates and individual exceptions therefore need clear rules. The aim is not to penalise customers, but to make eligibility understandable.

This guide explains how to classify commercial relationships, check automatic defaults and grant an exception when appropriate. OtoPatron examples refer to the existing customer and job order workflow. Numerical scenarios are illustrative, not forecasts or promises of increased revenue. Decide your business policy first, then use the customer loyalty settings to support it. A clear policy reduces the need for staff to improvise every time a vehicle arrives.

Separate a loyalty reward from a commercial agreement

A personal loyalty scheme asks a simple question: what reward will a returning customer receive after meeting the stated conditions? A commercial agreement asks a different question: what prices, service scope and payment arrangements apply to a business sending vehicles regularly? Both arrangements can exist for the same customer, but they serve different purposes. If a repair shop already receives an agreed price, decide explicitly whether a free wash is an additional benefit.

You might give a commercial customer an agreed price, a regular account reconciliation or a particular appointment arrangement. These are business decisions; do not assume the software applies each one automatically. Turning loyalty off does not close the customer's account, delete their records or change their payment method. Keeping these decisions separate helps staff avoid moving customers into an unintended accounting category. Use customer account tracking to review services and collections separately.

Start with a short written policy

A one-page operational rule is often more useful than a long promotional document. State which services count, when a reward becomes available, whether commercial customers are excluded by default, who may approve an exception and when a change takes effect. These questions cover many everyday situations. The policy should match what you tell customers: information given at reception must agree with what a colleague says on the phone.

Include a start date. If previously earned rewards require a separate decision, deal with them separately rather than assuming a new default recalculates history. For example, excluding commercial vehicles from new participation today does not automatically cancel last month's qualifying visits. Review existing points and outstanding rewards before explaining the change. Keep dated versions of the policy so staff can understand which conditions applied at the time of a particular transaction.

Customers, plates and phone numbers describe different things

A registration plate helps identify a vehicle record. A phone number supports communication and helps evaluate relationships between records. The customer card organises the service history. One person may have separate cards for different vehicles, while a household or workplace may share a phone. These fields are related, but they are not interchangeable identifiers. A change to one does not necessarily mean that every other part of the relationship has changed.

OtoPatron's multiple-plate eligibility check uses customer connections and appropriately matched phone numbers within the same company to determine the initial preference. It should not be interpreted as an automatic shared points account across different cards. The phone relationship helps evaluate the default; it does not itself pool rewards. Review the relevant customer and job records to understand where points belong. Use customer and vehicle management when checking or correcting these details.

Use the commercial customer marker deliberately

The commercial marker is useful for a repair shop, dealer, fleet contact or another business sending vehicles regularly. It describes the business relationship. Do not rely on vehicle count alone: someone may own two personal cars, while another person brings cars belonging to many different customers. Both situations involve multiple vehicles, but the commercial terms may be very different.

In OtoPatron, marking a customer as commercial gives an off default for automatic loyalty participation. This does not by itself change the customer's account type or payment method. When marking a repair shop as commercial, also record the relevant service arrangement in a short note. That helps colleagues understand the reason for the loyalty decision. If the relationship changes later, review both the marker and the permanent preference rather than allowing an outdated classification to govern new transactions indefinitely.

Why multiple plates can start with loyalty off

An off default creates a checkpoint before high-volume vehicle referrals unintentionally consume a scheme intended for individual returning customers. When different plates are connected to the same phone, a new job can start with loyalty unselected. Staff can read the explanation and apply the business policy before making a promise about rewards. The system provides a consistent starting point instead of silently treating every arrival in the same way.

This is a default, not a ban. If your policy includes an individual customer with two personal vehicles, you can use an explicit open preference. Multiple plates are not conclusive evidence of a commercial relationship: a shared family number or a recent vehicle change may explain them. Confirm the circumstances first, then decide whether an exception is appropriate. Software can organise known information; it cannot establish the full nature of a relationship from a phone number and plate count alone.

Understand automatic, always on and always off

The automatic customer preference allows the commercial and multiple-vehicle rules to determine the starting selection. Always on provides a deliberate permanent exception for a suitable customer. Always off keeps the customer outside new participation even if their vehicle count or commercial marker later changes. Make sure staff use these terms consistently. An always-on preference is broader than selecting loyalty for one visit.

Record the reason and date when granting a permanent preference. Examples might include an agreed household exception or a particular reward condition in a commercial relationship. A customer-level open preference should not be treated as a separate scheme that overrides a company-wide programme closure. Check that the company programme is available first. Periodic reviews also prevent a temporary decision from becoming an unnoticed permanent arrangement.

One-job selection is different from a permanent exception

You may want only one particular wash to contribute to loyalty. Selecting the loyalty option on the new job is a decision for that saved transaction. Do not assume the next job will start the same way. The permanent preference belongs to the customer card, while the job selection determines the participation recorded for that job. Demonstrate both cases in staff training because the practical effects are different.

Imagine a commercial customer receiving a one-off goodwill exception after a difficult handover. Staff obtain approval and record why today's wash is included. On the next visit, the automatic off default still applies; the goodwill decision has not become a new commercial agreement. Conversely, when an ongoing exception has genuinely been agreed, opening a single job's checkbox is not enough. The customer preference must be updated deliberately so future starting selections reflect the arrangement.

Keep phone formats consistent

A phone number may look different because of spaces, a country code or a leading zero. Equivalent formats should not make customer records impossible to review. A consistent entry standard still matters: decide which country code to use, who confirms the contact and what a shared business number represents. Good data should not depend entirely on the software correcting inconsistent input.

One phone linked to several plates does not prove that all the vehicles belong to one individual. A service adviser may provide their own contact for several customers' cars. An off default is a useful checkpoint in that situation, but the actual owners must remain distinguishable. When a phone changes, check that an old number has not been carried into an unrelated relationship. Granting a permanent exception without resolving incorrect contact data can conceal the underlying problem.

A name alone is not enough when the phone is missing

Different people may share the same name. Automatically grouping cards by name and excluding them from a scheme would therefore be unreliable. Review older records with missing contact information individually. Do not make a definite match until the relationship is confirmed. If several cards are known to represent a repair business, consciously applying the commercial marker is clearer than relying on a guess from similar names.

Complete missing details with the customer's knowledge. Do not enter invented shared numbers just to fill a required-looking field; that can create misleading multiple-vehicle relationships later. A blank number is more honest than false data. You can manage the appropriate card through its explicit preference. When a name search returns several similar records, check the plate and service history rather than selecting the first result automatically.

Example: an individual with two personal cars

Suppose a customer has two cars and uses the same personal phone for both. If your policy permits household vehicles to participate, you may decide to make an exception to the automatic off starting point. Confirm the relationship first. Then decide which customer cards need an always-on preference. Opening one card does not mean points from every connected record are combined into a single balance.

Explain the distinction to the customer: participation conditions and the location of existing points are separate matters. Open the relevant plate's card and check its reward status before making a promise. If household members share a phone, note the correct contact person. When one vehicle is sold, its old service history should not be confused with the new owner's details. Review the current relationship before retaining the exception or returning to automatic handling.

Example: a repair shop sending ten vehicles

Imagine a repair business sending ten different vehicles in one day. Because it already receives an agreed commercial price, you may decide not to add a personal loyalty reward automatically. Mark the relevant customer as commercial and use the automatic preference. At each arrival, check that the correct plate and commercial relationship are recorded. The vehicles may belong to the repair shop's clients, so they should not be treated as one physical vehicle.

A specific agreement can still justify a permanent open preference or a one-job exception. Consider the cost of adding a reward alongside the existing price arrangement before making that decision. The ten vehicles are an illustration of volume, not a revenue forecast. Reconcile services and collections separately at the agreed interval. The fleet account reconciliation guide provides a useful control approach without confusing reward eligibility with payment handling.

Customer eligibility and service eligibility are separate

A customer being included does not mean every service qualifies. A standard wash and a lengthy paint-correction or protective-film job have different cost structures. Decide which services count before managing customer exceptions. Otherwise, an eligible individual may expect a high-cost service to produce a reward that was never intended by the business.

OtoPatron allows service loyalty eligibility to be configured separately. Check this setting when adding a service, not just its name and price. When renaming or recreating similar services, confirm that the reward conditions remain correct. Staff should review both the customer selection and the service rules before promising points. Your written policy should also explain the service included in a reward. For jobs containing several services, the total price alone does not establish their loyalty treatment.

Evaluate reward cost with an illustrative calculation

The selling price of a free service is not the same as its additional cost to the business. Consumables, staff time, bay occupancy and the effect of turning away another booking are different factors. In a hypothetical worksheet, consumables might be eighty units and additional labour forty units, producing a direct total of one hundred and twenty units. These are teaching values, not market prices or a recommended selling price.

A reward delivered in a quiet period may have a different opportunity cost from one delivered on a fully booked Saturday. However, do not impose unexplained conditions that change during the day. Communicate any restrictions in advance. Review customer visit patterns, service scope and record quality as well as the number of rewards redeemed. A change in visits cannot automatically be attributed to the scheme; seasonality, price changes and the customer mix may also contribute.

Preserve historical points and job records

The new automatic default primarily affects how a new job starts. Switching commercial or multiple-plate customers to an off default does not automatically delete previous jobs or earned points. Staff should not tell customers that their history has disappeared just because the new starting selection changed. Review the current card and job history, then explain the treatment of the new transaction.

If historical points appear incorrect, treat that as a separate correction. Identify the affected transaction and reason before making broad deletions or arbitrary adjustments. Recording the date, plate, service and approval helps later review. An old member can show an automatic off status while historical points remain visible; these describe different periods and different decisions. Explain that distinction clearly rather than presenting it as a contradiction.

A reception check staff can follow

At vehicle intake, confirm the plate, choose the correct existing card and check the contact details. Read the commercial marker, the starting loyalty status and any relevant note. If an automatic exclusion reason appears, apply the policy instead of opening the checkbox by habit. The purpose of automation is to reach the appropriate rule quickly, not to remove every human judgement.

Before saving, check the services and the final loyalty selection again. If a plate or phone changed during entry, ensure that a previous customer's choice has not been carried into the wrong record. Training should include an excluded commercial customer and an approved individual with several vehicles. If staff can explain when to use a one-job exception and when to request a permanent preference, they understand the central distinction.

Assign responsibility for exceptions

Not every employee needs the same authority to change campaign rules. Decide who may alter a permanent customer preference and who may make a decision on an individual job. This should agree with the access available in the application. An always-on preference affects future jobs, so it carries more responsibility than a single transaction choice.

When considering an exception, review the customer's request, the existing agreement and earlier practice. Prepare a few short scenarios to prevent colleagues from offering inconsistent promises. Staff who want to resolve a sensitive situation should know which authorised person to contact. Review user access control alongside your operating routine. Clear responsibility supports traceable decisions without making customer service unnecessarily complicated.

Explain the policy in customer language

You do not need to describe technical matching rules to a customer. Explain that agreed commercial services are handled separately from the personal reward scheme and that specific conditions can be confirmed by an authorised person. For an individual with several cars, show which cards participate and where the current points are recorded. Do not imply a shared points pool unless such an arrangement actually exists and is supported by your process.

Keep the conversation calm and consistent. Check the record before staff debate the rule in front of the customer. If earlier information was different, review it and work towards a clear resolution; do not immediately blame the software or dismiss the customer's recollection. An authorised person can evaluate any correction. State how long the decision applies, especially where a one-off exception must not create an expectation for every future visit.

Review records and interpret results carefully

In a short weekly review, check newly marked commercial cards, permanent open exceptions and missing phone details. The purpose is operational accuracy, not unnecessary circulation of customer information. When many plates share a number, establish why. Correctly identifying a known repair-business relationship reduces repeated discussions at every vehicle arrival.

An increase or decrease in reward use alone does not establish success or failure. Services, customer groups, seasonality and older earned rewards can all affect the result. Review business reports alongside customer histories. Five rewards used one week are not automatically better or worse than two used the next week. Judge the programme against its intended purpose and the accuracy of the underlying records.

A practical launch checklist

Check the company programme and eligible services first. Identify commercial customers, verify phone details and decide whether known individual owners with several vehicles need an exception. Confirm that staff can distinguish permanent customer preferences from a one-job selection. Review existing points separately rather than assuming the new defaults change the past.

During the first week, review a few ordinary transactions with an authorised colleague. Confirm that the explanation given to the customer, the card preference and the saved job all reflect the same decision. Revisit the rule when commercial agreements change, not only after a complaint. Used with a clear policy, OtoPatron's car wash management software supports an understandable service process. A useful scheme is one staff can apply correctly and customers can understand.

Run a short desk exercise before the first day

Create a small set of fictional examples for staff training instead of sharing real customer details unnecessarily. The first card represents an individual with one car. The second is a repair business marked commercial. The third is a household using one phone for two plates. The fourth has no phone. Ask each colleague to explain where the automatic rule applies and where an authorised exception is needed.

Choosing the right checkbox is not enough; staff should explain why. Two cards with the same name and no phone should not be assumed to belong together. An always-on preference for a household does not automatically merge points. A commercial marker does not change the payment method. Finish with a short task card: find the record, confirm the relationship, check the starting selection, ask when needed and explain the decision.

Check the circumstances when a new plate appears

When a customer first brings another vehicle, ask what changed before replacing an old plate on a card. They may have bought a new car, sold the previous one or be bringing someone else's vehicle. These situations can require different loyalty decisions. A short note prevents the next employee from having to infer the whole relationship from the phone number alone.

A new plate can reveal a multiple-vehicle situation during job entry. An off default at that point does not mean earlier points were deleted. If the customer asks about applying an old reward to a new vehicle, consult the policy first. Do not promise an automatic transfer. A transfer or correction decision requires review of the existing records and the appropriate approval. Resolve unclear conditions before saving and avoid presenting a surprise restriction after the service.

Distinguish closing the programme from excluding one customer

Turning off the company programme is a company-wide operational decision affecting new participation. Excluding one customer is a customer-level choice. Closing the entire scheme because of a problem with one commercial relationship can create unintended changes for everyone else. Establish the level of the problem first: service eligibility, customer preference and company availability are separate checks.

Likewise, do not delete a customer card merely to exclude it from loyalty. Its service history, contact details and account relationship may still be needed. Changing the loyalty preference is a narrower decision. When reviewing requests from staff, explain exactly which level is being changed. Recheck older exceptions at the start of a new campaign and deliberately approve any arrangement that should carry forward.

Two final operational questions

What happens when a commercial customer has an always-on preference? While the company programme is available, this represents a deliberate exception. The commercial marker explains the automatic starting rule; it is not a permanent prohibition. Record the reason and scope of the open preference.

Must every plate sharing a phone have the same decision? No. The automatic check supports review of the relationship, while an explicit customer preference can provide an exception. Check the relevant card when entering the job. In particular, do not assume an exception on one card automatically extends to a newly created card for another plate. Understanding these details helps staff keep both the customer explanation and day-to-day handling consistent.