Synchronising passes

If you edit a pass template after you have issued passes you need to consider whether or not you need to update those issued passes with the new template content (synchronisation).
An event ticket where the event date or time has changed is a good example of when it is essential to synchronise your change across all issued passes. A minor change to a pass type that has frequent changes (for example, a loyalty card which displays the current points balance) can be left for an issued pass to pick up when it next updates.
Smartix Fair Use Policy applies to synchronisation, so you are limited to a single synchronisation per day.
Automatic synchronisation
Section titled “Automatic synchronisation”Some changes to Google passes are synchronised to all passes automatically. Typically these will be fields where you have selected “the same value for all passes”. In these cases, we send a new template to Google, which is automatically applied the next time a pass is viewed. Other changes must be updated on a per-pass basis. This means that Smartix must generate a new pass version for every issued pass and send it to Google. If you have a lot of passes this can be extremely costly. Hence the fair use policy.
There is no automatic synchronisation for Apple passes, so all changes require us notifying every pass on every installed device that there is a new pass version to download.
Initiating synchronisation
Section titled “Initiating synchronisation”After editing a template, choose Synchronise from the template menu. The synchronisation page shows how many passes are affected and whether Apple, Google or both require updates. Review the credit quote before confirming.
Synchronisation may take a while. We add an entry for every affected pass to a queue and process it in the background.