Short answer
RaftLabs built OOHPOD Rewards in a 10-week fixed-price engagement. The CRM-connected rewards software reflected customer eligibility and gave customers a web app for browsing rewards, claiming coupons, and competitions, while administrators managed users, campaigns, coupons, banners, and reporting. From 7 October to 31 December 2024, the dashboard recorded 67 total users, 93 logins, 92 reward views, and 37 coupons claimed.
Engagement
The OOHPOD Rewards engagement
- End brand
- OOHPOD
- Sector
- Parcel delivery and logistics
- Initial timeline
- 10 weeks
- Engagement
- Fixed-price initial build
- Team
- Frontend, backend, PM, and QA
- Platform
- Responsive customer web app and administration platform
- Market
- Ireland
- Service
- Loyalty program development
The situation
OOHPOD already held the customer relationship in its CRM. It did not have a rewards product that followed that relationship. A new customer had to appear in rewards without a second register, and a departing customer had to lose access without an operator editing a separate list.
Customers needed one place to browse offers, claim a coupon, keep that coupon, and enter a competition. Operators needed a separate surface for customers, categories, rewards, coupon inventory, competitions, banners, notifications, and reporting.
The initial fixed-price build took 10 weeks. From 7 October to 31 December 2024, the administration dashboard recorded 67 users, 93 logins, 92 reward views, and 37 coupons claimed. Those figures are platform activity, not partner sales.
The industry's own warnings apply. Any program with real value attracts abuse within weeks of launch: the same phone claiming a new-member bonus five times, duplicate accounts looping through sign-up incentives. And the silent killer of rewards programs is visible friction at redemption. Customers who struggle to claim a reward remember the struggle, not the reward. OOHPOD Rewards was built with eligibility derived from the CRM customer record and coupon inventory the operator controls
What makes a customer-only rewards program fail
Two lists of who is a customer
The support problem starts when eligibility lives in two places. An OOHPOD account can change in the CRM while the rewards platform still treats the person as active, or a new customer can wait on a manual import before a promised benefit appears.
Eligibility on this build is an integration, not an admin preference. When the CRM identifies a new OOHPOD customer, the rewards platform adds that customer. When the customer leaves, access is removed.
A coupon claim is not a redemption
The platform can record that a customer opened a reward and received a code. It cannot, without a partner integration, prove that the code was later used on the partner's website or in a store.
That limit changes the report an operator can show, and the promise a buyer should make inside the company. The dated dashboard counts coupon claims. It does not count attributable partner sales.
One campaign flow cannot hold every coupon rule
A generic coupon can expose the same value to many customers. A unique-coupon campaign needs an inventory of individual codes. Some rewards allow one claim per customer. Others allow repeat claims.
The administration model separates coupon type from claim frequency. Operators load unique codes or set a generic code, set dates, and publish or return a reward to draft. The platform applies the claim rule. A new partner campaign does not need a new customer flow.
The call
Partner redemption stayed out of the first release
The first release records a claim inside OOHPOD Rewards. It does not record a sale on a partner site or in a store.
Adding that second event would have required a data contract the 10-week scope did not have: shared identifiers, status updates, reconciliation, and consent. Shipping it anyway would have let a dashboard number stand in for a redemption the platform never saw.
This story fits a service business whose CRM already knows the customer, and whose offers do not share one coupon rule. It is the wrong reference when a configured loyalty product already matches eligibility, coupon inventory, and the report the operator has to defend. A comparable loyalty program development engagement should be scoped around that boundary before any build starts.
System flow
How CRM eligibility becomes a controlled rewards experience
Customer status, the rewards experience, and measurable platform activity stay separate.
Source
Customer CRM
The CRM remains the authority on whether a person is an active OOHPOD customer.
Sync
Eligibility integration
Customer additions and removals are reflected in rewards-platform access.
Experience
OOHPOD Rewards
Eligible customers browse offers, claim coupons, revisit claimed rewards, and enter competitions.
Operations
Admin and reporting
Operators manage campaigns and see registrations, logins, reward views, coupon claims, and competition activity.
What shipped
The operating loop, made visible
One loop: eligibility comes from the customer relationship, the customer acts on a reward, and the operator runs the campaign without bypassing those rules.
01
Customers browse, claim, and retrieve rewards in one place
Eligibility still follows the CRM, not an operator's list. Once inside, a customer can browse by category, claim an offer, and return to the issued coupon under My Rewards instead of recovering it from email or support.
OOHPOD RewardsDiscoverMy rewardsCompetitionsAMMember rewards
A little extra, just for you.
Search rewardsNewCoffee on us
Food & drink
Weekend cinema
Experiences
Family day out
Local offers
View couponYour claimed reward is ready
Saved under My rewards
Reconstruction. Not a product screenshot. Shows the customer reward flow described in the project record. 02
Operators control campaign rules without a new release
An operator can keep a reward in draft, set its dates, choose a generic code or unique inventory, preview the customer view, and publish it. The product applies the claim rule while the operator owns campaign content and timing.
Rewards adminOverviewOCampaignsCCouponsCCustomersCDraftCampaigns / Edit
Weekend cinema offer
Campaign name
Weekend cinema offerStarts
08 OctEnds
31 DecUnique codes
One code per claim
Generic code
Shared code
Coupon inventory84 availableCustomer preview
Weekend cinema
A new customer reward available for a limited time.
Ready to publishReconstruction. Not a product screenshot. Shows the campaign controls described in the project record. 03
Reports stop at the event the platform can prove
The administration view can count users, logins, reward views, coupon claims, and competition activity. It cannot turn a claim inside OOHPOD Rewards into a partner sale the platform never observed.
Activity report07 Oct — 31 Dec 2024Total users
67
Logins
93
Reward views
92
Coupons claimed
37
Reward activity
Views and coupon claims by week
Views ClaimsOctNovDecReconstruction. The four figures come from the 7 October to 31 December 2024 administration dashboard.
Also included
The full campaign loop lives in one product.
Proof
What the first dated dashboard window recorded
All four figures were measured, not projected. They cover 7 October to 31 December 2024 in the OOHPOD Rewards administration dashboard.
| Result | What changed | Period or context | Evidence and limitation |
|---|---|---|---|
| 67 total users | The dashboard recorded 67 users during the selected window. | 7 October to 31 December 2024 | Measured in the administration dashboard. |
| 93 logins | The platform recorded 93 login events during the selected window. | 7 October to 31 December 2024 | Measured in the administration dashboard. |
| 92 reward views | Customers opened reward details 92 times during the selected window. | 7 October to 31 December 2024 | Measured in the administration dashboard. |
| 37 coupons claimed | Customers claimed 37 coupons inside OOHPOD Rewards during the selected window. | 7 October to 31 December 2024 | Measured in the administration dashboard. Claimed means the coupon was issued inside OOHPOD Rewards, not redeemed with a partner. |
What changed
What was true before the release, and what the release made observable
- OOHPOD held customers in its core systems and had no dedicated rewards experience for them
- Customers had no single place to browse offers or retrieve a coupon they had already claimed
- Publishing a reward or a competition required a development change
- A new OOHPOD customer is added to rewards from the CRM, and a departing customer loses access
- Eligible customers browse rewards, claim coupons, review claimed offers, and enter competitions
- Operators publish rewards and competitions, including unique and generic coupon inventory, without a new customer flow for each campaign
- The dashboard reports users, logins, reward views, and coupon claims. It does not report partner redemption
Common questions
Name the customer system of record, the events that add or remove access, and what happens when those events are delayed or fail. Also name coupon type, claim limits, inventory exhaustion, expiry, which campaign edits an operator may make without engineering, and which events the dashboard is allowed to count. Partner redemption is a separate contract if you need it.
The 10 weeks covered the customer web app, the administration platform, campaign controls, and CRM-connected eligibility described here. Partner redemption, and any feature after the initial release, sat outside that timeline. A similar window depends on identity, CRM readiness, reward rules, partner data, and how fast those decisions get approved.
This page does not state a price. The loyalty software cost guide is the place to read how scope changes the number before a fixed price is set.
Related work
Related rewards platform work
Energia Rewards platform migration
A 10-12 week rebuild that migrated roughly 500,000 registered users and cut support tickets by 80% (client-reported).
Musgrave receipt campaign platform
A receipt-submission platform that recorded 1,610 submissions across four SuperValu and Centra competition periods.
Bella Skin Institute loyalty app
A custom mobile loyalty program with QR-based point earning, expiring rewards, and an operator-owned admin experience.