Should a car wash put fleet and corporate accounts on the same loyalty card as regular customers?

No — a fleet account is a billing relationship, not a loyalty customer

A fleet or corporate account (a taxi company, a delivery fleet, a company with 20 pool cars) pays on an invoice or a negotiated monthly rate, not per wash, so a stamp or points card built for a walk-in customer doesn't map onto it cleanly. Loyalty mechanics reward an individual for choosing you again; a fleet contract already locks in repeat business through the agreement itself, not through a reward.

The operational difference is who decides to keep coming back. A regular customer decides every single visit — that's exactly what a stamp card is built to influence. A fleet driver doesn't decide anything; the fleet manager signed a contract, and the driver is just dropping off car #14 because dispatch told them to. Putting a driver through the same QR-and-form enrollment as a walk-in customer wastes their time and clutters your customer list with people who aren't the actual decision-maker.

Keep the two systems separate: run your consumer stamp or points card exactly as you would without any fleet business, and track fleet volume the old way — a shared log, a monthly invoice, a simple count of vehicles washed under the account number. Waya doesn't need to know about the contract at all.

The mechanic recommendation: one light-touch card for the fleet's actual decision-maker

If you still want a wallet presence for a fleet relationship, give one card to the fleet manager or the person who renews the contract, not to every driver who rotates through. A single points or balance card that quietly accrues volume for reporting purposes — "142 vehicles washed this month under account #7" — gives the fleet manager something concrete to see when renewal time comes, without pretending a driver's individual visit choice matters.

Frame the reward, if you offer one, as a relationship perk rather than a per-visit stamp: a free detail on the fleet's 100th wash of the quarter, addressed to the manager, not scattered across a dozen individual driver enrollments that nobody is tracking. That keeps the card count low and avoids burning through your customer cap on people who will never re-enroll a car under their own name.

• One card per fleet account (the manager), not one per driver
• Track fleet volume as a relationship metric, not a per-visit stamp count
• Reserve the reward for renewal-time leverage, not immediate per-wash gratification
• Keep consumer stamp cards untouched and running exactly as for walk-in customers

The named risk: burning your Free-plan customer cap on people who aren't loyalty customers

The real risk is mechanical, not strategic: Free stops adding new customers at 100, and a single fleet with 15 rotating drivers can eat 15 of those 100 slots if every driver scans the same QR poster meant for consumers. On a single-branch wash already running close to the ceiling, that's a meaningful chunk of your remaining room spent on people who will never return under their own enrollment.

Avoid it by not putting a fleet-facing QR poster next to the consumer one, and by briefing whoever runs the till not to ask fleet drivers to scan and enroll individually. If a fleet is large enough to matter, it's large enough to justify a direct conversation with the manager instead of a QR code at the bay.

A worked comparison: 3 branches, one fleet contract

A wash with 3 branches on Growth running one taxi-fleet contract alongside its regular walk-in business is a common setup. The table below shows how the two customer types differ operationally — worth reading before deciding who gets a card and who gets an invoice line.

What to say at the till when a fleet driver asks about the loyalty card

Give the attendant a one-line answer so nobody improvises: "This card is for personal customers — your company account is billed separately, ask your manager about that." That keeps the driver from feeling brushed off while keeping your consumer enrollment list clean.

If the fleet manager does want visibility into volume, reading your dashboard for the manager's single relationship card (if you set one up) is enough — there's no need to build a second reporting system on top of Waya for this.

How this fits the rest of your loyalty setup

None of this changes how you run loyalty for everyone else. Keep the consumer stamp or points card, the win-back trigger, and your geofence exactly as described in the car wash loyalty guide — fleet accounts are a side channel, not a redesign.

One limit to keep in mind either way: Waya has no POS or till integration, so any stamp — consumer or fleet-manager card — is added by a staff member scanning a phone, not pulled automatically from a billing system; there's no SMS channel, only wallet lock-screen messages, and the Android merchant app is still in closed testing, so managers checking the dashboard on Android should use the web version.

Setting up a fleet account without disrupting consumer loyalty

Adding a fleet relationship on the side takes a handful of deliberate steps, mostly about keeping the two audiences from overlapping rather than building anything new.

1. Step 1: agree billing terms outside Waya

   Settle the invoice or negotiated rate with the fleet manager the way you normally would — Waya isn't part of this conversation.

2. Step 2: decide if a relationship card is worth it

   Only set one up if the manager wants visibility into volume; many fleet contracts don't need a card at all.

3. Step 3: issue one card to the manager, not to drivers

   If you do issue a card, enroll the fleet manager directly rather than putting a QR poster where drivers will scan it themselves.

4. Step 4: brief the till on what to say

   Give attendants the one-line script so fleet drivers aren't asked to scan the consumer QR code by mistake.

5. Step 5: keep consumer enrollment untouched

   Run your regular stamp or points card exactly as before — fleet accounts shouldn't change anything about walk-in loyalty.