Digital Membership Cards for Salesforce: A Launch Guide

Replacing plastic cards and PDFs with live wallet passes is a data project, a design project, and a rollout project. Here's the sequence that works.

1. Decide what drives the card

Pick the Salesforce object that represents membership — Contact, a Membership custom object, or an NPSP structure. Every field you show on the card (name, member ID, tier, expiry) should live on or be reachable from that record, because the card will update whenever the record does.

2. Design per tier, not per member

One template per visual design. Tiers usually mean separate templates (colors, benefits text) driven by the same object. Follow the image specs — logo 150×150, strip 1125×294, under 100 KB — and keep the front to the five or six fields a front-desk person needs at a glance.

3. Wire the automation

A record-triggered Flow issues the pass when membership activates, sends the enrollment email with the add-to-wallet link, and pushes updates on tier change or renewal. Kemicard ships sample flows you can clone — see the Flow integration guide.

4. Roll out in waves

Start with staff, then a friendly member segment, then everyone via Bulk Actions. Expect the add-to-wallet link in a renewal or welcome email to be your highest-converting placement; a QR code at the front desk catches walk-ins.

5. Use the channel you just built

The card is also a push channel: renewal reminders, event invitations, and geofenced lock-screen messages when members are near your venue. Programs that treat the pass as media — not just ID — see the engagement gains. Explore membership cards and real customer stories.