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.
- Tattoo Studio Management
- Integrations and source ownership
Integrations and source ownership
Connect payments, booking channels, client messaging and identity with clear ownership of each record.
- Tattoo Studio Management
- Payment provider
- Online booking and portfolio site
- Client messaging
- Identity provider
Systems to connect
-
Payment provider. Deposit and balance events arrive with the provider’s event identifier and reference.
-
Online booking and portfolio site. Requests from your website or booking widget can create Requested appointments; portfolios and galleries stay on your site.
-
Client messaging. Reminders and aftercare messages are sent from your messaging tool, linked to the appointment.
-
Identity provider. Map team members to user accounts; disabling a sign-in must remove access here too.
How connections are governed
Each connection needs an agreed source of truth, field mapping, event identifier and retry policy. Keep credentials in the approved secret store and grant the smallest permitted scope. A repeated payment event must not add a second deposit, and a repeated booking request must not hold a second station. Queue rejected records with their source identifier and a visible reason.
Reconcile source totals to accepted, rejected and pending events. Review a provider timeout, a duplicate delivery, a changed source record and a revoked credential before enabling schedules. Availability depends on each provider’s API, commercial access and configuration.
Use the implementation plan to agree integration acceptance criteria.
Set up Tattoo Studio Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.