Systems to connect

• Payment providers. Configure the provider-evidence connection and preserve the event identity, type, verified state and booking reference. Agree which events satisfy the salon’s deposit policy before using them for confirmation.
• Consent collection. Connect the source of the required consent material or attach it through the agreed operating process. Use an evidence-type convention and file title that the reviewer can recognize.
• Customer information. Set up a connection when customer names and appointment context come from another system. Retain a clear booking identifier so common customer names do not cause records to be confused.
• Product and stock systems. Connect the source that owns product lot identity or stock balances when completed service use needs an external handoff. Agree the unit convention and accepted close-out version used in that exchange.
• External reporting. Configure an approved destination for booking and service-use results where another team needs them. Preserve the organization, source revision and operation references needed to explain the exported outcome.

Assign an owner to each source and agree which identifiers are authoritative. Keep provider verification tied to the trusted evidence process. Preserve the supported operation identity for a successful retry, and test how failed attempts are corrected before assuming they will be reevaluated automatically.

Rehearse an unknown booking reference and a repeated provider event before regular exchange. Keep attachment visibility and organizational access aligned with the intended reviewers. Store credentials in the connection’s secure settings and route business decisions through the configured authorized actions.