After a short scoping call we provide a fixed timeline — most standard builds land in roughly one working week depending on customization (custom booking forms, payment flow, and calendar integrations add time). We build on a branch, deploy to your staging environment for review, then install on production with a smoke-test pass. You are not buying an instant Marketplace download; you are commissioning a module that ECOSIRE builds, installs, and configures on your store.

Every build includes a defined warranty/support period for bug fixes after go-live, plus an optional ongoing support retainer. Because you receive the full source code, you are never locked in — we test compatibility against your target Magento Open Source or Adobe Commerce version, and we handle adjustments needed for Magento minor/security upgrades as a scoped change. Update work beyond the warranty window is quoted transparently.

Yes. The module is built using standard Magento 2 framework patterns — dependency injection, plugins, observers, service contracts, db_schema.xml — that run on both editions. If you are on Adobe Commerce, we can also align with edition-specific features (such as B2B or commerce staging) where relevant to your booking workflow.

Yes. Each staff member or resource has its own schedule, working hours, breaks, and exceptions. Availability is computed server-side from those rules, and confirmed bookings sync to Google Calendar and/or export as per-staff iCal/ICS feeds so external calendars stay in step with Magento.

Yes. Bookings route through your existing Magento payment method as a deposit, full payment, or pay-at-venue, using the standard order/quote workflow — we do not impose a new gateway. For headless setups, availability and booking creation are exposed through REST and GraphQL so PWA Studio or a custom front end can consume them directly.