Rooms & resources
Create bookable rooms, venues or resources with their own schedules and limits.
Pluginory Booking · In development
Booking that fits the way your business actually works.
Pluginory Booking is being built for rooms, venues, studios and other time-based resources — with clear availability, flexible rules and a WordPress-native workflow.
Room & resource first
Locale ready
Flexible payments
Built to stay maintainable
pluginory
BookingsCalendar List Resources
September 2026‹›
Mon 14Tue 15Wed 16Thu 17Fri 18
10:00 - 12:00Birthday Party
11:00 - 13:00Private Event
12:00 - 14:00Studio Session
10:00 - 11:30Open Session
14:00 - 15:30Team Booking
Book your time
Booking for businesses that sell time, space and access.
Instead of forcing every business into an employee appointment model, Pluginory Booking starts with resources: rooms, studios, saunas, sports spaces, meeting rooms and other bookable places.
Active development
Pluginory Booking
A focused WordPress booking system for resource-based businesses, designed around real operational rules rather than generic calendar forms.
Resource-firstRooms and spaces are first-class bookable objects.
WordPress-nativeManage bookings in the admin you already use.
Local when neededLocale packs can add country-specific defaults without bloating the core.
ExtensiblePayments and regional integrations are designed as adapters, not hard-coded dependencies.
The boring operational details are the product.
Availability, buffers, exceptions and manual changes are where booking systems usually become painful. Pluginory is being designed around those details from the start.
Availability rules
Control opening hours, blocked periods, exceptions and bookable windows.
Buffers & turnaround
Leave automatic setup, cleanup or safety time between different booking types.
Manual bookings
Staff can create, edit and confirm bookings without sending the customer through checkout.
Flexible pricing
Build toward pricing that can vary by time, resource, booking type and defined business rules.
Clear customer flow
Keep the path from choosing a time to confirming a booking short, mobile-friendly and understandable.
Who it is for
If customers reserve a place for a period of time, Pluginory should fit.
The first version is intentionally narrow: businesses where availability belongs to a room, space or other resource — not primarily to an employee calendar.
Party rooms & play spaces
Photo & recording studios
Saunas & private leisure spaces
Sports & training rooms
Meeting & event rooms
Other time-based resources
EE
First predefined locale
Estonia
- Euro and European date/time defaults
- VAT configuration defaults
- Estonian and English interface readiness
- Local payment adapters can be added separately
Global core, local setup
Start local without locking the product to one country.
Pluginory is being structured around locales. A locale can define sensible defaults such as currency, date and time formats, tax settings and regional behavior, while every important value remains editable by the site owner.
- Estonia can ship with tested defaults first
- Users can define their own locale settings
- New country packs can be added without rewriting the booking engine
- Translations remain separate from business rules
Payments without lock-in
One booking flow, multiple payment adapters.
The booking engine should not care which provider processes the payment. That keeps the core smaller and lets local providers be added without coupling the whole product to one gateway.
Manual bank transfer
A simple offline payment path with configurable account and payment instructions.
Payment adapter API
A common interface for creating payments, receiving status updates and confirming bookings.
Montonio
A local adapter can connect directly to Montonio without making Montonio a core dependency.
Stripe / PayPal
International providers can use the same payment interface when the product expands to more markets.
No fake “trusted by 10,000 businesses” numbers.
Pluginory is early. The website is live, Booking is in active development, and the first milestone is a useful Lite release that can be tested by real businesses.
Pluginory website
Brand, product positioning, documentation structure and public release notes.
Booking Lite 1.0
Generalizing the proven booking workflow into a clean installable WordPress plugin.
External pilot users
Validate setup, documentation and everyday workflows outside the original test environment.
Booking Pro
Advanced availability, integrations, multi-resource features and paid support.
Start with a useful free version. Pay when automation starts saving money.
Final Pro pricing will be published before paid access opens. We would rather validate value first than invent a price for an unfinished product.
For a simple resource booking setup and for evaluating whether Pluginory fits your workflow.
Free
- Core resource booking flow
- Basic availability
- Manual booking management
- Manual payment instructions
For businesses that need deeper rules, integrations and more operational control.
Price to be announced
- Advanced buffers & availability
- Multiple resources
- Payment provider adapters
- Priority product support
Why Pluginory
Focused tools instead of another all-in-one monster.
Pluginory exists to turn practical WordPress business workflows into maintainable products. The goal is not to ship the longest feature list. It is to solve a defined problem well, document it properly and keep the product understandable as it grows.
Real workflows firstFeatures should come from actual operational problems, not from copying competitor checklists.
Useful before cleverA reliable booking rule is worth more than an impressive feature nobody needs.
Global architecture, local knowledgeBuild the core so it can travel, while validating the first releases in markets we understand.
No pretend tractionPublic claims, pricing and testimonials should become stronger as the product earns them.
Ideas, not promises.
We are deliberately not building several products at once. These are directions worth exploring only after Booking proves that people outside the original use case are willing to use and pay for Pluginory.
Pluginory Checkout
A fast one-page and direct-buy checkout layer for WooCommerce and booking flows.
Pluginory POS
A focused point-of-sale workflow for businesses already running on WordPress and WooCommerce.
Pluginory Product Finder
Guided product recommendations based on store-defined questions, attributes and rules.
Documentation is part of the product
A feature is not finished if nobody can figure out how to use it.
Every public release is planned to ship with a short setup path, a detailed admin guide, troubleshooting notes, developer references where relevant, and a readable changelog.
Quick Start
From installation to the first working booking flow.
Admin Guide
Settings explained with examples and expected outcomes.
Developer Docs
Hooks, filters, adapter interfaces and extension points.
Changelog
A version-by-version record of additions, fixes and breaking changes.
Early access
Contact Pluginory →
Run a room, studio, venue or other bookable space?
We are looking for a small number of real businesses to test the first general-purpose version of Pluginory Booking and tell us where the workflow breaks.
Decisions, releases and practical lessons.
The blog is for useful product notes: what changed, why a decision was made and what we learned from real use.
Why Pluginory Booking starts with rooms, not staff calendars
The product problem, the target customer and the constraints that shape the first public release.
Global core, local defaults
Why country-specific behavior belongs in locale packs instead of being hard-coded into the booking engine.
Payments as adapters, not dependencies
A maintainable way to support local gateways and global providers without coupling the core product to one vendor.