Click here

Fat Hippo App: Third-Party Loyalty Integration

Change Request Reference: CREQ-18072025 | 23-July-2025

Enable loyalty earning for orders placed via third-party platforms (Uber Eats, Just Eat, Deliveroo) and claimed within the Fat Hippo App. This proposed feature will allow customers to earn loyalty stamps by submitting delivery receipt details.

Overview of Proposed Change

Currently, orders placed via third-party delivery platforms are not connected to the 5Loyalty system, meaning customers do not earn loyalty on these transactions. This change request proposes a solution to bridge this gap.

The proposed feature would allow customers to earn loyalty through the Fat Hippo App by manually submitting their delivery receipt details, identifying their order using a transaction reference number from their delivery receipt.

Loyalty Structure & Rules

Loyalty Award

One loyalty stamp will be awarded per delivery order submitted through the new system. To qualify, the receipt must show at least one burger in the order.

Exclusive Process

This process is exclusive to delivery receipts and does not follow standard loyalty earning rules.

Visibility

Once verified, earned loyalty will appear in the customer's loyalty journey/history within the Fat Hippo App and will be visible under Admin Panel > CRM > History.

The proposed system aims to create a seamless experience for customers while maintaining the integrity of the loyalty programme.

User Interface Design

The proposed feature would include a dedicated interface within the Fat Hippo App where customers can submit their third-party delivery receipts. The wireframe illustrates how customers would:

  • Navigate to the loyalty section
  • Select "Claim Third-Party Order"
  • Enter their order reference number
  • Receive confirmation of their loyalty stamp

Wireframe showing the proposed user journey for claiming third-party delivery loyalty.


Error Handling & Messaging

Receipt claimed

"This receipt has been claimed and loyalty earned will be added to your account shortly."

Receipt not recognised

"Please check the receipt details and try again."

Receipt expired

"The date on this receipt has expired."

Invalid receipt

"Please enter a valid order number"

Max claims reached

"You have reached the maximum amount of claims for today. Try again tomorrow!"

Receipt already claimed

"Looks like this receipt has already been claimed."

Receipt invalid

"No qualifying items were found on this receipt"

The proposed system would include comprehensive error handling to guide users and prevent duplicate claims or fraud.

Implementation Timeline

1

Sign-off & Requirements

Client approval and receipt of all required deliverables

2

Development Phase

4-8 weeks of development work

3

QA & Testing

Thorough quality assurance testing

4

App Store Submission

Resubmission for review and re-release

Note: Development will only commence once the change request is formally approved.

Cost Breakdown

This proposed change would be implemented free of charge as part of our continued support and partnership with Fat Hippo, despite the standard development rate of £500 per day + VAT.

Conditions & Sign-off

  • This request includes only the development outlined above and is being delivered at no cost
  • Any additional development outside of this scope will require a separate change request and quote
  • All client deliverables must be provided before development can begin
  • The client must confirm that the change request meets expectations within 14 days of going live