Who this is for: studio operators (admin panel) · Product: Podyx V2

A slot blocker holds time on your calendar when there is no booking to hold it. Maintenance, a personal commitment, a setup day, or simply time you do not want sold. To your clients it behaves exactly like a booking: the slot is gone from your booking page.

Watch the Slot Blockers walkthrough

Operations → Blocked slots, and directly from your calendar.

When you sync a calendar, every existing event is imported immediately as a slot blocker. Imported items keep the event names from the source calendar. They do not arrive as bookings, but they do block availability on your booking page and they carry their own buffer time, so external commitments protect your schedule without you copying anything across by hand.

From the calendar you can create a slot blocker, a booking, or a bundle booking. Use a slot blocker whenever you need to hold time and there is no real reservation behind it.

Start and End are dropdowns, not free text. Start offers every quarter hour. End steps by your studio's session increment, up to 23:59. Both follow your studio's 12-hour or 24-hour setting, so the times read the way the rest of your calendar does.

The point is alignment. A blocker you type by hand should sit on the same grid your booking page actually sells, otherwise it leaves an unbookable three-minute sliver behind it that no client can ever fill. The dropdowns make that impossible to do by accident.

⚠️ Blocks created through Zapier, the API or Google Calendar still accept any time. So you may see a blocker sitting at 10:07 that you could not have created by hand. That is expected — it came from outside the CMS.

If the blocker you are about to save falls inside the buffer of a neighbouring session or block, Podyx shows a Scheduling conflict warning before it is created. You can go back and adjust the times, or create it anyway. You will see the same warning whether you are working on the Blocked Slots page or on the calendar.

The warning is not a refusal. Blocking time inside a buffer is sometimes exactly the right call — you know the room is already reset, or the buffer is there for a turnaround that does not apply today. What it catches is the accidental version: blocking an hour without noticing it eats the gap you deliberately left after a session.

💡 Read the warning, then decide. It is there to make the choice deliberate, not to make it for you.

If someone edits a blocker that was created in Podyx from inside Google Calendar, its time, title and location revert to the Podyx version. Podyx stays the source of truth for the blockers you create there, so a stray drag in Google will not quietly move blocked time and reopen a slot you meant to hold.

Two things are kept: notes and attendees added in Google stay on the event. And blockers that were imported from Google in the first place are not affected at all — those are still driven by the source calendar, exactly as before.

💡 If you need to change a Podyx blocker, change it in Podyx. That way the change sticks.

💡 The Block Slot and Remove actions are only shown to roles that have permission to perform them — a read-only team member can view the blockers list without seeing controls they cannot use.

With two-way calendar sync and room-level availability, slot blockers are less essential than they used to be, because a lot of blocking now happens on its own. They are still genuinely useful as a ledger of blocked time: a clear, filterable record of why a slot was unavailable, which a raw calendar does not give you.

Podyx will not allow two slot blockers on the same time at once. If overlapping events appear through your synced calendar, they surface as conflicts so you can decide which one should win.

Use slot blockers to hold time that is not a booking. Synced calendar events become blockers automatically, and you can add your own from the calendar. When you create one by hand, Start and End are dropdowns — quarter hours for Start, your session increment for End, up to 23:59 — which keeps the blocker on the same grid your booking page sells, while blocks arriving from Zapier, the API or Google Calendar can still land on any time. If a new blocker lands inside a neighbouring buffer, you get a scheduling conflict warning before it is saved, and you can adjust it or create it anyway. Blockers you create in Podyx keep their Podyx time, title and location even if someone edits them in Google. Edit or remove them from the Blocked Slots page, filter by room and date range, and let conflicts handle any overlaps.

Related: In-app Calendar · Conflicts · Availability · Connect Google Calendar