· 8 min read

How to Add Event Registration to Your Shopify Store

Shopify sells the products beautifully and does nothing at all for the author reading on the 14th. Here's how to put a Shopify event calendar with sign-ups on the store itself, without a ticketing app.

Picture a bookshop whose online store runs on Shopify. A nephew set it up. The owner can edit a product listing or fix a typo on a page, but avoids anything that looks like code.

The events are a different story. The shop hosts an author reading and a book club every month, and both exist only as Facebook posts. There's no sign-up, no headcount, no list of who came last time. The store sells the books; the events, the nights the shop is actually full of people, live somewhere else entirely, and the two never touch.

The claim this post makes: the store can hold the events too. A Shopify page accepts an embed the same way it accepts a YouTube video, which means a Shopify event calendar can live on the store itself: the month's readings, each with its own sign-up form. No ticketing app, no second website, and nobody sent to Eventbrite to register for a free reading.

What Shopify gives you out of the box

Honesty first: Shopify is a store, and it's excellent at being one. It is not an events platform, and it doesn't pretend to be. There's no native event calendar, no RSVP button, nothing that knows what a Tuesday-evening book club is.

So shops improvise, usually down one of three routes.

Some create each event as a product. It technically works: the reading gets a page, people "buy" a free ticket. But a free event through a checkout flow is clunky for everyone. Attendees enter shipping details for something that will never ship, and the shop's order history fills with $0 sales that aren't sales.

Some install a ticketing app from the Shopify App Store, which is the right move in a specific case covered below. It's also heavier than most shops need for free events.

And most do what the shop above does: post the event on Facebook or Eventbrite and hope, with the store never mentioning the event at all. The people already browsing the site, the warmest audience the shop has, never find out the reading exists.

When a Shopify event app is the right call

The App Store route deserves a fair hearing, because sometimes it wins.

A Shopify event registration app like Evey or Experiences exists to sell tickets through Shopify itself: inventory, checkout, refunds, all inside the store's existing machinery. A bookshop charging $40 for a bookbinding workshop with fifteen seats is well served there. The payment runs through the checkout the shop already trusts, the ticket is a real order, and a refund works like any other refund. Paid ticketing with real inventory is what those apps are for, and if that's your event, install one.

The gap is everything else. The free author reading. The monthly book club. The RSVP-style sign-up where the point is a headcount and a list of names, not a transaction. Paying a ticketing app's monthly fee to collect names for a free book club is the over-serve; a bare Google Form link in a Facebook post is the under-serve. Most of a small shop's events live in that middle, and neither end of the market is built for them. Collecting sign-ups without a checkout is the same problem covered in how to collect RSVPs on your website. Shopify just happens to be the website.

A Shopify event calendar without an app

The middle route is an embed. A Shopify event calendar added this way is one paste: the page editor accepts custom HTML (on newer themes, that's a "Custom Liquid" section; on any theme, the page editor's HTML view does the same job), and a small snippet pasted there renders the full calendar on the page.

The word "embed" does more scaring than the thing itself deserves. An embed is a short block of text that tells a page to display something hosted elsewhere. The store already does this any time a page shows a YouTube clip: the video isn't stored in Shopify, the page just knows where to find it. The calendar works the same way. The events live in a dashboard, the snippet displays them on the page, and nothing about the store's theme, checkout, or apps changes.

Where the calendar goes is the shop's call. Most give events their own page, linked from the main nav next to Shop and About. A shop that runs one event a month might drop the upcoming-events list at the bottom of the homepage instead. Either way the snippet is the same paste.

Nobody writes the snippet and nobody edits it. It arrives ready to copy, gets pasted once, and the calendar appears. For a shop like the one above, this is a five-minute job for the nephew, and the owner never touches it again. Adding next month's reading happens in the dashboard, not on the website; the page updates itself.

Visitors see the month's events in the store's own colours. The calendar reads them off the page around it, so it renders like part of the theme rather than a widget dropped on top, and it keeps matching after a redesign. They click the reading, fill in a name and email, and they're registered. No new tab, no account to create, no third-party platform between them and a bookshop they were already standing in, digitally speaking. (The general version of this approach, for any platform, is in the complete guide to embedding an events calendar.)

What changes when registration lives on the store

The mechanics matter more than the pitch, so concretely, three things change.

The headcount arrives early. With a Sign Up button on the events page, the reading shows its number days out: 18 registered means setting out 22 chairs, not 30 chairs and hope. The night-before guesswork, and the no-show spiral that comes with it, is the subject of reducing no-shows at small business events, and a visible number is where fixing it starts. Automatic reminder emails the day before do most of the rest.

Full becomes a measurement instead of a problem. Set a cap of 25 on the reading and, when it fills, the form switches to a waitlist on its own. Eleven names past capacity isn't an apology at the door. It's the audience for a second night, already found and already counted.

And every registration builds a list the shop owns. Names, emails, which events each person turned up for, exportable as a CSV in one click. For a shop that has run years of events through Facebook posts, this is usually the first mailing list it has ever had, and it's made of exactly the right people: the ones who come to things.

Setting it up, in order

Framed as the bookshop's setup, start to finish.

Create a calendar in Turnout and pick the display format: a monthly grid or a simple upcoming-events list. Add the month's two events: the author reading on the 14th, the book club on the 28th. Give the reading a capacity of 25, since that's what the chairs allow.

The book club gets one custom field: a dropdown asking whether to set aside a copy of this month's book. Every registration comes back with the answer attached, so ordering stock for the club stops being a guess. Custom fields cover the rest of what shops actually need to ask: party size for the kids' story hour, a dietary note for the wine-and-cheese evening.

Copy the snippet, and have the nephew paste it into a Custom Liquid section on the store's Events page. That's the five-minute, one-time step. From there, registrations arrive by email as they happen, the calendar keeps itself current, and the waitlist tends itself if the reading fills.

The store's product pages didn't change. The checkout didn't change. The events page just started doing its job. More of what this looks like for a bookshop specifically (book clubs, signings, kids' story hours) is on the bookshops use-case page.

The store that holds the whole business

A bookshop's website has always been asked to do two things: sell the books and fill the room. Shopify handles the first out of the box. The second has been left to Facebook's algorithm and a stack of folding chairs.

With the calendar on the store, both halves finally live at the same address. Someone browsing the shelves at 11pm finds the reading three clicks later and signs up on the spot. The store stops being just the catalogue and starts being the shop: the books, and the nights it's full.

Explore by use case

Back to Turnout