Built for how a cafe with weekly live music actually works: a band every Sunday, a pub quiz once a month, tickets that cost a few euros, and bar staff scanning at the door with a phone.<\/p>\n\n
The plugin does six things, and does those six well:<\/p>\n\n
Calendar and ticket sales.<\/strong> Every night is its own page with its own address, so it can be found on its own. Recurring nights are scheduled a quarter ahead automatically. Free nights that still need a reservation are part of the same system.<\/p>\n\n Payment without a middleman account.<\/strong> The money goes straight from the guest to the venue's own account. Mollie and Stripe are supported; iDEAL works with both, and the provider most used in your country is listed first.<\/p>\n\n In the guest's own calendar.<\/strong> Every night has an \"Add to calendar\" link: a plain .ics file with the right time, the venue and the doors time. If a night is called off, the appointment is marked cancelled instead of quietly disappearing.<\/p>\n\n Tickets that arrive.<\/strong> The ticket email is one of the few emails where delivery really matters. So the plugin checks SPF, DKIM and DMARC, processes bounces, and shows on the dashboard which guest did not get their tickets.<\/p>\n\n A door scanner that works offline.<\/strong> The tickets live on the device, signed, so the scanner can tell on its own whether a QR code is genuine even without wifi. Scans are sent along as soon as there is a connection again. A ticket for a different night is recognised, and on a second scan it tells you what time the first one was.<\/p>\n\n And what happens at the bar.<\/strong> Someone walks in without a ticket: sell one at the door, cash or card, and let them straight in. Someone transfers the money or pays later: mark that order as paid by hand. Both count normally towards revenue, the VAT return and the head count at the door.<\/p>\n\n Already running The Events Calendar with Event Tickets? The plugin converts those events in place: the same page, the same address, the same image and the same SEO fields. No search results are lost and shared links keep working. Orders and attendees come along as history.<\/p>\n\n Selling with Event Tickets Plus through WooCommerce? That comes along too: there a ticket is a WooCommerce product and an order is a WooCommerce order, and both are read. The rest of your shop is left alone. Always start with the dry run: it changes nothing and shows what would happen.<\/p>\n\n No seat maps, no time slots, no subscriptions. This is built for nights where people walk in, not for theatres with numbered rows.<\/p>\n\n This plugin can connect to the external services below. Nothing is sent anywhere until you choose to.<\/p>\n\n Mollie (payment provider).<\/strong> When you connect your Mollie account, the plugin creates payments and refunds through the Mollie API on your behalf. The order number, amount, description and your site's hostname are sent with each payment. See the Mollie terms<\/a> and privacy policy<\/a>.<\/p>\n\n Stripe (payment provider).<\/strong> When you connect your Stripe account, payments and refunds are created on your Stripe account through smoothentree.com (see below), because Stripe only lets the platform add the service fee. The order number, amount, description, your site's hostname and the guest's email address are sent with each payment. See the Stripe terms<\/a> and privacy policy<\/a>.<\/p>\n\n Postmark (email delivery, optional).<\/strong> Only when you choose Postmark as the sending method under Ticket sales, Settings and enter an API token, the plugin sends email through the Postmark API (api.postmarkapp.com). What is sent, each time an email is sent: the sender name and address you configured, the recipient's email address, the subject, the text and HTML body of the message, and its attachments (the QR code images of the tickets). The plugin also reads delivery and bounce notifications that Postmark sends back to your site, so the dashboard can show which guest did not receive their tickets. See the Postmark terms<\/a> and privacy policy<\/a>.<\/p>\n\n Resend (email delivery, optional).<\/strong> Only when you choose Resend as the sending method and enter an API key, the plugin sends email through the Resend API (api.resend.com). The same data is sent as for Postmark: sender, recipient, subject, both bodies and the attachments, each time an email is sent, plus the delivery and bounce notifications that come back. See the Resend terms<\/a> and privacy policy<\/a>.<\/p>\n\n Pay. (payment provider, disabled by default).<\/strong> The adapter for Pay. (pay.nl) ships with the plugin but is not available in the settings; a site only gets it by enabling it with the filter smoothentree_experimental_gateways. If it is enabled and you enter your Pay. credentials, payments and refunds are created through the Pay. API (rest.pay.nl): the order number, the amount, a short description of the event, your Pay. service id and the addresses this site should be sent back to. See the Pay. terms<\/a> and privacy policy<\/a>.<\/p>\n\n smoothentree.com (the connection service for this plugin).<\/strong> When you click \"Connect with Mollie\" or \"Connect with Stripe\", your browser is sent to smoothentree.com, which forwards you to Mollie and receives the access tokens on your behalf; the tokens are then handed back to your site in encrypted form. After that, your site contacts smoothentree.com once a day and before a payment when the token is about to expire, to refresh the token and to read the current service fee. What is sent: the refresh token (Mollie), your site's URL and a connection id. For Stripe, every payment, status check and refund passes through smoothentree.com, which forwards it to Stripe on behalf of your account. The service keeps a record of which sites are connected and when they were last seen; it does not store your tokens. Without the connection, paid tickets are not possible; free reservations work without any external service. See the terms<\/a> and privacy statement<\/a>.<\/p>\n\n Service fee.<\/strong> Each paid ticket carries a small fixed service fee for Smooth Entree, split off during payment. By default the guest pays it and it is shown as a separate line on the receipt, so the venue pays nothing; in the settings the venue can choose to carry it instead. This fee is separate from the transaction costs charged by your own payment provider, which you agree with them and which do not pass through us.<\/p>\n\n The door scanner uses jsQR (https:\/\/github.com\/cozmo\/jsQR, Apache License\n2.0) to read QR codes in browsers without a built-in BarcodeDetector, which in\npractice means mostly Safari on iOS. The unminified source is in\nassets\/vendor\/jsqr.js, with the licence next to it.<\/p>\n\n\n After that, take a look at the Health screen: it tells you whether email, caching and background tasks are set up correctly.<\/p>\n\n\n No. The plugin creates a payment at the venue's own provider, with the venue's own keys. The money goes straight to that account.<\/p><\/dd>\n Only one of them can win, and that is enforced in the database, not in the code around it. The second one is told politely that it just sold out.<\/p><\/dd>\n By default that order is still accepted and marked as an overbooking; you see it on the dashboard. One extra guest in a cafe is usually less trouble than sending money back. Refunding automatically is possible too, and that is a setting.<\/p><\/dd>\n Yes, in two places. In the admin under Orders: pick the night and the ticket, the number, cash or card, and whether the guest goes straight in. And in the door scanner itself, because the person with the phone is at the door and not behind the bar: there is a \"Sell a ticket\" button with that night's ticket types. In both cases the email address may be left empty; then no email is sent, because the guest is standing right in front of you.<\/p><\/dd>\n Yes. There the tickets are WooCommerce products and the orders are WooCommerce orders, including when those already live in WooCommerce's own tables instead of with the posts. Both are read, with the attendees and with who was inside at the time. Other products in your shop are left alone. Do the dry run first: it changes nothing and shows what would happen.<\/p><\/dd>\n English, Dutch, German, French, Spanish, Italian, Portuguese, Polish, Czech, Hungarian, Romanian, Greek, Swedish, Danish, Norwegian, Finnish, Turkish and Japanese, with the regional variants for Belgium, Austria, Switzerland, Canada, Mexico and Brazil, and formal versions of Dutch and German. The plugin follows the language of your site: the admin screens, the event page, the checkout, the ticket emails and the door scanner. Dates, amounts and the web addresses of the pages it creates follow that language too.<\/p>\n\n Corrections and improvements are very welcome on translate.wordpress.org.<\/p><\/dd>\n Yes. That night's tickets are on the device, with a signature the device can use to see for itself whether a QR code comes from this venue. Scans are kept and sent as soon as there is a connection again.<\/p><\/dd>\n\n<\/dl>\n\n\nMigrating from another plugin<\/h4>\n\n
What it deliberately does not do<\/h4>\n\n
External services<\/h3>\n\n
Included software<\/h3>\n\n
\n
\/wp-content\/plugins\/<\/code>, or install it from the admin screen.<\/li>\n\n
Does the money pass through you?<\/h3><\/dt>\n
What happens if two people buy the last ticket at the same time?<\/h3><\/dt>\n
What if someone pays after their reservation has expired?<\/h3><\/dt>\n
Can I sell at the door?<\/h3><\/dt>\n
I sell with Event Tickets Plus through WooCommerce. Can I switch?<\/h3><\/dt>\n
Which languages does it speak?<\/h3><\/dt>\n
Does the door scanner work without internet?<\/h3><\/dt>\n
0.1.0<\/h4>\n\n
\n