GridMagik's booking, customer, calendar, venue-operations, and racing foundations are available now. Stripe is beta. Gifts, complete waiver signing, campaigns, external calendars, and third-party POS integrations are labeled as partial or planned.
Evaluate the working foundation and the remaining delivery work separately, then put the scope your venue needs in writing.
Stripe Connect checkout, Terminal, multi-tender, and partial refunds are implemented in sandbox; the Square Terminal foundation passes mocked provider tests.
The reservation core is available; per-product deposits, operator-issued gift vouchers, partial tenders, and Stripe refunds are controlled beta.
A tenant-aware hosted booking flow with real availability. Embeds, custom domains, advanced SEO, and cart recovery remain separate rollout work.
Weekly, monthly, agenda, and list views combine availability, reservations, holds, payment state, and racing-event overlays.
Customer and participant profiles, booking history, and waiver-status tracking. Complete legal-document and guardian signing flows are planned.
Product-aware promo codes and secure stored-value vouchers are in controlled beta. Campaign delivery, audience segmentation, and attribution remain planned.
Email provider and reservation-delivery foundations exist. Complete lifecycle templates, delivery controls, SMS, and campaign automation are still being finished.
Public booking and the app shell are responsive; dense inventory and reporting views are being converted to mobile cards route by route.
App, booking, onboarding, marketing, authentication, and admin route groups now expose loading and recoverable error states.
Payment, waiver, booking, and rig states are visible; a complete proactive notification and escalation system remains rollout work.
Role-aware navigation, tenant access checks, and audit records form the current staff-control foundation.
GridMagik no longer uses placeholder adoption numbers, fabricated testimonials, or roadmap features to fill the page. The product earns each status through a testable operating path and keeps the unresolved boundary visible.
Request a walkthrough centered on your booking, payment, venue, and racing workflow. Any dependency that is not ready stays labeled and moves into written scope.
