Getting Started

Core Concepts

One app, eight modules: bookings, customers, staff, orders, inventory, payments, check-in, reports

Availability: QUMI distinguishes Implemented, Controlled release, In review, and Planned. A source route/module is not automatically a generally available feature or stable external API contract.

Tenant

An isolated business organization inside the shared QUMI platform.

Membership, role and permission

A user acts through tenant membership and role/permission context. Roles describe broad operating position; permissions authorize domain actions.

Resource

Operational capacity such as a desk, room, chair, equipment item, service slot, table-like asset or other bookable/sellable capacity.

Availability and booking hold

Availability is derived from resource policy, schedule, capacity and existing occupancy. A hold temporarily protects capacity while a booking/customer transaction is completed.

Catalogue and order

Catalogue/menu items represent sellable items/add-ons. Orders can be standalone or linked to a booking/session.

Payable state and payment

Operational completion and financial settlement are distinct. QUMI keeps payment/payable authority separate from workflow completion.

Template and vertical

A template establishes repeatable tenant configuration. Current vertical authority includes workspace, restaurant, retail and services, plus hybrid/unresolved states.

Storefront authority

The public storefront resolves tenant, branding, location/contact and capabilities before selecting the correct customer transaction journey.