How to manage Kemicard Templates (Template_Pass__c) — the records that control branding, data mapping, and visual layout of your digital wallet passes.
What a template manages
- Branding — logos, colors, images, and organization names.
- Data mapping — which Salesforce fields appear on the front and back of the pass.
- Barcode configuration — QR code types and the source data field.
- Email delivery — the email templates used for pass distribution.
- Notifications — how push notifications appear on mobile devices.
Two editing methods
| Method | What it is | When to use |
|---|---|---|
| Template Builder (recommended) | Custom visual editor in the Kemicard Console with live side-by-side previews of the Apple and Google passes. | Day-to-day design updates — colors, images, field mapping, barcodes. |
| Template record page | Standard Salesforce detail page for editing specific field values, with a Configuration Banner showing the linked configuration status. | Fields that are not exposed in the Builder (see below). |
To open a template in the Builder: open the Kemicard Console, use the search box in the Template Builder section to find the template by name, and select it — the visual editor loads with live previews.
Fields only editable on the record page
Subheader__c— title label for usage location.App_Launch_URL__c— URL for associated mobile apps.Relevant_Date__c&Expiration_Date__c— pass relevance and expiry logic.Sample_Record__c— the Salesforce ID that drives Builder previews.From_Email_Address__c— the sender's email address.
Template Builder — visual settings
Style tab
- Background Color — the pass background.
- Font Color (Apple) — text color; note Apple may override it when a Strip Image is used.
- Label Color (Apple) — color for field labels.
- Strict format: colors must be
rgb(R, G, B)with no decimal values.
Barcodes tab
Configure the QR type and the source data field. After changing a mapped field or barcode source, use Upload & Preview Passes and verify on a physical device before rolling out.
Remember: installed passes refresh automatically after template changes (via a record-trigger flow) — always test the update on a sample record first, since changes reach every member's wallet.
Related: Template Builder guide · Loyalty templates · Event templates