nisebookings
Nederlands Start building

Switching

Coming from WordPress and Bookly?

A well-built WordPress site is fine. This is not about the CMS being slow or old. It is about choosing the stack for your next site freely, with the bookings outside it. Nothing has to move today: the booking form works in a WordPress page too.

Start building Read the docs

What changes

Same client, same bookings, a different architecture around them.

  • One plugin fewer to keep alive

    A booking plugin comes with add-ons, a licence and PHP versions to track. Here the booking logic is a hosted service. There is nothing to update on your side.

  • No more fighting the theme

    The booking form is a web component that inherits your font and takes your colours. Rebuild the site in Astro or Next.js and it comes along unchanged.

  • The business gets its own admin

    Not a corner of wp-admin, but an admin of its own: calendar, customers, payments and mail. Payments go to its own Mollie account.

  • Script the boring part

    Services, staff, schedules, opening hours and webhooks are all in the management API. A new client account is a script or a prompt, not an afternoon of clicking.

Does it do what Bookly does?

Against Bookly and its add-ons, as of today. Whatever is missing is listed.

Present

  • Appointments per service, with duration, price and buffer times
  • Staff or resources: a staff member can be a room, a boat or a device
  • Schedules per weekday, opening hours and days off
  • Capacity per slot, and a waiting list that mails when a seat frees up
  • Recurring series (weekly, monthly) and packages of sessions
  • Compound and collaborative services: one booking, several staff or resources
  • Extras, coupons and deposits (a percentage or a fixed amount up front)
  • Event tickets, each with its own code
  • Intake questions per service, file uploads included
  • Day-based rentals, priced per day
  • Cancel and reschedule by the customer, through a link in the mail
  • Reminders, confirmations and a calendar feed per staff member
  • VAT per service, included or excluded

Partly

  • Calendar sync: an iCal feed per staff member; Bookly also reads Google and Outlook
  • Invoices: Mollie sends a payment confirmation; there is no invoice PDF per booking yet
  • WordPress: the plugin exists and is maintained, but is not in the wordpress.org directory
  • Customer side: cancel and reschedule links work; there is no customer login with a booking history
  • Languages: Dutch and English. The account language sets the booking form, customer pages and mails; the admin follows each person who logs in

Not there (and not promised)

  • SMS and WhatsApp messages
  • Two-way Google or Outlook calendar sync
  • Gift cards, wallet balances and credit notes
  • Bookkeeping exports and invoice PDFs
  • WooCommerce integration: no shop, no cart handoff
  • Importing existing Bookly data with a button
  • Multiple locations in one account

The path, in three steps

  1. Today: keep WordPress

    Paste the two lines into a Custom HTML block, or use the plugin. One page with a booking form is enough to test with the client.

  2. Later: rebuild the site

    In Astro, Next.js or plain HTML. The booking form moves as a script tag. Services, staff and bookings stay in the account.

  3. After: nothing to migrate

    The booking data never lived in the CMS, so there is nothing to export or import. The site changes; the booking system keeps running.

In an Astro page

<script src="https://app.nisebookings.com/widget.js" defer></script>
<nise-booking data-key="YOUR_PUBLIC_KEY"></nise-booking>

Stay on Bookly if…

  • you need SMS, WhatsApp or two-way calendar sync in the same tool;
  • the shop and the bookings are one thing (WooCommerce);
  • the site is WordPress, will stay WordPress, and the plugin does what you need;
  • you need gift cards, invoices or bookkeeping exports today.

Questions about switching

Can I keep WordPress for now?

Yes. Paste the two lines into a Custom HTML block, or use the plugin. Rebuild the site later and the bookings stay where they are.

Can I import my Bookly data?

There is no import button. A script or a coding agent rebuilds services, staff and schedules through the management API. Let upcoming appointments run out in the old system.

Where does the money go?

Into your client’s own Mollie account. nisebookings stores the amount and the status, never card or bank details.

Does my client have to learn something new?

Yes, a separate admin. Everyone who logs in uses it in Dutch or English.

Can my client get their data out?

Everything is readable through the API. There is no one-click export file yet.

Who maintains it?

nisebookings does: hosting, updates, the booking form and the mail. There is nothing to update on your side.

Where is it built?

By nise in The Hague, the Netherlands.

Put bookings on your next site.

Start free and build against a sandbox. Pay once your client takes real bookings.

Start building Read the docs

Free account. All you need is an e-mail address.