Choosing a Digital Event Passport Vendor for a Singapore Retail Campaign

Selecting a digital event passport vendor for a Singapore retail campaign involves more than comparing screens or scanning features. The passport sits inside a wider campaign operation involving shoppers, participating outlets, frontline teams, rewards, communications, data handling and issue resolution. A polished demonstration may show the intended journey, but procurement should also establish who prepares campaign content, configures locations, supports users and handles exceptions.

Start with a written campaign scenario that every shortlisted supplier must address. Describe the expected customer journey, campaign period, participating locations, validation method, reward logic, anticipated operating conditions and any required connections with existing systems. This makes proposals easier to compare and reduces the risk of each vendor pricing a different interpretation of the project.

Define the passport journey before requesting proposals

A digital event passport can support activities such as visiting participating stores, completing tasks, collecting stamps or unlocking a reward. The appropriate journey depends on the campaign objective and the behaviour expected from participants. Procurement teams should avoid prescribing technology before confirming the operational experience.

Document how a participant enters the campaign, identifies themselves if necessary, discovers activities, records completion and receives confirmation. Include less convenient scenarios: a shopper has limited connectivity, scans the wrong location, changes device, repeats an activity or asks a retailer for assistance. Suppliers can then explain what their proposed approach would do, rather than answering only for an ideal journey.

For broader planning context, review the retail campaign digital event passport guide before preparing the procurement brief.

Ask questions that expose the complete scope

Proposal questions should reveal both the solution and the work required to deliver it. Useful questions include:

• Participant access: Is the journey browser-based, app-based or dependent on another platform? What must participants provide?
• Activity validation: How are visits or tasks confirmed, and what prevents obvious accidental or repeated submissions?
• Campaign administration: Who creates locations, activities, content, campaign rules and user messages?
• Reward handling: Does the scope cover eligibility only, reward issuance, fulfilment coordination or none of these?
• Retail operations: What devices, connectivity, signage, training or staff actions are expected at each outlet?
• Reporting: Which agreed campaign events can be reported, how often and in what format?
• Support: Who receives participant and outlet questions, during which hours, and how are incidents escalated?
• Data: What information is collected, where is it processed, who can access it and when is it removed?

Answers should be assessed against the agreed brief and selected tools. Technical behaviour, integrations and reporting detail may vary by implementation, so request explicit descriptions rather than assuming a feature is standard.

Structure demonstrations around real operating scenarios

Do not let the demonstration become a vendor-led tour. Give each supplier the same scenarios and ask them to show or explain the relevant workflow. A useful session could cover first-time participation, successful activity completion, an invalid attempt, a reward threshold, an outlet seeking help and an administrator reviewing campaign activity.

Separate working functionality from mock-ups, proposed configuration and future development. If an element cannot be demonstrated, ask what will be delivered, which dependency prevents the demonstration and how that item will be accepted later. Record responses in the evaluation notes so visual polish does not outweigh unresolved operational work.

Compare responsibilities and exclusions

A responsibility matrix is often more revealing than a feature checklist. Assign an owner for campaign rules, creative assets, copy, participant terms, privacy notices, outlet information, testing data, staff briefing, reward inventory, support scripts, launch approval and post-campaign reporting.

Ask vendors to list exclusions beside their responsibilities. Common areas requiring clarification include hardware, venue or outlet connectivity, third-party licences, messaging charges, translation, accessibility review, integration work, reward fulfilment, on-site staffing and changes after approval. An exclusion is not necessarily a weakness, but it must be visible before commercial comparison.

If the passport forms one part of a wider experience, compare the supplier boundary with the procurement approach used for a retail digital brand activation vendor. This can help identify work that belongs to the overall campaign rather than the passport component.

Set acceptance criteria before appointment

Acceptance should be tied to observable outcomes under agreed conditions. Instead of stating that scanning must “work smoothly,” specify the supported devices or browsers, test locations, validation steps and expected result. Include approved content, activity rules, administrative access, required reports and agreed exception paths.

A practical acceptance plan may include:

1. Reviewing the configured journey against the approved campaign flow.
2. Testing each location and activity using agreed test cases.
3. Checking duplicate, incomplete and invalid participation scenarios.
4. Confirming approved messages, links, dates and reward conditions.
5. Verifying agreed access controls and reporting outputs.
6. Logging defects, assigning owners and retesting material fixes.
7. Recording launch approval and any accepted limitations.

Privacy and compliance responsibilities should also be documented, but vendors should not be treated as legal advisers unless separately appointed for that purpose. The campaign owner should obtain appropriate advice for consent language, terms, retention and regulatory obligations where required.

Use a weighted supplier evaluation

Score categories according to campaign risk rather than giving every feature equal value. Suggested categories include journey fit, operational feasibility, delivery plan, support model, implementation dependencies, data approach, acceptance method, relevant team experience and total commercial scope. Require evaluators to provide short evidence notes for important scores.

Commercial review should compare the same baseline. Identify one-time delivery fees, recurring charges, usage assumptions, optional items, third-party costs and rates for approved changes. Where suppliers use different pricing structures, calculate against the campaign’s stated duration and operating assumptions instead of comparing headline totals alone.

Digital lucky draws may introduce different eligibility, fulfilment and governance questions. Where that mechanic is also being sourced, evaluate it through the separate digital lucky draw vendor selection guide rather than assuming the passport scope covers it.

What to confirm before signing

The final proposal and agreement should identify deliverables, milestones, dependencies, review periods, change control, support coverage, acceptance steps and ownership of supplied assets. Confirm who can approve campaign rules and launch decisions. Ensure assumptions made during sales discussions appear in the written scope.

Get Out! Events can scope and deliver digital event passport work through GO Labs as part of a wider retail campaign. The final approach, technical outcomes and operating responsibilities depend on the agreed brief and selected tools. A disciplined selection process gives both buyer and supplier a clearer basis for designing, testing and running the campaign.