Sugar Calendar

WordPress

Every ticket sold through Sugar Calendar becomes an Apple or Google Wallet pass, so it sits on your attendee's phone instead of in an email they have to find at the door.

Download pluginVersion 2.0.0 · 104 KB · .zip

In WordPress go to Plugins → Add Plugin → Upload Plugin, choose the file and activate it.

Step-by-step setup guide, with screenshots →

Already using 1.0? 2.0 installs into a new folder, so WordPress treats it as a separate plugin. When you activate it, it copies your 1.0 settings and the record of every pass 1.0 issued, and from then on it creates, updates and expires the passes. 1.0 stays switched off, with a reminder, until you deactivate and delete it. A receipt page using the 1.0 [sugar_calendar_addtowallet] shortcode keeps working.

How it works

1Install the plugin and paste your AddToWallet API key on its Settings tab.
2Design the pass on the Pass design tab, or keep the default.
3Someone gets tickets to one of your Sugar Calendar events.
4Their ticket receipt offers Add to Apple Wallet and Add to Google Wallet for each ticket.

What your attendee sees

The wallet buttons are added directly under Sugar Calendar's ticket receipt, the page buyers land on after checkout and reach again from their receipt email, so the checkout flow is unchanged. To place them yourself, put the [atw_sc_wallet_passes] shortcode on that page.

A Sugar Calendar ticket receipt for two tickets, with Add to Apple Wallet and Add to Google Wallet buttons for each attendee under the receipt

Both wallets are offered every time, so someone buying on a laptop can still get the pass onto whichever phone they carry.
An order for several tickets shows a set of buttons per ticket, each labelled with the attendee's name, because each person needs their own barcode at the door.
The pass carries the attendee's name, the event, the date, time and location.
Reloading or sharing the receipt never creates a second pass for the same ticket.

What you configure

Four tabs in wp-admin: Pass design, Tickets & passes, Settings and Help.

Pass design: A visual editor with a live Apple Wallet and Google Wallet preview, front and back, filled in with your latest ticket. Set your business name, logo and colour, a header line, the pass title, up to three fields on the front, and sections on the back for text, links, phone numbers, email addresses and addresses.
+ Data Field: Puts each ticket's details on the pass: the attendee's name, the event, ticket type, date, start and end time, venue or location and its address, event page, ticket code, ticket and order numbers, price paid and more.
Tickets & passes: Every ticket and whether its pass was issued, expired or failed, with the reason when one could not be created (for example, no credits left) and why a pass was expired.
Settings: Your API key, checked with AddToWallet before it is saved and never sent to the browser, which orders issue passes and what expires them, and your credit balance. It warns you when Sugar Calendar has no Payment Success Page set.
Help: A contact form that goes straight to the AddToWallet team.

What you get

Apple and Google buttons on Sugar Calendar's ticket receipt, so nobody is stuck on the wrong device
One pass per ticket, each labelled with the attendee's name, so a group order gets everyone through the door
The barcode is Sugar Calendar's own ticket code, the same one on the ticket and in the ticket email
Free and paid tickets sold through Sugar Calendar's own event ticketing, in Lite and Pro
When an event moves, changes location or its details change, passes already in wallets are updated without using another credit
Refunded or trashed orders, trashed or deleted tickets and deleted events expire the pass straight away; you choose which on the Settings tab
Times on the pass are in the event's own time zone, and all-day events show no times
A hero image per event if you like, your choice of barcode format, and a Wallet reminder before the event that you can switch off

Requirements

WordPress: 5.8 or newer, tested up to 7.1
PHP: 7.4 or newer
Sugar Calendar: Lite or Pro, 3.12 or newer, selling tickets with a Payment Success Page set, tested with 3.17.0
AddToWallet: An account and API key, with credits available

Good to know

Each pass uses one credit when it is created, so an order for four tickets uses four. Updating a pass after a change uses none, and expiring it does not refund the credit. If your balance runs out, ticket sales carry on as normal but no pass is created; Tickets & passes shows why. Sugar Calendar needs a Payment Success Page set (Sugar Calendar › Settings › Payments), since that receipt is where the buttons go. RSVPs are not supported: passes are issued for tickets, free or paid. A receipt link works for 72 hours, as in Sugar Calendar itself, which then emails the buyer a fresh one.