Configured tenants can publish a hosted catalog, item details, server-generated availability, guest details, and reservation confirmation. It is the supported public booking surface today. Embeds, custom-domain automation, cart recovery, and advanced SEO tooling remain separate delivery work.
The public flow reads tenant configuration and active products, generates eligible availability on the server, collects the booking party's details, and carries the resulting reservation into staff operations.
A pretty calendar can go stale between selection and submission. GridMagik validates the exact server-generated time, locks the relevant product and shared resources, rereads overlapping reservations, and only then commits capacity.
Confirmation and account access use tenant-bound high-entropy tokens, while Stripe payment activation stays tenant-gated. Extras and operator-issued gift redemption are available, and fixed or percentage deposits with later balance collection are controlled beta. Consumer gift purchase, self-service reschedule/cancellation, and advanced cart recovery remain explicit roadmap work.
Available and planned surfaces are separated so the rollout does not depend on assumptions.
Show active public booking items in the tenant context.
Generate eligible dates and exact slots from configured rules.
Collect the booking party and create the operational record.
Use the public flow on narrow and wide viewports with accessible controls.
Core identity and content controls exist; full design-token coverage is being consolidated.
The supported current handoff is a hosted link, not an unreleased widget.
Use the hosted tenant URL in a link or generated QR placement.
Tenant-bound high-entropy access tokens, signed basket state, throttling, and no-referrer controls protect public booking links.
Yes, for configured tenants. Production use still requires the tenant's products, availability, public access, communications, and any enabled payment path to pass the launch checklist.
Not with a supported production plugin today. Link to the hosted booking destination; embeds and CMS packages are planned.
Stripe-connected checkout exists in controlled beta. A venue must complete Stripe account, webhook, amount, currency, refund-policy, and reconciliation readiness before live money is enabled.
Guests can select server-priced extras, redeem an operator-issued gift voucher, and—when a venue enables an explicit product rule—pay a fixed or percentage deposit before returning for the remaining balance. These payment paths are controlled beta. The basket can retain multiple reservation links, but it does not create one atomic charge across several bookings. Consumer gift purchase remains planned.
30-minute walkthrough. Your pricing, your calendar, your receipts — running live in a sandbox on your data. No slides.
