OOHPOD is a parcel delivery and logistics business in Ireland. Its customers send and collect parcels, often only when they need to, and they have plenty of other places to take that business. OOHPOD wanted a way to thank those customers and give them a reason to come back, without asking them to do anything complicated.
LoyaltyPass built OOHPOD Rewards for that job: a customer rewards web app, plus an administration platform for the team running it. Customers use the web app. The team uses the admin platform to run offers, coupons and competitions.
The full record is published by RaftLabs, our parent studio: the OOHPOD Rewards case study.
The problem, in plain terms
Most people do not send parcels every week. They come when they have something to send, they compare prices, and they may not return for months. A business like that cannot rely on habit alone to bring people back.
OOHPOD already had customers. What it did not have was a simple way to reward them. Any program had to reach people who were already customers, not ask the public to sign up from scratch. It also had to avoid two common traps: asking customers to download a new app just to collect an offer, and asking staff to keep a second list of members up to date by hand. A list maintained by hand goes stale quickly, as people join and leave.
So the job was clear. Build rewards on top of the customer list OOHPOD already kept, make offers easy to find and claim, and give the team proper controls to run it.
What we built
The build had two parts: the web app customers see, and the administration platform behind it. It was a 10-week fixed-price build.
In the web app, customers browse current offers and claim coupons. Some coupons are generic, meaning the same offer is open to everyone who is eligible. Others use unique codes held as inventory. That means each code exists once, so a claimed code cannot be claimed twice, and the team can see how many codes are left. Once a customer claims a coupon, they can find it again under "My Rewards" instead of hunting through old messages. Customers can also enter competitions run through the same app.
Who can use it is decided by eligibility, and eligibility syncs from the customer database (the CRM, the system that holds customer records). When a new customer is added there, they become eligible. When a customer leaves, they are removed. Nobody has to update the rewards list separately.
In the administration platform, operators manage customers, categories, rewards, coupon inventory, competitions, banners and notifications. They also get reporting on how many people used the program and what they claimed.
What happened, measured
The first measured window ran from 7 October to 31 December 2024. Over that window, measured in the admin dashboard, the program recorded 67 users, 93 logins, 92 reward views and 37 coupons claimed.
Those four numbers need one honest caveat. A coupon claimed is not a coupon redeemed. The platform records that a customer opened a reward and received a code. Without a partner integration, meaning a direct link into the system where the code is spent, it cannot prove the code was later used. So a claim shows interest and intent. It does not prove a sale.
We report these numbers because they are the numbers we have. 67 users is a small start. This was a small program in its first quarter, not a scale story, and this page will not dress it up as one. Measured small numbers are worth more than big vague ones, because a team can act on them. OOHPOD could see that people logged in, looked at rewards and claimed coupons, and could decide what to offer next from evidence.
What this means for a program like yours
If you run a service business, your customers probably already sit in a customer database. That is the right starting point. Sync eligibility from the database you have instead of building a separate member list that someone has to maintain.
Start simple. Offers and coupons are enough to learn whether your customers will respond at all. Competitions and banners can support that, but the first question is basic: will people log in, look, and claim?
Measure that honestly before you claim anything bigger. Count logins, views and claims in your own reporting, and keep claims separate from sales until you have a way to prove the link between the two. A small, honest first quarter gives you a base you can trust. A large, vague claim gives you nothing to build on.
Talk to the studio
LoyaltyPass is a studio that builds custom loyalty software for mid-size and large organisations. If your customers already sit in a database and you want rewards built on top of it, we can scope that build with you. Book a scoping call. Projects start at $9,500.


