Workflow blueprint

Salon management needs versioned service instructions before checkout

An appointment-to-handoff record, not product advice, sensitivity screening, medical guidance, licence verification, safety management or payment processing.

Carry the client request into confirmed service scope, staff acknowledgement, supplied consent or product references, changed instructions, observed events, stop decisions, completion statement and retail handoff.

TL;DR — Carry the client request into confirmed service scope, staff acknowledgement, supplied consent or product references, changed instructions, observed events, stop decisions, completion statement and retail handoff.
1

Confirm appointment and service scope

Record the requested service, time, assigned professional, expected duration, client-supplied context and exact confirmed version.

2

Reference external product and consent evidence

Attach supplied product identifiers, instruction sources, consent references and specialist questions without interpreting suitability.

3

Version changes during the appointment

Preserve consultation changes, declined additions, staff substitution, observed reaction, stop request and responsible response owner.

4

Separate completion from checkout

Record what was reported complete, exclusions, product movement, rebooking question and the authorised commercial handoff.

Page-specific decision aid

An appointment, service-instruction, consent-source, product-reference, observation, stop and checkout handoff book

The book follows a colour appointment through confirmation, consultation-led scope change, external patch-test reference, substitute professional, product-source question, declined add-on, client stop request, incomplete service note, retail return, rebooking question and a checkout handoff that retains every exclusion.

  • A product reference is not treatment advice.
  • A consent file is not proof of suitability.
  • Checkout does not certify the service result.
Scope first

What Codeblix would confirm before implementation

This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.

  • Appointment confirmation cites an exact service instruction
  • Product references keep their external source and version
  • A client stop request remains visible after checkout
  • Product sensitivity medical classification licensing safety biometric payment and outcome proof excluded

Use the related planning tools

Run the operational calculation, save the result in the URL and share it with your team.

Map this workflow to your operation

Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.

Discuss your workflow