igor800

<p>Robina is a free, open-source booking and appointment plugin for WordPress, built for service businesses that want a capable booking system without subscription fees. It is service- and resource-centric: the bookable unit is a service with its own availability, while staff, locations and resources are optional layers you add only if you need them.</p>
<h4>Highlights</h4>
<ul>
<li><strong>Front-end booking widget (Vue 3).</strong> A clean multi-step wizard — Service, Date & time, Details, Confirm — added to any page with the <code>[robina_booking_form]</code> shortcode, or as a popup button with <code>[robina_booking_button]</code>.</li>
<li><strong>Capacity-aware availability.</strong> Slots are computed from your business hours, slot step and buffers. Assign staff to a service and each one adds a parallel slot; a staff member booked anywhere counts as busy. With no staff, a service has a single capacity per location.</li>
<li><strong>Group classes.</strong> Give a service a capacity above 1 (say 20 or 40 — there is no upper limit) and several customers can book the same session until it fills up — ideal for classes, workshops and large group sessions.</li>
<li><strong>Staff (optional).</strong> Tag the people who provide a service, pin them to one or more locations, and give them their own weekly hours. When a customer picks a location, only the staff who work there are offered.</li>
<li><strong>Locations (optional).</strong> Offices or branches with their own optional weekly hours; each service declares where it is available.</li>
<li><strong>Native WordPress admin.</strong> A branded Catalog (services, categories, resources), a Month/Week/Day Calendar with in-place booking creation, plus Bookings, Customers, Staff and Locations screens — all in plain WordPress UI.</li>
<li><strong>Email notifications</strong> to the owner and the customer on every new booking.</li>
<li><strong>Optional online payments</strong> — Pay on site, WooCommerce, Stripe or PayPal (see “External services” below). Leave them all off for free bookings.</li>
<li><strong>Self-contained and private.</strong> No external CDNs and no trackers; the phone-input flags and every front-end asset ship inside the plugin. Uninstalling removes Robina’s tables and options.</li>
</ul>
<h4>Service-centric by design</h4>
<p>Robina deliberately keeps availability on the <em>service</em>, not on a mandatory “employee”. Staff, locations and resources are optional capacity and scope layers, so Robina also suits non-staff models such as equipment rental or table booking.</p>
<h3>External services</h3>
<p>By default Robina works entirely on your own site and contacts no third party. It only talks to an external service when <strong>you, the admin, enable and configure a payment gateway</strong>, and only when a customer actually chooses to pay with it. No data is sent anywhere otherwise — Robina has no “home” server and sends no telemetry or analytics.</p>
<p><strong>Stripe</strong> — used only when you enable “Stripe” and enter your API keys. When a customer pays by card, Robina creates a Stripe Checkout Session and redirects the customer to Stripe’s hosted payment page, and it receives Stripe webhooks to confirm payment. Data sent to Stripe: the booking amount, currency, a short description and the customer’s email. Card details are entered on Stripe’s site, never on yours.<br />
Terms: https://stripe.com/legal — Privacy: https://stripe.com/privacy</p>
<p><strong>PayPal</strong> — used only when you enable “PayPal” and enter your client ID and secret. When a customer pays with PayPal, Robina creates a PayPal order, redirects the customer to PayPal to approve it, then captures it on return. Data sent to PayPal: the booking amount, currency and a reference id.<br />
Terms: https://www.paypal.com/legalhub/home — Privacy: https://www.paypal.com/legalhub/privacy-full</p>
<p><strong>WooCommerce</strong> (optional, local) — if you enable WooCommerce checkout and WooCommerce is installed, Robina creates a pending WooCommerce order and hands payment off to WooCommerce. Robina makes no external call itself; any outbound requests are made by WooCommerce and its own gateways under their policies.</p>
<p><strong>Map link</strong> — a location’s address is turned into a plain “view on map” link to Google Maps (https://www.google.com/maps/search/…). It is only a link: nothing is transmitted and no map is loaded unless a visitor clicks it.</p>
<h3>Source code</h3>
<p>Robina is fully open source (GPLv2+). The front-end widget is compiled with Vite from the Vue source that ships inside the plugin under <code>/resources</code>. The build files (<code>package.json</code>, <code>package-lock.json</code>, <code>vite.config.js</code>) are bundled too, so the compiled assets in <code>/assets/dist</code> can be regenerated from source with:</p>
<pre><code>npm install && npm run build
</code></pre>
<p>Bundled third-party libraries (installed via npm, both MIT-licensed):</p>
<ul>
<li>Vue 3 (^3.4) — https://github.com/vuejs/core</li>
<li>intl-tel-input (^29.0) — https://github.com/jackocnr/intl-tel-input</li>
</ul>


Robina

Free, open-source booking and appointments for WordPress: services, staff, locations, capacity-aware availability and optional payments.

ablancodev

<p>Appointment SW lets visitors book appointments from any page on your site. You configure as many working windows per day as you need, block holidays, optionally allow guest bookings, and Appointment SW takes care of slot availability, email notifications and capability checks.</p>
<p>Version 2.0 is a deep modernisation of the original plugin while keeping every shortcode, option and database table from 1.x in working order. Existing sites can update without re-doing setup.</p>
<h4>What’s new in 2.0</h4>
<ul>
<li>Modern booking flow: clicking a free slot opens a confirmation modal — no more page reloads to advance the booking.</li>
<li>Admin booking modal with live client search and an inline “Add client” button, so receptionists can book a brand new client without leaving the calendar.</li>
<li>Arbitrary number of time windows per day (not just two).</li>
<li>Server-rendered Settings page using the WordPress Settings API, with an onboarding section that creates the shortcode pages for you in one click.</li>
<li>Public REST API under <code>/wp-json/appointmentsw/v1/</code> for availability, bookings, holidays, settings, and user search.</li>
<li>Capability-based permissions: <code>appointmentsw_manage</code> (administer) and <code>appointmentsw_book</code> (book a slot).</li>
<li>Prepared statements across every database query, plus new indexes on bookings, bookmeta and holidays for faster lookups on busy calendars.</li>
<li>Hardened request dispatcher: strict capability checks, sanitized input and escaped output throughout.</li>
<li>Filterable email templates via <code>appointmentsw/email/{event}/{audience}/{subject|body}</code>.</li>
<li>Optional WooCommerce integration is now a separate companion plugin so this core stays lean.</li>
</ul>
<h4>Shortcodes</h4>
<ul>
<li><code>[appointmentsw_form]</code> — booking form for visitors.</li>
<li><code>[appointmentsw_myaccount]</code> — logged-in user appointments (view and cancel).</li>
<li><code>[appointmentsw_admin]</code> — frontend admin calendar with client search and one-click client creation.</li>
<li><code>[appointmentsw_vacations]</code> — block holidays from the frontend.</li>
</ul>
<h4>Backwards compatibility</h4>
<p>All 1.x shortcodes keep rendering, bundled Bootstrap 3 assets are still enqueued so existing theme overrides keep working, the legacy <code>core/</code> classes remain loaded, and legacy options (<code>asw-guest</code>, <code>asw-duration</code>, <code>asw-numdays</code>, <code>asw-maxoffset</code>, <code>asw-start_time_*</code>, <code>asw-end_time_*</code>) are migrated transparently into the new <code>appointmentsw_settings</code> option the first time the new code reads them.</p>


Appointment SW

Self-service appointment booking for WordPress. Calendar, arbitrary time windows, holidays, modal booking flow, REST API.

Robina vs Appointment SW