Hotel & Property Booking

主な機能

Custom `bookable` Magento product type with EAV booking attributes, so reservations live in the catalog and respect store/website scope rather than being bolted on as separate CMS pages

Per-night availability calendar backed by dedicated `ecosire_booking_availability` tables, surfaced on the product page and validated server-side at add-to-cart

Occupancy and guest configuration (adults, children, max capacity per room/property type) enforced via a `quote_item_qty` checkout observer

Seasonal and dynamic per-night pricing through a `catalog_product_get_final_price` plugin/interceptor that computes the stay total from rate rules, not a flat product price

Multiple room and property types modeled as configurable bookable variants with independent calendars, rates, and min-night-stay rules

Booking confirmation emails and printable PDF/HTML vouchers rendered through Magento's transactional email and template layer

REST endpoints (`/V1/ecosire-booking/availability`, `/reservations`) and GraphQL resolvers for headless, PWA Studio, and channel-manager integrations

Service contracts (`ReservationRepositoryInterface`, `AvailabilityManagementInterface`) wired through `di.xml` for clean, upgrade-safe extension points

Admin reservation calendar grid with granular ACL (`Ecosire_HotelBooking::reservations`) controlling who can view, create, modify, or cancel bookings

Cron-driven hold expiry and availability recalculation so abandoned carts release inventory automatically

Race-condition-safe reservation writes (row-level locking / atomic decrement) preventing double-booking of the last available night

Works on Magento Open Source and Adobe Commerce, multi-store and multi-currency aware, installed and tested against your live theme

受注生産、すべておまかせ

自分での設定は不要 — ECOSIRE が構築・インストール・サポートする実働アプリです。

ご注文

一回限りの構築料金から始めます。キックオフで一緒に範囲を決めます。

構築とインストール

ECOSIRE がお客様の Magento 2 上で構築・設定・インストールします。

本番稼働 + サポート

約2〜4週間で稼働し、リリース後のサポート期間が付きます。

この製品について

Magento's catalog was built to sell quantities of products, not nights in a room. Stock the same suite twice on the same dates and core Magento has no idea you've double-booked. Hotel & Property Booking is a build-to-order Magento 2 / Adobe Commerce extension that re-models your rooms and rental properties as date-aware, capacity-aware inventory the storefront can actually reserve.

ECOSIRE delivers this as a proper module under app/code/Ecosire/HotelBooking — not a theme hack or a pile of CMS widgets. A custom bookable product type, EAV booking attributes, and dedicated availability tables back a per-night calendar. A catalog_product_get_final_price price plugin and a checkout quote_item_qty observer enforce occupancy limits and per-night rates so guests can only book dates that are genuinely open. Reservations are persisted through service contracts (ReservationRepositoryInterface), exposed over both REST (/V1/ecosire-booking/availability) and GraphQL for headless/PWA Studio storefronts, and locked against race conditions so two guests can't grab the last room on the same night.

Admin gets a calendar grid under a dedicated menu with full ACL (Ecosire_HotelBooking::reservations), seasonal and dynamic pricing rules, multiple room/property types, and automatic confirmation emails with printable vouchers rendered through Magento's transactional template system. A cron job releases expired holds and recalculates availability.

Because every property has its own rules — minimum-night stays, cleaning fees, channel-manager sync, tax per jurisdiction — we scope each build to your operation rather than shipping a one-size box. You tell us your room types and rate logic; we build, install on your environment (Open Source or Adobe Commerce), test against your theme, and support it after go-live. Honest delivery: this is custom engineering with a real lead time, not an instant Marketplace download.

得られるもの

Installable Magento 2 module `Ecosire/HotelBooking` under `app/code` with `composer.json`, `registration.php`, and semantic-versioned releases

Database schema via `db_schema.xml` (availability, reservations, rate rules) plus data/schema patches for clean upgrades

Admin reservation calendar UI, system configuration section, and ACL definitions in `acl.xml`

REST and GraphQL API layer with `webapi.xml`, schema, and resolver classes for headless/channel-manager use

Transactional email templates and voucher layout integrated with your store branding

Installation on your staging and production environment (Open Source or Adobe Commerce), including `setup:upgrade`, DI compilation, and static-content deploy

Technical handover docs, admin user guide, and a post-launch support window with bug fixes and Magento-version compatibility updates

これは誰のためのものですか

Independent hotel & guesthouse operators

Properties with a handful of room types that need real nightly availability and confirmation vouchers on their existing Magento store, without paying for an enterprise PMS or a SaaS booking engine with per-reservation fees.

Vacation-rental and multi-property managers

Operators listing several distinct properties, each with its own calendar, seasonal rates, and minimum-night rules, who want all bookings flowing through one Magento back office and checkout.

Magento agencies & headless/PWA teams

Build partners who need a reservation engine exposed over GraphQL and REST that plugs into a PWA Studio storefront or an external channel manager, delivered as a maintainable module rather than throwaway custom code.

Hotel & Property Booking の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
Date-aware nightly availability (no double-booking)	付属	部分的なサポート	付属	含まれていない
Built, installed & supported for your specific properties	付属	部分的なサポート	含まれていない	含まれていない
Occupancy & guest-capacity enforcement at checkout	付属	部分的なサポート	部分的なサポート	含まれていない
Seasonal / dynamic per-night pricing	付属	部分的なサポート	部分的なサポート	含まれていない
REST + GraphQL APIs for headless / channel managers	付属	部分的なサポート	部分的なサポート	部分的なサポート
Upgrade-safe module (service contracts, di.xml, ACL)	付属	含まれていない	部分的なサポート	付属
No recurring per-reservation or SaaS fee	付属	付属	部分的なサポート	付属
Tailored to your room types & rate rules out of the box	付属	付属	含まれていない	含まれていない

Hotel & Property Booking に関するよくある質問

Is this an instant download from the Adobe Commerce Marketplace?

No. Hotel & Property Booking is built to order. After purchase, ECOSIRE scopes your room/property types and rate logic, engineers the module against your Magento version and theme, then installs and tests it on your environment. There is no instant Marketplace download or auto-provisioned license — you get custom, supported software.

What is the typical delivery lead time?

A standard build with your defined room types, occupancy rules, and seasonal pricing typically lands within about 2–4 weeks of requirements sign-off. Scope that adds channel-manager sync, complex tax-per-jurisdiction, or a fully custom PWA Studio front end extends that timeline. We confirm a firm schedule in writing before work starts.

Do I get ongoing support and updates after launch?

Yes. Every build includes a post-launch support window covering bug fixes and compatibility updates for Magento minor/security releases. Because the module is delivered as versioned source under `app/code`, you own it outright — no recurring license fee. Extended support, new features, and major-version upgrades (for example Magento 2.4.x line moves) are available as a maintenance retainer.

Does it work with Adobe Commerce as well as Magento Open Source?

Yes. The module targets the shared Magento 2 framework, so it installs on both Magento Open Source and Adobe Commerce. On Adobe Commerce we can additionally integrate with B2B company accounts, shared catalogs, and advanced staging where relevant. We tell you up front which edition-specific features apply to your plan.

Can it integrate with my channel manager or external booking sources?

Yes, via the REST and GraphQL availability/reservation APIs. We can build push/pull sync to a channel manager (such as an iCal feed or a provider API) so availability stays consistent across Magento and third-party listing sites. This is scoped per integration since each provider's API differs; we confirm feasibility during requirements.