Magento 2 Booking & Appointment Reservation

主な機能

Custom Magento 2 booking product type registered via module.xml/registration.php, layered on the Catalog and Quote stack so bookable items behave like first-class products in cart, checkout and order history

Many-bookings-per-day and many-days-per-booking modes to cover both short appointments and multi-day rentals from the same engine

Time-slot and appointment scheduling with configurable slot length, granularity and per-slot capacity

Rental, event and appointment booking types selectable per product, each with its own availability semantics

Staff or resource assignment binding each slot to a person, room or rentable unit, with conflict prevention across overlapping reservations

Admin booking calendar and grid built on Magento UI components with full ACL under Magento_Backend so only authorized roles manage reservations

Availability rules engine: buffer/lead times, blackout dates, recurring weekly schedules and capacity caps enforced before add-to-cart

Cron job that releases expired cart holds and recomputes slot availability so abandoned bookings don't lock inventory

Service contracts (@api PHP interfaces) and repositories exposing reservation data in an upgrade-safe, override-friendly way

REST and GraphQL endpoints for reservations so headless / PWA Studio storefronts and external calendars can read and write availability

Plugins/interceptors and sales_order_place_after observers that convert quote items into persisted reservations atomically with the order

Order, invoice and email integration so booking date/time/resource details appear on confirmations and in the customer account

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

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

ご注文

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

構築とインストール

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

本番稼働 + サポート

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

この製品について

Magento Open Source and Adobe Commerce ship with simple, configurable, bundled, grouped, virtual and downloadable product types — but nothing that sells time. If you rent equipment, schedule appointments, run tours or sell event seats, the native catalog can't express "this Tuesday, 2:00–3:00 PM, with this technician, only 4 left." This extension adds that missing dimension.

ECOSIRE builds a dedicated Ecosire_Booking module under app/code, registered through registration.php and module.xml, that introduces a booking product type layered on Magento's Catalog and Quote stack. We wire it in the standard way: a custom type model, di.xml preferences and plugins/interceptors on the add-to-cart and quote-item flows, observers on sales_order_place_after to materialize reservations, and service contracts (PHP interfaces with @api annotations) so your reservation data stays accessible and upgrade-safe.

Bookings carry their own EAV-backed options: many-bookings-per-day and many-days-per-booking modes, time-slot and appointment scheduling, and rental / event / appointment booking types. Availability is enforced with configurable rules — buffer times, lead time, blackout dates, per-slot capacity — and a cron-driven job releases abandoned-cart holds so inventory isn't locked forever.

Staff or resource assignment lets you bind each slot to a person, room or unit, with an admin grid and calendar (UI components / Knockout) secured by proper ACL under Magento_Backend. Customers see live availability on the storefront PDP, and bookings expose REST and GraphQL coverage so your headless front end, PWA Studio storefront, or external calendar can read and write reservations.

This is honest build-to-order: ECOSIRE scopes it to your Magento version, edition and theme, develops it, installs it on your environment, and supports it. It is not a one-click Adobe Commerce Marketplace download.

得られるもの

A composer-installable Ecosire_Booking module placed under app/code (or your vendor repo) and enabled via bin/magento setup:upgrade on your environment

Custom booking product type, EAV booking options, and database schema delivered via declarative schema (db_schema.xml) with data patches where needed

Admin configuration, booking grid and calendar UI with role-based ACL wired into your Magento admin

Storefront PDP booking widget themed to match your current frontend/theme and locale

REST and GraphQL schema (schema.graphqls) plus generated API documentation for the reservation endpoints

Installation on your staging and production Magento environments, smoke-tested against your edition (Open Source or Adobe Commerce) and version

Handover docs covering configuration, availability rules, cron setup and an admin walkthrough

Source code ownership with a defined post-delivery support and bug-fix window

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

Rental & equipment shops

Stores renting gear, vehicles, venues or tools that need multi-day reservations, per-unit availability and automatic release of abandoned holds — without forcing customers through email back-and-forth.

Appointment-based service businesses

Salons, clinics, studios and repair shops selling time with specific staff. They need time-slot booking, staff assignment and conflict prevention tied directly to Magento checkout and payment.

Event & tour organizers

Operators selling seats, sessions or dated tickets who need capacity-limited slots, blackout dates and booking details carried onto orders, invoices and confirmation emails.

Magento 2 Booking & Appointment Reservation の比較方法

基準	エコシエール	カスタムビルド	競合他社	Magento 2 標準機能
Sell time-based products (slots, rentals, appointments) natively	付属	付属	付属	含まれていない
Built, installed and supported on your store (not just a code zip)	付属	部分的なサポート	含まれていない	含まれていない
Scoped to your exact Magento version, edition and theme	付属	付属	部分的なサポート	含まれていない
Staff/resource assignment with conflict prevention	付属	部分的なサポート	部分的なサポート	含まれていない
REST + GraphQL coverage for headless / PWA storefronts	付属	部分的なサポート	部分的なサポート	含まれていない
Upgrade-safe service contracts & declarative schema	付属	部分的なサポート	部分的なサポート	付属
Predictable one-time price with delivery lead time	付属	含まれていない	付属	含まれていない
Source code ownership handed to you	付属	付属	含まれていない	含まれていない

Magento 2 Booking & Appointment Reservation に関するよくある質問

How long does delivery take, and what happens after I order?

This is built-to-order, not an instant download. After purchase, ECOSIRE confirms your Magento version, edition (Open Source or Adobe Commerce) and theme, then scopes the build. A standard booking implementation typically takes about 2–4 weeks depending on the booking types, availability rules and any headless/GraphQL requirements. We develop on our environment, then install and smoke-test it on your staging before production.

Do I get ongoing support and updates after the module is installed?

Yes. Delivery includes a defined post-launch support and bug-fix window for issues in the code we shipped. Because the module is pinned to your Magento version, ongoing compatibility with future Magento/Adobe Commerce upgrades, new feature requests and version migrations are handled under a separate support or retainer arrangement, which we'll quote based on your needs. You own the source code either way.

Will this work on both Magento Open Source and Adobe Commerce?

Yes. The module is built against Magento's stable framework APIs (service contracts, di.xml, declarative schema), so it runs on Magento Open Source and Adobe Commerce. On Adobe Commerce we can additionally align with edition-specific features such as B2B, shared catalogs or commerce-grade staging where relevant; we confirm the exact integration points during scoping.

Can the booking data be used by a headless or PWA Studio storefront?

Yes. Reservations are exposed through both REST and GraphQL. We provide a schema.graphqls covering availability queries and booking mutations so a headless front end, PWA Studio storefront, or external calendar/CRM can read availability and create bookings using the same service contracts the storefront uses.

How does it prevent double-booking the same slot, staff member or rental unit?

Availability is validated server-side before add-to-cart and again at order placement via interceptors and a sales_order_place_after observer, so reservations persist atomically with the order. Per-slot capacity, staff/resource binding and overlap checks prevent conflicts, and a cron job releases expired cart holds so a slot abandoned in checkout becomes bookable again.