Contact person: Custom Event/Loyalty Passes for Android and Apple Wallet

Phone:Show

Email:Show

Location: Nerang, Australia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Background / Current Scenario

We are currently operating a store loyalty program integrated with our Point of Sale
(POS) system.
1. Customers are issued a physical loyalty card with a barcode linked to the POS system.

2. Customers can visit a specific link (Eg. [login to view URL]) and either:

- Scan the barcode on their physical loyalty card, or
- Manually enter the barcode number.

3. Once entered, the website generates a digital wallet pass (Apple Wallet or Google
Wallet) containing the same barcode.

4. When customers return to the store, the cashier can scan the barcode from the digital
wallet pass instead of the physical card to retrieve their record in the POS system.

5. The system is currently live and functioning on both Apple and Android devices.

Note that no mobile app download from Google or Apple Stores is involved for the user's phone needed to create the passes

Objectives
• Migrate to a new Apple Developer account while maintaining the functionality of existing
passes.
• Build an Admin UI that allows real-time styling and multi-pass management.
• Introduce role-based logins and data management for scalability (multiple
businesses).
• Enhance customer registration by collecting email and phone number at pass
activation.


Phase 1: Change the Certificate (Apple Developer Account Migration)

1. Transfer the Apple certificate from the current Apple Developer account to the new
account.
- Access to both accounts and a copy of the existing certificate is available.

2. Ensure both previously issued passes and all new passes communicate with the new
Apple Developer account, not the old one.

3. Update the Node.js service running on [login to view URL] to point to the
new Apple Developer account.
- Source code is available.



Phase 2: Dynamic Pass Styling (Apple & Android) & Multi-Pass Management with Role-Based Access

Goal 1: Provide a simple method—via an Admin UI—to update the design of all passes
dynamically.

1. Pass design elements, such as colours, logos, and layout, must be editable via the
admin UI. (Live demo update would be essential)

2. Background and text colours should be customizable, while the barcode area remains
unchanged.

3. On saving changes, all stored passes (existing and new) should automatically update
with the new styling via PassKit / Google Pay mechanisms.

4. A database of issued passes should be introduced for easier management and
tracking.

5. During pass registration, customers should also be required to enter their email and
phone number along with the barcode.

6. The super-admin should have the ability to define what data fields (e.g., name, email,
phone) are mandatory or optional at registration.

Goal 2: The Admin UI should be extended to support multiple passes with independent configurations
and role-based access.

1. Enable creation and management of multiple distinct passes (e.g., Pass 1 for Business
A and Pass 2 for Business B).

2. Each pass should have its own design elements (colours, logos, barcodes, and layout).

3. Passes must be separated in the system to ensure changes to one pass do not affect
others. Further, users need to be redirected to the respective subdomain so that the users in
Business A will not download Business B passes

4. Role-based logins:
-Each business/pass has its own login, limited to managing its own pass, and
data.
- A super-admin login must have full access to all passes and their
configurations.

5. Database separation:
- Each business/pass login should only have access to view and manage their own
own issued passes (and associated customer data).
- The super-admin has consolidated access to view and manage all passes and
customer records across businesses.

6. Subdomain-Based/ Unique Link-Based Isolation
- Customers must be redirected to the respective business subdomain or Unique Link for pass
registration.
- Example:
1. Business A → [login to view URL]
2. Business B → [login to view URL]

or
1. Business A → [login to view URL] A
2. Business B → [login to view URL] B

- This ensures customers of Business A can only see and download passes for
Business A and are never exposed to passes from Business B (and vice versa).

Deliverables

• Updated Apple Developer certificate integration (Phase 1).
• Admin UI with dynamic styling controls for passes and a Role-based login system with super-admin/global access and business-level restricted
access (Phase 2).
• Databases for issued passes, including customer details (barcode, email, phone, etc.), in a user-friendly appearance
• Documentation on how to manage, update, and deploy passes.


To further strengthen the development, the following features may be considered:
1. Push Notifications – Send targeted offers, reminders, or updates directly to customers’
wallet passes.
2. Offers & Discounts – Ability to attach special offers or coupons to passes and update
them dynamically.
3. Analytics Dashboard – Track pass activations, active users, scans, and redemption
rates across businesses. (Preferably)
4. POS System Integration Enhancements – Direct API integrations with POS to enable
live validation of usage. (Preferably)
5. Multi-language Support – Localise pass content and admin UI for different user bases." (client-provided description)