Salon Colour Records: Does “Test Done” Refer to This Product and This Appointment?
A customer has a colour appointment next week and an old note saying “test done”. Before building a salon app around that note, ask what it actually records: which product was considered, which instructions applied, what happened and who reviewed the information for the proposed service. A permanent green badge on the customer profile cannot answer those questions.
The useful commissioning decision is whether the system preserves a product-specific testing and review history or merely remembers that somebody once ticked a box. It should support the salon's professionally approved procedure, not diagnose an allergy or promise that colouring is safe.
Previous use is not a lifetime clearance
The US Food and Drug Administration's guidance on hair dyes explains that sensitivities can develop with repeated exposure and formulations can change. It says to follow instructions and do the skin test before every use. Crucially, it also says a reaction remains possible even when no reaction is seen in the skin test.
Those qualifications belong together. Do not turn “no reaction reported” into “allergy-free”, “medically cleared” or an automatic permission to apply any colour. The FDA is a US source; it does not establish a salon's legal obligations in another country. The responsible professional must approve the applicable product instructions and local procedure.
This article specifies record handling, not a testing technique, testing interval or treatment protocol. The app must not invent those instructions from a generic calendar setting.
Keep the proposed colour separate from the customer's history
Give the intended service its own product reference. Agree with the salon which details reliably identify what will be used, including the relevant formulation or manufacturer information available to staff. A friendly colour name alone may not distinguish different products or a changed formulation.
Store the testing event separately: date, applicable instructions reference, product reference, reported or observed outcome, recording person and any outstanding review. Keep an outcome that has not been supplied visibly unknown. An appointment being booked, a reminder being delivered and a result being reviewed are not interchangeable events.
This distinction helps reception staff answer a practical question: is an appropriate review still outstanding for the product now proposed? They should not have to interpret an unexplained historic note or make a clinical judgment.
A changed product needs an explicit review path
Imagine the customer asks to change the colour at the appointment. The old record should remain attached to the product it described. The app should show that the new proposal does not automatically inherit that record's meaning.
Ask the salon to define who assesses the change and what may happen while that assessment is unresolved. A calendar slot can remain booked without the software representing the colour service as approved. If a different service is offered instead, record the actual agreed change rather than quietly renaming the original product.
Do not allow a receptionist's scheduling override to erase an adverse outcome or impersonate a qualified review. A software permission to edit appointments is not professional authority to decide suitability.
Record a concern without pretending to treat it
An adverse report, missing result or uncertain product identity needs a named follow-up route. The FDA advises contacting a healthcare provider for necessary medical help when a reaction occurs. A salon portal must not replace that help with a routine booking ticket or a reassuring automated reply.
Have the responsible professionals approve customer-facing wording, including what to do when urgent help is needed. Keep clinical advice outside an unreviewed chatbot or generic notification template. Staff should be able to record that the proposed service is on hold without selecting a diagnosis from a compulsory list.
Access also needs deliberate design. Discuss which staff need the detailed record and what reception needs to see to manage the appointment. Do not copy sensitive history into public calendar descriptions, reminder messages or shared customer lists merely because it is stored in the app.
Demonstrate the ambiguous cases before launch
Use fictional records to test these journeys:
- A repeat customer has a historical note but no product identity.
- The intended product changes after an event has been recorded.
- A reminder is delivered but no outcome is supplied.
- A customer reports a concern after an earlier review.
- An appointment is moved while the professional assessment remains unresolved.
- A staff member with calendar access cannot rewrite the review history.
Agree the expected display, responsible person and permitted next action for each case. None should end with the app issuing a blanket safety certificate. A useful business-app brief starts with these real distinctions, not a promise to automate professional judgment.
Source and boundaries
US FDA: Hair Dyes, particularly “Allergic reactions”, the safety checklist and reporting advice. Its warnings about repeat exposure, formulation changes and residual risk support the factual discussion. Product-linked records, access controls and acceptance journeys above are proposed software requirements, not FDA certification of a workflow or a substitute for current product instructions and competent professional advice.