How to run a birthday reward that costs almost nothing

The whole year costs a few hundred riyals

A birthday reward is the cheapest repeat-visit trigger a small shop can run, and most shops price it wrong. Give away a named service upgrade — a large instead of a medium, an extra shot, a free hot towel — and each claim costs you 2 to 4 SAR of goods. Give away 20% off the bill and each claim costs you real revenue on a purchase the customer was already making.

Here's the shape of it for a shop with 400 enrolled cards. Birthdays spread across the calendar, so you're messaging roughly one twelfth of your list each month. If 60% of your customers filled in the field, that's about 20 messages a month and 240 a year. At 3 SAR of goods per claim and a 35% claim rate, the whole program costs you around 250 SAR across twelve months.

Two things Waya doesn't do here, so you can plan around them. There's no one-click birthday trigger that fires on its own yet: as of 18 August 2026 the automatic triggers are new signup, stamp added, reward redeemed, and 14-day inactive, so the birthday send is a job you run yourself once a month. And Waya doesn't send SMS. The message arrives on the customer's lock screen through the Apple Wallet or Google Wallet pass they already added.

Why a service upgrade beats a percentage off

A percentage off discounts a transaction that was already going to happen. The customer walks in, orders what they always order, and you hand back part of the bill. There's no upgrade in it for them and no margin left in it for you.

An upgrade costs you the ingredient, not the price. A large latte instead of a medium is maybe 60 ml of milk and a little more coffee. On the menu it reads like a 9 SAR gift; on your invoice it's under 2 SAR. Barbers have the cleanest version of this: add the beard trim or the hot towel that lists at 20 SAR and costs you a towel and eight minutes.

Upgrades also don't teach the wrong lesson. A percentage-off birthday trains people to wait for the code and to feel shortchanged the rest of the year. An upgrade is a gift with a name on it: your usual, but bigger, because it's your birthday. Nobody starts expecting that in March.

Pick one item and write it down in plain words. "Any drink up one size." "A free extra scoop." "A free beard trim with any haircut." "Something on the house" is what turns a 3 SAR gift into a 40 SAR one at 11pm on a Thursday when the cashier is guessing.

Collect the day and the month, and stop there

In Waya the birthday field is a toggle in the card's enrollment page settings. Switch it on and the one-screen enrollment form — first name, mobile number — gains one more field. You get three input modes: Gregorian date, Hijri date, or age only.

What the reward actually runs on is the day and the month. The year is dead weight. Waya matches birthdays on month-and-day across all years, so a customer born on 14 March is treated the same whether that was 1988 or 2004. The age-only mode stores just a birth year if you'd rather not hold a date, but you can't run a birthday reward from it, so choose a date mode when the birthday gift is the reason you're asking.

The Hijri mode matters in Saudi Arabia. Plenty of customers know their birthday as a Hijri date and would have to go look up the Gregorian one. Waya converts the Hijri input into a Gregorian date and keeps the original alongside it, so the customer types the date they actually know.

Leave the field optional, and turn it on before you plan the campaign. A required birthday on a QR form at the till costs you enrollments, because the person holding a phone in one hand and a coffee in the other will just walk off. The field only appears on the enrollment form, so cards that enrolled before you switched it on won't carry a date — every month the toggle stays off is a month of blank records.

Send three days early, give a seven-day window

Send the message two or three days before the birthday, not on the day. On the day the person already has a plan: dinner is booked, family is coming, the phone is busy. Two days out you're still in the running to become the plan.

Make the reward valid for seven days with the birthday in the middle. A one-day coupon fails every time the birthday lands on your day off, or on a Friday when the customer is with family, or during Ramadan, when many Saudi cafes and restaurants close through the daytime and trade late into the night. A week costs you nothing extra and removes the most common reason a birthday gift goes unused.

Wallet messages land on the lock screen, and the offer text stays on the back of the pass. That's the practical edge over a WhatsApp blast: three days later the customer doesn't have to hunt for your message, because the card in their wallet still says what they get. Nothing gets buried in a thread.

Write the message like a person would, in one line, with the expiry date in it. "Happy birthday from Kayan Coffee — your next drink is on us, any size, until 22 August. Just show your card." Skip the emoji wall and skip the terms and conditions.

Capping the cost across a full year

Write the worst case down before you launch, then decide whether you can live with it. The ceiling is simple: every customer who gave you a birthday claims once, at your unit cost. 240 dates on file times 3 SAR of goods is 720 SAR, and that is for the entire year across the entire list.

Run the same arithmetic on 20% off a 55 SAR average check and the ceiling becomes 240 times 11 SAR, or 2,640 SAR, coming off revenue rather than out of a goods budget. Same customers, same gesture, close to four times the exposure. That gap is the whole argument for the upgrade.

Three caps do the rest of the work. Name one specific item so the cashier never has to make a judgment call. Require the card scan, so the gift is recorded as a redemption you can count. And because the match is on day-and-month, the reward can only come round once a year per person by definition.

One quiet advantage worth knowing: a birthday send only touches a twelfth of your list at a time, which is why it fits where a broadcast doesn't. A 90-customer shop on the free plan sends about 5 birthday messages a month against a 100-message allowance. A single broadcast to that same list would eat 90 of them.

The five-minute monthly routine

Once the field is on and dates are accumulating, the send is a short monthly job. Open the notifications composer, pick this month's birthdays as your recipients, write the one-liner with the expiry date, and send. There's no birthday trigger to flip on today, so put it in your calendar for the first of the month.

Then brief the till. Stick one line where the cashier can see it: "Birthday = any drink up one size. Scan the card first." The scan is what turns a gift into a row in your dashboard, and without it you'll never know whether the reward moved anything. Staff scan from an ordinary phone, so there's nothing to install at the counter and no POS integration involved.

After three months, compare the birthday group against everyone else on one number: did they come back at all in the 30 days after the message. If they didn't, the timing isn't the problem. The item is too small or the wording is too vague, so change the gift before you change the schedule.

A last honest note on plans. The free tier gives you 100 customers and 100 wallet messages a month, and the automation, geofence, and history sections of the notifications tab sit on paid plans, though the birthday send itself works on the free plan. Growth at 85 SAR a month is where you land after 100 customers, and its 5,000 messages a month make birthday volume a rounding error.