Developer reference

Stay Suite is a domain-driven plugin. Custom post types hold properties and rooms; pricing, inventory, orders and payments live in dedicated database tables; a REST API drives both the storefront and the React admin app.

The code is organised by responsibility under src/:

The admin UI is a React + Vite single-page app mounted inside the Stay Suite menu; it talks to the same REST API documented below.

Activation registers the post types, creates the database tables, and flags a rewrite flush. It does not create any pages; the storefront pages are created on demand from the Setup screen.

A room links to its property through the _flss_property_id meta key. Property details live in meta: _flss_property_address, _flss_property_phone, _flss_property_email, and the check-in / check-out times.

Pricing, inventory, orders and payments are stored in custom tables (prefixed with the site’s $wpdb->prefix), not in post meta:

Equivalent blocks are registered for the block editor:

All routes are under /wp-json/flexatech-stay-suite/v1. Public read endpoints power the storefront; write and admin endpoints require the matching capability and a REST nonce.

Events you can listen to. Full argument details are in docs/HOOKS.md in the plugin.

add_action(
  'flexatech_stay_suite/payment/completed',
  function ( int $order_id, int $payment_id ) {
    my_slack_notify( "Booking #{$order_id} paid." );
  },
  10,
  2
);

Change values before they are used:

add_filter(
  'flexatech_stay_suite/pricing/price_for_date',
  function ( int $cents, int $room_id, DateTimeImmutable $day ) {
    $weekend = in_array( (int) $day->format( 'N' ), [ 6, 7 ], true );
    return ( 42 === $room_id && $weekend )
      ? (int) round( $cents * 1.15 )
      : $cents;
  },
  10,
  3
);

Register a gateway on gateways/register and resolve it by id on gateway/<id>. Your class implements PaymentGatewayInterface.

add_filter(
  'flexatech_stay_suite/gateways/register',
  function ( array $gateways ) {
    $gateways['my_gateway'] = new My_Gateway();
    return $gateways;
  }
);

add_filter(
  'flexatech_stay_suite/gateway/my_gateway',
  fn () => new My_Gateway()
);

Frontend and email templates are overridable. Point a template name at your own file, or turn off the default single / archive room templates entirely.

Each transactional email exposes filters for its subject, recipients, headers, heading and body, keyed by email id (for example flexatech_stay_suite/email/customer_booking/headers). Emails are also event-driven, so you can attach your own listeners.

Every user-facing string is translatable under the flexatech-stay-suite text domain, on both the PHP side and the React admin app. Drop a .mo file in the standard languages directory to translate the plugin.

See readme.txt in the plugin for the authoritative changelog.