Flexatech Stay Suite

Flexatech Stay Suite is a professional room-reservation system for WordPress. It manages hotel rooms, rate plans with date-specific price and availability overrides, realtime availability computed straight from bookings (no stale caches), time-limited holds that prevent overbooking, coupons, and modern payment gateways with signature-verified, idempotent webhooks.

Every amount is stored and computed as integer cents, and the total charged is always re-computed on the server at checkout, so a tampered client payload can never lower the price.

📚 Documentation and live demo: read the setup guide, then book a room on the demo site before you install anything.

Highlights

• Rooms as a custom post type with per-room inventory, capacity, deposit, and extras.
• Rate plans with priority, min/max stay, and per-date-range / day-of-week price rules.
• Realtime availability using half-open night semantics [check_in, check_out), so same-day turnover (a guest checks out and another checks in the same day) works correctly.
• Overbooking-safe holds: a time-limited hold reserves inventory during checkout and is swept automatically when it expires (WP-Cron).
• Coupons (percentage or fixed amount) with usage limits and expiry.
• Payment gateways: Offline / bank transfer (built in), plus Stripe and PayPal with sandbox/live modes and webhook verification. The charged amount always equals the server-computed total.
• Transactional emails for booking received (customer + admin), processing, completed, cancelled, and payment receipts, each toggleable with a custom subject.
• A modern React admin app for the dashboard, calendar, bookings, rate plans, coupons, and settings, backed by a versioned REST API (flexatech-stay-suite/v1).
• WP-CLI commands and full privacy exporter/eraser integration.

Ready for more? Two add-ons pick up where the free plugin stops

The free plugin is enough to run a real property. The add-ons are for the money you are currently leaving on the table: the fifth guest who pays the same as the second, the Friday night that costs the same as a Tuesday, the double booking that came in from Airbnb while you were asleep.

Both are separate plugins that extend Stay Suite through its documented hooks. They never patch its code, never touch its tables, and every figure they add is computed on the server, so a guest cannot edit a fee out of the request. Install one the day you need it; nothing in your existing setup has to be redone.

Stay Suite Occupancy: charge for who stays, not just which room

👉 Get Stay Suite Occupancy

A family of five in a room priced for two is a discount you never agreed to give. Occupancy puts the guest count back into the price:

• Extra-guest fee beyond a base occupancy you set per room, charged per guest, per night, exactly how Airbnb does it.
• Pet fee, either once per stay or per night, your choice per room.
• Per-type guest caps for adults, children, infants and pets, enforced both when the price is quoted and again at checkout, so an over-capacity stay can never slip through.
• Infants never count toward the paid headcount, and a room you have not configured keeps behaving exactly as it does on the free plugin.

Requires Flexatech Stay Suite 1.6.0 or newer.

Stay Suite Pro: the revenue, policy and channel layer

👉 Get Stay Suite Pro

Everything a property needs once bookings stop being occasional:

• Dynamic pricing. Weekend uplift on the weekdays you pick, seasonal percentage ranges, and an optional nightly floor and ceiling so a stacked rule can never price a room absurdly.
• Booking rules. Minimum and maximum nights, closed-to-arrival and closed-to-departure weekdays, and a booking window, set globally and overridable per room. Rejected stays are refused at quote time with a clear message, not after the guest has paid.
• Cancellation policies. Tiered “within N days of check-in, retain X” rules per room; the tightest matching tier wins and the free plugin issues the matching refund.
• Deposits and payment schedules. Take a deposit now and split the balance across dated instalments. The schedule always sums back to the exact order total, and [flssp_payment_schedule order="CODE"] shows it to the guest.
• Calendar sync, both directions. Every room gets a tokenised, revocable iCal export URL, and external feeds (Airbnb, Booking.com, Google Calendar, anything that speaks iCal) are polled hourly, with imported busy dates blocked from being booked again.
• Integration API and webhooks. An API-key-authenticated REST namespace to list availability, quote, create, read and cancel bookings, plus signed booking.created / booking.confirmed / booking.cancelled webhooks with a delivery log and exponential-backoff retries. Booking creation runs the free plugin’s own checkout service, so pricing is reused rather than reimplemented.

Requires Flexatech Stay Suite 1.5.0 or newer.

📚 Documentation for both add-ons, plus the live demo, is at https://hotel.flexacommerce.com/

Storefront pages

