These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- CrossFit Box Management
- Integrations and source ownership
Integrations and source ownership
Agree how identity, payment confirmation and accounting records enter the booking cycle.
- CrossFit Box Management
- Payment provider
- Identity provider
- Accounting platform
- Booking intake channel
Systems to connect
- Payment provider. Use an accepted provider response and stable payment reference before a pending receipt becomes confirmed. Reconcile refunds with the original booking.
- Identity provider. Map signed-in users to staff people and revoke access when a person is no longer active.
- Accounting platform. Agree whether posted charges and confirmed receipts are exported, and reconcile both sides by booking and period.
- Booking intake channel. If requests arrive outside the app, map the member, requested interval, places and chosen session to one booking identity.
How connections are governed
For each connection, decide which system owns the event, which identifier survives retries and who handles a rejected record. A repeated payment notice must resolve to the existing receipt. A changed booking request needs a fresh date and capacity check. Keep credentials in the approved secret store and expose only the fields needed for the connection. Reconcile accepted, pending and rejected items before relying on a financial total.
Use the implementation plan to define a pilot.
Set up CrossFit Box Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.