Fleet accounts need a separate card, not a tier bolted onto the consumer one
Sometimes — but the right move is usually a separate card for fleet customers, not a tier layered onto the same stamp or points card used by individual drivers. Dammam and Khobar sit at the center of Saudi Arabia's Eastern Province industrial and energy sector, and company vehicle fleets are a real, recurring source of volume that behaves nothing like a walk-in customer.
A fleet contract is usually a negotiated price and a billing relationship, not a per-visit reward relationship — mixing the two on one card design makes both harder to manage cleanly. The full car wash loyalty guide assumes a consumer stamp or points card; a fleet arrangement sits outside that model entirely.
How fleet washes differ operationally
A fleet customer isn't one person building up stamps over months; it's a company with many vehicles washed on a schedule, often invoiced rather than paid per visit at the till. The person swiping through your bay each time may not be the same driver twice.
That means the loyalty mechanic that works well for consumers — a stamp per visit tied to one phone number — doesn't map cleanly onto a fleet relationship where the phone number changes with the driver but the paying account doesn't.
- Fleet washes are often bulk-scheduled, not walk-in, so visit timing looks very different
- The billing relationship (invoice, contract rate) sits separately from any per-visit reward
- Multiple drivers may use the same fleet account, so per-phone tracking breaks down
A separate card keeps the consumer math clean
Run a distinct Waya card — or a distinct branch or program — for fleet accounts, so stamp counts and message triggers for individual retail customers don't get muddled by high-frequency fleet visits that don't behave like normal repeat business.
With multi-branch support up to 3 branches on Growth and unlimited on Premium, a Dammam or Khobar shop running both a retail bay and a fleet-focused schedule can keep the two lines of business on separate tracking without needing separate software.
| Aspect | Consumer loyalty card | Fleet account |
|---|---|---|
| Who's tracked | One driver, one phone number | One company, many vehicles/drivers |
| Reward basis | Stamps or points per visit | Negotiated contract rate |
| Messaging | Welcome, stamp, win-back triggers | Manual or none — usually invoiced separately |
The risk of mixing the two
The named risk here is diluted stamp math: if fleet vehicles get scanned onto the same consumer card as retail customers, a handful of fleet visits can quietly inflate visit counts and skew return-rate numbers on the dashboard, making it harder to see how your actual walk-in customers are behaving.
It also confuses messaging — a win-back trigger firing at a fleet account's generic contact number reads as noise, since the fleet relationship is managed by contract, not by a lock-screen nudge.
Where loyalty still helps a fleet-adjacent shop
None of this means fleet business can't benefit from Waya at all — it just means the benefit is on the retail side of the same location. Many Dammam and Khobar washes serve both company fleets during the day and individual drivers evenings and weekends; the individual side is exactly where a normal stamp card, geofence messages, and the 14-day win-back trigger earn their keep.
Waya has no POS or till integration either way, so a staff member scans each retail customer's card by hand — the fleet side, being invoiced separately, typically doesn't need scanning at all. See how to add staff accounts for setting up who's responsible for the retail scan at each shift.
Setting this up for a mixed fleet-and-retail shop
The setup separates cleanly once you decide which customers are actually loyalty-card customers.
- Decide who's on the loyalty card
Scope the program to walk-in retail customers only, not fleet accounts.
- Handle fleet billing separately
Keep fleet contracts and invoicing outside the loyalty card entirely.
- Set up branches if you run multiple bays
Add each location to the dashboard so retail stamps track correctly per branch.
- Train staff on the distinction
Make sure attendants know not to scan fleet vehicles onto the consumer card.
Frequently asked questions
Should a Dammam or Khobar car wash build a loyalty tier for fleet customers?
Sometimes, but as a separate card or arrangement rather than a tier on the same consumer card. Fleet business runs on contracts and invoicing, not per-visit stamps, and mixing the two distorts your retail numbers.
Why don't fleet vehicles fit a normal stamp card?
A fleet account often has multiple drivers using the same company account, and washes are frequently bulk-scheduled and invoiced rather than paid per visit — the per-phone stamp mechanic that works for individual customers doesn't map onto that pattern.
What's the risk of scanning fleet vehicles onto the retail loyalty card?
It inflates visit counts and skews return-rate numbers on the dashboard, making it harder to see how actual retail customers are behaving, and it can trigger irrelevant automatic messages to a fleet contact.
Can a car wash run both fleet and retail business on Waya?
Yes — track them separately. Run the loyalty card for retail, walk-in customers, and manage fleet contracts and billing outside the card entirely, using separate branches if you run multiple bays.
Does Waya scan fleet vehicles automatically at checkout?
No. Waya has no POS or till integration for either fleet or retail customers — a staff member scans each card by hand, though fleet accounts, being invoiced separately, typically don't need scanning at all.