Room browsing works with no setup: single room pages at /rooms/{slug}/, the room archive at /rooms/, and room-type and amenity archives all render inside your active theme automatically. Your theme’s own room templates take priority, and every plugin template can be overridden from a flexatech-stay-suite/ folder in your theme. Return false from the flexatech_stay_suite/frontend/use_default_templates filter to turn the automatic routing off.

For the cart and checkout steps, create a few pages under Pages → Add New and paste one shortcode into each, then Publish:

• Cart (required): [flexatech_hotel_cart]
• Checkout (required): [flexatech_hotel_checkout]
• Booking Confirmation (required): [flexatech_hotel_thankyou]
• My Bookings (recommended): [flexatech_hotel_account]
• Book a Room (optional landing page): [flexatech_hotel_search] and [flexatech_hotel_rooms]

The plugin finds these pages by scanning your published pages for each shortcode, so the titles and slugs are up to you. Put each flow shortcode on its own published page; if the same shortcode appears on more than one page, the first match is used. The Cart, Checkout, and Booking Confirmation pages are required because the flow redirects between them.

The three browsing shortcodes are also available as editor blocks: Room Search, Room List, and Single Room Booking.

Shortcode reference:

• [flexatech_hotel_search]: date and guests search form. Optional redirect="URL" sends results to another page.
• [flexatech_hotel_rooms]: grid of bookable rooms. Optional per_page, columns, and room_type.
• [flexatech_hotel_room id="123"]: one room’s booking widget; id defaults to the current room on a room page.
• [flexatech_hotel_cart], [flexatech_hotel_checkout], [flexatech_hotel_thankyou], [flexatech_hotel_account]: the cart, checkout, confirmation, and account screens.

The “Storefront pages” steps above are the full setup walkthrough; the FAQ below covers the common questions.

External services

This plugin can connect to Stripe and PayPal to take online payments for bookings. Both integrations are optional: the plugin only contacts them if the site owner enables that gateway in Settings → Payments with their own API keys and a guest actually selects it at checkout. The built-in Offline / bank-transfer gateway makes no external calls.

Card numbers are never sent to or stored on your server. Stripe collects card details in the browser (via Stripe.js) and your site only handles the resulting PaymentIntent id and client secret.

Stripe

Stripe processes credit-card payments when the Stripe gateway is enabled and a guest chooses to pay by card. Your site sends requests to the Stripe API (https://api.stripe.com) in these cases:

• When a guest starts a card payment at checkout, the plugin creates a PaymentIntent. It sends the charge amount (in the smallest currency unit), the currency, and the booking order id and order code as metadata.
• When you issue a refund, the plugin sends the PaymentIntent reference and the refund amount.
• Stripe also sends webhook notifications back to your site to confirm payment; the plugin only verifies the request signature against your webhook secret and does not send data to Stripe in response.

Your Stripe secret key is sent in the request authorization header so Stripe can authenticate the call.

Stripe’s terms and privacy policy: https://stripe.com/legal/ssa and https://stripe.com/privacy

PayPal

PayPal processes payments when the PayPal gateway is enabled and a guest chooses to pay with PayPal. Depending on sandbox or live mode, your site sends requests to https://api-m.sandbox.paypal.com or https://api-m.paypal.com in these cases:

• To authenticate, the plugin exchanges your PayPal client id and client secret for an OAuth access token.
• When a guest starts a PayPal payment at checkout, the plugin creates a PayPal order, sending the amount, currency, and the booking order id and order code as the order reference.
• When you issue a refund, the plugin sends the capture reference and the refund amount and currency.
• PayPal also sends webhook notifications back to your site to confirm payment; the plugin verifies each notification by calling PayPal’s verify-webhook-signature endpoint with your webhook id before acting on it.

PayPal’s user agreement and privacy policy: https://www.paypal.com/us/legalhub/useragreement-full and https://www.paypal.com/us/legalhub/privacy-full

Deactivation feedback

When you deactivate the plugin from the Plugins screen, a short optional feedback form asks why you are leaving. Whether you submit a reason or skip it, the plugin sends the result to the FlexaTech product-intelligence service at https://product-intelligence.flexacommerce.com so we can improve the plugin. This runs only in wp-admin, only around deactivation (and the following reactivation), and never blocks deactivation: if the service is unreachable, the plugin still deactivates normally.

What is sent: an anonymous per-site identifier (a random UUID generated on your site), the plugin slug, tier and version, the deactivation reason and any comment you choose to provide, and basic environment information (WordPress version, PHP version, and site locale). No email address, domain name, or raw IP address is sent.

FlexaTech service and privacy information: https://flexacommerce.com