ajayrajbanshi

<p>Nivaj Appointment Hub is a self-hosted appointment booking plugin for WordPress. Visitors pick a service, choose a date and time from your availability, and fill in their details — all without needing a third-party scheduling account. Bookings land in your WordPress admin and trigger configurable email notifications.</p>
<h4>Key features</h4>
<ul>
<li>Multiple bookable services with per-service duration, colour, location type (phone, in-person, video, custom), and image</li>
<li>Weekly availability rules — set working hours for each day of the week per service</li>
<li>Date-specific overrides — block dates (holidays) or open extra dates with custom hours</li>
<li>Buffer times before/after bookings to prevent back-to-back conflicts</li>
<li>Daily booking cap per service (optional)</li>
<li>Minimum booking notice and maximum advance-booking window</li>
<li>Custom fields per service (text, textarea, select, checkbox, number, phone, URL)</li>
<li>Email notifications on confirmation, cancellation, and admin alerts, plus reminder emails</li>
<li>Shortcode <code>[nivaj_ah_booking]</code> and a Gutenberg block to embed the widget</li>
<li>Optional floating “Book Now” popup button site-wide, with fullscreen mode</li>
<li>CSV export of all bookings</li>
<li>REST API endpoints under <code>/wp-json/nivaj-ah/v1/</code> for public booking actions</li>
<li>Works with guest visitors — no account required to book</li>
</ul>
<h4>Booking flow</h4>
<ol>
<li>Visitor selects a service from the list.</li>
<li>Visitor picks a date from the horizontal day strip (auto-advances past empty weeks).</li>
<li>Visitor picks a time slot, grouped by Morning / Afternoon / Evening.</li>
<li>Visitor fills in name, email, phone (optional), notes (optional), and any custom fields.</li>
<li>Booking is confirmed on screen and via email.</li>
</ol>
<h3>Privacy</h3>
<p>This plugin stores personal data submitted by visitors when they book an appointment: name, email address, phone number (optional), any custom field values you have configured, IP address (transiently, for rate limiting), and the booking details themselves.</p>
<p>Emails are sent through your site’s mailer (<code>wp_mail()</code>) to the visitor’s email address and the administrator email configured in Settings. No data is sent to external services by default.</p>
<p>If the <strong>Webhook</strong> integration is enabled in Settings, booking events are POSTed to the URL you configure. Site administrators are responsible for ensuring that the destination complies with their privacy policy and applicable data protection law.</p>
<p>Booking records are retained until manually deleted or until the plugin is uninstalled via the Plugins screen, which drops all plugin tables and options.</p>
<h3>Development</h3>
<p>Source code: https://github.com/ajayrajbanshi/nivaj-appointment-hub</p>
<p>The compiled JavaScript and CSS files in <code>assets/build/</code> are generated from the human-readable source under <code>src/</code> (React/JSX components and SCSS) using <code>@wordpress/scripts</code> (webpack).</p>
<p>To build from source:</p>
<pre><code>npm install
npm run build
</code></pre>
<p>This produces <code>assets/build/admin-app.{js,css}</code>, <code>assets/build/booking-widget.{js,css}</code>, and <code>assets/build/block-editor.js</code> from <code>src/admin-app/</code>, <code>src/booking-widget/</code>, and <code>src/block-editor/</code> respectively. To produce the wordpress.org distribution zip, run <code>npm run package</code>.</p>
<p>No third-party libraries are bundled outside of <code>@wordpress/*</code> packages provided by WordPress core (<code>wp-element</code>, <code>wp-components</code>, <code>wp-i18n</code>, <code>wp-api-fetch</code>, <code>wp-blocks</code>, <code>wp-block-editor</code>).</p>


Nivaj Appointment Hub

A flexible appointment booking system for WordPress. Define services, set availability, and let visitors book time slots without leaving your site.

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.

Nivaj Appointment Hub vs Robina