You need four fields, not a CRM
A shop serving 300 customers a month doesn't need a CRM. It needs four fields per customer: first name, mobile number, the date they enrolled, and the date they last walked in. Every report worth reading comes out of those four. A wallet loyalty card collects all of them without your cashier typing a word.
The notebook and the WhatsApp group aren't failing because they're low-tech. They fail on one specific question: who hasn't been in for 30 days? Answering that from a notebook means a human reading every line. Answering it from a WhatsApp group isn't possible at all.
There's a second problem with the group. Every member can see every other member's number, and everyone gets the same message. A loyalty program only pays off when you can talk to 40 quiet regulars without bothering the 260 who came in yesterday.
Waya's enrollment form asks for a first name and a mobile number. One screen. The customer scans the QR code by the till, types two things, and taps to add the pass to Apple Wallet or Google Wallet. No app, no password, no account, and about ten seconds of counter time. Anything that isn't an iPhone or Android phone gets a web card instead.
What the wallet pass records by itself
Once the pass is in the wallet, the pass is the record. Your cashier scans it on an ordinary phone, from the web dashboard or the Waya merchant iOS app. That scan writes a timestamped row: which branch, which staff account, stamps added or a reward redeemed. Nobody retypes a name and nobody hunts for the right page in a notebook.
That's the whole data model. Enrollments plus scans. From those two things the dashboard derives visit counts, redemptions, the split between new and returning customers, and which regulars have gone quiet. One card can run across several branches, and every scan lands in the same dashboard.
Here's what it doesn't capture, because that matters more than the feature list. There's no POS integration and no hardware, so Waya never sees the basket. It doesn't know the customer bought a flat white and a croissant, or what they spent, unless staff enter an amount on a points or balance card. It sends no SMS. Item-level sales history is your till's job.
The card design is yours: colors, logo, stamp count, reward wording, Arabic or English. The data shape is fixed, and that's deliberate. There's one small set of numbers to learn and no schema to design, which is exactly what a shop without a data team should want.
The three numbers worth reading every week
Number one: new customers in the last seven days. This measures one thing, and it isn't the software. It measures whether your staff is still asking people to scan. If you serve roughly 300 customers a month and 4 enrolled this week, nobody is asking, and no setting will fix that.
Number two: returning customers. The dashboard splits new from returning, and returning is the only figure that tells you the card is changing behavior. Watch the count, not the percentage, for the first two months. Small denominators make percentages swing for no real reason.
Number three: regulars who've gone quiet. These are customers who used to come in and haven't for 30 days. That list is where your messages belong, and you can send win-back messages from the same screen. Messages arrive on the phone's lock screen through the wallet, not by SMS, so no customer number is handed to a messaging app. On the free plan you get 100 messages a month, so 40 quiet regulars is a far better use of them than a blast to everybody.
The fourth number, and the arithmetic behind it
Check redemptions monthly rather than weekly, because redemptions are your reward cost. If six stamps earn a drink that costs you 8 SAR to make, every redemption is 8 SAR out the door. Thirty redemptions in a month is 240 SAR of product. That's the line to weigh against the 85 SAR a month for the Growth plan, not your enrollment count.
Here's a worked example with the assumptions in the open. Say 300 customers a month, 40 of them enroll in the first month, and 18 of those 40 come back at least once more. Those 18 extra visits at an average 25 SAR ticket are 450 SAR. Six of them redeem a reward costing you 8 SAR, so 48 SAR goes back out.
Those inputs are invented to show the arithmetic, not a forecast, and not something Waya can promise. Swap in your own ticket size, your own reward cost, and your own enrollment rate after four weeks of real data. If the answer is thin, the fix is usually the reward threshold, not the platform.
A ten-minute Monday routine
Pick one morning and keep it. Open the dashboard, read the three numbers, and write them in the same notebook you were using before. Four weeks of three numbers on one page beats a dashboard you never open.
Then take one action, not three. If new customers dropped, the conversation is with your staff, not with the settings. If returning is flat after six weeks, your reward is probably too far away, so revisit the stamp count. If the quiet list is growing, send one message to that list and nothing else that week.
Resist the urge to add fields. Birthdays, email addresses, favorite orders: they all sound useful and they all cost counter time. A two-field form gets filled while the customer waits for change. A six-field form gets abandoned.
When you actually do need a CRM
Some businesses genuinely need more. If you sell high-ticket items with a sales cycle measured in weeks, run an online store with carts and shipping, or send long email sequences, a wallet pass isn't your system of record. Waya doesn't do email marketing, doesn't integrate with a POS, and doesn't send SMS. Read the privacy page if you want the specifics on what's stored.
If you already keep a list in a spreadsheet, Excel and CSV import is included on the paid plans. Note the order of operations: the wallet card is created when the customer scans your QR code and taps to add the pass. An import consolidates history; the QR is still what turns a phone number into a live card.
Price the alternatives before you commit. As of August 2026, Niqati, the best-known loyalty name in Saudi Arabia and the leader by search share, prices by quote. Btaqa publishes tiers at 108, 250, and 380 SAR a month. OneCup is around 150 SAR a month, and Watily is 149 SAR a month with loyalty bundled into a wider plan. Check each vendor's own page before deciding, because published prices move, and most of these products ship real wallet passes too.
The structural difference is where you start. Every one of them begins with a paid subscription. Waya starts at 0 SAR and stays there up to 100 customers and 100 messages a month, with no credit card. Both limits are hard stops rather than surprise charges: at 100 customers enrollment pauses, and everyone already enrolled keeps their card and keeps collecting. There are 100+ shops across Saudi Arabia on the platform, 5,000+ cards living in wallets, and a 4.9/5 average rated by 90 merchants. If a notebook is your current CRM, start on the free plan and see what four fields can tell you.
Frequently asked questions
Do I need a CRM to run a loyalty program?
No. A shop-level loyalty program runs on four data points per customer: first name, mobile number, enrollment date, and last visit date. A wallet loyalty card records all four on its own, so the pass becomes the customer record. CRMs start earning their keep when you have sales pipelines, email sequences, or item-level purchase history to manage.
What customer data does a wallet loyalty card collect?
With Waya, enrollment collects a first name and a mobile number, and everything after that comes from staff scans. Each scan records the time, the branch, the staff account, and whether stamps were added or a reward was redeemed. Because there's no POS integration, the card never sees basket contents or the amount spent, unless staff enter an amount on a points or balance card.
Can I import my existing customer list from Excel?
Yes, Excel and CSV import is included on the paid plans, Growth at 85 SAR a month and Premium at 149 SAR a month. The wallet card itself is still created when the customer scans your QR code and taps to add the pass. So the import gets your history into one place while the QR code does the work of turning contacts into live cards.
What happens after 100 customers on the free plan?
Enrollment stops at 100 customers, and everyone already enrolled keeps their card and keeps collecting stamps. The free plan also caps wallet messages at 100 per month, and both are hard stops rather than overage charges. Growth at 85 SAR a month removes the customer cap and raises the limit to 5,000 messages a month.
Does a loyalty card work without a POS or cash register integration?
Yes. Waya has no POS integration and no hardware; staff scan the customer's card on an ordinary phone using the web dashboard or the Waya merchant iOS app. It sits beside whatever till or payment terminal you already have. The trade-off is real: loyalty data and sales data stay in two separate systems, so you can't match a stamp to a specific receipt.