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/tiem has changed is a good example of where it is essential to synchronise your change across all issued passes. Whereas a minor change to a pass type that has frequent changes (eg. a loyalty card which displays the current points balance) can be left for issued pass to pick up changes when they next update.
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 you can choose the synchronise option in the top menu. The popup will show you how many passes will be synchronised. Dependign upon the changes you have made, you may see that only Apple or only Google passes require synchronisation.
Synchronisation may take a while. We add a entry for every pass to a queue and process it in the background.